
From nobody Sun Jan  5 16:42:57 2020
Return-Path: <internet-drafts@ietf.org>
X-Original-To: art@ietf.org
Delivered-To: art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B43D6120106; Sun,  5 Jan 2020 16:42:54 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <art@ietf.org>, <adam@nostrum.com>, <mt@mozilla.com>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.115.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <157827137473.4889.3757817972550697504.idtracker@ietfa.amsl.com>
Date: Sun, 05 Jan 2020 16:42:54 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/QMd8sI8-p3yskB0GSY74Qee0IJE>
Subject: [art] New Version Notification - draft-nottingham-rfc7320bis-03.txt
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jan 2020 00:42:55 -0000

A new version (-03) has been submitted for draft-nottingham-rfc7320bis:
https://www.ietf.org/internet-drafts/draft-nottingham-rfc7320bis-03.txt

Sub state has been changed to AD Followup from Revised ID Needed


The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-nottingham-rfc7320bis/

Diff from previous version:
https://www.ietf.org/rfcdiff?url2=draft-nottingham-rfc7320bis-03

Please note that it may take a couple of minutes from the time of submission
until the diff is available at tools.ietf.org.

IETF Secretariat.


From nobody Mon Jan  6 15:25:07 2020
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: art@ietf.org
Delivered-To: art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BE24A12007C; Mon,  6 Jan 2020 15:25:04 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <art@ietf.org>, <draft-nottingham-rfc7320bis@ietf.org>, <adam@nostrum.com>, <mt@lowentropy.net>, <mt@mozilla.com>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.115.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <157835310477.8003.967640368806248903.idtracker@ietfa.amsl.com>
Date: Mon, 06 Jan 2020 15:25:04 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/SkuVZ2Hizd-DJafV9m0-0DN2GzM>
Subject: [art] Datatracker State Update Notice: <draft-nottingham-rfc7320bis-03.txt>
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jan 2020 23:25:05 -0000

IESG state changed:

New State: IESG Evaluation

(The previous state was Waiting for Writeup::AD Followup)


Datatracker URL: https://datatracker.ietf.org/doc/draft-nottingham-rfc7320bis/


From nobody Mon Jan  6 15:54:33 2020
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: art@ietf.org
Delivered-To: art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E91A51208FC; Mon,  6 Jan 2020 15:54:25 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: "The IESG" <iesg@ietf.org>, <art@ietf.org>, <iesg-secretary@ietf.org>, <draft-nottingham-rfc7320bis@ietf.org>, <mt@mozilla.com>, <mt@lowentropy.net>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.115.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <157835486595.8108.11925708600830430853.idtracker@ietfa.amsl.com>
Date: Mon, 06 Jan 2020 15:54:25 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/E1TeHYc4QGC_nyTFS4TbwA-C564>
Subject: [art] Telechat update notice: <draft-nottingham-rfc7320bis-03.txt>
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jan 2020 23:54:32 -0000

Placed on agenda for telechat - 2020-01-23
Datatracker URL: https://datatracker.ietf.org/doc/draft-nottingham-rfc7320bis/


From nobody Mon Jan  6 22:59:58 2020
Return-Path: <john-ietf@jck.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C455F1200BA; Mon,  6 Jan 2020 22:57:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 avWJNij_kYRR; Mon,  6 Jan 2020 22:57:42 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A01A2120096; Mon,  6 Jan 2020 22:57:42 -0800 (PST)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1ioio6-0005qR-CL; Tue, 07 Jan 2020 01:57:38 -0500
Date: Tue, 07 Jan 2020 01:57:32 -0500
From: John C Klensin <john-ietf@jck.com>
To: iesg@ietf.org
cc: art@ietf.org, mnot@mnot.net, ietf@ietf.org, urn@ietf.org
Message-ID: <87E116C31DAF1434C3C3937F@PSB>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/6ogA39Tljn7vjfHJ4h3u58h4ReQ>
Subject: [art] URNs and Last Call: <draft-nottingham-rfc7320bis-02.txt> (URI Design and Ownership) to Best Current Practice
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2020 06:57:49 -0000

Hi.

My apologies for the extreme lateness of this note.  I have
tried to pass URN work on to others since RFCs 8141 and 8254 and
had assumed that someone else would check through this document
to be sure that it appropriately covered both locator-type and
name-type URIs (particularly URNs) (see RFC 3986 Section 1.1.3).
I had assumed that reviews within the ART area and/or a specific
ART Area Review would address that topic but, AFAICT, they may
not have done so.

I've had occasion to look through the document and I'm actually
not sure about the name-locator distinction as it may apply to
it.  This note will be short and is rather more about asking the
IESG to be sure that any possible issues are addressed than to
try to do a detailed review of the issues.

AFAICT, the focus of the I-D is to be sure that applications and
elaborations of any URI scheme be firmly under the control and
management of the owner of that scheme and that possible
deviations from that principle are well-controlled.
http://www.w3.org/TR/2004/REC-webarch-20041215, Section 2.2.2.1,
cited in the draft as [webarch] is clear that the ownership of a
URN is delegated to the owners of URN Namespaces rather than
being bound to the "urn" URI scheme itself.  I believe it is
possible to read this document in a way that has no impact on
URNs and URN namespaces.   However, it appears to me that, if
read without appropriate care, some of the restrictions imposed
on queries and fragments may be inconsistent with mechanisms and
syntax for use in particular URN Namespaces or URNs generally
that were contemplated and extensively discussed during the
development of RFC 8141.  Those ideas were deferred by the WG
for future work but the mechanisms may well be in use in
important URN namespaces.  Because the last paragraph of Section
1.1 of this I-D essentially declares any existing specification,
even a standards-track one or one adopted by other bodies, that
does not comply with the recommendations of the I-D to be
incorrect and in need of correction, the effects of a reading
that retroactively restricts URN Namespace practices that are
under the control of the Namespace owners could be quite serious.

My preference would be that someone who has been more active
with URN work and Namespace registrations in the last couple of
years do a careful review of the document to determine whether
my concerns justify some tuning of the text.  However, given how
late it is in the review process (again, my apologies for not
catching the issue until now), a reasonable alternative would be
to simply insert a sentence early in the I-D that says that it
applies primarily to locator-type URIs although name-type ones
may find it useful as general guidance _or_ to explicitly call
out the difference in ownership between URNs and other URI
schemes.

 thanks,
   john

p.s. It would be, IMO, helpful if the IESG and the community
would think about the implications of BCP (or IETF-stream
Informational) documents that effectively obsolete or deprecate
existing standards without identifying them or explicitly
updating them and whose responsibility it is to find the
discrepancies.


From nobody Tue Jan  7 05:51:18 2020
Return-Path: <hallam@gmail.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF899120116; Tue,  7 Jan 2020 05:51:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.418
X-Spam-Level: 
X-Spam-Status: No, score=-1.418 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-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 9elndMSc72sa; Tue,  7 Jan 2020 05:51:13 -0800 (PST)
Received: from mail-ot1-f51.google.com (mail-ot1-f51.google.com [209.85.210.51]) (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 D29FC1200E9; Tue,  7 Jan 2020 05:51:12 -0800 (PST)
Received: by mail-ot1-f51.google.com with SMTP id r9so3138572otp.13; Tue, 07 Jan 2020 05:51:12 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=eghn3hP3jtmuNjohEJYEDOQUrurtsHvXeadmEi9ViJk=; b=kDhYFbIrRTEL+r8iZ355Yyys/peGACUpVYr/gc5ukiCzV92hu8MdYzSV8Mj6Rs/8iW QK/VkkXoxE+4UoPTQZB7iTHHkVNVpp+ukc8u/QNFq9nxEOzXGzQmEDldIAcERpQRFt27 jS23ZL68xppbnn8WscAq7nCl3PutMUA34nwMQIR5Tv2X+GvN3Vr5yOHeES6b6K8AxPMn 2VVnFTPs5aZVPO4PhWT+c/6By6txn+2QJmsZ/8W1QmVSr4QcX2XkOza0joEcYa8k8ODh 0Jz/mUlyUVrza2brukgVbDchTyIvUuac9kzyriNJu3H3GHbYFbMlsTLRb4qyI13N2/40 sHzw==
X-Gm-Message-State: APjAAAXKHEeythAjWkaM+ADxWUgoq/bllPce8HlCjyYp0TDFGviGnasA EKallDh1sQZ2+J72BSiQyyWszIapDbUjBeh3LUw=
X-Google-Smtp-Source: APXvYqyl2MRtMbSQuAsXASaJwKEuBFtvuaxU0+2sUD7CKJe7T1Kd5/9xT3dKYXvJZb9t3JhNSVWshpd+vE+pOH1ojRk=
X-Received: by 2002:a9d:7305:: with SMTP id e5mr116440368otk.64.1578405072086;  Tue, 07 Jan 2020 05:51:12 -0800 (PST)
MIME-Version: 1.0
References: <87E116C31DAF1434C3C3937F@PSB>
In-Reply-To: <87E116C31DAF1434C3C3937F@PSB>
From: Phillip Hallam-Baker <ietf@hallambaker.com>
Date: Tue, 7 Jan 2020 08:51:00 -0500
Message-ID: <CAMm+Lwi5tWUNK5nO4d8qoum03fV-1bchfP_Qu3ktANgRDd-RVg@mail.gmail.com>
To: John C Klensin <john-ietf@jck.com>
Cc: The IESG <iesg@ietf.org>,  "General Area Review Team (gen-art@ietf.org)" <art@ietf.org>, Mark Nottingham <mnot@mnot.net>, urn@ietf.org,  IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a22c17059b8d11e6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/QDQ_26w4GQOt2nX6MWBXVtryXBk>
Subject: Re: [art] URNs and Last Call: <draft-nottingham-rfc7320bis-02.txt> (URI Design and Ownership) to Best Current Practice
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2020 13:51:16 -0000

--000000000000a22c17059b8d11e6
Content-Type: text/plain; charset="UTF-8"

I remain of the view that the URN/URL distinction is unhelpful because it
is meaningless. There are no sharp boundaries between categories of
identifier as the distinction supposes.

Before making this argument in more detail, I will make a plea for respect.
I find that the biggest obstacle to getting clarity on naming is that when
faced with an analysis that contradicts deeply held beliefs, the usual
response is to tell people to 'do some research' or 'understand the issues'.

The URN/URI distinction does not in fact represent an essential distinction
between types identifiers as claimed. It describes a difference in source
of authority at best, not an essential property.

1) DNS names are names.

This is easy to see, it is what the N stands for. The signifier bears no
direct relation to the signified. It is a purely conventional relationship.

2) IP addresses are also names

Again, the signifier bears no direct relation to the signified. It is a
purely conventional relationship.

3) File names are names

Again, the signifier bears no direct relation to the signified. It is a
purely conventional relationship.

4) HTTP local paths are names

See above.


So a HTTP URL consists of

<method part> :// <IANA name part> // <local name part>

So a URL is obviously a form of name. The location semantics are not
intrinsic to the name itself, they are intrinsic to its mode of use.


If you look at practically every UR'N' scheme it has precisely the same
form albeit with different syntax. There is a method part and some
hierarchical delegation of naming. But (with rare exceptions) it is naming
all the way down.

The reason URL/URL discussions are so notoriously unproductive is people
are attempting to make an intrinsic distinction between classes of name
where there is none.


The only forms of network identifier that are not pure names are data URIs
and the ones that are indexical such as the ni: scheme described in RFC6920.

But even that distinction can be bent. The strong Internet Names I propose
here:
https://www.ietf.org/id/draft-hallambaker-mesh-udf-08.html define a subset
of DNS labels that are indexical rather than names. And those have some
important and useful properties. They allow the result of a trust decision
to be encapsulated as an atomic name.


On Tue, Jan 7, 2020 at 1:58 AM John C Klensin <john-ietf@jck.com> wrote:

> Hi.
>
> My apologies for the extreme lateness of this note.  I have
> tried to pass URN work on to others since RFCs 8141 and 8254 and
> had assumed that someone else would check through this document
> to be sure that it appropriately covered both locator-type and
> name-type URIs (particularly URNs) (see RFC 3986 Section 1.1.3).
> I had assumed that reviews within the ART area and/or a specific
> ART Area Review would address that topic but, AFAICT, they may
> not have done so.
>
> I've had occasion to look through the document and I'm actually
> not sure about the name-locator distinction as it may apply to
> it.  This note will be short and is rather more about asking the
> IESG to be sure that any possible issues are addressed than to
> try to do a detailed review of the issues.
>
> AFAICT, the focus of the I-D is to be sure that applications and
> elaborations of any URI scheme be firmly under the control and
> management of the owner of that scheme and that possible
> deviations from that principle are well-controlled.
> http://www.w3.org/TR/2004/REC-webarch-20041215, Section 2.2.2.1,
> cited in the draft as [webarch] is clear that the ownership of a
> URN is delegated to the owners of URN Namespaces rather than
> being bound to the "urn" URI scheme itself.  I believe it is
> possible to read this document in a way that has no impact on
> URNs and URN namespaces.   However, it appears to me that, if
> read without appropriate care, some of the restrictions imposed
> on queries and fragments may be inconsistent with mechanisms and
> syntax for use in particular URN Namespaces or URNs generally
> that were contemplated and extensively discussed during the
> development of RFC 8141.  Those ideas were deferred by the WG
> for future work but the mechanisms may well be in use in
> important URN namespaces.  Because the last paragraph of Section
> 1.1 of this I-D essentially declares any existing specification,
> even a standards-track one or one adopted by other bodies, that
> does not comply with the recommendations of the I-D to be
> incorrect and in need of correction, the effects of a reading
> that retroactively restricts URN Namespace practices that are
> under the control of the Namespace owners could be quite serious.
>
> My preference would be that someone who has been more active
> with URN work and Namespace registrations in the last couple of
> years do a careful review of the document to determine whether
> my concerns justify some tuning of the text.  However, given how
> late it is in the review process (again, my apologies for not
> catching the issue until now), a reasonable alternative would be
> to simply insert a sentence early in the I-D that says that it
> applies primarily to locator-type URIs although name-type ones
> may find it useful as general guidance _or_ to explicitly call
> out the difference in ownership between URNs and other URI
> schemes.
>
>  thanks,
>    john
>
> p.s. It would be, IMO, helpful if the IESG and the community
> would think about the implications of BCP (or IETF-stream
> Informational) documents that effectively obsolete or deprecate
> existing standards without identifying them or explicitly
> updating them and whose responsibility it is to find the
> discrepancies.
>
> _______________________________________________
> art mailing list
> art@ietf.org
> https://www.ietf.org/mailman/listinfo/art
>

--000000000000a22c17059b8d11e6
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"fon=
t-size:small">I remain of the view that the URN/URL distinction is unhelpfu=
l because it is meaningless. There are no sharp boundaries=C2=A0between cat=
egories of identifier as the distinction supposes.</div><div class=3D"gmail=
_default" style=3D"font-size:small"><br></div><div class=3D"gmail_default" =
style=3D"font-size:small">Before making this argument in more detail, I wil=
l make a plea for respect. I find that the biggest obstacle to getting clar=
ity on naming is that when faced with an analysis that contradicts deeply h=
eld beliefs, the usual response is to tell people to &#39;do some research&=
#39; or &#39;understand the issues&#39;.</div><div class=3D"gmail_default" =
style=3D"font-size:small"><br></div><div class=3D"gmail_default" style=3D"f=
ont-size:small">The URN/URI distinction does not in fact represent an essen=
tial distinction between types identifiers as claimed. It describes a diffe=
rence in source of authority at best, not an essential property.</div><div =
class=3D"gmail_default" style=3D"font-size:small"><br></div><div class=3D"g=
mail_default" style=3D"font-size:small">1) DNS names are names.</div><div c=
lass=3D"gmail_default" style=3D"font-size:small"><br></div><div class=3D"gm=
ail_default" style=3D"font-size:small">This is easy to see, it is what the =
N stands for. The signifier bears no direct relation to the signified. It i=
s a purely conventional relationship.</div><div class=3D"gmail_default" sty=
le=3D"font-size:small"><br></div><div class=3D"gmail_default" style=3D"font=
-size:small">2) IP addresses are also names</div><div class=3D"gmail_defaul=
t" style=3D"font-size:small"><br></div><div class=3D"gmail_default" style=
=3D"font-size:small">Again, the=C2=A0signifier bears no direct relation to =
the signified. It is a purely conventional relationship.</div><div class=3D=
"gmail_default" style=3D"font-size:small"><br></div><div class=3D"gmail_def=
ault" style=3D"font-size:small">3) File names are names</div><div class=3D"=
gmail_default" style=3D"font-size:small"><br></div><div class=3D"gmail_defa=
ult" style=3D"font-size:small">Again, the=C2=A0signifier bears no direct re=
lation to the signified. It is a purely conventional relationship.<br></div=
><div class=3D"gmail_default" style=3D"font-size:small"><br></div><div clas=
s=3D"gmail_default" style=3D"font-size:small">4) HTTP local paths are names=
</div><div class=3D"gmail_default" style=3D"font-size:small"><br></div><div=
 class=3D"gmail_default" style=3D"font-size:small">See above.</div><div cla=
ss=3D"gmail_default" style=3D"font-size:small"><br></div><div class=3D"gmai=
l_default" style=3D"font-size:small"><br></div><div class=3D"gmail_default"=
 style=3D"font-size:small">So a HTTP URL consists of</div><div class=3D"gma=
il_default" style=3D"font-size:small"><br></div><div class=3D"gmail_default=
" style=3D"font-size:small">&lt;method part&gt; :// &lt;IANA name part&gt; =
// &lt;local name part&gt;</div><div class=3D"gmail_default" style=3D"font-=
size:small"><br></div><div class=3D"gmail_default" style=3D"font-size:small=
">So a URL is obviously a form of name. The location semantics are not intr=
insic to the name itself, they are intrinsic to its mode of use.=C2=A0</div=
><div class=3D"gmail_default" style=3D"font-size:small"><br></div><div clas=
s=3D"gmail_default" style=3D"font-size:small"><br></div><div class=3D"gmail=
_default" style=3D"font-size:small">If you look at practically every UR&#39=
;N&#39; scheme it has precisely the same form albeit with different syntax.=
 There is a method part and some hierarchical delegation of naming. But (wi=
th rare exceptions) it is naming all the way down.</div><div class=3D"gmail=
_default" style=3D"font-size:small"><br></div><div class=3D"gmail_default" =
style=3D"font-size:small">The reason URL/URL discussions are so notoriously=
 unproductive is people are attempting to make an intrinsic distinction bet=
ween classes of name where there is none.</div><div class=3D"gmail_default"=
 style=3D"font-size:small"><br></div><div class=3D"gmail_default" style=3D"=
font-size:small"><br></div><div class=3D"gmail_default" style=3D"font-size:=
small">The only forms of network identifier that are not pure names are dat=
a URIs and the ones that are indexical such as the ni: scheme described in =
RFC6920.</div><div class=3D"gmail_default" style=3D"font-size:small"><br></=
div><div class=3D"gmail_default" style=3D"font-size:small">But even that di=
stinction can be bent. The strong Internet Names I propose here:</div><div =
class=3D"gmail_default" style=3D"font-size:small"><a href=3D"https://www.ie=
tf.org/id/draft-hallambaker-mesh-udf-08.html">https://www.ietf.org/id/draft=
-hallambaker-mesh-udf-08.html</a>=C2=A0define a subset of DNS labels that a=
re indexical rather than names. And those have some important and useful pr=
operties. They allow the result of a trust decision to be encapsulated as a=
n atomic name.<br></div><div class=3D"gmail_default" style=3D"font-size:sma=
ll"><br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=
=3D"gmail_attr">On Tue, Jan 7, 2020 at 1:58 AM John C Klensin &lt;<a href=
=3D"mailto:john-ietf@jck.com">john-ietf@jck.com</a>&gt; wrote:<br></div><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-lef=
t:1px solid rgb(204,204,204);padding-left:1ex">Hi.<br>
<br>
My apologies for the extreme lateness of this note.=C2=A0 I have<br>
tried to pass URN work on to others since RFCs 8141 and 8254 and<br>
had assumed that someone else would check through this document<br>
to be sure that it appropriately covered both locator-type and<br>
name-type URIs (particularly URNs) (see RFC 3986 Section 1.1.3).<br>
I had assumed that reviews within the ART area and/or a specific<br>
ART Area Review would address that topic but, AFAICT, they may<br>
not have done so.<br>
<br>
I&#39;ve had occasion to look through the document and I&#39;m actually<br>
not sure about the name-locator distinction as it may apply to<br>
it.=C2=A0 This note will be short and is rather more about asking the<br>
IESG to be sure that any possible issues are addressed than to<br>
try to do a detailed review of the issues.<br>
<br>
AFAICT, the focus of the I-D is to be sure that applications and<br>
elaborations of any URI scheme be firmly under the control and<br>
management of the owner of that scheme and that possible<br>
deviations from that principle are well-controlled.<br>
<a href=3D"http://www.w3.org/TR/2004/REC-webarch-20041215" rel=3D"noreferre=
r" target=3D"_blank">http://www.w3.org/TR/2004/REC-webarch-20041215</a>, Se=
ction 2.2.2.1,<br>
cited in the draft as [webarch] is clear that the ownership of a<br>
URN is delegated to the owners of URN Namespaces rather than<br>
being bound to the &quot;urn&quot; URI scheme itself.=C2=A0 I believe it is=
<br>
possible to read this document in a way that has no impact on<br>
URNs and URN namespaces.=C2=A0 =C2=A0However, it appears to me that, if<br>
read without appropriate care, some of the restrictions imposed<br>
on queries and fragments may be inconsistent with mechanisms and<br>
syntax for use in particular URN Namespaces or URNs generally<br>
that were contemplated and extensively discussed during the<br>
development of RFC 8141.=C2=A0 Those ideas were deferred by the WG<br>
for future work but the mechanisms may well be in use in<br>
important URN namespaces.=C2=A0 Because the last paragraph of Section<br>
1.1 of this I-D essentially declares any existing specification,<br>
even a standards-track one or one adopted by other bodies, that<br>
does not comply with the recommendations of the I-D to be<br>
incorrect and in need of correction, the effects of a reading<br>
that retroactively restricts URN Namespace practices that are<br>
under the control of the Namespace owners could be quite serious.<br>
<br>
My preference would be that someone who has been more active<br>
with URN work and Namespace registrations in the last couple of<br>
years do a careful review of the document to determine whether<br>
my concerns justify some tuning of the text.=C2=A0 However, given how<br>
late it is in the review process (again, my apologies for not<br>
catching the issue until now), a reasonable alternative would be<br>
to simply insert a sentence early in the I-D that says that it<br>
applies primarily to locator-type URIs although name-type ones<br>
may find it useful as general guidance _or_ to explicitly call<br>
out the difference in ownership between URNs and other URI<br>
schemes.<br>
<br>
=C2=A0thanks,<br>
=C2=A0 =C2=A0john<br>
<br>
p.s. It would be, IMO, helpful if the IESG and the community<br>
would think about the implications of BCP (or IETF-stream<br>
Informational) documents that effectively obsolete or deprecate<br>
existing standards without identifying them or explicitly<br>
updating them and whose responsibility it is to find the<br>
discrepancies.<br>
<br>
_______________________________________________<br>
art mailing list<br>
<a href=3D"mailto:art@ietf.org" target=3D"_blank">art@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/art" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/art</a><br>
</blockquote></div></div>

--000000000000a22c17059b8d11e6--


From nobody Tue Jan  7 08:17:03 2020
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08A5712011B; Tue,  7 Jan 2020 08:16:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable 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 awvczxoQv_1e; Tue,  7 Jan 2020 08:16:29 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E27512025D; Tue,  7 Jan 2020 08:15:43 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 7B32B3897A; Tue,  7 Jan 2020 11:15:22 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 9864060A; Tue,  7 Jan 2020 11:15:42 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Phillip Hallam-Baker <ietf@hallambaker.com>
cc: John C Klensin <john-ietf@jck.com>, "General Area Review Team \(gen-art\@ietf.org\)" <art@ietf.org>, urn@ietf.org, The IESG <iesg@ietf.org>, IETF Discussion Mailing List <ietf@ietf.org>
In-Reply-To: <CAMm+Lwi5tWUNK5nO4d8qoum03fV-1bchfP_Qu3ktANgRDd-RVg@mail.gmail.com>
References: <87E116C31DAF1434C3C3937F@PSB> <CAMm+Lwi5tWUNK5nO4d8qoum03fV-1bchfP_Qu3ktANgRDd-RVg@mail.gmail.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Tue, 07 Jan 2020 11:15:42 -0500
Message-ID: <29803.1578413742@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/zEODZcVTo71Jawe_BVHj6G046zI>
Subject: Re: [art] URNs and Last Call: <draft-nottingham-rfc7320bis-02.txt> (URI Design and Ownership) to Best Current Practice
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2020 16:16:42 -0000

--=-=-=
Content-Type: text/plain


Phillip Hallam-Baker <ietf@hallambaker.com> wrote:
    > I remain of the view that the URN/URL distinction is unhelpful because it is
    > meaningless. There are no sharp boundaries between categories of identifier
    > as the distinction supposes.

    > Before making this argument in more detail, I will make a plea for respect. I
    > find that the biggest obstacle to getting clarity on naming is that when
    > faced with an analysis that contradicts deeply held beliefs, the usual
    > response is to tell people to 'do some research' or 'understand the issues'.

    > The URN/URI distinction does not in fact represent an essential distinction
    > between types identifiers as claimed. It describes a difference in source of
    > authority at best, not an essential property.

I agree with you.

I think that we might have found new ways in which they are meaningfully
distinct had to a uquitious way to resolve the more abstract URNs.
That didn't happen, and I don't imagine that it is coming in the way envisioned.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl4Urq4ACgkQgItw+93Q
3WWONgf8DeSN6pqvnrPmk6JBkccxZSOJo0qaGFxfwTLm37ssBZi2B0/wJTlqsLam
DHobBseXAa9QIczNhhIraUBZ3o/cxlLj75MkyRiutga8olIFSdavmK8VOC7AcXY5
Q9j2DesWlYGW4rWABOmm3jyGFo9jGjmM4Q6cvrtveXCDcUGtg3WFaLJqjeHHBWVY
nIwqBZSCgfy0Rg/XB/WpzDWB8QIm1g88HKCGvt8eSw6bQHLD/8vp1DImWe61ZrEt
rjNRm8GpJ2xJt2552IUAz4GJyKkJ3FVUaG1cNGmyRCYGzpdnHmKPSkIi+FiQx2Jo
+khrc3dQLwSYBsZ5Z0NDjIEb5NO7+g==
=2Q2o
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Tue Jan  7 08:35:33 2020
Return-Path: <adam@nostrum.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96375120855; Tue,  7 Jan 2020 08:35:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.98
X-Spam-Level: 
X-Spam-Status: No, score=-1.98 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.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 d05P0sxs3B5X; Tue,  7 Jan 2020 08:35:22 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 68DFD120851; Tue,  7 Jan 2020 08:35:18 -0800 (PST)
Received: from Svantevit.local (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id 007GZEEY063997 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 7 Jan 2020 10:35:16 -0600 (CST) (envelope-from adam@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1578414917; bh=kh6+P4K8azbFqbi6ACYIBh3BOFCHbZc1rccEKnmGM0A=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=TDf+0KU4w5wgOd6b0WPrKO0xIbU/DD0d7eEr+PG1cQXNYXNtUdCcFNV0jDgAL4De3 6KkWoZf38deb3FsVYydMxXdm3v4P/L1sUvue8E/836iG8eWgUW5TomcufbkQbPwzf0 2wHAQJpFo5KSt5gVTnAnXSOk5rPdChZKWXxRHE9I=
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be Svantevit.local
To: John C Klensin <john-ietf@jck.com>, iesg@ietf.org
Cc: art@ietf.org, mnot@mnot.net, urn@ietf.org, ietf@ietf.org
References: <87E116C31DAF1434C3C3937F@PSB>
From: Adam Roach <adam@nostrum.com>
Message-ID: <a267e8d7-e88f-fe84-a3d4-eb12b88a46ad@nostrum.com>
Date: Tue, 7 Jan 2020 10:35:09 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <87E116C31DAF1434C3C3937F@PSB>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/wo8bBwRO9Ihyx9WcSUtAp4O503U>
Subject: Re: [art] URNs and Last Call: <draft-nottingham-rfc7320bis-02.txt> (URI Design and Ownership) to Best Current Practice
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2020 16:35:28 -0000

To help with framing this conversation, the changes from RFC 7320 are 
highlighted here:

https://www.ietf.org/rfcdiff?url1=rfc7320&url2=draft-nottingham-rfc7320bis-03

I have some rather extensive thoughts on the process of creating bis 
documents [1]. While I'm not going to reiterate all of them here, I want 
to highlight a specific passage that seems to bear on John's comments:

>    One major concern that drives these incremental document updates is
>    that an attempt to republish an RFC as originally described in RFC
>    2026 can result in such an effort being bogged down by issues that
>    exist in text unrelated to the desired changes.  Such issues can
>    arise from a change in the consensus of the IETF around best current
>    practices, such as in the areas of security, privacy, or
>    architectural design of an underlying protocol.  This complication
>    arises from the fact that processing of an updated full version of an
>    RFC is procedurally identical to processing of a green-field
>    definition of a new protocol: review by the IETF at large, and review
>    by the IESG, are performed on the entire document, leaving legacy
>    text open to comments that will delay - and occasionally block -
>    publication of such documents.


/a

____
[1] https://tools.ietf.org/html/draft-roach-bis-documents-00

On 1/7/20 12:57 AM, John C Klensin wrote:
> Hi.
>
> My apologies for the extreme lateness of this note.  I have
> tried to pass URN work on to others since RFCs 8141 and 8254 and
> had assumed that someone else would check through this document
> to be sure that it appropriately covered both locator-type and
> name-type URIs (particularly URNs) (see RFC 3986 Section 1.1.3).
> I had assumed that reviews within the ART area and/or a specific
> ART Area Review would address that topic but, AFAICT, they may
> not have done so.
>
> I've had occasion to look through the document and I'm actually
> not sure about the name-locator distinction as it may apply to
> it.  This note will be short and is rather more about asking the
> IESG to be sure that any possible issues are addressed than to
> try to do a detailed review of the issues.
>
> AFAICT, the focus of the I-D is to be sure that applications and
> elaborations of any URI scheme be firmly under the control and
> management of the owner of that scheme and that possible
> deviations from that principle are well-controlled.
> http://www.w3.org/TR/2004/REC-webarch-20041215, Section 2.2.2.1,
> cited in the draft as [webarch] is clear that the ownership of a
> URN is delegated to the owners of URN Namespaces rather than
> being bound to the "urn" URI scheme itself.  I believe it is
> possible to read this document in a way that has no impact on
> URNs and URN namespaces.   However, it appears to me that, if
> read without appropriate care, some of the restrictions imposed
> on queries and fragments may be inconsistent with mechanisms and
> syntax for use in particular URN Namespaces or URNs generally
> that were contemplated and extensively discussed during the
> development of RFC 8141.  Those ideas were deferred by the WG
> for future work but the mechanisms may well be in use in
> important URN namespaces.  Because the last paragraph of Section
> 1.1 of this I-D essentially declares any existing specification,
> even a standards-track one or one adopted by other bodies, that
> does not comply with the recommendations of the I-D to be
> incorrect and in need of correction, the effects of a reading
> that retroactively restricts URN Namespace practices that are
> under the control of the Namespace owners could be quite serious.
>
> My preference would be that someone who has been more active
> with URN work and Namespace registrations in the last couple of
> years do a careful review of the document to determine whether
> my concerns justify some tuning of the text.  However, given how
> late it is in the review process (again, my apologies for not
> catching the issue until now), a reasonable alternative would be
> to simply insert a sentence early in the I-D that says that it
> applies primarily to locator-type URIs although name-type ones
> may find it useful as general guidance _or_ to explicitly call
> out the difference in ownership between URNs and other URI
> schemes.
>
>   thanks,
>     john
>
> p.s. It would be, IMO, helpful if the IESG and the community
> would think about the implications of BCP (or IETF-stream
> Informational) documents that effectively obsolete or deprecate
> existing standards without identifying them or explicitly
> updating them and whose responsibility it is to find the
> discrepancies.
>


From nobody Tue Jan  7 09:48:22 2020
Return-Path: <barryleiba@gmail.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A14A1200E9; Tue,  7 Jan 2020 09:48:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level: 
X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 Sj02Aq8RDiIK; Tue,  7 Jan 2020 09:48:14 -0800 (PST)
Received: from mail-io1-f47.google.com (mail-io1-f47.google.com [209.85.166.47]) (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 B48E31200CC; Tue,  7 Jan 2020 09:48:14 -0800 (PST)
Received: by mail-io1-f47.google.com with SMTP id h8so243535iob.2; Tue, 07 Jan 2020 09:48:14 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=IuOpvnuUwP/KQ++zdKH6O9Dn1kirFI26FmD411J8kFo=; b=Mfw4ZjImsvORLT7oJY47TinaeoBE4xmWTTXxw9Ynel8EI0ijKfg2ZxlLgUC/HxaDW6 5FyPFryWTmLfQKP2szTM1OsSnaRv6csegUGgVzxg/tg0j6OySZndVf7DZG6xQrSecxjH ZeNDkNMAvSRlTbGZBjRpNdzfRzZpxJ8dOIetbxoO4NB0m7xw62+lArmJD5Q62YRUO+B8 F7rcmFmhDjE49xG7DzEPKwpQps++qVIuT0dvfzMTapLVpmABUnYDGEwftm/InEJZRGmt DkFDlZ2JSXlVVG5bwEkjenKYRI12UW/1voi5PLOy/bDDq9trr8CxE9EjE9nU2bVfuNoO bFTQ==
X-Gm-Message-State: APjAAAXKyZ6zs5BAfpV/zXgWalNcry127VVhsoSq1Fa0Ep/kEbe/RYrJ c4wFvbGSnpqAchvsaTJysA3Y2M8QHzahKIjePaMEuA==
X-Google-Smtp-Source: APXvYqz+iMHKRZ6cE/ZPkUmY/G7J7oTUieATdjzbRNz0GeAS2qd7qpmAN1yC/IUyviKzZwXXAF4nw+lZLuprGt/73V8=
X-Received: by 2002:a5e:8417:: with SMTP id h23mr84197ioj.17.1578419293573; Tue, 07 Jan 2020 09:48:13 -0800 (PST)
MIME-Version: 1.0
References: <87E116C31DAF1434C3C3937F@PSB>
In-Reply-To: <87E116C31DAF1434C3C3937F@PSB>
From: Barry Leiba <barryleiba@computer.org>
Date: Tue, 7 Jan 2020 12:48:02 -0500
Message-ID: <CALaySJJoeBVnsc300eD0d0Kpqan-n2U_ckmr0OCpmOSy=s9w=w@mail.gmail.com>
To: John C Klensin <john-ietf@jck.com>
Cc: IESG <iesg@ietf.org>, art@ietf.org, Mark Nottingham <mnot@mnot.net>, urn@ietf.org, IETF discussion list <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/8PgNFH8F-1d7Zdncv7nS3Zs80gw>
Subject: Re: [art] URNs and Last Call: <draft-nottingham-rfc7320bis-02.txt> (URI Design and Ownership) to Best Current Practice
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2020 17:48:16 -0000

I think we need to tease apart two things in John's note: the URN
scheme, and the concept of URNs as opposed to URLs, the two together
forming what we call URIs.

It's clear to me that BCP 190 has no actual effect on "urn:", because
the things it talks about simply don't apply there, or are taken care
of by the fact that URN namespaces are completely controlled by the
owners of the namespaces.  There is no internal hierarchy within URN
namespaces unless the specification of the namespace creates one and
defines how that hierarchy works and is managed.

For the other part of the issue, I'm not fully in agreement with
Phillip and Michael, in that I do think there's a useful distinction
between a URI that names something without specifying how to locate
it... and one that is a locator.  There is, for example, a fundamental
difference between, say, "http:" and "ni:" (see RFC 6920).

That said, I also think that existing URI schemes that define *names*
lack hierarchies, and are similarly not really affected by BCP 190.
As I read through 7320bis and placed my "Yes" ballot, I didn't see
anything, neither in the original text nor in the changed text, that
made me question this, and as I look back through it now I still
don't.

So I don't have any concerns here.  If anyone has something specific
to raise, please raise it now, while the document is still in IESG
Evaluation and we can more easily discuss it and make changes.

Barry

On Tue, Jan 7, 2020 at 1:58 AM John C Klensin <john-ietf@jck.com> wrote:
>
> Hi.
>
> My apologies for the extreme lateness of this note.  I have
> tried to pass URN work on to others since RFCs 8141 and 8254 and
> had assumed that someone else would check through this document
> to be sure that it appropriately covered both locator-type and
> name-type URIs (particularly URNs) (see RFC 3986 Section 1.1.3).
> I had assumed that reviews within the ART area and/or a specific
> ART Area Review would address that topic but, AFAICT, they may
> not have done so.
>
> I've had occasion to look through the document and I'm actually
> not sure about the name-locator distinction as it may apply to
> it.  This note will be short and is rather more about asking the
> IESG to be sure that any possible issues are addressed than to
> try to do a detailed review of the issues.
>
> AFAICT, the focus of the I-D is to be sure that applications and
> elaborations of any URI scheme be firmly under the control and
> management of the owner of that scheme and that possible
> deviations from that principle are well-controlled.
> http://www.w3.org/TR/2004/REC-webarch-20041215, Section 2.2.2.1,
> cited in the draft as [webarch] is clear that the ownership of a
> URN is delegated to the owners of URN Namespaces rather than
> being bound to the "urn" URI scheme itself.  I believe it is
> possible to read this document in a way that has no impact on
> URNs and URN namespaces.   However, it appears to me that, if
> read without appropriate care, some of the restrictions imposed
> on queries and fragments may be inconsistent with mechanisms and
> syntax for use in particular URN Namespaces or URNs generally
> that were contemplated and extensively discussed during the
> development of RFC 8141.  Those ideas were deferred by the WG
> for future work but the mechanisms may well be in use in
> important URN namespaces.  Because the last paragraph of Section
> 1.1 of this I-D essentially declares any existing specification,
> even a standards-track one or one adopted by other bodies, that
> does not comply with the recommendations of the I-D to be
> incorrect and in need of correction, the effects of a reading
> that retroactively restricts URN Namespace practices that are
> under the control of the Namespace owners could be quite serious.
>
> My preference would be that someone who has been more active
> with URN work and Namespace registrations in the last couple of
> years do a careful review of the document to determine whether
> my concerns justify some tuning of the text.  However, given how
> late it is in the review process (again, my apologies for not
> catching the issue until now), a reasonable alternative would be
> to simply insert a sentence early in the I-D that says that it
> applies primarily to locator-type URIs although name-type ones
> may find it useful as general guidance _or_ to explicitly call
> out the difference in ownership between URNs and other URI
> schemes.
>
>  thanks,
>    john
>
> p.s. It would be, IMO, helpful if the IESG and the community
> would think about the implications of BCP (or IETF-stream
> Informational) documents that effectively obsolete or deprecate
> existing standards without identifying them or explicitly
> updating them and whose responsibility it is to find the
> discrepancies.
>


From nobody Tue Jan  7 11:12:01 2020
Return-Path: <john-ietf@jck.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D40C61200FB; Tue,  7 Jan 2020 11:11:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 z84cV2DVfgNG; Tue,  7 Jan 2020 11:11:52 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9ADFF1200FD; Tue,  7 Jan 2020 11:11:52 -0800 (PST)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1iouGZ-0008r3-9f; Tue, 07 Jan 2020 14:11:47 -0500
Date: Tue, 07 Jan 2020 14:11:40 -0500
From: John C Klensin <john-ietf@jck.com>
To: Adam Roach <adam@nostrum.com>, iesg@ietf.org
cc: art@ietf.org, mnot@mnot.net, urn@ietf.org, ietf@ietf.org
Message-ID: <444B2465A9B73F3D0DE59FFF@PSB>
In-Reply-To: <a267e8d7-e88f-fe84-a3d4-eb12b88a46ad@nostrum.com>
References: <87E116C31DAF1434C3C3937F@PSB> <a267e8d7-e88f-fe84-a3d4-eb12b88a46ad@nostrum.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/R1HXBiIpE_6ca5jGNCMNwE-DTAw>
Subject: Re: [art] URNs and Last Call: <draft-nottingham-rfc7320bis-02.txt> (URI Design and Ownership) to Best Current Practice
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2020 19:11:55 -0000

--On Tuesday, January 7, 2020 10:35 -0600 Adam Roach
<adam@nostrum.com> wrote:

> To help with framing this conversation, the changes from RFC
> 7320 are highlighted here:
>=20
> =
https://www.ietf.org/rfcdiff?url1=3Drfc7320&url2=3Ddraft-nottingh=
a
> m-rfc7320bis-03
>=20
> I have some rather extensive thoughts on the process of
> creating bis documents [1]. While I'm not going to reiterate
> all of them here, I want to highlight a specific passage that
> seems to bear on John's comments:
>=20
>> =C2=A0=C2=A0 One major concern that drives these incremental =
document
>> updates is =C2=A0=C2=A0 that an attempt to republish an RFC =
as
>> originally described in RFC =C2=A0=C2=A0 2026 can result in =
such an
>> effort being bogged down by issues that =C2=A0=C2=A0 exist in =
text
>> unrelated to the desired changes.=C2=A0 Such issues can =
=C2=A0=C2=A0
>> arise from a change in the consensus of the IETF around best
>...

Adam,

I studied those comments when you first posted them.  I believe
that I sent comments at that time, but to summarize and
highlight them in a shorter note, I see a key problem (and
several others that may be less important and that were
addressed in my earlier comments) with an replacement document
that does not address all open issues in its predecessor:

It leaves the reader with the understanding that the new
document represents the IETF's best understanding of the topic
covered (not merely a view of the most urgent problems to be
fixed).  Put differently, it implies that any issues not address
are unimportant.   That can be mitigated somewhat by including a
section identifying known outstanding issues, but
draft-nottingham-rfc7320bis-03 does not appear to contain such a
section.=20

In addition, as your quoted comment above implies, an
incremental document that nonetheless replaces an earlier one is
a change to what 2026 specifies.  I do not believe it is
appropriate to change the procedures of 2026 by ignoring it, nor
do I believe that examples of its being ignored in the past
constitute justification for ignoring it in the future.  Just as
we tried to do with NEWTRK and ISDs (arguably a different
approach to at least part of the problem you are trying to
address), a change to how we handle replacement documents that
ignores (if nothing else) 2026's "no known defects" rule
requires an update or other change to 2026 before the desired
approach is appealed to in order to justify a particular
document.

That, and my p.s., aside, I had hoped my note would rather
carefully avoid dragging us back into either this issue or the
ones raised by Phillip and Barry (like Barry, I don't fully
agree with the former).  It seems to me that both that comment
and part of Barry's raise fundamental questions about how
RFC3986 is defined and what it specifies.  Those issues are
probably best addressed at another time. =20

Instead, I was trying to raise a far more narrow question: Given
that RFC 3986 separates names and locators and that we have
already had confusion about what is appropriate in URNs based on
the language there, does this document make things worse?  I
think it may.  Even a statement fragment (from the first
paragraph of Section 3 and inherited from 7320) like "...as
links that are exchanged as part of the protocol, rather than
statically specified syntax" are inconsistent with the use of
keyword values in some URN namespaces as static indicators.  If
you want to ask the slightly different question of whether, if
RFC 7320 made things worse, does this I-D make things even worse
than that, I don't have an easy answer except to note at least
one example: The last paragraph of Section 2.3, which appears to
be new, says

> Extensions MUST NOT define a structure within individual URI
> components (e.g., a prefix or suffix), again to avoid
> collisions and erroneous client assumptions.

But, as I understand that rule, it is precisely what some rules,
and provisions for namespace-specific rules, in RFC 8141, do.

Again, the solution at this point appears to be either to be
much more careful about binding the statements in the I-D to the
concept of ownership or to indication that this specification
does not apply to URNs (or, if preferred, to what 3986 describes
as "name" URIs) at all.

best,
   john



From nobody Tue Jan  7 11:54:08 2020
Return-Path: <hallam@gmail.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BAA81200FD; Tue,  7 Jan 2020 11:53:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.398
X-Spam-Level: 
X-Spam-Status: No, score=-1.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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 VxQRab6X6ZKR; Tue,  7 Jan 2020 11:53:53 -0800 (PST)
Received: from mail-oi1-f179.google.com (mail-oi1-f179.google.com [209.85.167.179]) (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 2E27D1200B3; Tue,  7 Jan 2020 11:53:53 -0800 (PST)
Received: by mail-oi1-f179.google.com with SMTP id p67so498786oib.13; Tue, 07 Jan 2020 11:53:53 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ibvo7OmV9+zNwjb1AHdIT1vKqOZQ/LoeRVExlz19n8A=; b=m1eKD0DimMFXqj4PPYNigVO2KLLhsOBcW3N5+HschzBt+d9XjpTKCZ/Pinkv2KhwI6 /729Vyj9Ypp8nKx39lxkkD7U/6zh2JzQMBRHfbhi1lQotksNohLdUoc7K88OuYM1pfV0 i/PcO0X9FqdyPGze2jdPj9SbTRie5igCxN5dikPihXBTVFxhXQXdkgTY9SW7cUZQeqs6 5VLE2ipuU/9W/b3KGvHBNje5cb4P27TSO7e0iXGJ32U8HsMcv73sgPPcgc+vGKgVclc6 lPDRz9EhRrdsL+2vGi21eDGUIlye82PLhiQi45GD/+YzRhhz2IUb5Vw8yWrGrD5nvXAg qz7Q==
X-Gm-Message-State: APjAAAVLkUtD/oWlIfGNatz89g9iIJD+2cQYUSWADx6ep60Oae18a7w9 1phCnNwm4cpfsmYDFX9ioIKNriKUYWtF/vQFNKzbQ38td/U=
X-Google-Smtp-Source: APXvYqxvdqhMzuAeUM4BwZOAH1pf43T/A6RUak2okFVC3rLZ+5z6tKjB5FKIzUkgspI3SuwGkc7UO64MnMwpg2rrT1s=
X-Received: by 2002:a54:4f04:: with SMTP id e4mr48512oiy.111.1578426832209; Tue, 07 Jan 2020 11:53:52 -0800 (PST)
MIME-Version: 1.0
References: <87E116C31DAF1434C3C3937F@PSB> <CAMm+Lwi5tWUNK5nO4d8qoum03fV-1bchfP_Qu3ktANgRDd-RVg@mail.gmail.com> <29803.1578413742@localhost>
In-Reply-To: <29803.1578413742@localhost>
From: Phillip Hallam-Baker <ietf@hallambaker.com>
Date: Tue, 7 Jan 2020 14:53:43 -0500
Message-ID: <CAMm+LwjFUfayeeHmWTRiGiCBz-+afBOnoXVcF1PxzMibS6t-Uw@mail.gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: John C Klensin <john-ietf@jck.com>,  "General Area Review Team (gen-art@ietf.org)" <art@ietf.org>, urn@ietf.org, The IESG <iesg@ietf.org>, IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a3494a059b922212"
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/3_-2TsgIp43bMu4AKD3PyfP2VHI>
Subject: Re: [art] URNs and Last Call: <draft-nottingham-rfc7320bis-02.txt> (URI Design and Ownership) to Best Current Practice
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2020 19:53:55 -0000

--000000000000a3494a059b922212
Content-Type: text/plain; charset="UTF-8"

On Tue, Jan 7, 2020 at 12:48 PM Barry Leiba <barryleiba@computer.org>
wrote:

> For the other part of the issue, I'm not fully in agreement with
> Phillip and Michael, in that I do think there's a useful distinction
> between a URI that names something without specifying how to locate
> it... and one that is a locator.  There is, for example, a fundamental
> difference between, say, "http:" and "ni:" (see RFC 6920).


That is precisely what I was talking about when I said that ni: is
indexical. But that is no longer an essential distinction either.

We can distinguish names that are under IANA authority (DNS, IP) from those
that are not. But that is the limit of it.


Given that it was announced today that SHA-1 was broken, lets take another
look at a SIN:

alice@mm--mb2gk-6duf5-ygyyl-jny5e-rwshz.example.com

That is a valid email address. It can be routed on the Internet (not the
best privacy choice but possible). But it is a name that can be bound to a
security policy.

So if  mb2gk-6duf5-ygyyl-jny5e-rwshz is the UDF (SHA-2-512) of Alice's
OpenPGP encryption key. We have an implicit semantic here: Encrypt all mail
sent to this address with the key that has fingerprint
mb2gk-6duf5-ygyyl-jny5e-rwshz

The reason that I have hammered on the fact that the name/locator
distinction being bogus is precisely because the obsession with defining a
distinction where there is NO difference has caused the neglect of a
situation where there is a very real and important one.

https://www.ietf.org/id/draft-hallambaker-mesh-udf-08.html#name-secure-internet-names

A Strong Internet Name allows ANY URI with a DNS component to be turned



On Tue, Jan 7, 2020 at 11:15 AM Michael Richardson <mcr+ietf@sandelman.ca>
wrote:

>
> Phillip Hallam-Baker <ietf@hallambaker.com> wrote:
>     > I remain of the view that the URN/URL distinction is unhelpful
> because it is
>     > meaningless. There are no sharp boundaries between categories of
> identifier
>     > as the distinction supposes.
>
>     > Before making this argument in more detail, I will make a plea for
> respect. I
>     > find that the biggest obstacle to getting clarity on naming is that
> when
>     > faced with an analysis that contradicts deeply held beliefs, the
> usual
>     > response is to tell people to 'do some research' or 'understand the
> issues'.
>
>     > The URN/URI distinction does not in fact represent an essential
> distinction
>     > between types identifiers as claimed. It describes a difference in
> source of
>     > authority at best, not an essential property.
>
> I agree with you.
>
> I think that we might have found new ways in which they are meaningfully
> distinct had to a uquitious way to resolve the more abstract URNs.
> That didn't happen, and I don't imagine that it is coming in the way
> envisioned.
>

HTTPs are names but they are a name that embodies a (fairly) unambiguous
means of location.

Having had the misfortune to engage in discussion with acolytes of a
prominent opponent of post-modernism, I have been writing a defense of
postmodernism today. One of the chief arguments made by the postmodernists
is that perfect knowledge is an illusion. And I think that is a profound
observation that is essential to understanding why the original concept of
URNs and for that matter most registration schemes are doomed to fail.

The Web succeeded because of 404 Not Found. The links are scruffy. And that
is fine if you are OK with the idea that knowledge can be scruffy, that it
will never be perfect. And that is why the Web came out of CERN because
(good) scientists understand that there is no absolute knowledge and that
what we are arriving at is a better approximation to the truth, not the
truth itself.

There have been plenty of people making that type of argument since ancient
times. But until the mid 80s, most scientists had a very rigid epistemology
that was essentially Victorian in its outlook. Scientists were serious
people who were finding out profound and universal truths and we had all be
very very careful not to make mistakes because that 'would be bad'.

I would encourage people to take a look at what research scientists in
their 20s and 30s are saying about their approach to science. They are
utterly rejecting that view.

What politicians now call 'Western values' and demand other countries
observe is a modern construct that is fifty years (racial tolerance) old at
most. In some areas, what is now the fixed consensus is less than a decade
old (evolve already). The reason we have the nonsense of .com, .org, .net
etc is because DNS was designed by people who had an essentially Victorian
view of epistemology in which taxonomy represents essential qualities.
(Whether the same is true of the extension TLDs I will leave aside)

The reason I and others received (and continue to receive from some) the
patronizing responses we do (do some research you ignorant baboon! you
don't understand) is that we have profoundly different and fundamentally
incompatible epistemologies and some people regard mine as heresy. Both are
capable of self examination. But mine is capable of examining theirs, they
can only reject mine. So its like me trying to explain complex numbers to
someone who insists that you can't take the square root of a negative
number and can't get past that.

The route out of formal methods to PoMo is that to solve the problems we
faced in the 1980s in formal methods, it was necessary to apply
meta-mathematics and understand the limitations of logic. And once you do
that you are in Post Modernism.


So the URN notion that we must carefully decide how to resolve before we
defined schemes was wrong. It was and is much more important to have a
catalog that is as *complete *as possible than for the entries to be
*correct*.

Resolution of many types of name is inherently ambiguous because the
context varies. We cannot resolve a barcode on a physical object like a can
of beans. But we can ask for information on the can of beans and we can
order an instance of the can of beans for delivery. And both forms of
'location' are going to be subjective and depend on the context in which
they are attempted.

--000000000000a3494a059b922212
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"fon=
t-size:small"><div class=3D"gmail_quote"><div class=3D"gmail_default"><span=
 class=3D"gmail_default"></span>On Tue, Jan 7, 2020 at 12:48 PM Barry Leiba=
 &lt;<a href=3D"mailto:barryleiba@computer.org">barryleiba@computer.org</a>=
&gt; wrote:=C2=A0=C2=A0<br></div></div><blockquote style=3D"margin:0px 0px =
0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class=3D=
"gmail_quote"><span class=3D"gmail_default"></span>For the other part of th=
e issue, I&#39;m not fully in agreement with<br>Phillip and Michael, in tha=
t I do think there&#39;s a useful distinction<br>between a URI that names s=
omething without specifying how to locate<br>it... and one that is a locato=
r.=C2=A0 There is, for example, a fundamental<br>
difference between, say, &quot;http:&quot; and &quot;ni:&quot; (see RFC 692=
0).=C2=A0=C2=A0</blockquote><div><br></div><div class=3D"gmail_default">Tha=
t is precisely what I was talking about when I said that ni: is indexical. =
But that is no longer an essential distinction either.</div><div class=3D"g=
mail_default"><br></div><div class=3D"gmail_default">We can distinguish nam=
es that are under IANA authority (DNS, IP) from those that are not. But tha=
t is the limit of it.</div><div class=3D"gmail_default"><br></div><div clas=
s=3D"gmail_default"><br></div><div class=3D"gmail_default">Given that it wa=
s announced today that SHA-1 was broken, lets take another look at a SIN:</=
div><div class=3D"gmail_default"><br></div></div></div><div><div class=3D"g=
mail_default" style=3D"font-size:small"><span style=3D"font-family:&quot;No=
to Sans&quot;,Arial,Helvetica,sans-serif;font-size:14px"><a href=3D"mailto:=
alice@mm--mb2gk-6duf5-ygyyl-jny5e-rwshz.example.com">alice@mm--mb2gk-6duf5-=
ygyyl-jny5e-rwshz.example.com</a></span></div><br></div><div><div class=3D"=
gmail_default" style=3D"font-size:small">That is a valid email address. It =
can be routed on the Internet (not the best privacy choice but possible). B=
ut it is a name that can be bound to a security policy.</div><div class=3D"=
gmail_default" style=3D"font-size:small"><br></div><div class=3D"gmail_defa=
ult" style=3D"font-size:small">So if=C2=A0

mb2gk-6duf5-ygyyl-jny5e-rwshz is the UDF (SHA-2-512) of Alice&#39;s OpenPGP=
 encryption key. We have an implicit semantic here: Encrypt all mail sent t=
o this address with the key that has fingerprint mb2gk-6duf5-ygyyl-jny5e-rw=
shz

</div><br></div><div><div class=3D"gmail_default" style=3D"font-size:small"=
>The reason that I have hammered on the fact that the name/locator distinct=
ion being bogus is precisely because the obsession with defining a distinct=
ion where there is NO difference has caused the neglect of a situation wher=
e there is a very real and important one.</div><br></div><div><div class=3D=
"gmail_default" style=3D"font-size:small"><a href=3D"https://www.ietf.org/i=
d/draft-hallambaker-mesh-udf-08.html#name-secure-internet-names">https://ww=
w.ietf.org/id/draft-hallambaker-mesh-udf-08.html#name-secure-internet-names=
</a></div></div><div><br></div><div><div class=3D"gmail_default" style=3D"f=
ont-size:small">A Strong Internet Name allows ANY URI with a DNS component =
to be turned </div><br></div><div><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Tue, Jan 7, 2020 at 11:15 AM Micha=
el Richardson &lt;<a href=3D"mailto:mcr%2Bietf@sandelman.ca">mcr+ietf@sande=
lman.ca</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-lef=
t:1ex"><br>
Phillip Hallam-Baker &lt;<a href=3D"mailto:ietf@hallambaker.com" target=3D"=
_blank">ietf@hallambaker.com</a>&gt; wrote:<br>
=C2=A0 =C2=A0 &gt; I remain of the view that the URN/URL distinction is unh=
elpful because it is<br>
=C2=A0 =C2=A0 &gt; meaningless. There are no sharp boundaries between categ=
ories of identifier<br>
=C2=A0 =C2=A0 &gt; as the distinction supposes.<br>
<br>
=C2=A0 =C2=A0 &gt; Before making this argument in more detail, I will make =
a plea for respect. I<br>
=C2=A0 =C2=A0 &gt; find that the biggest obstacle to getting clarity on nam=
ing is that when<br>
=C2=A0 =C2=A0 &gt; faced with an analysis that contradicts deeply held beli=
efs, the usual<br>
=C2=A0 =C2=A0 &gt; response is to tell people to &#39;do some research&#39;=
 or &#39;understand the issues&#39;.<br>
<br>
=C2=A0 =C2=A0 &gt; The URN/URI distinction does not in fact represent an es=
sential distinction<br>
=C2=A0 =C2=A0 &gt; between types identifiers as claimed. It describes a dif=
ference in source of<br>
=C2=A0 =C2=A0 &gt; authority at best, not an essential property.<br>
<br>
I agree with you.<br>
<br>
I think that we might have found new ways in which they are meaningfully<br=
>
distinct had to a uquitious way to resolve the more abstract URNs.<br>
That didn&#39;t happen, and I don&#39;t imagine that it is coming in the wa=
y envisioned.<br></blockquote><div><br></div><div><div class=3D"gmail_defau=
lt" style=3D"font-size:small">HTTPs are names but they are a name that embo=
dies a (fairly) unambiguous means of location.</div><div class=3D"gmail_def=
ault" style=3D"font-size:small"><br></div><div class=3D"gmail_default" styl=
e=3D"font-size:small">Having had the misfortune to engage in discussion wit=
h acolytes of a prominent opponent of post-modernism, I have been writing a=
 defense of postmodernism today. One of the chief arguments made by the pos=
tmodernists is that perfect knowledge is an illusion. And I think that is a=
 profound observation that is essential to understanding why the original c=
oncept of URNs and for that matter most registration schemes are doomed to =
fail.</div><div class=3D"gmail_default" style=3D"font-size:small"><br></div=
><div class=3D"gmail_default" style=3D"font-size:small">The Web succeeded b=
ecause of 404 Not Found. The links are scruffy. And that is fine if you are=
 OK with the idea that knowledge can be scruffy, that it will never be perf=
ect. And that is why the Web came out of CERN because (good) scientists und=
erstand that there is no absolute knowledge and that what we are arriving a=
t is a better approximation to the truth, not the truth itself.=C2=A0</div>=
<div class=3D"gmail_default" style=3D"font-size:small"><br></div><div class=
=3D"gmail_default" style=3D"font-size:small">There have been plenty of peop=
le making that type of argument since ancient times. But until the mid 80s,=
 most scientists had a very rigid epistemology that was essentially Victori=
an in its outlook. Scientists were serious people who were finding out prof=
ound and universal truths and we had all be very very careful not to make m=
istakes because that &#39;would be bad&#39;.</div><div class=3D"gmail_defau=
lt" style=3D"font-size:small"><br></div><div class=3D"gmail_default" style=
=3D"font-size:small">I would encourage people to take a look at what resear=
ch scientists in their 20s and 30s are saying about their approach to scien=
ce. They are utterly rejecting that view.<br></div><div class=3D"gmail_defa=
ult" style=3D"font-size:small"><br></div><div class=3D"gmail_default" style=
=3D"font-size:small">What politicians now call &#39;Western values&#39; and=
 demand other countries observe is a modern construct that is fifty years (=
racial tolerance) old at most. In some areas, what is now the fixed consens=
us is less than a decade old (evolve already). The reason we have the nonse=
nse of .com, .org, .net etc is because DNS was designed by people who had a=
n essentially Victorian view of epistemology in which taxonomy represents e=
ssential qualities. (Whether the same is true of the extension TLDs I will =
leave aside)</div><div class=3D"gmail_default" style=3D"font-size:small"><b=
r></div><div class=3D"gmail_default" style=3D"font-size:small">The reason I=
 and others received (and continue to receive from some) the patronizing re=
sponses we do (do some research you ignorant baboon! you don&#39;t understa=
nd) is that we have profoundly different and fundamentally incompatible epi=
stemologies and some people regard mine as heresy. Both are capable of self=
 examination. But mine is capable of examining theirs, they can only reject=
 mine. So its like me trying to explain complex numbers to someone who insi=
sts that you can&#39;t take the square root of a negative number and can&#3=
9;t get past that.</div><div class=3D"gmail_default" style=3D"font-size:sma=
ll"><br></div><div class=3D"gmail_default" style=3D"font-size:small">The ro=
ute out of formal methods to PoMo is that to solve the problems we faced in=
 the 1980s in formal methods, it was necessary to apply meta-mathematics an=
d understand the limitations of logic. And once you do that you are in Post=
 Modernism.</div><div class=3D"gmail_default" style=3D"font-size:small"></d=
iv><br></div><div><br></div><div class=3D"gmail_default" style=3D"font-size=
:small">So the URN notion that we must carefully decide how to resolve befo=
re we defined schemes was wrong. It was and is much more important to have =
a catalog that is as <i>complete </i>as possible than for the entries to be=
 <i>correct</i>.</div><div class=3D"gmail_default" style=3D"font-size:small=
"><br></div><div class=3D"gmail_default" style=3D"font-size:small">Resoluti=
on of many types of name is inherently ambiguous because the context varies=
. We cannot resolve a barcode on a physical object like a can of beans. But=
 we can ask for information on the can of beans and we can order an instanc=
e of the can of beans for delivery. And both forms of &#39;location&#39; ar=
e going to be subjective and depend on the context in which they are attemp=
ted.</div></div></div>

--000000000000a3494a059b922212--


From nobody Tue Jan  7 14:49:40 2020
Return-Path: <cdel@firsthand.net>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCAC512085F; Tue,  7 Jan 2020 14:49:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.219
X-Spam-Level: 
X-Spam-Status: No, score=-1.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=firsthand.net
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 Dc9Y9WfyBA1W; Tue,  7 Jan 2020 14:49:34 -0800 (PST)
Received: from tranquility.default.cdelarrinaga.uk0.bigv.io (tranquility.default.cdelarrinaga.uk0.bigv.io [IPv6:2001:41c8:51:8b8::184]) (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 23A66120843; Tue,  7 Jan 2020 14:49:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=firsthand.net; s=tranquility;  h=Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:References:Cc:To:Subject; bh=l3BqeZDh4QF5H1jBkVTSzGJNkwQgCM6w9+2U9m8feTo=;  b=S0/Ei+GGCl87tWLGc61z8D2CKw/PSFmcPDm2dKkUND1gfQVpSq+zjDZwVO/1dZ6dDvKZ407YoMeUV21tKIaS+gIgJqPOu5tTn/39h6cvVVqIDv2MzgfH9rn6KbDvfEKQjN7MItMPCXz81ohxFZRoSe+p4jpvRm0hZGm/s1V3X00=;
Received: from 188.29.164.240.threembb.co.uk ([188.29.164.240] helo=[192.168.43.165]) by tranquility.default.cdelarrinaga.uk0.bigv.io with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from <cdel@firsthand.net>) id 1ioxfH-0007Uo-B5; Tue, 07 Jan 2020 22:49:31 +0000
To: Phillip Hallam-Baker <ietf@hallambaker.com>
Cc: "General Area Review Team (gen-art@ietf.org)" <art@ietf.org>, urn@ietf.org, The IESG <iesg@ietf.org>, IETF Discussion Mailing List <ietf@ietf.org>
References: <87E116C31DAF1434C3C3937F@PSB> <CAMm+Lwi5tWUNK5nO4d8qoum03fV-1bchfP_Qu3ktANgRDd-RVg@mail.gmail.com> <29803.1578413742@localhost> <CAMm+LwjFUfayeeHmWTRiGiCBz-+afBOnoXVcF1PxzMibS6t-Uw@mail.gmail.com>
From: Christian <cdel@firsthand.net>
Message-ID: <86e1f21b-b594-b390-fe67-c5f495cffa64@firsthand.net>
Date: Tue, 7 Jan 2020 22:49:29 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2
MIME-Version: 1.0
In-Reply-To: <CAMm+LwjFUfayeeHmWTRiGiCBz-+afBOnoXVcF1PxzMibS6t-Uw@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------279B353DDDBD3A4C1F8B6BB7"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/tDdqmbRG4wd21unNC5FnoNpntb0>
Subject: Re: [art] URNs and Last Call: <draft-nottingham-rfc7320bis-02.txt> (URI Design and Ownership) to Best Current Practice
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2020 22:49:39 -0000

This is a multi-part message in MIME format.
--------------279B353DDDBD3A4C1F8B6BB7
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

picking up as a post modern fag end...

On 07/01/2020 19:53, Phillip Hallam-Baker wrote:
> Resolution of many types of name is inherently ambiguous because the 
> context varies.. We cannot resolve a barcode on a physical object like 
> a can of beans. But we can ask for information on the can of beans and 
> we can order an instance of the can of beans for delivery. And both 
> forms of 'location' are going to be subjective and depend on the 
> context in which they are attempted.

I suppose the question is can a schema capture both identifier and 
locator contexts (my plural) unambiguously in all cases?

Should I take your post modernist interpretation as saying the answer is 
no - we have to live with ambiguity, even to the extent of the failure 
to resolve one or other or possibly both and do so without breaking wind?

But given this interpretation what language is needed if URI and URN 
linguistically don't meet the need?

Or is the other interpretation to offer a list of contexts that work and 
exclude application for the others?

In which case which is the more useful approach for building real world 
apps and their networks?

It rather kills the idea of hard coded registries for all eventualities 
I think. That I like. As I really like the import of post modernist 
sensibility. This argument is worth something.

best Christian


--------------279B353DDDBD3A4C1F8B6BB7
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>picking up as a post modern fag end... <br>
    </p>
    <div class="moz-cite-prefix">On 07/01/2020 19:53, Phillip
      Hallam-Baker wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAMm+LwjFUfayeeHmWTRiGiCBz-+afBOnoXVcF1PxzMibS6t-Uw@mail.gmail.com">
      <div class="moz-text-html" lang="x-unicode">
        <div dir="ltr">
          <div class="gmail_quote">
            <div class="gmail_default" style="font-size:small">Resolution
              of many types of name is inherently ambiguous because the
              context varies.. We cannot resolve a barcode on a physical
              object like a can of beans. But we can ask for information
              on the can of beans and we can order an instance of the
              can of beans for delivery. And both forms of 'location'
              are going to be subjective and depend on the context in
              which they are attempted.</div>
          </div>
        </div>
      </div>
    </blockquote>
    <p>I suppose the question is can a schema capture both identifier
      and locator contexts (my plural) unambiguously in all cases?</p>
    <p>Should I take your post modernist interpretation as saying the
      answer is no - we have to live with ambiguity, even to the extent
      of the failure to resolve one or other or possibly both and do so
      without breaking wind?</p>
    <p>But given this interpretation what language is needed if URI and
      URN linguistically don't meet the need?  <br>
    </p>
    <p>Or is the other interpretation to offer a list of contexts that
      work and exclude application for the others? <br>
    </p>
    <p>In which case which is the more useful approach for building real
      world apps and their networks? </p>
    <p>It rather kills the idea of hard coded registries for all
      eventualities I think. That I like. As I really like the import of
      post modernist sensibility. This argument is worth something. <br>
    </p>
    <p>best Christian<br>
    </p>
  </body>
</html>

--------------279B353DDDBD3A4C1F8B6BB7--


From nobody Tue Jan  7 15:50:55 2020
Return-Path: <masinter@gmail.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F530120220; Tue,  7 Jan 2020 15:50:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level: 
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 M-p5R1erC1Db; Tue,  7 Jan 2020 15:50:46 -0800 (PST)
Received: from mail-pj1-x102d.google.com (mail-pj1-x102d.google.com [IPv6:2607:f8b0:4864:20::102d]) (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 C9DDF12013C; Tue,  7 Jan 2020 15:50:46 -0800 (PST)
Received: by mail-pj1-x102d.google.com with SMTP id n59so264243pjb.1; Tue, 07 Jan 2020 15:50:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=sender:from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-transfer-encoding:thread-index :content-language; bh=DiIo7NMrRDey82VslgS7RqWDOXU/ANdYEskZ4LE+xj0=; b=WgdE6q9IrMy8uh5DxP9/FsDDSoq/T72KU4is7umg1DViJ31ObwQPtpRVPskknNEF7Y NZcaXMRty5Tc8T1Ot5G8ze6il1LJtW68qvCY3c8Md38yME+iuw/TZ8XSQcJabHAcG8Xy MgHeB3axrUwdfvTu7QauiJ/+S3sdlmka/wi1cRpiXFYsQ29541XhGSY29kYZbEOTKyLF d6mhywywHHhPc9muIAbOGuDbxP0SFjvQtH62+7H005uephMYlWm9ySk3QjDWh2ST8Pg2 odzMWZto7nWDRxPILzhIZ+rUlq5uLg1ZDVBISGrNE21YFPGyKDO643BijwRs6ldLrilX zH5A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:to:cc:references:in-reply-to:subject :date:message-id:mime-version:content-transfer-encoding:thread-index :content-language; bh=DiIo7NMrRDey82VslgS7RqWDOXU/ANdYEskZ4LE+xj0=; b=Updw1r5zGrR87yCXikt6KL9LAr68IQttyM1BxfHCblrbgIj5Rmc3MB3B/xOnAmvNVs IvdZ9V0bApTkrv6dRL9F77I4rx3HAHU6LSDcDPB1nkXJXvijpzW7BcBrXOEPMFxh5CXd GOz1lFwFZze5J4VuKHFSQgsa7rq8EsUdI/QsP+2ZgYlsZf9gTERl9U8v+xHc/SHVfqQU 6gRFSKf+3WA1cSqmlMjxT4sh7PEvke0ZvGET1ROh61AarN1XpFoCi+em9jrEHTk7N50z mj6OdVLYJmb7a+Kvd7C2+QspFOYVLqZsmwSvbObrW1bBxaQFzMGykCsk0ScM2kogoC9Y treQ==
X-Gm-Message-State: APjAAAV30FDSf/EXqJ0c8UFCnT1RfbKkJM/hE55ErjB8nq687E6xT0hr uqMdKx1wRlLKqRCo/7SjN/DnDt1HOUc=
X-Google-Smtp-Source: APXvYqwrP37wxzxYz1LLUlfLGi4QxfZPqL6XKJy/rpg9P9VJKkljSnwBKAxlfws0HiZpqMe89qMBgQ==
X-Received: by 2002:a17:902:b691:: with SMTP id c17mr2370243pls.254.1578441046082;  Tue, 07 Jan 2020 15:50:46 -0800 (PST)
Received: from TVPC (c-67-169-101-78.hsd1.ca.comcast.net. [67.169.101.78]) by smtp.gmail.com with ESMTPSA id n2sm832253pgn.71.2020.01.07.15.50.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 07 Jan 2020 15:50:45 -0800 (PST)
Sender: Larry Masinter <masinter@gmail.com>
From: Larry Masinter <LMM@acm.org>
X-Google-Original-From: "Larry Masinter" <lmm@acm.org>
To: "'John C Klensin'" <john-ietf@jck.com>, "'Adam Roach'" <adam@nostrum.com>,  <iesg@ietf.org>
Cc: <art@ietf.org>, <mnot@mnot.net>, <urn@ietf.org>, <ietf@ietf.org>
References: <87E116C31DAF1434C3C3937F@PSB> <a267e8d7-e88f-fe84-a3d4-eb12b88a46ad@nostrum.com> <444B2465A9B73F3D0DE59FFF@PSB>
In-Reply-To: <444B2465A9B73F3D0DE59FFF@PSB>
Date: Tue, 7 Jan 2020 15:50:43 -0800
Message-ID: <002b01d5c5b5$47227290$d56757b0$@acm.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQHlIqFVvsYjY3mX8ZSjZXIfuJ5VFQIu5gyCAc3WKQanoPwSoA==
Content-Language: en-us
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/pulWh_v5NlYBoRRCgxl8YHRH-M0>
Subject: Re: [art] URNs and Last Call: <draft-nottingham-rfc7320bis-02.txt> (URI Design and Ownership) to Best Current Practice
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2020 23:50:48 -0000

FWIW, while I agree with the "spirit of  making this BCP guidance, 
rather than rules", I don't see how changing "MAY" to "can"
or a "SHOULD NOT... but instead" to "are encouraged to"
is helpful (substituting terms that are well-defined with
words that seem to be similar in meaning but less well-defined.

The keywords MAY, SHOULD, SHOULD NOT seem to me
to be sufficient "guidance" in a BCP-status document.

Perhaps it would be helpful to add  a kind of applicability statement at the
beginning that these guidelines are intended to apply to
"http:" and "https:" URIs and those  with similar patterns
and SHOULD be considered for others, although they don't
 seem to be relevant for URI-schemes that don't use the generic syntax
with hierarchical paths  (such as "urn:" or "data:" or "mailto")

There is no need to consider the philosophic difference
between a name and a locator.

It's a matter of choosing a syntax for serialization of
a data structure and the implication of ownership
 and origin that comes with some syntactic arrangements
for some implementations.

Larry
-- 
https://LarryMasinter.net



From nobody Tue Jan  7 16:18:56 2020
Return-Path: <hallam@gmail.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 018CF120020; Tue,  7 Jan 2020 16:18:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.417
X-Spam-Level: 
X-Spam-Status: No, score=-1.417 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=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 eprzhI2QcRT4; Tue,  7 Jan 2020 16:18:43 -0800 (PST)
Received: from mail-ot1-f45.google.com (mail-ot1-f45.google.com [209.85.210.45]) (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 A0D21120018; Tue,  7 Jan 2020 16:18:43 -0800 (PST)
Received: by mail-ot1-f45.google.com with SMTP id w21so1872110otj.7; Tue, 07 Jan 2020 16:18:43 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=KsVsYPYLQE+I76X+hyia3u6/V4SaimYB4tgvgMkBFIg=; b=s+TzLfuLp7ERgKo6bxXmImLC7XCUPicw5hMjoYj8QqSj3WtSmruBY0PuyFd5aPFG3x tB7agE5NCN9yIWMcjYOcRbcq01khCR24F0ugOun+qsJmbbTgOKb2Qe6mPUHqFVI/2vkt RH+rivCqR3v78mTyE+lUWqXPxLhyk3b8i681vXQgxqxFMATGBcbaOyTyFUBlaDmbUNGM w+BjKyhzzogLCuyfkjVnTbsgbomqD9HM3x8Bt7qzagRna8F+7EbOTBaS/ArWXN4TbKTX zhlL7TyAUzdRNq6lO4faGFk8GCizKbGf5WTuLqpZRBXleSIj+PPMM5RjNOzPPLn4JYvv kamw==
X-Gm-Message-State: APjAAAWozV0ABXK6gVh5QPJOv806qUiYx66ZqvSnLLh/oh4470TRVloF hSeaCxjnntP4n9dQ5vOqzPwJdTMQ95MlL1jL256H/D+K
X-Google-Smtp-Source: APXvYqzK9pkdVgjhJ5NhspvQeo4oZHQcUrAy9DpjYmbl15A2HT0wXtwWMS5yCwjuu/1SBh5Cw0i07RRxjOsm67x+oNc=
X-Received: by 2002:a05:6830:1481:: with SMTP id s1mr2229466otq.66.1578442722735;  Tue, 07 Jan 2020 16:18:42 -0800 (PST)
MIME-Version: 1.0
References: <87E116C31DAF1434C3C3937F@PSB> <CAMm+Lwi5tWUNK5nO4d8qoum03fV-1bchfP_Qu3ktANgRDd-RVg@mail.gmail.com> <29803.1578413742@localhost> <CAMm+LwjFUfayeeHmWTRiGiCBz-+afBOnoXVcF1PxzMibS6t-Uw@mail.gmail.com> <86e1f21b-b594-b390-fe67-c5f495cffa64@firsthand.net>
In-Reply-To: <86e1f21b-b594-b390-fe67-c5f495cffa64@firsthand.net>
From: Phillip Hallam-Baker <ietf@hallambaker.com>
Date: Tue, 7 Jan 2020 19:18:31 -0500
Message-ID: <CAMm+Lwg2K-9Hjuu+jh-gR59iMSMqg5=Doms3j4rDoK_YqjD3ZA@mail.gmail.com>
To: Christian <cdel@firsthand.net>
Cc: "General Area Review Team (gen-art@ietf.org)" <art@ietf.org>, urn@ietf.org, The IESG <iesg@ietf.org>, IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c97be0059b95d5ad"
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/vkJc0I4hPW6amyZcoLuP9uO9TAQ>
Subject: Re: [art] URNs and Last Call: <draft-nottingham-rfc7320bis-02.txt> (URI Design and Ownership) to Best Current Practice
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jan 2020 00:18:45 -0000

--000000000000c97be0059b95d5ad
Content-Type: text/plain; charset="UTF-8"

On Tue, Jan 7, 2020 at 5:49 PM Christian <cdel@firsthand.net> wrote:

> picking up as a post modern fag end...
> On 07/01/2020 19:53, Phillip Hallam-Baker wrote:
>
> Resolution of many types of name is inherently ambiguous because the
> context varies.. We cannot resolve a barcode on a physical object like a
> can of beans. But we can ask for information on the can of beans and we can
> order an instance of the can of beans for delivery. And both forms of
> 'location' are going to be subjective and depend on the context in which
> they are attempted.
>
> I suppose the question is can a schema capture both identifier and locator
> contexts (my plural) unambiguously in all cases?
>
Definitely not because the identifier interpretation can change over time.
Additional contexts can be added. The identifier may be grandfathered into
a new scheme. It may be abandoned.

> Should I take your post modernist interpretation as saying the answer is
> no - we have to live with ambiguity, even to the extent of the failure to
> resolve one or other or possibly both and do so without breaking wind?
>
We can deny that the ambiguity exists. We can say the earth is flat as
well. But it won't change anything.

> But given this interpretation what language is needed if URI and URN
> linguistically don't meet the need?
>
> Or is the other interpretation to offer a list of contexts that work and
> exclude application for the others?
>
> In which case which is the more useful approach for building real world
> apps and their networks?
>
I believe that the Internet was founded on the principle of allowing every
user to experiment and to extend. It is thus impossible to enumerate all
possible uses. It is however possible to identify uses that are useful
generally and network effects strongly (unfortunately too strongly)
encourage focusing on common uses.

> It rather kills the idea of hard coded registries for all eventualities I
> think. That I like. As I really like the import of post modernist
> sensibility. This argument is worth something.
>
> best Christian
>

--000000000000c97be0059b95d5ad
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"fon=
t-size:small"><br></div></div><br><div class=3D"gmail_quote"><div dir=3D"lt=
r" class=3D"gmail_attr">On Tue, Jan 7, 2020 at 5:49 PM Christian &lt;<a hre=
f=3D"mailto:cdel@firsthand.net">cdel@firsthand.net</a>&gt; wrote:<br></div>=
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
 =20
   =20
 =20
  <div>
    <p>picking up as a post modern fag end... <br>
    </p>
    <div>On 07/01/2020 19:53, Phillip
      Hallam-Baker wrote:<br>
    </div>
    <blockquote type=3D"cite">
      <div lang=3D"x-unicode">
        <div dir=3D"ltr">
          <div class=3D"gmail_quote">
            <div style=3D"font-size:small">Resolution
              of many types of name is inherently ambiguous because the
              context varies.. We cannot resolve a barcode on a physical
              object like a can of beans. But we can ask for information
              on the can of beans and we can order an instance of the
              can of beans for delivery. And both forms of &#39;location&#3=
9;
              are going to be subjective and depend on the context in
              which they are attempted.</div>
          </div>
        </div>
      </div>
    </blockquote>
    <p>I suppose the question is can a schema capture both identifier
      and locator contexts (my plural) unambiguously in all cases?</p></div=
></blockquote><div><div class=3D"gmail_default" style=3D"font-size:small">D=
efinitely not because the identifier interpretation can change over time. A=
dditional contexts can be added. The identifier may be grandfathered into a=
 new scheme. It may be abandoned.</div></div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204=
);padding-left:1ex"><div>
    <p>Should I take your post modernist interpretation as saying the
      answer is no - we have to live with ambiguity, even to the extent
      of the failure to resolve one or other or possibly both and do so
      without breaking wind?</p></div></blockquote><div><div class=3D"gmail=
_default" style=3D"font-size:small">We can deny that the ambiguity exists. =
We can say the earth is flat as well. But it won&#39;t change anything.=C2=
=A0</div></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0p=
x 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
    <p>But given this interpretation what language is needed if URI and
      URN linguistically don&#39;t meet the need?=C2=A0 <br>
    </p>
    <p>Or is the other interpretation to offer a list of contexts that
      work and exclude application for the others? <br>
    </p>
    <p>In which case which is the more useful approach for building real
      world apps and their networks?=C2=A0</p></div></blockquote><div><div =
class=3D"gmail_default" style=3D"font-size:small">I believe that the Intern=
et was founded on the principle of allowing every user to experiment and to=
 extend. It is thus impossible to enumerate all possible uses. It is howeve=
r possible to identify uses that are useful generally and network effects s=
trongly (unfortunately too strongly) encourage focusing on common uses.</di=
v></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex=
;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
    <p>It rather kills the idea of hard coded registries for all
      eventualities I think. That I like. As I really like the import of
      post modernist sensibility. This argument is worth something. <br>
    </p>
    <p>best Christian<br>
    </p>
  </div>

</blockquote></div></div>

--000000000000c97be0059b95d5ad--


From nobody Tue Jan  7 16:31:07 2020
Return-Path: <stpeter@mozilla.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44DF4120018 for <art@ietfa.amsl.com>; Tue,  7 Jan 2020 16:31:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mozilla.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 H9f5yJGVpSoC for <art@ietfa.amsl.com>; Tue,  7 Jan 2020 16:31:03 -0800 (PST)
Received: from mail-io1-xd35.google.com (mail-io1-xd35.google.com [IPv6:2607:f8b0:4864:20::d35]) (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 427051200E7 for <art@ietf.org>; Tue,  7 Jan 2020 16:31:03 -0800 (PST)
Received: by mail-io1-xd35.google.com with SMTP id n21so1290428ioo.10 for <art@ietf.org>; Tue, 07 Jan 2020 16:31:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mozilla.com; s=google;  h=subject:to:cc:references:from:openpgp:autocrypt:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=GEmqktg5R6YlC/lTNgD0xWDOxoKsEXTtJtguhv3Lphg=; b=M23p7xZoHcSzvfaRoMklcm2lLX0MJFarEppfvTJNEWiOAxazkqK4PGFCS6AgWjzb18 uvI67mwhOxx8dSuq4Waz+6TmMZO7N8U8C5Xbw24hyPoKedu6PuAKeNmRrnhDb3RgZHnK y1lfDuoAsp1IIVESUO64sKovA74fdZKx13630=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:openpgp:autocrypt :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=GEmqktg5R6YlC/lTNgD0xWDOxoKsEXTtJtguhv3Lphg=; b=LBuL276RN6CnR1HYp/zBTHsqjPjWTMlj2MtSKaZ8EcHOpIm/G8xBn3KMZsdO2CR/Di eZIzETLCtTRX0e9q1rGWvI5xeDei5zDr7cbRe+d68Z3+8IJduawu0e++cSNEu2ro8rS0 uJQSvGGjjKJFP3priGKedBsK+LqXCUmebibWlO4fst5Ab1X79YWcJHxF+PYeSpvrGeJW UfdsDhSeISTqV1LnSqNAsPsEZFBqS3tDwe7nODBlfE8auwk9RTubyMcxQi/a+LaMeMN6 XAf44ufMKgasHjHVvi6jiL9s3GeXmebL0/jQ2V6xuPk5EDFL6q1ZPkbcC+w8mXQF1zwM jy7w==
X-Gm-Message-State: APjAAAX8P4LwT/gsFks1q12/RzpC527d+cdEzc09t3hpEPi0vx/5jDmD m5hlTi8IBawDDSuW4xgzqcHjNg==
X-Google-Smtp-Source: APXvYqzp5quT3VRoz26zX84/B/mFs8sjjqA3VG/HXAi+dXbzPNFii9KHriFxYRUZGvd25w1XJ4DJ+w==
X-Received: by 2002:a5d:8901:: with SMTP id b1mr1304834ion.246.1578443462391;  Tue, 07 Jan 2020 16:31:02 -0800 (PST)
Received: from dragon.local ([76.25.3.152]) by smtp.gmail.com with ESMTPSA id y18sm393992ilm.9.2020.01.07.16.31.01 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 07 Jan 2020 16:31:01 -0800 (PST)
To: John C Klensin <john-ietf@jck.com>, Adam Roach <adam@nostrum.com>, iesg@ietf.org
Cc: art@ietf.org, mnot@mnot.net, urn@ietf.org, ietf@ietf.org
References: <87E116C31DAF1434C3C3937F@PSB> <a267e8d7-e88f-fe84-a3d4-eb12b88a46ad@nostrum.com> <444B2465A9B73F3D0DE59FFF@PSB>
From: Peter Saint-Andre <stpeter@mozilla.com>
Openpgp: preference=signencrypt
Autocrypt: addr=stpeter@mozilla.com; prefer-encrypt=mutual; keydata= mQINBFonEf4BEADvZ+RGsJoOyZaw2rKedB9pBb2nNXVGgymNS9+FAL/9SsfcrKaGYSiWEz7P Lvc97hWH3LACFAHvnzoktv+4IWHjItvhdi9kUQ3Gcbahe55OcdZuSXXH3w5cHF0rKz9aYRpN jENqXM5dA8x4zIymJraqYvHlFsuuPB8rcRIV9SKsvcy14w9iRqu770NjXfE/aIsyRwwmTPiU FQ0fOSDPA/x2DLjed/GYHem90C5vF4Er9InMqH5KAMLnjIYZ9DbPx5c5EME4zW/d648HOvPB bm+roZs4JTHBhjlrTtzDDpMcxHq1e8YPvSdDLPvgFXDcTD4+ztkdO5rvDkbc61QFcLlidU8H 3KBiOVMA/5Rgl4lcWZzGfJBnwvSrKVPsxzpuCYDg01Y/7TH4AuVkv5Na6jKymJegjxEuJUNw CBzAhxOb0H9dXROkvxnRdYS9f0slcNDBrq/9h9dIBOqLhoIvhu+Bhz6L/NP5VunQWsEleGaO 3gxGh9PP/LMyjweDjPz74+7pbyOW0b5VnIDFcvCTJKP0sBJjRU/uqmQ25ckozuYrml0kqVGp EfxhSKVqCFoAS4Q7ux99yT4re2X1kmlHh3xntzmOaRpcZsS8mJEnVyhJZBMOhqE280m80ZbS CYghd2K0EIuRbexd+lfdjZ+t8ROMMdW5L51CJVigF0anyYTcAwARAQABtCdQZXRlciBTYWlu dC1BbmRyZSA8c3RwZXRlckBtb3ppbGxhLmNvbT6JAlQEEwEIAD4WIQQ1VSPTuPTvyWCdvvRl YYwYf2gUqQUCWicR/gIbIwUJCWYBgAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRBlYYwY f2gUqdaREAChG8qU1853mP0sv2Mersns8TLG1ztgoKHvMXFlMUpNz6Oi6CjjaMNFhP7eUY4T D43+yQs7f4qCkOAPWuuqO8FbNWQ+yUoVkqF8NUrrVkZUlZ1VZBMQHNlaEwwu1CGoHsLoRohP SiZ0hpmGTWB3V6cDDK4KN6nl610WJbzE9LeKY1AxtePdJi2KM281U0Fz8ntij1jWu0gF2xU4 Sez46JDogHLWKgd0srauhcCVzZjAhiWrXp1+ryzSWYaZO8Kh8SnF1f4o6jtYikMqkxUaI5nX wvD3kNX4AMSkCAZfG7Jcfj/SLDojTcREgO87g7B9bcOOsHN4lj3lHoFV0aXpgPmjfIvAjJHu fHkXZAQAH8w0u9bgJqRn703+A4NPfLopnjegyhlNi7fQ3cMQV1H7Oj7WrB/pCcprx+1u/6Uq oTtDwWh1U5uVthVAI0QojpNWR08zABDX19TlGtVoeygaQV3CAEolxTiYQtCfVavUzUplCZ/t 3v4YiRov+NylflJd+1akyOs1IAgARf444BnoH1fotkpfXNOpp9wUXXwsQcFRdP7vpMkSCkc0 sxPNTVX3ei0QImp4NsrFdaep7LV3zEb3wkAp6KE5Qno4hVVEypULbvB0G6twNZbeRfcs2Rjp jnPb2fofvg2WhAKB20dnRfIfK8OKTD/P+JDcauJANjmekLkCDQRaJxH+ARAApPwkbOTChAQu jMvteb/xcwuL5JZElmLxIqvJhqybV7JknM+3ATyN0CTYQFvPTgIrhpk4zSn0A6pEePdK8mKK 5/aHyd7pr7rLEi1sI/X3UE8ld/E83MExksKrYbs0UX1wSQwYXU6g64KicnuP2Abqg+8wrQ18 1nPcZci9jJI75XVPnTdUpZD5aaQWGp7IJ06NTbiOk30I50ORfulgKoe4m3UfsMALFxIx3pJk oy76xC2tjxYGf+4Uq1M0iK3Wy655GrcwXq/5ieODNUcAZzvK5hsUVRodBq0Lq3g1ivQF4ba7 RQayDzlW6XgoeU49xnCr9XdZYnTnj4iaPmr2NtY6AacBwRz+bJsyugeSyGgHsnVGyUSMk8YN wZHvUykMjH21LLzIUX5NFlcumLUXDOECELCJwewui4W81sI5Sq/WDJet+iJwwylUX22TSulG VwDS+j66TLZpk1hEwPanGLwFBSosafqSNBMDVWegKWvZZVyoNHIaaQbrTIoAwuAGvdVncSQz ttC6KkaFlAtlZt3+eUFWlMUOQ9jxQKTWymyliWKrx+S6O1cr4hwVRbg7RQkpfA8E2Loa13oO vRSQy/M2YBRZzRecTKY6nslJo6FWTftpGO7cNcvbmQ6I++5cBG1B1eNy2RFGJUzGh1vlYo51 pdfSg0U1oPHBPCHNvPYCJ7UAEQEAAYkCPAQYAQgAJhYhBDVVI9O49O/JYJ2+9GVhjBh/aBSp BQJaJxH+AhsMBQkJZgGAAAoJEGVhjBh/aBSpAw0P/1tEcEaZUO1uLenNtqysi3mQ6qAHYALR Df3p2z/RBKRVx0DJlzDfDvJ2R/GRwoo+vyCviecuG2RNKmJbf1vSm/QTtbQMUjwut9mx6KCY CyKwniqdhaMBmjCfV2DB2MxxZLYMtDfx/2mY7vzAci7AkjC+RkSUByMEOkyscUydKC/ETdf9 tvI8GhTY/8Q7JSylS3lQA5pMUHiIf+KpSmqKZeBPkGc7nSKM1w1UKUvFAsyyVsiG6A/hWrTr 7tTQAl7YfjtOGE8n4IKGktvrT99bbh9wdWKZ5FdHUN9hx2Q8VP8+0lR1CH2laVFbEwCOv1vM W4cgQDLxwwpo1iOTdHBVtQDxlQ9hPMKVlB1KP9KjchxuiLc24wLmCjP3pDMml4LQxOYB34Eq cgPZ3uHvJZG309sb2wTMTWaXobWNI++ZrsRD5GTmuzF3kkx3krtrq6HI5NSaemxK6MTDTjDN Rj/OwTl0yU35eJXuuryB20GFOSUsxiw00I2hMGQ1Cy9L/+IW6Dvotd8O3LmKh2tFArzXaKLx /rZyGNurS/Go5YjHp8wdJOs7Ka2p1U31js24PMWO6hf6hIiY2WRUsnE6xZNhvBTgKOY6u0KT V6hTevFqEw7OAZDCWUoE2Ob2/oHGZCCMW5SLAMgp7eihF0kGf2S2CmpIFYXGb61hAD8SqSY7 Fn7V
Message-ID: <f082480f-d114-4c97-5c54-4caeebe66acd@mozilla.com>
Date: Tue, 7 Jan 2020 17:31:00 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <444B2465A9B73F3D0DE59FFF@PSB>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/qg7ZheAGMAOn_GxqJmz2Y4TdJuM>
Subject: Re: [art] URNs and Last Call: <draft-nottingham-rfc7320bis-02.txt> (URI Design and Ownership) to Best Current Practice
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jan 2020 00:31:05 -0000

On 1/7/20 12:11 PM, John C Klensin wrote:

> Instead, I was trying to raise a far more narrow question: Given
> that RFC 3986 separates names and locators and that we have
> already had confusion about what is appropriate in URNs based on
> the language there, does this document make things worse?  I
> think it may.  Even a statement fragment (from the first
> paragraph of Section 3 and inherited from 7320) like "...as
> links that are exchanged as part of the protocol, rather than
> statically specified syntax" are inconsistent with the use of
> keyword values in some URN namespaces as static indicators. 

Indeed, it's not immediately obvious what a "protocol" would be in the
case of many URN namespaces, precisely because the URN is a name rather
than a locator.

> If
> you want to ask the slightly different question of whether, if
> RFC 7320 made things worse, does this I-D make things even worse
> than that, I don't have an easy answer except to note at least
> one example: The last paragraph of Section 2.3, which appears to
> be new, says
> 
>> Extensions MUST NOT define a structure within individual URI
>> components (e.g., a prefix or suffix), again to avoid
>> collisions and erroneous client assumptions.
> 
> But, as I understand that rule, it is precisely what some rules,
> and provisions for namespace-specific rules, in RFC 8141, do.

It's not clear to me whether a URN namespace counts as a 7320bis
protocol extension (which can "offer new capabilities that could apply
to any identifier, or to a large subset of possible identifiers");
however a definition of, say, URN r-components would probably fit the
bill, and such a definition might well define structures that would
violate the aforementioned MUST NOT.

> Again, the solution at this point appears to be either to be
> much more careful about binding the statements in the I-D to the
> concept of ownership or to indication that this specification
> does not apply to URNs (or, if preferred, to what 3986 describes
> as "name" URIs) at all.

That might be the best approach.

Peter


From nobody Tue Jan  7 17:30:32 2020
Return-Path: <sm@elandsys.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53160120077 for <art@ietfa.amsl.com>; Tue,  7 Jan 2020 17:30:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.697
X-Spam-Level: 
X-Spam-Status: No, score=-1.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.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 T5qLz56TZ89B for <art@ietfa.amsl.com>; Tue,  7 Jan 2020 17:30:30 -0800 (PST)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id 4C3E8120018 for <art@ietf.org>; Tue,  7 Jan 2020 17:30:30 -0800 (PST)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.116.59.4]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 0081UG0T024080 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 7 Jan 2020 17:30:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1578447029; x=1578533429; i=@elandsys.com; bh=rcabrE1w3f252YiU3n4nNMGe9z1/yK/gWYy0Tmynky8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=k/Bu21b9IvRayp72RHk9b3Hy3Rk1EZ5yYxT5uklVBnt7jdk/emzSdIbqXuyq0AzOQ xb2Lr8eHJEKozTbbtjBQvIqu+YEeGxIufYUOMBXlENGnRYZeJMRznTeg5XzlS8rGFD oKN7uXjNwZtj9SqffVXl5kC9nX+n4B0wSrG8pNCc=
Message-Id: <6.2.5.6.2.20200107163256.0f2810b8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 07 Jan 2020 17:26:07 -0800
To: Adam Roach <adam@nostrum.com>, Mark Nottingham <mnot@mnot.net>
From: S Moonesamy <sm+ietf@elandsys.com>
Cc: art@ietf.org
In-Reply-To: <a267e8d7-e88f-fe84-a3d4-eb12b88a46ad@nostrum.com>
References: <87E116C31DAF1434C3C3937F@PSB> <a267e8d7-e88f-fe84-a3d4-eb12b88a46ad@nostrum.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/ewPVbE5l_XskGR26qsb8qX6QfWM>
Subject: Re: [art] URNs and Last Call: <draft-nottingham-rfc7320bis-02.txt> (URI Design and Ownership) to Best Current Practice
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jan 2020 01:30:31 -0000

Hi Adam, Mark,
At 08:35 AM 07-01-2020, Adam Roach wrote:
>To help with framing this conversation, the changes from RFC 7320 
>are highlighted here:
>
>https://www.ietf.org/rfcdiff?url1=rfc7320&url2=draft-nottingham-rfc7320bis-03
>
>I have some rather extensive thoughts on the process of creating bis 
>documents [1].

I was going to comment about the document as there was an 
announcement about it.  After reading your note I wondered whether it 
was worthwhile to comment if I have to restrict my comments to what 
was changed since RFC 7302.  For what it is worth, I have very little 
interest in getting into a lengthy discussion about URNs v/s URIs.

There are some design considerations in Section 1.2 of RFC 3986, 
which is an Internet Standard.  Section 2 of the draft states that 
the section is doing an update by "advising Specifications".  First 
of all, it is convoluted when an Internet Standard is being updated 
by a "BCP".  Secondly, it does not make sense to advise 
specifications as one generally provides advise to people instead of, 
for example, RFCs.

The example in Section 2.2 references RFC 1034 for the "authority 
component" whereas RFC 3986 references RFC 1034 and RFC 1123.   Is 
Section 3.2.2 of RFC 3986 being updated and replaced by what is in this draft?

Regards,
S. Moonesamy 


From nobody Tue Jan  7 18:07:28 2020
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: art@ietf.org
Delivered-To: art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D33BC12007C; Tue,  7 Jan 2020 18:07:25 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <art@ietf.org>, <draft-nottingham-rfc7320bis@ietf.org>, <adam@nostrum.com>, <mt@lowentropy.net>, <mt@mozilla.com>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.115.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <157844924586.25245.2924601796385452074.idtracker@ietfa.amsl.com>
Date: Tue, 07 Jan 2020 18:07:25 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/lK4PZtHPs8w0MwBqEOg6BkO_ybo>
Subject: [art] Datatracker State Update Notice: <draft-nottingham-rfc7320bis-03.txt>
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jan 2020 02:07:26 -0000

IANA review state changed to "IANA OK - No Actions Needed"
Datatracker URL: https://datatracker.ietf.org/doc/draft-nottingham-rfc7320bis/


From nobody Tue Jan  7 21:08:50 2020
Return-Path: <john-ietf@jck.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57E20120041; Tue,  7 Jan 2020 21:08:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 dwM6zHv61ByI; Tue,  7 Jan 2020 21:08:47 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BCA8B120025; Tue,  7 Jan 2020 21:08:47 -0800 (PST)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1ip3aC-000A6x-Tu; Wed, 08 Jan 2020 00:08:40 -0500
Date: Wed, 08 Jan 2020 00:08:34 -0500
From: John C Klensin <john-ietf@jck.com>
To: Peter Saint-Andre <stpeter@mozilla.com>, Adam Roach <adam@nostrum.com>, iesg@ietf.org
cc: art@ietf.org, mnot@mnot.net, urn@ietf.org, ietf@ietf.org
Message-ID: <83F6216862324B84D43C9280@PSB>
In-Reply-To: <f082480f-d114-4c97-5c54-4caeebe66acd@mozilla.com>
References: <87E116C31DAF1434C3C3937F@PSB> <a267e8d7-e88f-fe84-a3d4-eb12b88a46ad@nostrum.com> <444B2465A9B73F3D0DE59FFF@PSB> <f082480f-d114-4c97-5c54-4caeebe66acd@mozilla.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/ParjA7Gpx99tNE6Bo1TfzR2PEtE>
Subject: Re: [art] URNs and Last Call: <draft-nottingham-rfc7320bis-02.txt> (URI Design and Ownership) to Best Current Practice
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jan 2020 05:08:50 -0000

--On Tuesday, January 7, 2020 17:31 -0700 Peter Saint-Andre
<stpeter@mozilla.com> wrote:

>...
>> If
>> you want to ask the slightly different question of whether, if
>> RFC 7320 made things worse, does this I-D make things even
>> worse than that, I don't have an easy answer except to note
>> at least one example: The last paragraph of Section 2.3,
>> which appears to be new, says
>> 
>>> Extensions MUST NOT define a structure within individual URI
>>> components (e.g., a prefix or suffix), again to avoid
>>> collisions and erroneous client assumptions.
>> 
>> But, as I understand that rule, it is precisely what some
>> rules, and provisions for namespace-specific rules, in RFC
>> 8141, do.
> 
> It's not clear to me whether a URN namespace counts as a
> 7320bis protocol extension (which can "offer new capabilities
> that could apply to any identifier, or to a large subset of
> possible identifiers"); however a definition of, say, URN
> r-components would probably fit the bill, and such a
> definition might well define structures that would violate the
> aforementioned MUST NOT.

I was trying to avoid getting dragged down into details, both in
the hope of keeping the message as short as possible and to
avoid a distracting side-discussion, but, yes r-components and
the issues associated with pass-through information for those
URN namespaces that resolve to one or more URLs were examples
that crossed my mind.

>> Again, the solution at this point appears to be either to be
>> much more careful about binding the statements in the I-D to
>> the concept of ownership or to indication that this
>> specification does not apply to URNs (or, if preferred, to
>> what 3986 describes as "name" URIs) at all.
> 
> That might be the best approach.

If we don't want both the discussion and the document to drag
out, I believe so.

best,
   john


From nobody Wed Jan  8 10:11:33 2020
Return-Path: <adam@nostrum.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79567120059 for <art@ietfa.amsl.com>; Wed,  8 Jan 2020 10:11:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.98
X-Spam-Level: 
X-Spam-Status: No, score=-1.98 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.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 ZHuEs4mV6i0W for <art@ietfa.amsl.com>; Wed,  8 Jan 2020 10:11:30 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 4AF39120019 for <art@ietf.org>; Wed,  8 Jan 2020 10:11:30 -0800 (PST)
Received: from Svantevit.local (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id 008IBFVC017925 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 8 Jan 2020 12:11:16 -0600 (CST) (envelope-from adam@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1578507078; bh=RK80AGRZNq2ufeZNbqvgAjTwv0aETAn4Oz87fLgj7Ro=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=pu6q/oLCHCGAEH6X/xJGosCusGv8OV7qfiYhhY+GYuh2oooUFLlLnVwTfBl1euDgE fD+4xyUWPqA510GdgQihqyFydRnET1UBR0TnfoE8OqmwTb2Owc4KFobhDxDD39MT2e 5O218/rTsQr5KnsQIy8sa6P6RTqMgFKPAc87EKIE=
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be Svantevit.local
To: S Moonesamy <sm+ietf@elandsys.com>, Mark Nottingham <mnot@mnot.net>
Cc: art@ietf.org
References: <87E116C31DAF1434C3C3937F@PSB> <a267e8d7-e88f-fe84-a3d4-eb12b88a46ad@nostrum.com> <6.2.5.6.2.20200107163256.0f2810b8@elandnews.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <9eda86bf-a31d-a45f-ac8c-98cb7f38e9d1@nostrum.com>
Date: Wed, 8 Jan 2020 12:11:10 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <6.2.5.6.2.20200107163256.0f2810b8@elandnews.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/9vLaVe7X5siI6FMwDL5VObSQ1K4>
Subject: Re: [art] URNs and Last Call: <draft-nottingham-rfc7320bis-02.txt> (URI Design and Ownership) to Best Current Practice
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jan 2020 18:11:31 -0000

On 1/7/20 7:26 PM, S Moonesamy wrote:
> I was going to comment about the document as there was an announcement 
> about it.  After reading your note I wondered whether it was 
> worthwhile to comment if I have to restrict my comments to what was 
> changed since RFC 7302.


To be clear, what I posted is my personal opinion (as are the following 
two paragraphs), and isn't an official IESG position, much less an IETF 
consensus position. Nothing in the process prevents you from commenting 
on whatever you want.

That said, I think it is a bad idea to slow down or stop improvements to 
a document by asking for unrelated and possibly contentious changes, 
especially at (or, to be honest, somewhat after) the last minute. The 
IETF has a long history of letting "perfect" become the enemy of "good," 
leading to author frustration, participant fatigue, and very long delays 
in publication.

For further clarity: I think it would be completely reasonable to turn 
around and propose yet another bis version of BCP 190 to fix any further 
perceived defects as soon as this version is published, and then work 
towards building consensus that such changes are required. The changes 
in the current bis are needed to address a demonstrable and ongoing 
problem. It seems imprudent to delay needed tactical changes based on 
last-minute musings about what else might be changed.

/a


From nobody Wed Jan  8 18:22:42 2020
Return-Path: <sm@elandsys.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4983E120142 for <art@ietfa.amsl.com>; Wed,  8 Jan 2020 18:22:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.698
X-Spam-Level: 
X-Spam-Status: No, score=-1.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.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 DftbAkpG4HOs for <art@ietfa.amsl.com>; Wed,  8 Jan 2020 18:22:39 -0800 (PST)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id 638E7120020 for <art@ietf.org>; Wed,  8 Jan 2020 18:22:39 -0800 (PST)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.115.142.251]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 0092MPkQ022005 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 8 Jan 2020 18:22:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1578536556; x=1578622956; i=@elandsys.com; bh=1OlXD1W2tCNXsXxEO27nNDYfh6rkLN/+CUGqwEigX8A=; h=Date:To:From:Subject:In-Reply-To:References; b=eqwU4q/FVBN2+2rzQCggEaHtkNsgi9oa4Cc+gG1m+h0JDy4J7h/G1uRPFe+RX8xjE B1vm65jRoc58F9rWcz3r+RHjSv96hglRze757Ehwq40ij2HfXDvkZlda0+QCVOmqrO 10/YFkOKDSpbyFU/IjWBcb5TaVJjOOeT86LYLlDM=
Message-Id: <6.2.5.6.2.20200108174717.08105d68@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 08 Jan 2020 18:21:55 -0800
To: Adam Roach <adam@nostrum.com>, art@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <9eda86bf-a31d-a45f-ac8c-98cb7f38e9d1@nostrum.com>
References: <87E116C31DAF1434C3C3937F@PSB> <a267e8d7-e88f-fe84-a3d4-eb12b88a46ad@nostrum.com> <6.2.5.6.2.20200107163256.0f2810b8@elandnews.com> <9eda86bf-a31d-a45f-ac8c-98cb7f38e9d1@nostrum.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/oR-39yJ2ZZ1Y2FEFlYFfwNwMnSE>
Subject: Re: [art] URNs and Last Call: <draft-nottingham-rfc7320bis-02.txt> (URI Design and Ownership) to Best Current Practice
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2020 02:22:40 -0000

Hi Adam,
At 10:11 AM 08-01-2020, Adam Roach wrote:
>To be clear, what I posted is my personal opinion (as are the 
>following two paragraphs), and isn't an official IESG position, much 
>less an IETF consensus position. Nothing in the process prevents you 
>from commenting on whatever you want.
>
>That said, I think it is a bad idea to slow down or stop 
>improvements to a document by asking for unrelated and possibly 
>contentious changes, especially at (or, to be honest, somewhat 
>after) the last minute. The IETF has a long history of letting 
>"perfect" become the enemy of "good," leading to author frustration, 
>participant fatigue, and very long delays in publication.

I didn't understand why the above referred to the comments being sent 
at the last minute.  After reading the Last Call announcement again I 
would not disagree that the comments were sent after the last 
minute.  I'd say that it is okay to ignore them as the purpose of 
sending the comments was neither to cause author/participant 
frustration or fatigue nor to delay publication of this draft.

Regards,
S. Moonesamy 


From nobody Wed Jan  8 19:47:44 2020
Return-Path: <worley@alum.mit.edu>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE91E120020 for <art@ietfa.amsl.com>; Wed,  8 Jan 2020 19:47:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.984
X-Spam-Level: 
X-Spam-Status: No, score=-0.984 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcastmailservice.net
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 w_OLaFz2FW2e for <art@ietfa.amsl.com>; Wed,  8 Jan 2020 19:47:38 -0800 (PST)
Received: from resqmta-ch2-06v.sys.comcast.net (resqmta-ch2-06v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F76A120142 for <art@ietf.org>; Wed,  8 Jan 2020 19:47:37 -0800 (PST)
Received: from resomta-ch2-08v.sys.comcast.net ([69.252.207.104]) by resqmta-ch2-06v.sys.comcast.net with ESMTP id pOmHiaBcqL7xwpOnJiiXy5; Thu, 09 Jan 2020 03:47:37 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20180828_2048; t=1578541657; bh=LIk+nGUmj9dsh+ZllqFYe2TKFOBNhhqyibgS4JuJ380=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=nzQdVTsGw34UvXcpjAEd8fpYic9TXsV+DjVA8zz5phn2aajczQ18kl7OQjGX/96O2 So7P4oyi4KsFTFjbb+hvhp9kHEJjvaUCafuuB0Y6oTcEko/ZXKuFAyclkQ9ynEXHvr SxGLG14oXjC8iRNwOSS5xJg+trHAs+61COpkfXxsySGD9BtLt2MYLjY9A3TlWCCSIr OkDwV5fJEeBRAEghU6x2KyfW9N/vxCzRNV5riRoikI+PvTsafHms57F9AgBXGBstW6 T91y3nXU9fVOEKPVfinYhU+lZXqNtc5Yc7ajOjcFnBe78hc5DfBPZg4aUXtCU5DOuv T9jSp2ycN+5OA==
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4600:1e00:222:fbff:fe91:d396]) by resomta-ch2-08v.sys.comcast.net with ESMTPA id pOnHim3Bday2upOnIiO4Wu; Thu, 09 Jan 2020 03:47:36 +0000
X-Xfinity-VMeta: sc=0.00;st=legit
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id 0093lY5M014578; Wed, 8 Jan 2020 22:47:34 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id 0093lYv6014573; Wed, 8 Jan 2020 22:47:34 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: art@ietf.org, mnot@mnot.net, urn@ietf.org
In-Reply-To: <87E116C31DAF1434C3C3937F@PSB> (john-ietf@jck.com)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Wed, 08 Jan 2020 22:47:33 -0500
Message-ID: <874kx58f56.fsf@hobgoblin.ariadne.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/VEximaMEo9CGqLp9nZ8VX8jhM-8>
Subject: Re: [art] URNs and Last Call: <draft-nottingham-rfc7320bis-02.txt> (URI Design and Ownership) to Best Current Practice
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2020 03:47:42 -0000

I am surprised to read a document that is marked "best current practice"
but filled with MUST and MUST NOT specifications.  I expect "best
current practice" to be advisory.  However, perhaps I am not
understanding the IETF use of BCP.  But this document does claim the
right to override any existing RFC, which seems to be excessive unless
the document receives very wide vetting and approval:

   There may be existing IETF specifications that already deviate from
   the guidance in this document.  In these cases, it is up to the
   relevant communities (i.e., those of the URI scheme as well as that
   which produced the specification in question) to determine an
   appropriate outcome; e.g., updating the scheme definition, or
   changing the specification.

As a nit, there is a reference to "BCP115":

   [BCP115]   Hansen, T., Hardie, T., and L. Masinter, "Guidelines and
              Registration Procedures for New URI Schemes", BCP 115,
              RFC 4395, February 2006,
              <https://tools.ietf.org/html/bcp115>.

but my copy of bcp-index.txt says:

0115 [BCP number 115 is retired. It was mistakenly assigned to RFC
     4395. RFC 4395 is BCP 35.]

And I think the name/locator distinction is easy to overemphasize.  It
is often useful, but instead of trying to hammer all applications into a
single theoretical structure separating "names" and "locators", it's
less error-prone and more useful to examine each instance of the
distinction individually in the context within which it will operate, at
which point all sorts of knotty theoretical problems have obvious
solutions.

Getting down to the substance of this document, it seems to largely be
about how ownership of subsets of the universe of URIs is delegated.  We
intend the delegation to look something like:

    URIs->              (owned by the IETF)
        schema->        (owned by the IETF)
            namespace->       (e.g. owned by the URN experts)
                authority->   (owned by the domain registrant)
                    path prefixes->    (owned by the operator of the host)
                        resources      (owned by the application instance)

The problem arises when a single instance of an "application" demands a
particular structure for the URI subset delegated to it, but we expect
the instance's owner to be unwilling/unable to delegate a subset with
that structure, e.g., because the subset demands a particular path
prefix or a particular form of authority, or uses query parts in
specific ways that might not be supported by the instance owner's
preferred deployment method.

So it might be useful to express these rules more explicitly in terms of
delegeated URI subsets, and to say what sort of URI subsets an
application instance can reasonably demand to be delegated to it and
which it cannot.

Dale


From nobody Wed Jan  8 20:34:23 2020
Return-Path: <john-ietf@jck.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 237B21200EB for <art@ietfa.amsl.com>; Wed,  8 Jan 2020 20:34:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.398
X-Spam-Level: 
X-Spam-Status: No, score=-1.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_ABOUTYOU=0.5, SPF_HELO_NONE=0.001, SPF_NONE=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 Cvo95srGcDdG for <art@ietfa.amsl.com>; Wed,  8 Jan 2020 20:34:21 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7134120020 for <art@ietf.org>; Wed,  8 Jan 2020 20:34:20 -0800 (PST)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1ipPWH-000DQi-6e; Wed, 08 Jan 2020 23:34:05 -0500
Date: Wed, 08 Jan 2020 23:33:56 -0500
From: John C Klensin <john-ietf@jck.com>
To: Adam Roach <adam@nostrum.com>
cc: S Moonesamy <sm+ietf@elandsys.com>, Mark Nottingham <mnot@mnot.net>, art@ietf.org
Message-ID: <36528CF21FDE2B32FA1E3C06@PSB>
In-Reply-To: <9eda86bf-a31d-a45f-ac8c-98cb7f38e9d1@nostrum.com>
References: <87E116C31DAF1434C3C3937F@PSB> <a267e8d7-e88f-fe84-a3d4-eb12b88a46ad@nostrum.com> <6.2.5.6.2.20200107163256.0f2810b8@elandnews.com> <9eda86bf-a31d-a45f-ac8c-98cb7f38e9d1@nostrum.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/bxBToobm0UYSEJNHRyH2P5lYRVo>
Subject: Re: [art] URNs and Last Call: <draft-nottingham-rfc7320bis-02.txt> (URI Design and Ownership) to Best Current Practice
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2020 04:34:22 -0000

--On Wednesday, January 8, 2020 12:11 -0600 Adam Roach
<adam@nostrum.com> wrote:
 
> To be clear, what I posted is my personal opinion (as are the
> following two paragraphs), and isn't an official IESG
> position, much less an IETF consensus position. Nothing in the
> process prevents you from commenting on whatever you want.
> 
> That said, I think it is a bad idea to slow down or stop
> improvements to a document by asking for unrelated and
> possibly contentious changes, especially at (or, to be honest,
> somewhat after) the last minute. The IETF has a long history
> of letting "perfect" become the enemy of "good," leading to
> author frustration, participant fatigue, and very long delays
> in publication.

Adam,

To clarify in return: In part because I was painfully aware that
the nominal closing date for the Last Call had passed, I was
careful to ask myself two questions before posting anything.
They were (1) Is there anything in this I-D that is sufficiently
confusing or otherwise problematic that it could plausibly be
used in the future to impede other work even thought the IETF,
broadly, was not aware of that potential issue when it was
approved?  I believe that question is reasonable whether the
issue appears in the predecessor document or not. (2) Given that
there is a predecessor document, is there anything in this I-D
that could make things worse, rather than better?  Now, both of
those questions, but especially the second, go to your comment
about "improvements to a document".  Even if I had no other
reservations about your model of incremental documents (at least
as I understand it), if some changes make things worse, it seems
to me unreasonable to me to ignore them and assert that the
document should go through because some of the proposed changes
are improvements.  I hope you agree.

For the same "lateness" reason and in recognition of your (and,
incidentally, my own) concerns about "unrelated and possibly
contentious changes", I was careful to propose an extremely
simple fix in the form of a clarification about URI types to
which the specification does not apply. 

The particular issues in this case are especially important
because there is a history of text in RFC 3986 and associated
documents (text that some would suggest was ill-considered) has
been used in the past to block, impede, or nit-pick relatively
recent work on URNs to the point that the WG gave up and
concluded, essentially, that part of the work could not be done
in the IETF.   That turns the implied question of plausibility
above from a hypothetical into a known reality and, wrt this
particular document, should force the question of whether it is
part of the problem or part of the solution... again, going to
questions about sweeping assertions of "improvement".  That
seems especially important in this case given the recent
[re-]appearance of "later, therefore superceding or more
authoritative regardless of 'updates' or 'obsoletes' status"
arguments in the IETF, reinforced by text in this I-D that
appears to me to say that any specification that disagrees with
the recommendations of this one is broken and requires a fix.

Of course, if one reads the I-D (and 7320) the way Barry does,
as simply not applicable to URNs or other URIs whose structure
is not hierarchical, then there is no problem at all.   A number
of comments that followed my original message strongly suggest
that reasonable people in the community do not find that reading
as obvious as Barry does.  And, again, the best solution at this
point is not a rewrite or other major change, just insertion of
a short clarification about scope and/or applicability.


> For further clarity: I think it would be completely reasonable
> to turn around and propose yet another bis version of BCP 190
> to fix any further perceived defects as soon as this version
> is published, and then work towards building consensus that
> such changes are required.

My apologies, but I think the above is sufficiently hypothetical
to be, in practice, spurious. draft-nottingham-rfc7320bis is an
AD-sponsored document, sponsored, if I read the tracker
correctly, by you.   Now, suppose that someone were to post an
I-D tomorrow, or at some point pre-publication of
draft-nottingham-rfc7320bis, proposing to replace it with a new
version and address other issues.    Would you be willing to
AD-sponsor that draft or would you (as I hope you would) say
"the community has spent enough time on this issue for a while,
so, unless a critical emergency causing serious harm can be
demonstrated, let's let it sit for a year or three" (or impose
criteria for level of obvious community interest that would
amount to the same thing).  Even if your answer is "yes, you
would sponsor it", can you guarantee that someone would do so
after March 27 (versus putting it off for an extended period or
forever)?  

We've seen enough things die in the IETF because the problem
wasn't big and pressing enough and no AD felt like sponsoring
the work (for whatever good, bad, or arbitrary reasons) that
saying "it would be completely reasonable to turn around and
propose yet another bis version..." is unpersuasive in the
absence of guarantees that I don't believe any sensible AD would
make. 

> The changes in the current bis are
> needed to address a demonstrable and ongoing problem. It seems
> imprudent to delay needed tactical changes based on
> last-minute musings about what else might be changed.

If this were a technical specification and there were
significant technical issues (e.g., requirements that
implementation experience had demonstrated were infeasible), I'd
certainly agree with "imprudent to delay".  But, this is a BCP
and, as others have pointed out, almost all of the changes are
dropping 2119/8174 requirements language in favor of lower-case
statements and more general guidance.  If the one-sentence
description of "Changes from RFC7320" in Appendix A of the I-D
is accurate, that is _all_ of the changes.   Getting from there
to "demonstrable and ongoing problem" and/or "needed tactical
changes" seems to me like a stretch. YMMD, but it is clear from
other comments that I'm not the only one to react that way.

  best,
    john



From nobody Wed Jan  8 20:41:15 2020
Return-Path: <mnot@mnot.net>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BC0B1200EB for <art@ietfa.amsl.com>; Wed,  8 Jan 2020 20:41:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.201
X-Spam-Level: 
X-Spam-Status: No, score=-2.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, GB_ABOUTYOU=0.5, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=HXa8nU3X; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=QfAil1gU
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 P0slqXkQBU8F for <art@ietfa.amsl.com>; Wed,  8 Jan 2020 20:41:10 -0800 (PST)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 73865120020 for <art@ietf.org>; Wed,  8 Jan 2020 20:41:10 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id AFE979A6; Wed,  8 Jan 2020 23:41:09 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Wed, 08 Jan 2020 23:41:10 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm1; bh=E X0MGtDve5UYLgNtY7/bvtpA1oZ+h9ryuJlorOvSGrY=; b=HXa8nU3XJxgOF8hzn uf/RkKmQksK6eKyq9Wsn2FrZcGbdF7vwsW+I8jAkR1zZaxMzKfJKtDP3248q3GlW zAh+dmc8aLmM5Fl9j0fFG8d+urRWJW6qdw5kb4F+Xu3DCWah/Kvm2c4dcqA6sjBJ dHl/TjKxhp99y2PjMDRqXqRAdyefGtIXJxq0rwDzGDkeuK5B0QOl4SXD4Hv0HC5i zm+k55nESC/o8EdtffPxoqRI+uuXtX/fvVAl3ntyp95zme+oYg3moMTomjub6MfL v2f6QHzl89WAWWK1rVGJfy+/W9c7mAF9IozgO9s9Gf2M1owNhJNjI4DyVl7x8WgG S2GjQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=EX0MGtDve5UYLgNtY7/bvtpA1oZ+h9ryuJlorOvSG rY=; b=QfAil1gURnG4dsO48aIlf/vzDaM1oKeVwF0DLxleluGzADyCj1y/6Wor8 m23wZUeVWyDGZAHhPwIoksyy6+teGfpFVYahzWe5ob7nBIaoXTjuL4Jhgnkp5GMF FIykMokPKpjEFV5Th+KZfXefzI03S2LkpxTVzVb7xUDJlXV16Fl9QCoDKkS3Pr97 jNj2fbGcls9K2eaijfYTJR6aBPb5KDp/K6eIMh8kB+nyJr0a3qo+fk5h9Ra5E7J1 UwbyHR84m3OKXCLwaP3JaUPHANhUjEEDF71VpoqRhwPQ90xQjHJZBHXAbxOf6j5j jPhCYspo3xLPoU3SmFm2TfELwQQxA==
X-ME-Sender: <xms:464WXrf4tmEwjRQJMVsYB6uk9JkDTFa5TN0CsJyehHws5E0CkEmnyw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrvdehledgieehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurheptggguffhjgffgffkfhfvofesthhqmhdthhdtvdenucfhrhhomhepofgrrhhk ucfpohhtthhinhhghhgrmhcuoehmnhhothesmhhnohhtrdhnvghtqeenucffohhmrghinh epmhhnohhtrdhnvghtnecukfhppeduudelrddujedrudehkedrvdehudenucfrrghrrghm pehmrghilhhfrhhomhepmhhnohhtsehmnhhothdrnhgvthenucevlhhushhtvghrufhiii gvpedt
X-ME-Proxy: <xmx:464WXsNg7GpzbN2XjG3R80hMtoy5WM2QVxt4_iwE5dFBD6N6Nxi-gw> <xmx:464WXrK3IAIawnvoJSul6uNVFa4LAq4UJtOTuxRtwK7kiNM8KNYUAA> <xmx:464WXqk0WQCRsMthNFNxSEwhHGy4rSEfGFQ4w1F8EAi7jtAv3lx6hQ> <xmx:5a4WXm2I43mDFzMumWnogM-zxQxOZFLkUgGBJH6GCxydm7iKctMnig>
Received: from macbook-pro.mnot.net (unknown [119.17.158.251]) by mail.messagingengine.com (Postfix) with ESMTPA id 9146080061; Wed,  8 Jan 2020 23:41:05 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.40.2.2.4\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <36528CF21FDE2B32FA1E3C06@PSB>
Date: Thu, 9 Jan 2020 15:41:03 +1100
Cc: Adam Roach <adam@nostrum.com>, S Moonesamy <sm+ietf@elandsys.com>, art@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <0384BB91-938A-4EFC-95AD-0BBDD14EC485@mnot.net>
References: <87E116C31DAF1434C3C3937F@PSB> <a267e8d7-e88f-fe84-a3d4-eb12b88a46ad@nostrum.com> <6.2.5.6.2.20200107163256.0f2810b8@elandnews.com> <9eda86bf-a31d-a45f-ac8c-98cb7f38e9d1@nostrum.com> <36528CF21FDE2B32FA1E3C06@PSB>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.3608.40.2.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/-8-II0iqKKUV1GMoaicCYbWFsVg>
Subject: Re: [art] URNs and Last Call: <draft-nottingham-rfc7320bis-02.txt> (URI Design and Ownership) to Best Current Practice
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2020 04:41:14 -0000

John,

In my mind (albeit containing limited knowledge of URNs), exempting URNs =
isn't the right solution, because they potentially face the same issues =
as more traditional URIs.

For example, if someone were to come along and say "the string 'foo' in =
fragment identifiers is magical", that would affect URNs as well, =
probably to their detriment unless the proper work were done.

Of course, if the definition of a particular NID or whatever allowed =
such a thing to be done, it would be fine -- within that scope -- and I =
think that's already covered by the draft.

Likewise, if URNs want to define special conventions overall for URNs, =
that's also within scope -- provided that the scheme is updated =
properly.

If this isn't clear enough in the document, I'm happy to make it so.

Cheers,


> On 9 Jan 2020, at 3:33 pm, John C Klensin <john-ietf@jck.com> wrote:
>=20
>=20
>=20
> --On Wednesday, January 8, 2020 12:11 -0600 Adam Roach
> <adam@nostrum.com> wrote:
>=20
>> To be clear, what I posted is my personal opinion (as are the
>> following two paragraphs), and isn't an official IESG
>> position, much less an IETF consensus position. Nothing in the
>> process prevents you from commenting on whatever you want.
>>=20
>> That said, I think it is a bad idea to slow down or stop
>> improvements to a document by asking for unrelated and
>> possibly contentious changes, especially at (or, to be honest,
>> somewhat after) the last minute. The IETF has a long history
>> of letting "perfect" become the enemy of "good," leading to
>> author frustration, participant fatigue, and very long delays
>> in publication.
>=20
> Adam,
>=20
> To clarify in return: In part because I was painfully aware that
> the nominal closing date for the Last Call had passed, I was
> careful to ask myself two questions before posting anything.
> They were (1) Is there anything in this I-D that is sufficiently
> confusing or otherwise problematic that it could plausibly be
> used in the future to impede other work even thought the IETF,
> broadly, was not aware of that potential issue when it was
> approved?  I believe that question is reasonable whether the
> issue appears in the predecessor document or not. (2) Given that
> there is a predecessor document, is there anything in this I-D
> that could make things worse, rather than better?  Now, both of
> those questions, but especially the second, go to your comment
> about "improvements to a document".  Even if I had no other
> reservations about your model of incremental documents (at least
> as I understand it), if some changes make things worse, it seems
> to me unreasonable to me to ignore them and assert that the
> document should go through because some of the proposed changes
> are improvements.  I hope you agree.
>=20
> For the same "lateness" reason and in recognition of your (and,
> incidentally, my own) concerns about "unrelated and possibly
> contentious changes", I was careful to propose an extremely
> simple fix in the form of a clarification about URI types to
> which the specification does not apply.=20
>=20
> The particular issues in this case are especially important
> because there is a history of text in RFC 3986 and associated
> documents (text that some would suggest was ill-considered) has
> been used in the past to block, impede, or nit-pick relatively
> recent work on URNs to the point that the WG gave up and
> concluded, essentially, that part of the work could not be done
> in the IETF.   That turns the implied question of plausibility
> above from a hypothetical into a known reality and, wrt this
> particular document, should force the question of whether it is
> part of the problem or part of the solution... again, going to
> questions about sweeping assertions of "improvement".  That
> seems especially important in this case given the recent
> [re-]appearance of "later, therefore superceding or more
> authoritative regardless of 'updates' or 'obsoletes' status"
> arguments in the IETF, reinforced by text in this I-D that
> appears to me to say that any specification that disagrees with
> the recommendations of this one is broken and requires a fix.
>=20
> Of course, if one reads the I-D (and 7320) the way Barry does,
> as simply not applicable to URNs or other URIs whose structure
> is not hierarchical, then there is no problem at all.   A number
> of comments that followed my original message strongly suggest
> that reasonable people in the community do not find that reading
> as obvious as Barry does.  And, again, the best solution at this
> point is not a rewrite or other major change, just insertion of
> a short clarification about scope and/or applicability.
>=20
>=20
>> For further clarity: I think it would be completely reasonable
>> to turn around and propose yet another bis version of BCP 190
>> to fix any further perceived defects as soon as this version
>> is published, and then work towards building consensus that
>> such changes are required.
>=20
> My apologies, but I think the above is sufficiently hypothetical
> to be, in practice, spurious. draft-nottingham-rfc7320bis is an
> AD-sponsored document, sponsored, if I read the tracker
> correctly, by you.   Now, suppose that someone were to post an
> I-D tomorrow, or at some point pre-publication of
> draft-nottingham-rfc7320bis, proposing to replace it with a new
> version and address other issues.    Would you be willing to
> AD-sponsor that draft or would you (as I hope you would) say
> "the community has spent enough time on this issue for a while,
> so, unless a critical emergency causing serious harm can be
> demonstrated, let's let it sit for a year or three" (or impose
> criteria for level of obvious community interest that would
> amount to the same thing).  Even if your answer is "yes, you
> would sponsor it", can you guarantee that someone would do so
> after March 27 (versus putting it off for an extended period or
> forever)? =20
>=20
> We've seen enough things die in the IETF because the problem
> wasn't big and pressing enough and no AD felt like sponsoring
> the work (for whatever good, bad, or arbitrary reasons) that
> saying "it would be completely reasonable to turn around and
> propose yet another bis version..." is unpersuasive in the
> absence of guarantees that I don't believe any sensible AD would
> make.=20
>=20
>> The changes in the current bis are
>> needed to address a demonstrable and ongoing problem. It seems
>> imprudent to delay needed tactical changes based on
>> last-minute musings about what else might be changed.
>=20
> If this were a technical specification and there were
> significant technical issues (e.g., requirements that
> implementation experience had demonstrated were infeasible), I'd
> certainly agree with "imprudent to delay".  But, this is a BCP
> and, as others have pointed out, almost all of the changes are
> dropping 2119/8174 requirements language in favor of lower-case
> statements and more general guidance.  If the one-sentence
> description of "Changes from RFC7320" in Appendix A of the I-D
> is accurate, that is _all_ of the changes.   Getting from there
> to "demonstrable and ongoing problem" and/or "needed tactical
> changes" seems to me like a stretch. YMMD, but it is clear from
> other comments that I'm not the only one to react that way.
>=20
>  best,
>    john
>=20
>=20

--
Mark Nottingham   https://www.mnot.net/


From nobody Wed Jan  8 22:21:43 2020
Return-Path: <john-ietf@jck.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AEC9120118 for <art@ietfa.amsl.com>; Wed,  8 Jan 2020 22:21:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 x4hFNsYBEor9 for <art@ietfa.amsl.com>; Wed,  8 Jan 2020 22:21:40 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7FF5120020 for <art@ietf.org>; Wed,  8 Jan 2020 22:21:40 -0800 (PST)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1ipRCE-000DhG-Ju; Thu, 09 Jan 2020 01:21:30 -0500
Date: Thu, 09 Jan 2020 01:21:24 -0500
From: John C Klensin <john-ietf@jck.com>
To: Mark Nottingham <mnot@mnot.net>
cc: Adam Roach <adam@nostrum.com>, S Moonesamy <sm+ietf@elandsys.com>, art@ietf.org
Message-ID: <3997764BF11775ABCD720F02@PSB>
In-Reply-To: <0384BB91-938A-4EFC-95AD-0BBDD14EC485@mnot.net>
References: <87E116C31DAF1434C3C3937F@PSB> <a267e8d7-e88f-fe84-a3d4-eb12b88a46ad@nostrum.com> <6.2.5.6.2.20200107163256.0f2810b8@elandnews.com> <9eda86bf-a31d-a45f-ac8c-98cb7f38e9d1@nostrum.com> <36528CF21FDE2B32FA1E3C06@PSB> <0384BB91-938A-4EFC-95AD-0BBDD14EC485@mnot.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/trk5arFDIJTfgP3ZpXukrltqf04>
Subject: Re: [art] URNs and Last Call: <draft-nottingham-rfc7320bis-02.txt> (URI Design and Ownership) to Best Current Practice
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2020 06:21:42 -0000

--On Thursday, January 9, 2020 15:41 +1100 Mark Nottingham
<mnot@mnot.net> wrote:

> John,
> 
> In my mind (albeit containing limited knowledge of URNs),
> exempting URNs isn't the right solution, because they
> potentially face the same issues as more traditional URIs.
> 
> For example, if someone were to come along and say "the string
> 'foo' in fragment identifiers is magical", that would affect
> URNs as well, probably to their detriment unless the proper
> work were done.
> 
> Of course, if the definition of a particular NID or whatever
> allowed such a thing to be done, it would be fine -- within
> that scope -- and I think that's already covered by the draft.
> 
> Likewise, if URNs want to define special conventions overall
> for URNs, that's also within scope -- provided that the scheme
> is updated properly.
> 
> If this isn't clear enough in the document, I'm happy to make
> it so.

Mark, I don't think it is clear enough in the document.  To a
certain extent, what you've said above is that a rather
different way of looking at all of this is that scope of control
associated with various bits of URIs is very important and one
has to be quite clear about scope of control and what those
scopes cover (possibly with different answers for different URI
components and/or schemes).  

I also suggest that interpretation, and at least some of what
you write above, is problematic given Barry's reading and
interpretation that the whole document does not apply to URNs
(and maybe not to other things that share some of the properties
of URNs) because of lack of hierarchy, at least at the scheme
level.

It seems to me that, in turn, takes us squarely into the middle
of the problem that Adam is trying to avoid, which is going back
and reexamining the basic assumptions and structure of the text
rather then, e.g., applying a simple patch about scope.  While
the copies to the IETF and IESG lists have been removed, I hope
and trust someone will make non-ART IESG members aware of that
direction before the teleconference.

If there is really the urgency to get this approved and done
that Adam seems to believe there is, this is really unfortunate
and I apologize for my part in it.

best,
  john




From nobody Thu Jan  9 01:56:51 2020
Return-Path: <sm@elandsys.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 019E4120105 for <art@ietfa.amsl.com>; Thu,  9 Jan 2020 01:56:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.698
X-Spam-Level: 
X-Spam-Status: No, score=-1.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.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 yu1PBFOgqa7y for <art@ietfa.amsl.com>; Thu,  9 Jan 2020 01:56:48 -0800 (PST)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id EEA4F1200E3 for <art@ietf.org>; Thu,  9 Jan 2020 01:56:47 -0800 (PST)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.115.142.251]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 0099uYDk007971 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Jan 2020 01:56:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1578563807; x=1578650207; i=@elandsys.com; bh=jZGbfmh/1W5Q89mHcVdKy0RP+KLyz3g/0pGxpy8WPRo=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Qipiiju/W6bIVll0LlquG5sjjpPRVR8zqTs7Kj5LeFYvkgx15dcTJ5IjbLxFhUyQg DtYtdSlcvIXnfjn+c/P9UKncwevreIukX7fn9U7eMd4eWlu29j07MvH1FsFIxJnx8V QcrsEiBZzZYoq8W/w9qg92qL5N3fcd+rKaGMdy2c=
Message-Id: <6.2.5.6.2.20200109004407.12fbf610@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 09 Jan 2020 01:53:36 -0800
To: John C Klensin <john-ietf@jck.com>, art@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Cc: Mark Nottingham <mnot@mnot.net>, Adam Roach <adam@nostrum.com>
In-Reply-To: <36528CF21FDE2B32FA1E3C06@PSB>
References: <87E116C31DAF1434C3C3937F@PSB> <a267e8d7-e88f-fe84-a3d4-eb12b88a46ad@nostrum.com> <6.2.5.6.2.20200107163256.0f2810b8@elandnews.com> <9eda86bf-a31d-a45f-ac8c-98cb7f38e9d1@nostrum.com> <36528CF21FDE2B32FA1E3C06@PSB>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/KuI3J37YdmyxZI-oA5KXqEjsny8>
Subject: Re: [art] URNs and Last Call: <draft-nottingham-rfc7320bis-02.txt> (URI Design and Ownership) to Best Current Practice
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2020 09:56:49 -0000

Hi John,
At 08:33 PM 08-01-2020, John C Klensin wrote:
> > For further clarity: I think it would be completely reasonable
> > to turn around and propose yet another bis version of BCP 190
> > to fix any further perceived defects as soon as this version
> > is published, and then work towards building consensus that
> > such changes are required.
>
>My apologies, but I think the above is sufficiently hypothetical
>to be, in practice, spurious. draft-nottingham-rfc7320bis is an
>AD-sponsored document, sponsored, if I read the tracker
>correctly, by you.   Now, suppose that someone were to post an
>I-D tomorrow, or at some point pre-publication of
>draft-nottingham-rfc7320bis, proposing to replace it with a new
>version and address other issues.    Would you be willing to
>AD-sponsor that draft or would you (as I hope you would) say
>"the community has spent enough time on this issue for a while,
>so, unless a critical emergency causing serious harm can be
>demonstrated, let's let it sit for a year or three" (or impose
>criteria for level of obvious community interest that would
>amount to the same thing).  Even if your answer is "yes, you
>would sponsor it", can you guarantee that someone would do so
>after March 27 (versus putting it off for an extended period or
>forever)?

It would be very difficult to justify that there is a critical 
emergency causing harm when a document is not a technical 
specification.  If I understand what was proposed, I would have to 
work towards building consensus.  I'd say that the "perfect is the 
enemy of good" would likely not be applied then, and that is based on 
past experience.

>We've seen enough things die in the IETF because the problem
>wasn't big and pressing enough and no AD felt like sponsoring
>the work (for whatever good, bad, or arbitrary reasons) that

Yes.

Regards,
S. Moonesamy 


From nobody Sat Jan 18 12:05:32 2020
Return-Path: <rg+ietf@randy.pensive.org>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A28B0120019 for <art@ietfa.amsl.com>; Sat, 18 Jan 2020 12:05:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.597
X-Spam-Level: *
X-Spam-Status: No, score=1.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FORGED_RELAY_MUA_TO_MX=3.498, SPF_PASS=-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 Dmi-F9_XlLv3 for <art@ietfa.amsl.com>; Sat, 18 Jan 2020 12:05:29 -0800 (PST)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id A381B120043 for <art@ietf.org>; Sat, 18 Jan 2020 12:05:29 -0800 (PST)
Received: from [99.111.97.181] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Sat, 18 Jan 2020 12:05:29 -0800
From: "Randall Gellens" <rg+ietf@randy.pensive.org>
To: art@ietf.org
Cc: "Brian Rosen" <br@brianrosen.net>
Date: Sat, 18 Jan 2020 12:05:28 -0800
X-Mailer: MailMate (1.13.1r5671)
Message-ID: <26C2AFDA-6CC1-4345-9978-1E2392750F94@randy.pensive.org>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; markup=markdown
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/Ws7PKkXncPPCYpOVD9mI8PjcLvU>
Subject: [art] Registering the 'LoST-Validation' NAPTR Service Tag
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Jan 2020 20:05:31 -0000

Working in NENA, we've identified a need to register a new S-NAPTR 
service tag 'LoST-Validation'.

Background: as some may recall, the key motivator for LoST was emergency 
services, primarily the ability to lookup a service URN for a location 
(i.e., map "URN:SERVICE:SOS" to a SIP URI for a PSAP for a specific 
location), and secondarily the ability to validate a civic location 
(i.e., validate that a civic address is unique, dispatchable, and meets 
the requirements for the area). LoST provides the ability to do both. 
NENA i3 (which defines NG9-1-1) makes extensive use of LoST. One thing 
NENA i3 does that was not originally contemplated when LoST was 
developed is to allow separation of the core mapping function of LoST 
from the validation function. NENA i3 allows (but does not require) 
these two services to be provided separately (with the motivation that 
mapping is a time-crucial service done during emergency call setup, 
while validation is performed as data is provisioned into entities and 
is not time-crucial, so a provider might potentially provision and 
operate these two services differently). LoST uses U-NAPTR Application 
Unique Strings rather than URIs to refer to other LoST servers. There is 
currently one U-NAPTR service tag for LoST ("LoST"). In order to be able 
to separate service mapping from location validation, a second service 
tag is needed. Otherwise an entity can't tell from an Application Unique 
String which service is available and can't resolve an Application 
Unique String into a URI for a LoST server that assuredly is willing to 
perform location validation. We therefore propose to define 
"LoST-Validation" as a service tag. This will allow an entity to locate 
a LoST server willing to perform civic location validation, leaving 
"LoST" as the service tag for core service mapping.  (Of course, a LoST 
server located using the 'LoST' service tag might offer both mapping and 
validation, but the ability to use 'LoST-Validation' in NAPTR records 
makes explicit which LoST servers are willing to do validation.)

The Service Tags registry rules that require an RFC to add a tag, so I 
have submitted a small RFC to do this: 
https://www.ietf.org/internet-drafts/draft-gellens-lost-validation-00.txt

Comments, feedback, etc. are appreciated.

--Randall


From nobody Mon Jan 20 09:41:29 2020
Return-Path: <noreply@ietf.org>
X-Original-To: art@ietf.org
Delivered-To: art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id AE79E120938; Mon, 20 Jan 2020 09:41:27 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: =?utf-8?q?Mirja_K=C3=BChlewind_via_Datatracker?= <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-nottingham-rfc7320bis@ietf.org, art@ietf.org, mt@mozilla.com, mt@lowentropy.net
X-Test-IDTracker: no
X-IETF-IDTracker: 6.116.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: =?utf-8?q?Mirja_K=C3=BChlewind?= <ietf@kuehlewind.net>
Message-ID: <157954208770.1489.11278174847321637412.idtracker@ietfa.amsl.com>
Date: Mon, 20 Jan 2020 09:41:27 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/qfnCCh65hqK1tKTgdGzg3nl0aNo>
Subject: [art] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_draft-n?= =?utf-8?q?ottingham-rfc7320bis-03=3A_=28with_COMMENT=29?=
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jan 2020 17:41:28 -0000

Mirja Kühlewind has entered the following ballot position for
draft-nottingham-rfc7320bis-03: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-nottingham-rfc7320bis/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Please note the TSV-ART review (Thanks Joe!) and the issue raised regarding an
outstaying errata on RFC7320 that may impact the change in this doc.



From nobody Mon Jan 20 15:46:02 2020
Return-Path: <mnot@mnot.net>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3478B120831; Mon, 20 Jan 2020 15:46:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=QJmneXFg; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=JqmhfG4I
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 53Wl8AA98f9D; Mon, 20 Jan 2020 15:45:57 -0800 (PST)
Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com [64.147.123.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 704C3120801; Mon, 20 Jan 2020 15:45:54 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 837253F1; Mon, 20 Jan 2020 18:45:53 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Mon, 20 Jan 2020 18:45:53 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm1; bh=4 p49jRuVYQgqq0kqDnAEp0eKaydFyG8pXwdVzCu5q90=; b=QJmneXFgRQxsC4NXN 3zuiMprk1SNGXBdsY77JpRbVKmVitlULKZHu0ZGbY767HMToo5I/JsYXqlhEmKbW i+sKxc419balpNVdOuLQn8FoSNsxTsj0uXqP5ce1PjLdztO1QiT51yZMKNbEHkor 1Xt7NKCkw81SENe2kk6qQ0EWiqpzhaoCfw56jgy6SauX3ntjVNGnv+q4f+UKYJqr WhVNTiEL2pxhqAEiVURyLAUSZQ7WDbN791YSyCuG3LUJmykYTXI4/gCmfsSHp1Ei XDtE3Diq6LHEGjz76AgSAzR4pIObLViIWPNAsGAkEyW1xy9LpqvF0tWhqmn/eAYL 75MWw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=4p49jRuVYQgqq0kqDnAEp0eKaydFyG8pXwdVzCu5q 90=; b=JqmhfG4If8rqWvgBgOSA1l/FosYgH7hjIgi/SwaIj/gQDPuw/v8YD1/3g GbhcOQBAeSwqhNNqElHJ7M/OosJcvgAxS6VUmbVylqHV4ED3DokNpXj0U7wZoQlj CYn5IWjD/vwG6SbrLPZgJqCuAGfPjD2eC0RUyGYmtwVhdZhGg+mYp7E1+lE2fHfG p4+7u1cP6uYDypP9UEWv6cWQO7KswRUppl80JJ1vuFiwpoJOVAu/u+AgL6vA5xFy hctZuD57YWIRdwHVCU4EAB1gDZ/WWbsMJ0+ufk3brrF71hDewOl4+3LvqFlCvzBf 5l3TyDz6cvgtSYRMhfBLY4512wRkQ==
X-ME-Sender: <xms:sDsmXvn_L3N5CasEbSqca_q174XTlPI1yqsO4gP7iQOPWsuM_l9iSQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrudejgdduudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpegtggfuhfgjfffgkfhfvffosehtqhhmtdhhtdejnecuhfhrohhmpeforghrkhcu pfhothhtihhnghhhrghmuceomhhnohhtsehmnhhothdrnhgvtheqnecuffhomhgrihhnpe hivghtfhdrohhrghdpmhhnohhtrdhnvghtnecukfhppeduudelrddujedrudehkedrvdeh udenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmnh hothesmhhnohhtrdhnvght
X-ME-Proxy: <xmx:sDsmXuPRNDE9rgvmeFf4ZjcEu2xqbZ-rs-lB1wNrIAl8P46_-1LYOQ> <xmx:sDsmXvBVBOyVMY-DWbfBwFTotTVckW1LeVigRyou3MArmIHmkOWYcA> <xmx:sDsmXvV-uS9c2Lg0JsqT2uMs6PeL4WdQgzJk-U_VPgc7obzl2Xp6QQ> <xmx:sTsmXnAQ8HxRzeaeHzKRlTlScFNGo01FQGPRTzZ9WtBV_XkJt0HHjA>
Received: from macbook-pro.mnot.net (unknown [119.17.158.251]) by mail.messagingengine.com (Postfix) with ESMTPA id 205853060B1E; Mon, 20 Jan 2020 18:45:49 -0500 (EST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.40.2.2.4\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <157954208770.1489.11278174847321637412.idtracker@ietfa.amsl.com>
Date: Tue, 21 Jan 2020 10:45:46 +1100
Cc: The IESG <iesg@ietf.org>, art@ietf.org, draft-nottingham-rfc7320bis@ietf.org, Martin Thomson <mt@mozilla.com>, Martin Thomson <mt@lowentropy.net>
Content-Transfer-Encoding: quoted-printable
Message-Id: <9795DAFF-7989-4EFE-99AC-3510F4E1BFDD@mnot.net>
References: <157954208770.1489.11278174847321637412.idtracker@ietfa.amsl.com>
To: =?utf-8?Q?Mirja_K=C3=BChlewind?= <ietf@kuehlewind.net>
X-Mailer: Apple Mail (2.3608.40.2.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/UI8giTOt30r_bnPVlUbwMFicwFI>
Subject: Re: [art]  =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_draft-n?= =?utf-8?q?ottingham-rfc7320bis-03=3A_=28with_COMMENT=29?=
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jan 2020 23:46:00 -0000

Thanks, Mirja. The errata has already been applied, as I told Joe in my =
response to his review.

Cheers,


> On 21 Jan 2020, at 4:41 am, Mirja K=C3=BChlewind via Datatracker =
<noreply@ietf.org> wrote:
>=20
> Mirja K=C3=BChlewind has entered the following ballot position for
> draft-nottingham-rfc7320bis-03: No Objection
>=20
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut =
this
> introductory paragraph, however.)
>=20
>=20
> Please refer to =
https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>=20
>=20
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-nottingham-rfc7320bis/
>=20
>=20
>=20
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>=20
> Please note the TSV-ART review (Thanks Joe!) and the issue raised =
regarding an
> outstaying errata on RFC7320 that may impact the change in this doc.
>=20
>=20
> _______________________________________________
> art mailing list
> art@ietf.org
> https://www.ietf.org/mailman/listinfo/art

--
Mark Nottingham   https://www.mnot.net/


From nobody Tue Jan 21 00:45:55 2020
Return-Path: <ietf@kuehlewind.net>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0816120071; Tue, 21 Jan 2020 00:45:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 letHTm99mWZs; Tue, 21 Jan 2020 00:45:47 -0800 (PST)
Received: from wp513.webpack.hosteurope.de (wp513.webpack.hosteurope.de [IPv6:2a01:488:42:1000:50ed:8223::]) (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 84735120043; Tue, 21 Jan 2020 00:45:47 -0800 (PST)
Received: from 200116b82c7d67002c08dcbf0cee8de7.dip.versatel-1u1.de ([2001:16b8:2c7d:6700:2c08:dcbf:cee:8de7]); authenticated by wp513.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1itpAN-0004ey-5b; Tue, 21 Jan 2020 09:45:43 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Mirja Kuehlewind <ietf@kuehlewind.net>
In-Reply-To: <9795DAFF-7989-4EFE-99AC-3510F4E1BFDD@mnot.net>
Date: Tue, 21 Jan 2020 09:45:42 +0100
Cc: art@ietf.org, draft-nottingham-rfc7320bis@ietf.org, Martin Thomson <mt@mozilla.com>, The IESG <iesg@ietf.org>, Martin Thomson <mt@lowentropy.net>
Content-Transfer-Encoding: quoted-printable
Message-Id: <ECCFEB61-9F23-4DD0-988C-55F32FE9FA84@kuehlewind.net>
References: <157954208770.1489.11278174847321637412.idtracker@ietfa.amsl.com> <9795DAFF-7989-4EFE-99AC-3510F4E1BFDD@mnot.net>
To: Mark Nottingham <mnot@mnot.net>
X-Mailer: Apple Mail (2.3445.104.11)
X-bounce-key: webpack.hosteurope.de;ietf@kuehlewind.net;1579596347;97c73b85;
X-HE-SMSGID: 1itpAN-0004ey-5b
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/sekWF2ZJE-bkck7zhZOyexIL8HE>
Subject: Re: [art]  =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_draft-n?= =?utf-8?q?ottingham-rfc7320bis-03=3A_=28with_COMMENT=29?=
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2020 08:45:53 -0000

Hi Mark,

Great! I didn=E2=80=99t double-check and I didn=E2=80=99t see you reply =
to Joe=E2=80=A6

Thanks!
Mirja



> On 21. Jan 2020, at 00:45, Mark Nottingham <mnot@mnot.net> wrote:
>=20
> Thanks, Mirja. The errata has already been applied, as I told Joe in =
my response to his review.
>=20
> Cheers,
>=20
>=20
>> On 21 Jan 2020, at 4:41 am, Mirja K=C3=BChlewind via Datatracker =
<noreply@ietf.org> wrote:
>>=20
>> Mirja K=C3=BChlewind has entered the following ballot position for
>> draft-nottingham-rfc7320bis-03: No Objection
>>=20
>> When responding, please keep the subject line intact and reply to all
>> email addresses included in the To and CC lines. (Feel free to cut =
this
>> introductory paragraph, however.)
>>=20
>>=20
>> Please refer to =
https://www.ietf.org/iesg/statement/discuss-criteria.html
>> for more information about IESG DISCUSS and COMMENT positions.
>>=20
>>=20
>> The document, along with other ballot positions, can be found here:
>> https://datatracker.ietf.org/doc/draft-nottingham-rfc7320bis/
>>=20
>>=20
>>=20
>> =
----------------------------------------------------------------------
>> COMMENT:
>> =
----------------------------------------------------------------------
>>=20
>> Please note the TSV-ART review (Thanks Joe!) and the issue raised =
regarding an
>> outstaying errata on RFC7320 that may impact the change in this doc.
>>=20
>>=20
>> _______________________________________________
>> art mailing list
>> art@ietf.org
>> https://www.ietf.org/mailman/listinfo/art
>=20
> --
> Mark Nottingham   https://www.mnot.net/
>=20
>=20


From nobody Tue Jan 21 08:49:42 2020
Return-Path: <alissa@cooperw.in>
X-Original-To: expand-draft-nottingham-rfc7320bis.all@virtual.ietf.org
Delivered-To: art@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id 461CE120044; Tue, 21 Jan 2020 08:49:31 -0800 (PST)
X-Original-To: xfilter-draft-nottingham-rfc7320bis.all@ietfa.amsl.com
Delivered-To: xfilter-draft-nottingham-rfc7320bis.all@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBEC61200CC; Tue, 21 Jan 2020 08:49:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=VE8YJggR; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=swBxbc9C
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 mr9F_WlnBgA7; Tue, 21 Jan 2020 08:49:29 -0800 (PST)
Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com [64.147.123.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5EA7B120044; Tue, 21 Jan 2020 08:49:26 -0800 (PST)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id 67D20641; Tue, 21 Jan 2020 11:49:25 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Tue, 21 Jan 2020 11:49:25 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm2; bh=I zQJawLPnR1AXDZ0amzORqFL4y6KqWYkgae8kyzQENI=; b=VE8YJggR9JG9ykXTt Pn6Emoxki1ewGrqqzKES5yHwZA8G8SZj6ky9OZ3d+JIbgH1TkW2aNKfo5gQpfFb8 8TL7Od7gvHp1OouG/TQPTeYnIhfGZSzCiqdIDgcjHdA89EDP+7vwDSoJaBh0H130 LYj6Ggm0L8ZTrbndr1x4iFCNgEAbeDjqGXJJvPRVpcfuyVEY+s5FqeJB2GtXVCSy Px6VCvTIUkBhn4nsM7pkaDKj7rctOIEQkN1PbbGtD2bwKOjrCDop7c2gZoClcBfv yHg1FwW/9QQ0iJ50WY52erj0UrhVpjVD6kM1Dnju2p/htvpJsttU+x3d3by3IgQH Ncopw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=IzQJawLPnR1AXDZ0amzORqFL4y6KqWYkgae8kyzQE NI=; b=swBxbc9Cdrh23k2lzYB+XCiRCJNpwFro77zxxySqZNVjKzzKXgbsns0vG 2RNbeaLR0EQARvvWAzMdNgNUFNAK2PnSn/fCQnEhcfmfMdM7mRBaetqAp1075zYq 1DfSsrdC4plcmB5eljTed6/Qpm0IL59zNN8MaZOetwL0zyKN47lSTIIwe/UF+Y7t duUTVvQi9p+gBJjtovXktsNT6blOkp9h/Uy+Xhqc7rBKbSCsU7tHe1PslHVTDHsA RXA+MjSumyM/7uCPqk2HEy3ElvRFmNSAF7X1kW6Cj7B/d2IZnDCNPQQQxVC+20ht aovqWT9yVFuu/Mwg+eVNU2b9GgcxA==
X-ME-Sender: <xms:lCsnXm3SRHPVSOh1hdtAFwfp06RUzHxdJ75mJlEXxj4HAPpfatDX0w>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrudekgdelvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpegtggfuhfgjfffgkfhfvffosehtqhhmtdhhtdejnecuhfhrohhmpeetlhhishhs rgcuvehoohhpvghruceorghlihhsshgrsegtohhophgvrhifrdhinheqnecuffhomhgrih hnpehmnhhothdrnhgvthdpihgvthhfrdhorhhgnecukfhppedujeefrdefkedruddujedr jeeknecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprg hlihhsshgrsegtohhophgvrhifrdhinh
X-ME-Proxy: <xmx:lCsnXhvKJWN3Q_iUfWsFMZJLahgIZU_9uJWZddG5_HNH24a5380mnQ> <xmx:lCsnXmUidNzrFdM9p8fprymLr0oRDDHB6s6oyiRaM3lBm347NwjLuw> <xmx:lCsnXhx-QE8-l24X9qQbUErHO2R2d-RtUT1Br_YluUYhyLqZho1Mqw> <xmx:lSsnXq8j9WdeVU55ytEGLj6qcmvRWpzxX2pp_o3LHsuigYwVHwnA3g>
Received: from rtp-alcoop-nitro2.cisco.com (unknown [173.38.117.78]) by mail.messagingengine.com (Postfix) with ESMTPA id 030873280059; Tue, 21 Jan 2020 11:49:23 -0500 (EST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <4C01295C-6EDA-4C32-8BA3-BD8DA3B9C9A2@mnot.net>
Date: Tue, 21 Jan 2020 11:49:20 -0500
Cc: Carsten Bormann <cabo@tzi.org>, last-call@ietf.org, General Area Review Team <gen-art@ietf.org>, draft-nottingham-rfc7320bis.all@ietf.org, Martin Thomson <mt@lowentropy.net>
Content-Transfer-Encoding: quoted-printable
Message-Id: <94DB4F60-A4BD-4BFF-9587-673BC52A9361@cooperw.in>
References: <3a7db097-84c0-4c44-aed0-51196a6a16b6@www.fastmail.com> <9F9A2298-0088-40B2-A69C-7F63D17EB8E3@nostrum.com> <A88B004F-6426-41BF-9711-4071A63637B5@mnot.net> <23E269D1-06A1-4EE6-B886-5E5B3824C27E@tzi.org> <4C01295C-6EDA-4C32-8BA3-BD8DA3B9C9A2@mnot.net>
To: Mark Nottingham <mnot@mnot.net>, Robert Sparks <rjsparks@nostrum.com>
X-Mailer: Apple Mail (2.3445.9.1)
Resent-From: <alias-bounces@ietf.org>
Resent-To: mnot@mnot.net, adam@nostrum.com, mt@mozilla.com, art@ietf.org, mt@lowentropy.net
Resent-Message-Id: <20200121164931.461CE120044@ietfa.amsl.com>
Resent-Date: Tue, 21 Jan 2020 08:49:31 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/WIFubf13KSxfkNV4dwG-Ew2IxMg>
Subject: Re: [art] [Last-Call] Genart last call review of draft-nottingham-rfc7320bis-02
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2020 16:49:31 -0000

Robert, thanks for your review. Mark, thanks for your responses. I =
entered a Yes ballot. I have a comment below regarding the RFC 6838 =
reference.

> On Nov 26, 2019, at 9:32 PM, Mark Nottingham <mnot@mnot.net> wrote:
>=20
>=20
>=20
>> On 27 Nov 2019, at 1:13 pm, Carsten Bormann <cabo@tzi.org> wrote:
>>=20
>> On Nov 27, 2019, at 02:56, Mark Nottingham <mnot@mnot.net> wrote:
>>>=20
>>> Do we expect most readers to be comparing the documents so closely? =
This is an 'obsoletes', not an 'updates'.
>>=20
>> Speaking for myself as a reader only: Yes.
>=20
> My concern is that every time we add text to a document, we increase =
the cognitive load for readers; adding the reasoning for *every* =
decision and change expands a page of text into 2 to 3 (or more), so we =
need to impose a filter of some sort.
>=20
> The requirement in question is:
>=20
> "Media type definitions (as per [RFC6838]) SHOULD specify the fragment =
identifier syntax(es) to be used with them"
>=20
> It was removed because it was misleading (6838 doesn't make such a =
requirement a SHOULD), and the focus of this update was to reduce the =
number of unnecessary requirements.

I think a good solution here would be to add a sentence along the lines =
of the sentence above to the shepherd write-up. That way the rationale =
for the substitution is captured in the document=E2=80=99s history but =
not in the document itself.

Thanks,
Alissa


> 3986 isn't replacing that reference; it's providing a grounding for =
what fragment identifiers are.
>=20
> IME this information doesn't help the reader understand the document =
any better unless they're closely comparing the two documents (as =
reviewers are now doing, and thanks to them). If folks disagree, that's =
fine, but I'd like to understand why they think this information is =
worthy of documenting in-spec.
>=20
> Cheers,
>=20
> --
> Mark Nottingham   https://www.mnot.net/
>=20
> _______________________________________________
> art mailing list
> art@ietf.org
> https://www.ietf.org/mailman/listinfo/art


From nobody Tue Jan 21 09:30:17 2020
Return-Path: <ted.ietf@gmail.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0003412006B for <art@ietfa.amsl.com>; Tue, 21 Jan 2020 09:30:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level: 
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 Pfzy3XsxmGBv for <art@ietfa.amsl.com>; Tue, 21 Jan 2020 09:30:11 -0800 (PST)
Received: from mail-ot1-x331.google.com (mail-ot1-x331.google.com [IPv6:2607:f8b0:4864:20::331]) (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 06E4B120808 for <art@ietf.org>; Tue, 21 Jan 2020 09:30:11 -0800 (PST)
Received: by mail-ot1-x331.google.com with SMTP id p8so3637480oth.10 for <art@ietf.org>; Tue, 21 Jan 2020 09:30:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=R8psEXGY8yklSirkWGiwrupN+c+gLy97hjvMgswFy+I=; b=WH+B5ypbRXBhZ2WfSXxcw9x1gywiE/Li1IXjIBF2femQWf+eAJCSRg1r9Jca0F02RE mxw6sUUnfX/28kJoub6d8V5XKz3uRaQ5H1RArVdLzZrWYr6J5kiCQwhlnef/iUEgYn/R 6trvJWILHAUQqyxJOXv8X4/a/7M9i4GncrC/e/94YIioizIgQfiWZtlPm3eXVjE1cU77 n2tYWf0WJAEJHVs4stJSAwD1ma9ObM1zU1FJ5peqYP5KZ064uXUTv/Bn90CEeUe76wYA yMPgMatfywUGvQMHvJIlLwrXomNIOXASt4YeQfaWTpe0Q1mEJ4zR2iCAndrfzXEJlcoq BcOA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=R8psEXGY8yklSirkWGiwrupN+c+gLy97hjvMgswFy+I=; b=VWgDPlwpwkijQe9dYg9zmbZuXSIJ2P4S0ZtqV/qWztNisG/0VsukyhLl6+ntKVVJEw Um0z2C2MlJHTE6KXYidbLDz2dIJLMzNT+zTQ9CLG5fToYyiug2RVvFfSHW6b22MgoyQ5 IX82e/KheGY1kIscFUR2uOVq2UaOMywgWLkBKsXpj9HqV1JmFrRCze3vEPQHQfeym6Zd bdODVrO8XxorRjVZs38OX94ZWiPFlj21ekzyRdofhSC4FlC8QtT57y0m84b9I6dBdRN9 5pWVj444MaDpsPcK96kzL3AQBy5wgSBBNxs3k5gDbcpTGoVlgjdJExtpSFW/jEmqgxMO gIUA==
X-Gm-Message-State: APjAAAWbrSZrB2vQFgH9TKLmmgLhG3721nxSBDgkE8xatVf+rMNjXHXQ uLdBK55sxECllsEV7hRIFFzJzBsqpUkAr3jR8hM=
X-Google-Smtp-Source: APXvYqwFglqOVyOnhusfxyPHhm7W2IGjgZRDbJubz6FKOM6Ay/o1/RjSmAQBL66VP2rkPNK+Xl/cSRkHy/4cssXRGgc=
X-Received: by 2002:a05:6830:1487:: with SMTP id s7mr4197614otq.269.1579627810226;  Tue, 21 Jan 2020 09:30:10 -0800 (PST)
MIME-Version: 1.0
References: <26C2AFDA-6CC1-4345-9978-1E2392750F94@randy.pensive.org>
In-Reply-To: <26C2AFDA-6CC1-4345-9978-1E2392750F94@randy.pensive.org>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Tue, 21 Jan 2020 09:29:44 -0800
Message-ID: <CA+9kkMAWatHi0z4EXJEfvxtzX0ynQe4jNa7EckgyBMUSTpzrYw@mail.gmail.com>
To: Randall Gellens <rg+ietf@randy.pensive.org>
Cc: Applications and Real-Time Area Discussion <art@ietf.org>, Brian Rosen <br@brianrosen.net>
Content-Type: multipart/alternative; boundary="000000000000818830059ca9c2d3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/Y8RAqS5DyqLeYS7VNI3xL_7TIaE>
Subject: Re: [art] Registering the 'LoST-Validation' NAPTR Service Tag
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2020 17:30:16 -0000

--000000000000818830059ca9c2d3
Content-Type: text/plain; charset="UTF-8"

Hi Randy, Brian,

Thanks for the message.  I took a quick look at the document, and there are
two things that might want consideration.  The first is this text, which
tells you that the bursty validation traffic and the real-time functions
may be performed by the same server:

   A server identified using the 'LoST' service tag might
   also perform the validation function (and might resolve to the same
   URL as a server identified using the 'LoST-Validation' service tag),
   but the 'LoST-Validation' tag makes this explicit.

The "tag makes this explicit." doesn't seem to quite cover what you
want to say here.  Maybe:

Because some services are configured to provide
both real-time and validation functions, a server identified
using the 'LoST' service tag may also perform the validation function.
The 'Lost-Validation' service tag should, however, always be used
first when seeking
the validation service, as the two functions may be separate.
Fallback to the 'LoST'

may follow if the Lost-Validation service does not resolve.


Alternatively, you might cut this text and rely on the text in section 3.

Second, the document's IANA considerations says this:

IANA is requested to add 'LoST-Validation' to the S-NAPTR Application
   Service Tag registry created by [RFC3958]  This tag serves as a
   counter-part to the 'LoST' tag added by [RFC4848].

5.1.  U-NAPTR Registration

   This document registers the following U-NAPTR application service
   tag:

      Application Service Tag: LoST

      Defining Publication: This document.

Should this be S-NAPTR and LoST-Validation, respectively, or am I missing
something?

regards,

Ted

On Sat, Jan 18, 2020 at 12:05 PM Randall Gellens <rg+ietf@randy.pensive.org>
wrote:

> Working in NENA, we've identified a need to register a new S-NAPTR
> service tag 'LoST-Validation'.
>
> Background: as some may recall, the key motivator for LoST was emergency
> services, primarily the ability to lookup a service URN for a location
> (i.e., map "URN:SERVICE:SOS" to a SIP URI for a PSAP for a specific
> location), and secondarily the ability to validate a civic location
> (i.e., validate that a civic address is unique, dispatchable, and meets
> the requirements for the area). LoST provides the ability to do both.
> NENA i3 (which defines NG9-1-1) makes extensive use of LoST. One thing
> NENA i3 does that was not originally contemplated when LoST was
> developed is to allow separation of the core mapping function of LoST
> from the validation function. NENA i3 allows (but does not require)
> these two services to be provided separately (with the motivation that
> mapping is a time-crucial service done during emergency call setup,
> while validation is performed as data is provisioned into entities and
> is not time-crucial, so a provider might potentially provision and
> operate these two services differently). LoST uses U-NAPTR Application
> Unique Strings rather than URIs to refer to other LoST servers. There is
> currently one U-NAPTR service tag for LoST ("LoST"). In order to be able
> to separate service mapping from location validation, a second service
> tag is needed. Otherwise an entity can't tell from an Application Unique
> String which service is available and can't resolve an Application
> Unique String into a URI for a LoST server that assuredly is willing to
> perform location validation. We therefore propose to define
> "LoST-Validation" as a service tag. This will allow an entity to locate
> a LoST server willing to perform civic location validation, leaving
> "LoST" as the service tag for core service mapping.  (Of course, a LoST
> server located using the 'LoST' service tag might offer both mapping and
> validation, but the ability to use 'LoST-Validation' in NAPTR records
> makes explicit which LoST servers are willing to do validation.)
>
> The Service Tags registry rules that require an RFC to add a tag, so I
> have submitted a small RFC to do this:
> https://www.ietf.org/internet-drafts/draft-gellens-lost-validation-00.txt
>
> Comments, feedback, etc. are appreciated.
>
> --Randall
>
> _______________________________________________
> art mailing list
> art@ietf.org
> https://www.ietf.org/mailman/listinfo/art
>

--000000000000818830059ca9c2d3
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div>Hi Randy, Brian,</div><div><br></div=
><div>Thanks for the message.=C2=A0 I took a quick look at the document, an=
d there are two things that might want consideration.=C2=A0 The first is th=
is text, which tells you that the bursty validation traffic and the real-ti=
me functions may be performed by the same server:<br></div><div><br></div><=
div><pre>   A server identified using the &#39;LoST&#39; service tag might
   also perform the validation function (and might resolve to the same
   URL as a server identified using the &#39;LoST-Validation&#39; service t=
ag),
   but the &#39;LoST-Validation&#39; tag makes this explicit.<br><br></pre>=
<pre><span style=3D"font-family:arial,sans-serif">The &quot;tag makes this =
explicit.&quot; doesn&#39;t seem to quite cover what you want to say here. =
 Maybe:<br>   <br></span></pre><pre style=3D"margin-left:40px"><span style=
=3D"font-family:arial,sans-serif"><font size=3D"2">Because some services ar=
e configured to provide </font></span><br><span style=3D"font-family:arial,=
sans-serif"><font size=3D"2">both real-time and validation functions, a ser=
ver identified </font></span><br><span style=3D"font-family:arial,sans-seri=
f"><font size=3D"2">using the &#39;LoST&#39; service tag may also perform t=
he validation function. =C2=A0</font></span><br><span style=3D"font-family:=
arial,sans-serif"><font size=3D"2">The &#39;Lost-Validation&#39; service ta=
g should, however, always be used first when seeking </font></span><br><spa=
n style=3D"font-family:arial,sans-serif"><font size=3D"2">the validation se=
rvice, as the two functions may be separate.  Fallback to the &#39;LoST&#39=
;<br></font></span></pre><pre style=3D"margin-left:40px"><span style=3D"fon=
t-family:arial,sans-serif"><font size=3D"2">may follow if the Lost-Validati=
on service does not resolve.<br></font></span></pre><pre><span style=3D"fon=
t-family:arial,sans-serif"></span><span style=3D"font-family:arial,sans-ser=
if"> <br></span></pre><pre><span style=3D"font-family:arial,sans-serif">Alt=
ernatively, you might cut this text and rely on the text in section 3.  <br=
></span></pre></div></div><div>Second, the document&#39;s IANA consideratio=
ns says this:</div><div><br></div><div><pre>IANA is requested to add &#39;L=
oST-Validation&#39; to the S-NAPTR Application
   Service Tag registry created by [RFC3958]  This tag serves as a
   counter-part to the &#39;LoST&#39; tag added by [RFC4848].

5.1.  U-NAPTR Registration

   This document registers the following U-NAPTR application service
   tag:

      Application Service Tag: LoST

      Defining Publication: This document.</pre></div><div>Should this be S=
-NAPTR and LoST-Validation, respectively, or am I missing something?</div><=
div><br></div><div>regards,</div><div><br></div><div>Ted<br></div><div><br>=
</div><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On S=
at, Jan 18, 2020 at 12:05 PM Randall Gellens &lt;<a href=3D"mailto:rg%2Biet=
f@randy.pensive.org">rg+ietf@randy.pensive.org</a>&gt; wrote:<br></div><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left=
:1px solid rgb(204,204,204);padding-left:1ex">Working in NENA, we&#39;ve id=
entified a need to register a new S-NAPTR <br>
service tag &#39;LoST-Validation&#39;.<br>
<br>
Background: as some may recall, the key motivator for LoST was emergency <b=
r>
services, primarily the ability to lookup a service URN for a location <br>
(i.e., map &quot;URN:SERVICE:SOS&quot; to a SIP URI for a PSAP for a specif=
ic <br>
location), and secondarily the ability to validate a civic location <br>
(i.e., validate that a civic address is unique, dispatchable, and meets <br=
>
the requirements for the area). LoST provides the ability to do both. <br>
NENA i3 (which defines NG9-1-1) makes extensive use of LoST. One thing <br>
NENA i3 does that was not originally contemplated when LoST was <br>
developed is to allow separation of the core mapping function of LoST <br>
from the validation function. NENA i3 allows (but does not require) <br>
these two services to be provided separately (with the motivation that <br>
mapping is a time-crucial service done during emergency call setup, <br>
while validation is performed as data is provisioned into entities and <br>
is not time-crucial, so a provider might potentially provision and <br>
operate these two services differently). LoST uses U-NAPTR Application <br>
Unique Strings rather than URIs to refer to other LoST servers. There is <b=
r>
currently one U-NAPTR service tag for LoST (&quot;LoST&quot;). In order to =
be able <br>
to separate service mapping from location validation, a second service <br>
tag is needed. Otherwise an entity can&#39;t tell from an Application Uniqu=
e <br>
String which service is available and can&#39;t resolve an Application <br>
Unique String into a URI for a LoST server that assuredly is willing to <br=
>
perform location validation. We therefore propose to define <br>
&quot;LoST-Validation&quot; as a service tag. This will allow an entity to =
locate <br>
a LoST server willing to perform civic location validation, leaving <br>
&quot;LoST&quot; as the service tag for core service mapping.=C2=A0 (Of cou=
rse, a LoST <br>
server located using the &#39;LoST&#39; service tag might offer both mappin=
g and <br>
validation, but the ability to use &#39;LoST-Validation&#39; in NAPTR recor=
ds <br>
makes explicit which LoST servers are willing to do validation.)<br>
<br>
The Service Tags registry rules that require an RFC to add a tag, so I <br>
have submitted a small RFC to do this: <br>
<a href=3D"https://www.ietf.org/internet-drafts/draft-gellens-lost-validati=
on-00.txt" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/intern=
et-drafts/draft-gellens-lost-validation-00.txt</a><br>
<br>
Comments, feedback, etc. are appreciated.<br>
<br>
--Randall<br>
<br>
_______________________________________________<br>
art mailing list<br>
<a href=3D"mailto:art@ietf.org" target=3D"_blank">art@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/art" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/art</a><br>
</blockquote></div></div>

--000000000000818830059ca9c2d3--


From nobody Tue Jan 21 13:26:27 2020
Return-Path: <adam@nostrum.com>
X-Original-To: expand-draft-nottingham-rfc7320bis.all@virtual.ietf.org
Delivered-To: art@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id 517DB1200B8; Tue, 21 Jan 2020 13:26:16 -0800 (PST)
X-Original-To: xfilter-draft-nottingham-rfc7320bis.all@ietfa.amsl.com
Delivered-To: xfilter-draft-nottingham-rfc7320bis.all@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06D37120019; Tue, 21 Jan 2020 13:26:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.405
X-Spam-Level: 
X-Spam-Status: No, score=-1.405 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, KHOP_HELO_FCRDNS=0.275, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.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 BHJxTBaAb6Vr; Tue, 21 Jan 2020 13:26:10 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 0805312007A; Tue, 21 Jan 2020 13:26:10 -0800 (PST)
Received: from Zephyrus.local (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id 00LLPpBQ052300 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 21 Jan 2020 15:25:52 -0600 (CST) (envelope-from adam@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1579641953; bh=ZLeu6k9R2vbhwOxsCMGX1mLJQmRM/StinBBCRjosuXM=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=W+fqWIhAwbHjqa2q6kt4ClcYHqYiJ6sSwsNPyRBcZw1ia1eJT34JC+PdCSj2k47UP lrVkjyKhUTyD3F/mNELXf4FkLPtKfPSaJ4/6mef172jrh/xLrtKMrUeJ7YpW6FHDyc XCtryiGIXOBJ9v1ik0cVukvTEKzaVSCDd/UU4kWE=
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be Zephyrus.local
To: Alissa Cooper <alissa@cooperw.in>, Mark Nottingham <mnot@mnot.net>, Robert Sparks <rjsparks@nostrum.com>
Cc: Carsten Bormann <cabo@tzi.org>, last-call@ietf.org, General Area Review Team <gen-art@ietf.org>, draft-nottingham-rfc7320bis.all@ietf.org, Martin Thomson <mt@lowentropy.net>
References: <3a7db097-84c0-4c44-aed0-51196a6a16b6@www.fastmail.com> <9F9A2298-0088-40B2-A69C-7F63D17EB8E3@nostrum.com> <A88B004F-6426-41BF-9711-4071A63637B5@mnot.net> <23E269D1-06A1-4EE6-B886-5E5B3824C27E@tzi.org> <4C01295C-6EDA-4C32-8BA3-BD8DA3B9C9A2@mnot.net> <94DB4F60-A4BD-4BFF-9587-673BC52A9361@cooperw.in>
From: Adam Roach <adam@nostrum.com>
Message-ID: <87b5e05a-4ac5-367c-7a3f-472be1d63530@nostrum.com>
Date: Tue, 21 Jan 2020 15:25:46 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <94DB4F60-A4BD-4BFF-9587-673BC52A9361@cooperw.in>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Resent-From: <alias-bounces@ietf.org>
Resent-To: mnot@mnot.net, adam@nostrum.com, mt@mozilla.com, art@ietf.org, mt@lowentropy.net
Resent-Message-Id: <20200121212616.517DB1200B8@ietfa.amsl.com>
Resent-Date: Tue, 21 Jan 2020 13:26:16 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/sfbjSPevWpE5x_HvnadWWUKgzGE>
Subject: Re: [art] [Last-Call] Genart last call review of draft-nottingham-rfc7320bis-02
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2020 21:26:16 -0000

On 1/21/20 10:49, Alissa Cooper wrote:
> I think a good solution here would be to add a sentence along the lines of the sentence above to the shepherd write-up. That way the rationale for the substitution is captured in the document’s history but not in the document itself.


Thanks for the suggestion. I have added corresponding text to the 
shepherd's write-up.

/a


From nobody Tue Jan 21 17:30:38 2020
Return-Path: <rg+ietf@randy.pensive.org>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF8B91200C3 for <art@ietfa.amsl.com>; Tue, 21 Jan 2020 17:30:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.597
X-Spam-Level: *
X-Spam-Status: No, score=1.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FORGED_RELAY_MUA_TO_MX=3.498, SPF_PASS=-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 c0vUeYZc2SAt for <art@ietfa.amsl.com>; Tue, 21 Jan 2020 17:30:35 -0800 (PST)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id 4943A12002F for <art@ietf.org>; Tue, 21 Jan 2020 17:30:35 -0800 (PST)
Received: from [99.111.97.181] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Tue, 21 Jan 2020 17:30:34 -0800
From: "Randall Gellens" <rg+ietf@randy.pensive.org>
To: "Ted Hardie" <ted.ietf@gmail.com>
Cc: "Applications and Real-Time Area Discussion" <art@ietf.org>, "Brian Rosen" <br@brianrosen.net>
Date: Tue, 21 Jan 2020 17:30:33 -0800
X-Mailer: MailMate (1.13.1r5671)
Message-ID: <4ABAA1B5-88DC-466B-8A98-B576B8D4535B@randy.pensive.org>
In-Reply-To: <CA+9kkMAWatHi0z4EXJEfvxtzX0ynQe4jNa7EckgyBMUSTpzrYw@mail.gmail.com>
References: <26C2AFDA-6CC1-4345-9978-1E2392750F94@randy.pensive.org> <CA+9kkMAWatHi0z4EXJEfvxtzX0ynQe4jNa7EckgyBMUSTpzrYw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/hVlPzHqPb_FUO2hnA39I_hKPzV4>
Subject: Re: [art] Registering the 'LoST-Validation' NAPTR Service Tag
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jan 2020 01:30:37 -0000

On 21 Jan 2020, at 9:29, Ted Hardie wrote:

> Hi Randy, Brian,
>
> Thanks for the message.  I took a quick look at the document, and 
> there are
> two things that might want consideration.  The first is this text, 
> which
> tells you that the bursty validation traffic and the real-time 
> functions
> may be performed by the same server:
>
>    A server identified using the 'LoST' service tag might
>    also perform the validation function (and might resolve to the same
>    URL as a server identified using the 'LoST-Validation' service 
> tag),
>    but the 'LoST-Validation' tag makes this explicit.
>
> The "tag makes this explicit." doesn't seem to quite cover what you
> want to say here.  Maybe:
>
> Because some services are configured to provide
> both real-time and validation functions, a server identified
> using the 'LoST' service tag may also perform the validation function.
> The 'Lost-Validation' service tag should, however, always be used
> first when seeking
> the validation service, as the two functions may be separate.
> Fallback to the 'LoST'
>
> may follow if the Lost-Validation service does not resolve.
>
>
> Alternatively, you might cut this text and rely on the text in section 
> 3.

I see the issue and I like your first suggested rewording, I think that 
makes it more clear.  Thank you.


>
> Second, the document's IANA considerations says this:
>
> IANA is requested to add 'LoST-Validation' to the S-NAPTR Application
>    Service Tag registry created by [RFC3958]  This tag serves as a
>    counter-part to the 'LoST' tag added by [RFC4848].
>
> 5.1.  U-NAPTR Registration
>
>    This document registers the following U-NAPTR application service
>    tag:
>
>       Application Service Tag: LoST
>
>       Defining Publication: This document.
>
> Should this be S-NAPTR and LoST-Validation, respectively, or am I 
> missing
> something?

The tag name is definitely a typo, thank you very much for catching it.  
The registry name I'm not sure about.  The reason for the mismatch is 
that IANA calls the registry "S-NAPTR Application Service Tags" while 
RFC 5222 calls it "U-NAPTR application service tag" and RFC 3958 calls 
it "S-NAPTR Application Service Tags".  So, honestly, I don't know what 
to call it.  I've changed the draft to consistently use "S-NAPTR" since 
that's what IANA calls it.

The updated draft is at 
https://www.ietf.org/internet-drafts/draft-gellens-lost-validation-01.txt

(For some reason, the submit tool won't let me submit the .xml file, it 
insists the name is invalid.)

--Randall

>
> regards,
>
> Ted
>
> On Sat, Jan 18, 2020 at 12:05 PM Randall Gellens 
> <rg+ietf@randy.pensive.org>
> wrote:
>
>> Working in NENA, we've identified a need to register a new S-NAPTR
>> service tag 'LoST-Validation'.
>>
>> Background: as some may recall, the key motivator for LoST was 
>> emergency
>> services, primarily the ability to lookup a service URN for a 
>> location
>> (i.e., map "URN:SERVICE:SOS" to a SIP URI for a PSAP for a specific
>> location), and secondarily the ability to validate a civic location
>> (i.e., validate that a civic address is unique, dispatchable, and 
>> meets
>> the requirements for the area). LoST provides the ability to do both.
>> NENA i3 (which defines NG9-1-1) makes extensive use of LoST. One 
>> thing
>> NENA i3 does that was not originally contemplated when LoST was
>> developed is to allow separation of the core mapping function of LoST
>> from the validation function. NENA i3 allows (but does not require)
>> these two services to be provided separately (with the motivation 
>> that
>> mapping is a time-crucial service done during emergency call setup,
>> while validation is performed as data is provisioned into entities 
>> and
>> is not time-crucial, so a provider might potentially provision and
>> operate these two services differently). LoST uses U-NAPTR 
>> Application
>> Unique Strings rather than URIs to refer to other LoST servers. There 
>> is
>> currently one U-NAPTR service tag for LoST ("LoST"). In order to be 
>> able
>> to separate service mapping from location validation, a second 
>> service
>> tag is needed. Otherwise an entity can't tell from an Application 
>> Unique
>> String which service is available and can't resolve an Application
>> Unique String into a URI for a LoST server that assuredly is willing 
>> to
>> perform location validation. We therefore propose to define
>> "LoST-Validation" as a service tag. This will allow an entity to 
>> locate
>> a LoST server willing to perform civic location validation, leaving
>> "LoST" as the service tag for core service mapping.  (Of course, a 
>> LoST
>> server located using the 'LoST' service tag might offer both mapping 
>> and
>> validation, but the ability to use 'LoST-Validation' in NAPTR records
>> makes explicit which LoST servers are willing to do validation.)
>>
>> The Service Tags registry rules that require an RFC to add a tag, so 
>> I
>> have submitted a small RFC to do this:
>> https://www.ietf.org/internet-drafts/draft-gellens-lost-validation-00.txt
>>
>> Comments, feedback, etc. are appreciated.
>>
>> --Randall
>>
>> _______________________________________________
>> art mailing list
>> art@ietf.org
>> https://www.ietf.org/mailman/listinfo/art
>>




--Randall


From nobody Wed Jan 22 07:52:28 2020
Return-Path: <julian.reschke@gmx.de>
X-Original-To: expand-draft-nottingham-rfc7320bis.all@virtual.ietf.org
Delivered-To: art@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id 06AC81200D8; Wed, 22 Jan 2020 07:52:16 -0800 (PST)
X-Original-To: xfilter-draft-nottingham-rfc7320bis.all@ietfa.amsl.com
Delivered-To: xfilter-draft-nottingham-rfc7320bis.all@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D9CA1200BA; Wed, 22 Jan 2020 07:52:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
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 Q5MbGnilCjzK; Wed, 22 Jan 2020 07:52:13 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (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 6F71E1200D8; Wed, 22 Jan 2020 07:52:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1579708322; bh=yYLK9iZlreEypVTnt5cA/KkDfo9gDtLI7GKrdeRxD0Q=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=AbOz4uerZbaIqYHq7VNE8sDF4JwJ2oqL2bxy1R0B87GuNy4VaTegQdzjjcxH2A2GZ YY8mxTfITwSg7u+261KSa7ZyH+wp8tbIh5TLc2RTiIsvPp1cF7HPc0VXZ+JYd3HxMo C4EtOdCPwWpaQrsXBa9WIHfhS1gWaZdY1KHvXCIo=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.1.81] ([217.91.35.233]) by mail.gmx.com (mrgmx104 [212.227.17.168]) with ESMTPSA (Nemesis) id 1M42jQ-1iuIIU36vo-00062y; Wed, 22 Jan 2020 16:52:02 +0100
To: Robert Sparks <rjsparks@nostrum.com>, gen-art@ietf.org
Cc: last-call@ietf.org, draft-nottingham-rfc7320bis.all@ietf.org
References: <157480843342.13609.14136034204321908736@ietfa.amsl.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <596edafe-4ea8-8ef0-42c1-67911423afef@gmx.de>
Date: Wed, 22 Jan 2020 16:52:00 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1
MIME-Version: 1.0
In-Reply-To: <157480843342.13609.14136034204321908736@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:N2E3/TDG5cBtqVTyFYAqQxwwgA7OamGysab1jwx++zYfu+qShUa ZT230Yl1HQgGmstHIEmOoBwV4embiw7tptsGP90iU+n2N+YjA6qdmwCOuvZ/CXHPWtnyiZL xFYIM2+JQrqlE4nPc2MxawaHQVmwcFtjFnXOx4G3jcuj+htuM3Fnp5MjwV479qAuZUBdXxx LuoGIXy272ltNL0L2CicQ==
X-UI-Out-Filterresults: notjunk:1;V03:K0:+LrPpMHpMc8=:sN/uh0C1K8CmL4prvJ1V9I /crz2pXxIcvJIbUf3IRUm40MbcEhm/xWww1m76IQGc88y7LM4L4wSMlByUp/iZhV/Vs8a+WBI JHtgSYbDr8uhJV+zpvxpYTdLwnGb2pnop9/doTRlxS5zjiCogjyvjrxkZsRx5qCL043BsWnQA 0Omm8vgdi3MyjhDI7Htk1HGpLDXWgRyY33V8Gt/lgwW3zGP+k4akD8gnT7/dbxS/UGv4Qg2Pg CfgtcgWZ6WXWiXo+rsznYezBLClFVDbJyoKnQmGQkU8y9Y7mwOlVHENXptnBYcf1fQ+6Bn7sV ncK6xQIuwSLeXWOBmvKkQx9unUBuSeFlm+wsuZJa+5IXbNU1e9AW7wW8IdHxHoq+atmaW54JJ i+dJYQMaBR7q273loLEZLXUDg9OjpBonQczpsNPPf2IPs89xwVK90EbIdR7juSCG3L/GDcwu2 gejPgKPzrZtTSVxxfMw/qcfOcDFQ5oZAT51mKGztvgGH6R1t9AsLn5+uA8Szxzs0XEBjnBVt1 Pg6Ss9F8LNg4nrGZSV3rWPC8dSVko9aT8sKJVuHWOjosDI4rE+slwiy8sQ7o5CYc+OyneSVW7 jZ0AUzfrkaoj87Mh/XuYVSoERoZxndxD8k6fMw+k5IDjFJzk+QL76ofbsyx7yzQ+S45yqu3VC bta7TOOqEGL1VGnSyr5B3usc31QO4Ql3YcbsTop19SC+QqJYoSI2XSVyHkFNOA1ybL3vmQNyj hF7OmDi2XiiAEDS3OXRLMvX4ckE/n/TJFH9Yi7n9tGS4K7cyNY2pjfDzJlUcRB9GXjiZk4Z7q H16oS8ZlokKUjymrIEcK/mWIwILu9EgK5fA8slpAKROgZv16nIThzIyKNGKJpiSMisniu5jmb a2GO2ITXh7KCztuWYgJDJh36HeihaWLCWAGf8lNDH9sSkMIagFIodaNwtFtnU6pm248BxSkb1 LhS6z+U3Y9OZ4vBSHnRzFqL3dXInu9BT1LZiKsJajvZmbYsSBkkmJzhhG5shJIr4X9D/EjYgv ys9cQkFV8PY2PJMIrdOrkBACz4JngTh9AbCxFK4FpiSBj95BBAyhjq0EENOdTH0H6LLWNTNLM PUJwLvjYe3BEDaZgQFGO1T8OF42j/CgZNWaaM4PRE+vD72KVz/DzHT5lnL1duV3oqg0jp8f1X HRrJ0BaQfyvoV1s3revISOuzREc1RliVP0Ldjo9FlQOWZFU+JGmHSRU+imXHR4afH0/DQ=
Resent-From: <alias-bounces@ietf.org>
Resent-To: mnot@mnot.net, adam@nostrum.com, mt@mozilla.com, art@ietf.org, mt@lowentropy.net
Resent-Message-Id: <20200122155216.06AC81200D8@ietfa.amsl.com>
Resent-Date: Wed, 22 Jan 2020 07:52:16 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/XEZAPudeQLHr1-AqSyi2BsSHvgA>
Subject: Re: [art] Genart last call review of draft-nottingham-rfc7320bis-02
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jan 2020 15:52:16 -0000

On 26.11.2019 23:47, Robert Sparks via Datatracker wrote:
> ...
> It might be good to capture in the "Note to Readers" that the RFC Editor=
 should
> also remove Section 6.3 (URIs) since all the references to them will be =
removed
> with the removal of this Note.
> ...

FWIW, that's not needed as that section is inserted by xml2rfc; remove
the references, and the section will disappear automatically.

Best regards, Julian

PS: I truly believe that xml2rfc should not insert this section anyway.


From nobody Wed Jan 22 08:45:50 2020
Return-Path: <alissa@cooperw.in>
X-Original-To: expand-draft-nottingham-rfc7320bis.all@virtual.ietf.org
Delivered-To: art@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id ACFCF120124; Wed, 22 Jan 2020 08:45:38 -0800 (PST)
X-Original-To: xfilter-draft-nottingham-rfc7320bis.all@ietfa.amsl.com
Delivered-To: xfilter-draft-nottingham-rfc7320bis.all@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 533D6120143; Wed, 22 Jan 2020 08:45:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=C/0dXyio; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=WdV9FGWP
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 DA5PQANmsFb4; Wed, 22 Jan 2020 08:45:34 -0800 (PST)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 82076120124; Wed, 22 Jan 2020 08:45:34 -0800 (PST)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id 557C0572; Wed, 22 Jan 2020 11:45:33 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Wed, 22 Jan 2020 11:45:33 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-type:content-transfer-encoding:from:mime-version:subject :date:message-id:references:cc:in-reply-to:to; s=fm2; bh=i90/h5b KWMm/kjkzvXRyDF+x2/dY2/UmYpLUfWEqzXI=; b=C/0dXyio6vuYd72sQJrVaGH etyKHSsdC03cdqWkvuOClsoVAKotoycnn59HaLCuymco0rWHGYe17dD2ywARDSFd I3nnhxzx8oSbAH3DC3ByUL4pi4cXyWcBY9faBV589CS/Via3nECy7LeLFZr9PrkH 1baffAtwOf6hMQXVscWYMbUNLxlJqvLw8ZetdUQE/nQgseTNu/CvgIB+du7LKc1k Vh6V4ieq16ubxYfMen5WIE6fXfzIzINQce+FGUJ10vwX4DkQNzKELO6w88/VpAM1 2/WI3W0+ifST0TgGgFDcJdhvTM3AjqF0rrKYHmpbI5HARg3rpc+KXmsaEHtIsAg= =
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=i90/h5bKWMm/kjkzvXRyDF+x2/dY2/UmYpLUfWEqz XI=; b=WdV9FGWPJeF3V4XqSVNzs/EKWGBwJ9QN6lmJybKJArpatecekf7koWnhV AfMXgXXa7tIpAnHRBf0TG5SOymPbZJ1Y6qB4TdXJwn/DX6yfGKJAd+DossUbGdcN V/hKYUz8XtVayI3ASeP/oA2qku1zyxTCVAaPno/XmccXeXXq88ykj8LZDuNYREQe A+7P+JSHpi6OtIEDnTaaPWWslMJ98ObdcFkio3gOpbZfEz+bvLvUtNDl8D1ea/T7 p1rDTiOcvDW5q1nZ65bRwqWplubSY+o9ZEqKr3znXRekhpW1I+U08N4jJowH97GY x6SE9YgEmVCi7xj/ygTouO56777mQ==
X-ME-Sender: <xms:LHwoXt38mS8kuN6RVzzecFCWSmgM92zbgzVeStTI0pdlnQfJyGFbLg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrvddtgdekjecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpegtgffhggfufffkfhgjvffosehtqhhmtdhhtdejnecuhfhrohhmpeetlhhishhs rgcuvehoohhpvghruceorghlihhsshgrsegtohhophgvrhifrdhinheqnecukfhppeduie eirddujedtrdefuddrgeeknecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehm rghilhhfrhhomheprghlihhsshgrsegtohhophgvrhifrdhinh
X-ME-Proxy: <xmx:LHwoXg1i4P2-IMdyhgdjhzyM29qSF2xs0pz29KBo9g_z026Vax3oIg> <xmx:LHwoXtc3vyJFyQc9JpuooHBge8FBsHQcBPXfVQzdKUnLvai18QzjHQ> <xmx:LHwoXjdLLlfr3NRFY1LEjFR2znuCLYVjp_x0GSmFegWkqMp9DaI-gw> <xmx:LHwoXt0XB4BXHa4pH0-fixwJmdbOGO9IVSNEHwpMoIZz5o4Hc24-xg>
Received: from [10.54.46.129] (mobile-166-170-31-48.mycingular.net [166.170.31.48]) by mail.messagingengine.com (Postfix) with ESMTPA id 4BBBF3280063; Wed, 22 Jan 2020 11:45:32 -0500 (EST)
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: Alissa Cooper <alissa@cooperw.in>
Mime-Version: 1.0 (1.0)
Date: Wed, 22 Jan 2020 11:45:30 -0500
Message-Id: <9B7566E0-21F9-45EC-ACEA-665070AC54B2@cooperw.in>
References: <87b5e05a-4ac5-367c-7a3f-472be1d63530@nostrum.com>
Cc: Mark Nottingham <mnot@mnot.net>, Robert Sparks <rjsparks@nostrum.com>, Carsten Bormann <cabo@tzi.org>, last-call@ietf.org, General Area Review Team <gen-art@ietf.org>, draft-nottingham-rfc7320bis.all@ietf.org, Martin Thomson <mt@lowentropy.net>
In-Reply-To: <87b5e05a-4ac5-367c-7a3f-472be1d63530@nostrum.com>
To: Adam Roach <adam@nostrum.com>
X-Mailer: iPhone Mail (17C54)
Resent-From: <alias-bounces@ietf.org>
Resent-To: mnot@mnot.net, adam@nostrum.com, mt@mozilla.com, art@ietf.org, mt@lowentropy.net
Resent-Message-Id: <20200122164538.ACFCF120124@ietfa.amsl.com>
Resent-Date: Wed, 22 Jan 2020 08:45:38 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/EkbNUxZoOb1o5muJQggy2Qak908>
Subject: Re: [art] [Last-Call] Genart last call review of draft-nottingham-rfc7320bis-02
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jan 2020 16:45:39 -0000

Thanks!

> On Jan 21, 2020, at 4:27 PM, Adam Roach <adam@nostrum.com> wrote:
>=20
> =EF=BB=BFOn 1/21/20 10:49, Alissa Cooper wrote:
>> I think a good solution here would be to add a sentence along the lines o=
f the sentence above to the shepherd write-up. That way the rationale for th=
e substitution is captured in the document=E2=80=99s history but not in the d=
ocument itself.
>=20
>=20
> Thanks for the suggestion. I have added corresponding text to the shepherd=
's write-up.
>=20
> /a
>=20


From nobody Wed Jan 22 19:14:52 2020
Return-Path: <noreply@ietf.org>
X-Original-To: art@ietf.org
Delivered-To: art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D8C31200A1; Wed, 22 Jan 2020 19:14:50 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Benjamin Kaduk via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-nottingham-rfc7320bis@ietf.org, art@ietf.org, mt@mozilla.com, mt@lowentropy.net
X-Test-IDTracker: no
X-IETF-IDTracker: 6.116.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Benjamin Kaduk <kaduk@mit.edu>
Message-ID: <157974929057.12202.17704666202770133539.idtracker@ietfa.amsl.com>
Date: Wed, 22 Jan 2020 19:14:50 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/v6zLS2230WkDR4hNNERsa7CanZs>
Subject: [art] Benjamin Kaduk's Yes on draft-nottingham-rfc7320bis-03: (with COMMENT)
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2020 03:14:51 -0000

Benjamin Kaduk has entered the following ballot position for
draft-nottingham-rfc7320bis-03: Yes

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-nottingham-rfc7320bis/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thanks for the well-written document!  A few minor comments:

Section 2.1

   Applications and Extensions can require use of specific URI
   scheme(s); for example, it is perfectly acceptable to require that an
   Application support 'http' and 'https' URIs.  However, Applications
   ought not preclude the use of other URI schemes in the future, unless
   they are clearly only usable with the nominated schemes.

I'm having a little trouble squaring "can require specific schemes" with
"ought not preclude the use of other schemes".  How accurate would it be
to try to summarize this guidance as "specify what properties you need
the scheme to have, not the scheme itself"?

Section 2.4

side note: the discussion we give here about the flaws in assumptions
about query parameters named "sig" is more complete than the earlier
such discussion in Section 1; the earlier treatment is slightly
confusing without the additional context present here.  It's not really
clear that a forward reference would be appropriate, though, hence this
is just a side note.

Section 3

   Specifying more elaborate structures in an attempt to avoid
   collisions is not an acceptable solution, and does not address the
   issues in Section 1.  For example, prefixing query parameters with
   "myapp_" does not help, because the prefix itself is subject to the
   risk of collision (since it is not "reserved").

nit: I'm not sure what purpose the scare-quotes on "reserved" serve.
nit^2: the previous paragraph uses single-quotes around 'reserved'.



From nobody Wed Jan 22 22:57:40 2020
Return-Path: <mnot@mnot.net>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB3AB120115; Wed, 22 Jan 2020 22:57:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=sTCXe3lL; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=GOu7rBOA
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 hI53xrfGa3WF; Wed, 22 Jan 2020 22:57:30 -0800 (PST)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B79012003F; Wed, 22 Jan 2020 22:57:30 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 6764E2221C; Thu, 23 Jan 2020 01:57:28 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Thu, 23 Jan 2020 01:57:28 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm1; bh=5 tCr+OKPa0980ocqbEqvIU0qGWybwFqjPZKgI/8J/Fs=; b=sTCXe3lLIuxJhf63w tZeJfAVZOyZ5eLI++UBXx5fHBIuzEKBhlcyvhWNqqNDYVbVjXJVGJYzF9HD1oi6p /f29N7ZD5d62PH3Di+fXOJkOsbL2U6bsNHbba7pu0CO9Iegv/UfLGH9709wu63ZU R4DvZ0m7Ow1FCfnd/iXS9Cf3pHZ5hptf3/Sjg3QpfZXrCk4UUx4uIRKy3leg00Bn aXNJm6RbfVR6aMGC6V6lRdzozvqOlnwm5PkJPuVr5+B+4xPBlEWhOMv1Tk2wutoz hj4H5E5JZ7fGKfw/5e81eddkqWhOcURPbU+PBkDJG/4Jz158RAC2DbPOBHDyRBJt SCRiQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=5tCr+OKPa0980ocqbEqvIU0qGWybwFqjPZKgI/8J/ Fs=; b=GOu7rBOApi5PDew7IRtz0bFePG82M5OG4yi6p/maapNpp8W8oDnE/nPvr 2WEUfQJalvHq+ltPLn2heIsd1I/wGrpI9N1d1tiC/23byopHs2bUTb1pTYrsM3+t uKRp1RucdEHtE+N19sgdWBvXq5LFGb6KKOP+muXjawiLxD/5/j7Cv1+lsR1rqQGc PLFUUHBHzs+t+9DQg165cyVGFPfXBdkriVyH92WMppgKb4dw/f947p7sh1T2+VxI casqBmAvsV7XRLtXE/GMLqm3dfnRdziefn2zjE3//fLEDEAKG/fsEx8y2tlVU91I 7rdjZF+vGFVTX4MW0kCe8O7ZHyErg==
X-ME-Sender: <xms:10MpXnt9fUYwB0vDmpajOrPvKhPJlwjgp5ZEsawaCwvunxWymKUNcQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrvddugdeljecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpegtggfuhfgjfffgkfhfvffosehtqhhmtdhhtddvnecuhfhrohhmpeforghrkhcu pfhothhtihhnghhhrghmuceomhhnohhtsehmnhhothdrnhgvtheqnecuffhomhgrihhnpe hmnhhothdrnhgvthenucfkphepudduledrudejrdduheekrddvhedunecuvehluhhsthgv rhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhhnohhtsehmnhhothdrnh gvth
X-ME-Proxy: <xmx:10MpXv7SskyX_v0j6wS3z62YDwkapt-N_dfzYeM6Nx5JO-HsXogzCQ> <xmx:10MpXjsWo2nu-kFNhx_NnJYyakhu9W1KglP1_jdIiwhyFOX3_7ZqAQ> <xmx:10MpXhL0wJUBIfepZy_yadhVEcTf4rJ1PlxhFXRaGIiHeVTeVVC9dA> <xmx:2EMpXvWlDIcf171bB4TB27FPSXnkBGEhEd6x3WnsFn2OLWg_SsYpsQ>
Received: from macbook-pro.mnot.net (unknown [119.17.158.251]) by mail.messagingengine.com (Postfix) with ESMTPA id A8B373060ACF; Thu, 23 Jan 2020 01:57:25 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.40.2.2.4\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <157974929057.12202.17704666202770133539.idtracker@ietfa.amsl.com>
Date: Thu, 23 Jan 2020 17:57:23 +1100
Cc: The IESG <iesg@ietf.org>, draft-nottingham-rfc7320bis@ietf.org, art@ietf.org, Martin Thomson <mt@mozilla.com>, Martin Thomson <mt@lowentropy.net>
Content-Transfer-Encoding: quoted-printable
Message-Id: <0FD86723-7E98-4C8A-BFD5-83A7667FB065@mnot.net>
References: <157974929057.12202.17704666202770133539.idtracker@ietfa.amsl.com>
To: Benjamin Kaduk <kaduk@mit.edu>
X-Mailer: Apple Mail (2.3608.40.2.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/PQ14X-ExFQZ9YdIv61av1hLgAkc>
Subject: Re: [art] Benjamin Kaduk's Yes on draft-nottingham-rfc7320bis-03: (with COMMENT)
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2020 06:57:33 -0000

Hi Ben,

> On 23 Jan 2020, at 2:14 pm, Benjamin Kaduk via Datatracker =
<noreply@ietf.org> wrote:
>=20
> Section 2.1
>=20
>   Applications and Extensions can require use of specific URI
>   scheme(s); for example, it is perfectly acceptable to require that =
an
>   Application support 'http' and 'https' URIs.  However, Applications
>   ought not preclude the use of other URI schemes in the future, =
unless
>   they are clearly only usable with the nominated schemes.
>=20
> I'm having a little trouble squaring "can require specific schemes" =
with
> "ought not preclude the use of other schemes".  How accurate would it =
be
> to try to summarize this guidance as "specify what properties you need
> the scheme to have, not the scheme itself"?

Not really.=20

For example - my application might require implementations to support =
http schemes, but shouldn't say "never use the foo scheme."


> Section 2.4
>=20
> side note: the discussion we give here about the flaws in assumptions
> about query parameters named "sig" is more complete than the earlier
> such discussion in Section 1; the earlier treatment is slightly
> confusing without the additional context present here.  It's not =
really
> clear that a forward reference would be appropriate, though, hence =
this
> is just a side note.

Ack. Will take another look.


> Section 3
>=20
>   Specifying more elaborate structures in an attempt to avoid
>   collisions is not an acceptable solution, and does not address the
>   issues in Section 1.  For example, prefixing query parameters with
>   "myapp_" does not help, because the prefix itself is subject to the
>   risk of collision (since it is not "reserved").
>=20
> nit: I'm not sure what purpose the scare-quotes on "reserved" serve.
> nit^2: the previous paragraph uses single-quotes around 'reserved'.

The RFC Production Centre is well-acquainted with my penchant for "scare =
quotes", and will "deal" with me (and them) later.

Thanks,


--
Mark Nottingham   https://www.mnot.net/


From nobody Thu Jan 23 07:19:36 2020
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: art@ietf.org
Delivered-To: art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E00BD120844; Thu, 23 Jan 2020 07:19:34 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <art@ietf.org>, <draft-nottingham-rfc7320bis@ietf.org>, <adam@nostrum.com>, <mt@lowentropy.net>, <mt@mozilla.com>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.116.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <157979277491.22674.13320226498630440562.idtracker@ietfa.amsl.com>
Date: Thu, 23 Jan 2020 07:19:34 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/VVknsQyMBkanXZ_quWyNInVcx4k>
Subject: [art] Datatracker State Update Notice: <draft-nottingham-rfc7320bis-03.txt>
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2020 15:19:35 -0000

IESG state changed:

New State: Approved-announcement to be sent

(The previous state was IESG Evaluation)


Datatracker URL: https://datatracker.ietf.org/doc/draft-nottingham-rfc7320bis/


From nobody Tue Jan 28 11:41:38 2020
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: art@ietf.org
Delivered-To: art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DD8A7120024; Tue, 28 Jan 2020 11:41:30 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.116.1
Auto-Submitted: auto-generated
Precedence: bulk
Cc: The IESG <iesg@ietf.org>, adam@nostrum.com, art@ietf.org, draft-nottingham-rfc7320bis@ietf.org, mt@mozilla.com, mt@lowentropy.net, rfc-editor@rfc-editor.org
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Message-ID: <158024049090.4720.17738164691695007423.idtracker@ietfa.amsl.com>
Date: Tue, 28 Jan 2020 11:41:30 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/s2Pu9uNL4LLt5aNkWXYmW5Msa7I>
Subject: [art] Protocol Action: 'URI Design and Ownership' to Best Current Practice (draft-nottingham-rfc7320bis-03.txt)
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2020 19:41:31 -0000

The IESG has approved the following document:
- 'URI Design and Ownership'
  (draft-nottingham-rfc7320bis-03.txt) as Best Current Practice

This document has been reviewed in the IETF but is not the product of an IETF
Working Group.

The IESG contact person is Adam Roach.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-nottingham-rfc7320bis/





Technical Summary

   This document provides guidance on the specification of URI
   substructure in standards.

Working Group Summary

  This document is an AD-sponsored update to the existing BCP 190, based on
  feedback from the IETF community. During the processing of
  draft-ietf-trans-rfc6962-bis, the TRANS working group highlighted certain
  difficulties caused by one specific restriction that BCP 190 has
  historically imposed on the use of URL paths in standard protocols. After
  face-to-face discussion with the HTTPBIS working group in Montreal, and
  subsequent conversations on the ART-area mailing list, a clear consensus
  emerged to relax specific provisions of BCP 190 in ways that do not cause
  substantial damage to the URL namespace owners' ability to manage such
  namespaces.

Document Quality

  The document received significant feedback and support during its
  development. While there was some distress expressed over the
  basic concept of BCPs that restrict protocol development in any
  way -- and implicitly calling for a full deprecation of BCP 190
  and similar documents -- no objections were raised to the
  specific relaxations represented by this new version.

Personnel

  Martin Thomson is the document shepherd.
  Adam Roach is the responsible AD.


From nobody Tue Jan 28 14:07:36 2020
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: art@ietf.org
Delivered-To: art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 28990120018; Tue, 28 Jan 2020 14:07:35 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <art@ietf.org>, <draft-nottingham-rfc7320bis@ietf.org>, <adam@nostrum.com>, <mt@lowentropy.net>, <mt@mozilla.com>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.116.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <158024925516.25624.11849438164435201014.idtracker@ietfa.amsl.com>
Date: Tue, 28 Jan 2020 14:07:35 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/dQO4N_eE1eyd2XfpNMCzd1Akjuc>
Subject: [art] Datatracker State Update Notice: <draft-nottingham-rfc7320bis-03.txt>
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2020 22:07:35 -0000

IANA action state changed to "In Progress"
Datatracker URL: https://datatracker.ietf.org/doc/draft-nottingham-rfc7320bis/


From nobody Tue Jan 28 16:51:27 2020
Return-Path: <rg+ietf@randy.pensive.org>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2AA3C120106 for <art@ietfa.amsl.com>; Tue, 28 Jan 2020 16:51: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, FORGED_RELAY_MUA_TO_MX=3.799, 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 3EibcsFdu_Bh for <art@ietfa.amsl.com>; Tue, 28 Jan 2020 16:51:24 -0800 (PST)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id E88611200B3 for <art@ietf.org>; Tue, 28 Jan 2020 16:51:23 -0800 (PST)
Received: from [99.111.97.181] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Tue, 28 Jan 2020 16:51:23 -0800
From: "Randall Gellens" <rg+ietf@randy.pensive.org>
To: "Ted Hardie" <ted.ietf@gmail.com>, "Applications and Real-Time Area Discussion" <art@ietf.org>
Cc: "Brian Rosen" <br@brianrosen.net>
Date: Tue, 28 Jan 2020 16:51:22 -0800
X-Mailer: MailMate (1.13.1r5671)
Message-ID: <8B4763EE-63C2-448C-AB70-BC9EE5D91D7B@randy.pensive.org>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/ACV812IAaaUOsXr4T3_SA4w70ys>
Subject: [art] Please review: Registering the 'LoST-Validation' NAPTR Service Tag
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2020 00:51:25 -0000

Version -02 of the draft was uploaded today.  (Version -01 that 
addressed Ted's comments and some glitches I noticed was published on 
the 21st.)  This is a very short draft that registers a new NAPTR 
service tag.  I appreciate any reviews.

https://www.ietf.org/internet-drafts/draft-gellens-lost-validation-02.txt

Thanks!

On 21 Jan 2020, at 17:30, Randall Gellens wrote:

> On 21 Jan 2020, at 9:29, Ted Hardie wrote:
>
>> Hi Randy, Brian,
>>
>> Thanks for the message.  I took a quick look at the document, and 
>> there are
>> two things that might want consideration.  The first is this text, 
>> which
>> tells you that the bursty validation traffic and the real-time 
>> functions
>> may be performed by the same server:
>>
>>    A server identified using the 'LoST' service tag might
>>    also perform the validation function (and might resolve to the 
>> same
>>    URL as a server identified using the 'LoST-Validation' service 
>> tag),
>>    but the 'LoST-Validation' tag makes this explicit.
>>
>> The "tag makes this explicit." doesn't seem to quite cover what you
>> want to say here.  Maybe:
>>
>> Because some services are configured to provide
>> both real-time and validation functions, a server identified
>> using the 'LoST' service tag may also perform the validation 
>> function.
>> The 'Lost-Validation' service tag should, however, always be used
>> first when seeking
>> the validation service, as the two functions may be separate.
>> Fallback to the 'LoST'
>>
>> may follow if the Lost-Validation service does not resolve.
>>
>>
>> Alternatively, you might cut this text and rely on the text in 
>> section 3.
>
> I see the issue and I like your first suggested rewording, I think 
> that makes it more clear.  Thank you.
>
>
>>
>> Second, the document's IANA considerations says this:
>>
>> IANA is requested to add 'LoST-Validation' to the S-NAPTR Application
>>    Service Tag registry created by [RFC3958]  This tag serves as a
>>    counter-part to the 'LoST' tag added by [RFC4848].
>>
>> 5.1.  U-NAPTR Registration
>>
>>    This document registers the following U-NAPTR application service
>>    tag:
>>
>>       Application Service Tag: LoST
>>
>>       Defining Publication: This document.
>>
>> Should this be S-NAPTR and LoST-Validation, respectively, or am I 
>> missing
>> something?
>
> The tag name is definitely a typo, thank you very much for catching 
> it.  The registry name I'm not sure about.  The reason for the 
> mismatch is that IANA calls the registry "S-NAPTR Application Service 
> Tags" while RFC 5222 calls it "U-NAPTR application service tag" and 
> RFC 3958 calls it "S-NAPTR Application Service Tags".  So, honestly, I 
> don't know what to call it.  I've changed the draft to consistently 
> use "S-NAPTR" since that's what IANA calls it.
>
> The updated draft is at 
> https://www.ietf.org/internet-drafts/draft-gellens-lost-validation-01.txt
>
> (For some reason, the submit tool won't let me submit the .xml file, 
> it insists the name is invalid.)
>
> --Randall
>
>>
>> regards,
>>
>> Ted
>>
>> On Sat, Jan 18, 2020 at 12:05 PM Randall Gellens 
>> <rg+ietf@randy.pensive.org>
>> wrote:
>>
>>> Working in NENA, we've identified a need to register a new S-NAPTR
>>> service tag 'LoST-Validation'.
>>>
>>> Background: as some may recall, the key motivator for LoST was 
>>> emergency
>>> services, primarily the ability to lookup a service URN for a 
>>> location
>>> (i.e., map "URN:SERVICE:SOS" to a SIP URI for a PSAP for a specific
>>> location), and secondarily the ability to validate a civic location
>>> (i.e., validate that a civic address is unique, dispatchable, and 
>>> meets
>>> the requirements for the area). LoST provides the ability to do 
>>> both.
>>> NENA i3 (which defines NG9-1-1) makes extensive use of LoST. One 
>>> thing
>>> NENA i3 does that was not originally contemplated when LoST was
>>> developed is to allow separation of the core mapping function of 
>>> LoST
>>> from the validation function. NENA i3 allows (but does not require)
>>> these two services to be provided separately (with the motivation 
>>> that
>>> mapping is a time-crucial service done during emergency call setup,
>>> while validation is performed as data is provisioned into entities 
>>> and
>>> is not time-crucial, so a provider might potentially provision and
>>> operate these two services differently). LoST uses U-NAPTR 
>>> Application
>>> Unique Strings rather than URIs to refer to other LoST servers. 
>>> There is
>>> currently one U-NAPTR service tag for LoST ("LoST"). In order to be 
>>> able
>>> to separate service mapping from location validation, a second 
>>> service
>>> tag is needed. Otherwise an entity can't tell from an Application 
>>> Unique
>>> String which service is available and can't resolve an Application
>>> Unique String into a URI for a LoST server that assuredly is willing 
>>> to
>>> perform location validation. We therefore propose to define
>>> "LoST-Validation" as a service tag. This will allow an entity to 
>>> locate
>>> a LoST server willing to perform civic location validation, leaving
>>> "LoST" as the service tag for core service mapping.  (Of course, a 
>>> LoST
>>> server located using the 'LoST' service tag might offer both mapping 
>>> and
>>> validation, but the ability to use 'LoST-Validation' in NAPTR 
>>> records
>>> makes explicit which LoST servers are willing to do validation.)
>>>
>>> The Service Tags registry rules that require an RFC to add a tag, so 
>>> I
>>> have submitted a small RFC to do this:
>>> https://www.ietf.org/internet-drafts/draft-gellens-lost-validation-00.txt
>>>
>>> Comments, feedback, etc. are appreciated.
>>>
>>> --Randall


From nobody Wed Jan 29 12:04:19 2020
Return-Path: <ted.ietf@gmail.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD375120850 for <art@ietfa.amsl.com>; Wed, 29 Jan 2020 12:04:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level: 
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 joNxVdsts11D for <art@ietfa.amsl.com>; Wed, 29 Jan 2020 12:04:04 -0800 (PST)
Received: from mail-oi1-x22a.google.com (mail-oi1-x22a.google.com [IPv6:2607:f8b0:4864:20::22a]) (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 F1B43120127 for <art@ietf.org>; Wed, 29 Jan 2020 12:03:30 -0800 (PST)
Received: by mail-oi1-x22a.google.com with SMTP id z2so1018943oih.6 for <art@ietf.org>; Wed, 29 Jan 2020 12:03:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=OkflGKSrkuVdk2IVn1nPBLG4+Vj16IWbluMahyBU8Wk=; b=K6uQEt2mkTxnAJ7P61yhdRC1ChLoum7Od8RF8WKcOrlvPp7ONqdswzmWBN8X/7aGwj SR8DXLv48lzM+GSqTOuQAeibWn72XQ7fvQH3U3FVGCR9EpQOfm0esO95sk5tqsH1CXQO qpmUSN9iqaMmKgrn/Z9Q2cQjs4w+KE2x3l77C7amNG0d0PTnkpg8xn8Kkl0HODO/60+V QxkOuWOenh73WhCsOhpYSTinQzjkDJjUKHJPbunsIUInEydgZY7NA6WcjmLgT5kw0qR1 x1ltSTUhBJpg7NkDgl4R6kb69PsJ+pmGQoj0yMmsr/tgq1ZoDFGg+SSm/52PAaz/ZcWI aQpg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=OkflGKSrkuVdk2IVn1nPBLG4+Vj16IWbluMahyBU8Wk=; b=NEoLBfScesBQWRShJ6LYBMae5LNqi0gC18j1tNTScKjUNOJ7ioOvi6TtX6nkm5oEUb jtV6MEbvm+b8SleUoMl0xmz00VzF/EFWKcuCwjJqw294P+8FrH4WfAFLJbaTnH4zVzFj 9rmPsobAhe7rXdll93VsKKn6xOlycRPhSY+aR1rSYelcHFGn1tDeM9QKabAZya14G6wm HIFEPFyYwCAz5sYOoOIOOnIoMdW5PITwji91sONI3E69jHAcY7+jsLLEwXbyCmEkA5/F gVBj8Q2IT4copJx0bDAZVT8wTvLYXGA7DURr7HbUfD2XrviGzG0dudAxUjG9xWiy1aN0 jHcQ==
X-Gm-Message-State: APjAAAUT0zlOnU038FplOdBROck+UgWnFb3jimsQ8IxPF+rx4WSaokPl 9ZbfSROkVjdd8vTmlRdxKzSms+3fSbK2uPtHjDqOKvjj
X-Google-Smtp-Source: APXvYqxpvK128HsYkcFTk4PJl8dQP3fToe8DVIIEfjQlNwyqEccPp1j8kf207Th8fLaOk31oPnTxnsVYLzEjQPxeRPk=
X-Received: by 2002:a54:448b:: with SMTP id v11mr458427oiv.74.1580328210044; Wed, 29 Jan 2020 12:03:30 -0800 (PST)
MIME-Version: 1.0
References: <8B4763EE-63C2-448C-AB70-BC9EE5D91D7B@randy.pensive.org>
In-Reply-To: <8B4763EE-63C2-448C-AB70-BC9EE5D91D7B@randy.pensive.org>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Wed, 29 Jan 2020 12:03:04 -0800
Message-ID: <CA+9kkMA_-dBg5gsGJJ2Tobr4Pon2B6YpoY80ugP3kBVvgSw2zw@mail.gmail.com>
To: Randall Gellens <rg+ietf@randy.pensive.org>
Cc: Applications and Real-Time Area Discussion <art@ietf.org>, Brian Rosen <br@brianrosen.net>
Content-Type: multipart/alternative; boundary="000000000000969c5d059d4cd52f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/6cTVD-O6r5J3x4OSGopvJHBIh3k>
Subject: Re: [art] Please review: Registering the 'LoST-Validation' NAPTR Service Tag
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2020 20:04:15 -0000

--000000000000969c5d059d4cd52f
Content-Type: text/plain; charset="UTF-8"

I don't see any major issues with this.  As a very minor nit, this text:

   In the absense of any NAPTR
   records containing the 'LoST-Validation' service tag, the 'LoST'
   service tag is used.  Fallback to the 'LoST' service tag may follow
   if the 'Lost-Validation' service tag fails to result in a usable LoST
   server.  Using the 'LoST-Validation' service tag might result in the
   same URL as the 'LoST' service tag, or it may result in a different
   URL.  The URLs might result in the same physical servers being
   contacted, or different servers.

is a bit confusing.  Changing:

   Fallback to the 'LoST' service tag may follow
   if the 'Lost-Validation' service tag fails to result in a usable LoST
   server.

to something like:  "Clients MAY also fallback to the "LoST" service tag
if the "LoST-validation" service tag fails to resolve to a usable LoST server"

Would be slightly more readable to me.

regards,

Ted Hardie


On Tue, Jan 28, 2020 at 4:51 PM Randall Gellens <rg+ietf@randy.pensive.org>
wrote:

> Version -02 of the draft was uploaded today.  (Version -01 that
> addressed Ted's comments and some glitches I noticed was published on
> the 21st.)  This is a very short draft that registers a new NAPTR
> service tag.  I appreciate any reviews.
>
> https://www.ietf.org/internet-drafts/draft-gellens-lost-validation-02.txt
>
> Thanks!
>
> On 21 Jan 2020, at 17:30, Randall Gellens wrote:
>
> > On 21 Jan 2020, at 9:29, Ted Hardie wrote:
> >
> >> Hi Randy, Brian,
> >>
> >> Thanks for the message.  I took a quick look at the document, and
> >> there are
> >> two things that might want consideration.  The first is this text,
> >> which
> >> tells you that the bursty validation traffic and the real-time
> >> functions
> >> may be performed by the same server:
> >>
> >>    A server identified using the 'LoST' service tag might
> >>    also perform the validation function (and might resolve to the
> >> same
> >>    URL as a server identified using the 'LoST-Validation' service
> >> tag),
> >>    but the 'LoST-Validation' tag makes this explicit.
> >>
> >> The "tag makes this explicit." doesn't seem to quite cover what you
> >> want to say here.  Maybe:
> >>
> >> Because some services are configured to provide
> >> both real-time and validation functions, a server identified
> >> using the 'LoST' service tag may also perform the validation
> >> function.
> >> The 'Lost-Validation' service tag should, however, always be used
> >> first when seeking
> >> the validation service, as the two functions may be separate.
> >> Fallback to the 'LoST'
> >>
> >> may follow if the Lost-Validation service does not resolve.
> >>
> >>
> >> Alternatively, you might cut this text and rely on the text in
> >> section 3.
> >
> > I see the issue and I like your first suggested rewording, I think
> > that makes it more clear.  Thank you.
> >
> >
> >>
> >> Second, the document's IANA considerations says this:
> >>
> >> IANA is requested to add 'LoST-Validation' to the S-NAPTR Application
> >>    Service Tag registry created by [RFC3958]  This tag serves as a
> >>    counter-part to the 'LoST' tag added by [RFC4848].
> >>
> >> 5.1.  U-NAPTR Registration
> >>
> >>    This document registers the following U-NAPTR application service
> >>    tag:
> >>
> >>       Application Service Tag: LoST
> >>
> >>       Defining Publication: This document.
> >>
> >> Should this be S-NAPTR and LoST-Validation, respectively, or am I
> >> missing
> >> something?
> >
> > The tag name is definitely a typo, thank you very much for catching
> > it.  The registry name I'm not sure about.  The reason for the
> > mismatch is that IANA calls the registry "S-NAPTR Application Service
> > Tags" while RFC 5222 calls it "U-NAPTR application service tag" and
> > RFC 3958 calls it "S-NAPTR Application Service Tags".  So, honestly, I
> > don't know what to call it.  I've changed the draft to consistently
> > use "S-NAPTR" since that's what IANA calls it.
> >
> > The updated draft is at
> >
> https://www.ietf.org/internet-drafts/draft-gellens-lost-validation-01.txt
> >
> > (For some reason, the submit tool won't let me submit the .xml file,
> > it insists the name is invalid.)
> >
> > --Randall
> >
> >>
> >> regards,
> >>
> >> Ted
> >>
> >> On Sat, Jan 18, 2020 at 12:05 PM Randall Gellens
> >> <rg+ietf@randy.pensive.org>
> >> wrote:
> >>
> >>> Working in NENA, we've identified a need to register a new S-NAPTR
> >>> service tag 'LoST-Validation'.
> >>>
> >>> Background: as some may recall, the key motivator for LoST was
> >>> emergency
> >>> services, primarily the ability to lookup a service URN for a
> >>> location
> >>> (i.e., map "URN:SERVICE:SOS" to a SIP URI for a PSAP for a specific
> >>> location), and secondarily the ability to validate a civic location
> >>> (i.e., validate that a civic address is unique, dispatchable, and
> >>> meets
> >>> the requirements for the area). LoST provides the ability to do
> >>> both.
> >>> NENA i3 (which defines NG9-1-1) makes extensive use of LoST. One
> >>> thing
> >>> NENA i3 does that was not originally contemplated when LoST was
> >>> developed is to allow separation of the core mapping function of
> >>> LoST
> >>> from the validation function. NENA i3 allows (but does not require)
> >>> these two services to be provided separately (with the motivation
> >>> that
> >>> mapping is a time-crucial service done during emergency call setup,
> >>> while validation is performed as data is provisioned into entities
> >>> and
> >>> is not time-crucial, so a provider might potentially provision and
> >>> operate these two services differently). LoST uses U-NAPTR
> >>> Application
> >>> Unique Strings rather than URIs to refer to other LoST servers.
> >>> There is
> >>> currently one U-NAPTR service tag for LoST ("LoST"). In order to be
> >>> able
> >>> to separate service mapping from location validation, a second
> >>> service
> >>> tag is needed. Otherwise an entity can't tell from an Application
> >>> Unique
> >>> String which service is available and can't resolve an Application
> >>> Unique String into a URI for a LoST server that assuredly is willing
> >>> to
> >>> perform location validation. We therefore propose to define
> >>> "LoST-Validation" as a service tag. This will allow an entity to
> >>> locate
> >>> a LoST server willing to perform civic location validation, leaving
> >>> "LoST" as the service tag for core service mapping.  (Of course, a
> >>> LoST
> >>> server located using the 'LoST' service tag might offer both mapping
> >>> and
> >>> validation, but the ability to use 'LoST-Validation' in NAPTR
> >>> records
> >>> makes explicit which LoST servers are willing to do validation.)
> >>>
> >>> The Service Tags registry rules that require an RFC to add a tag, so
> >>> I
> >>> have submitted a small RFC to do this:
> >>>
> https://www.ietf.org/internet-drafts/draft-gellens-lost-validation-00.txt
> >>>
> >>> Comments, feedback, etc. are appreciated.
> >>>
> >>> --Randall
>

--000000000000969c5d059d4cd52f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>I don&#39;t see any major issues with this.=C2=A0 As =
a very minor nit, this text:</div><div><br></div><div><pre>   In the absens=
e of any NAPTR
   records containing the &#39;LoST-Validation&#39; service tag, the &#39;L=
oST&#39;
   service tag is used.  Fallback to the &#39;LoST&#39; service tag may fol=
low
   if the &#39;Lost-Validation&#39; service tag fails to result in a usable=
 LoST
   server.  Using the &#39;LoST-Validation&#39; service tag might result in=
 the
   same URL as the &#39;LoST&#39; service tag, or it may result in a differ=
ent
   URL.  The URLs might result in the same physical servers being
   contacted, or different servers.<br><br></pre><pre><span style=3D"font-f=
amily:arial,sans-serif">is a bit confusing.  Changing:</span><br><br>   Fal=
lback to the &#39;LoST&#39; service tag may follow
   if the &#39;Lost-Validation&#39; service tag fails to result in a usable=
 LoST
   server.<br><br></pre><pre><span style=3D"font-family:arial,sans-serif">t=
o something like:</span>  &quot;Clients MAY also fallback to the &quot;LoST=
&quot; service tag <br>if the &quot;LoST-validation&quot; service tag fails=
 to resolve to a usable LoST server&quot;<br><br></pre><pre><font face=3D"a=
rial,sans-serif">Would be slightly more readable to me.<br><br></font></pre=
><pre><font face=3D"arial,sans-serif">regards,<br><br></font></pre><pre><fo=
nt face=3D"arial,sans-serif">Ted Hardie<br></font></pre></div></div><br><di=
v class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Jan 2=
8, 2020 at 4:51 PM Randall Gellens &lt;<a href=3D"mailto:rg%2Bietf@randy.pe=
nsive.org">rg+ietf@randy.pensive.org</a>&gt; wrote:<br></div><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid=
 rgb(204,204,204);padding-left:1ex">Version -02 of the draft was uploaded t=
oday.=C2=A0 (Version -01 that <br>
addressed Ted&#39;s comments and some glitches I noticed was published on <=
br>
the 21st.)=C2=A0 This is a very short draft that registers a new NAPTR <br>
service tag.=C2=A0 I appreciate any reviews.<br>
<br>
<a href=3D"https://www.ietf.org/internet-drafts/draft-gellens-lost-validati=
on-02.txt" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/intern=
et-drafts/draft-gellens-lost-validation-02.txt</a><br>
<br>
Thanks!<br>
<br>
On 21 Jan 2020, at 17:30, Randall Gellens wrote:<br>
<br>
&gt; On 21 Jan 2020, at 9:29, Ted Hardie wrote:<br>
&gt;<br>
&gt;&gt; Hi Randy, Brian,<br>
&gt;&gt;<br>
&gt;&gt; Thanks for the message.=C2=A0 I took a quick look at the document,=
 and <br>
&gt;&gt; there are<br>
&gt;&gt; two things that might want consideration.=C2=A0 The first is this =
text, <br>
&gt;&gt; which<br>
&gt;&gt; tells you that the bursty validation traffic and the real-time <br=
>
&gt;&gt; functions<br>
&gt;&gt; may be performed by the same server:<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 A server identified using the &#39;LoST&#39; service =
tag might<br>
&gt;&gt;=C2=A0 =C2=A0 also perform the validation function (and might resol=
ve to the <br>
&gt;&gt; same<br>
&gt;&gt;=C2=A0 =C2=A0 URL as a server identified using the &#39;LoST-Valida=
tion&#39; service <br>
&gt;&gt; tag),<br>
&gt;&gt;=C2=A0 =C2=A0 but the &#39;LoST-Validation&#39; tag makes this expl=
icit.<br>
&gt;&gt;<br>
&gt;&gt; The &quot;tag makes this explicit.&quot; doesn&#39;t seem to quite=
 cover what you<br>
&gt;&gt; want to say here.=C2=A0 Maybe:<br>
&gt;&gt;<br>
&gt;&gt; Because some services are configured to provide<br>
&gt;&gt; both real-time and validation functions, a server identified<br>
&gt;&gt; using the &#39;LoST&#39; service tag may also perform the validati=
on <br>
&gt;&gt; function.<br>
&gt;&gt; The &#39;Lost-Validation&#39; service tag should, however, always =
be used<br>
&gt;&gt; first when seeking<br>
&gt;&gt; the validation service, as the two functions may be separate.<br>
&gt;&gt; Fallback to the &#39;LoST&#39;<br>
&gt;&gt;<br>
&gt;&gt; may follow if the Lost-Validation service does not resolve.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; Alternatively, you might cut this text and rely on the text in <br=
>
&gt;&gt; section 3.<br>
&gt;<br>
&gt; I see the issue and I like your first suggested rewording, I think <br=
>
&gt; that makes it more clear.=C2=A0 Thank you.<br>
&gt;<br>
&gt;<br>
&gt;&gt;<br>
&gt;&gt; Second, the document&#39;s IANA considerations says this:<br>
&gt;&gt;<br>
&gt;&gt; IANA is requested to add &#39;LoST-Validation&#39; to the S-NAPTR =
Application<br>
&gt;&gt;=C2=A0 =C2=A0 Service Tag registry created by [RFC3958]=C2=A0 This =
tag serves as a<br>
&gt;&gt;=C2=A0 =C2=A0 counter-part to the &#39;LoST&#39; tag added by [RFC4=
848].<br>
&gt;&gt;<br>
&gt;&gt; 5.1.=C2=A0 U-NAPTR Registration<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 This document registers the following U-NAPTR applica=
tion service<br>
&gt;&gt;=C2=A0 =C2=A0 tag:<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Application Service Tag: LoST<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Defining Publication: This document.<br>
&gt;&gt;<br>
&gt;&gt; Should this be S-NAPTR and LoST-Validation, respectively, or am I =
<br>
&gt;&gt; missing<br>
&gt;&gt; something?<br>
&gt;<br>
&gt; The tag name is definitely a typo, thank you very much for catching <b=
r>
&gt; it.=C2=A0 The registry name I&#39;m not sure about.=C2=A0 The reason f=
or the <br>
&gt; mismatch is that IANA calls the registry &quot;S-NAPTR Application Ser=
vice <br>
&gt; Tags&quot; while RFC 5222 calls it &quot;U-NAPTR application service t=
ag&quot; and <br>
&gt; RFC 3958 calls it &quot;S-NAPTR Application Service Tags&quot;.=C2=A0 =
So, honestly, I <br>
&gt; don&#39;t know what to call it.=C2=A0 I&#39;ve changed the draft to co=
nsistently <br>
&gt; use &quot;S-NAPTR&quot; since that&#39;s what IANA calls it.<br>
&gt;<br>
&gt; The updated draft is at <br>
&gt; <a href=3D"https://www.ietf.org/internet-drafts/draft-gellens-lost-val=
idation-01.txt" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/i=
nternet-drafts/draft-gellens-lost-validation-01.txt</a><br>
&gt;<br>
&gt; (For some reason, the submit tool won&#39;t let me submit the .xml fil=
e, <br>
&gt; it insists the name is invalid.)<br>
&gt;<br>
&gt; --Randall<br>
&gt;<br>
&gt;&gt;<br>
&gt;&gt; regards,<br>
&gt;&gt;<br>
&gt;&gt; Ted<br>
&gt;&gt;<br>
&gt;&gt; On Sat, Jan 18, 2020 at 12:05 PM Randall Gellens <br>
&gt;&gt; &lt;<a href=3D"mailto:rg%2Bietf@randy.pensive.org" target=3D"_blan=
k">rg+ietf@randy.pensive.org</a>&gt;<br>
&gt;&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt;&gt; Working in NENA, we&#39;ve identified a need to register a new=
 S-NAPTR<br>
&gt;&gt;&gt; service tag &#39;LoST-Validation&#39;.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Background: as some may recall, the key motivator for LoST was=
 <br>
&gt;&gt;&gt; emergency<br>
&gt;&gt;&gt; services, primarily the ability to lookup a service URN for a =
<br>
&gt;&gt;&gt; location<br>
&gt;&gt;&gt; (i.e., map &quot;URN:SERVICE:SOS&quot; to a SIP URI for a PSAP=
 for a specific<br>
&gt;&gt;&gt; location), and secondarily the ability to validate a civic loc=
ation<br>
&gt;&gt;&gt; (i.e., validate that a civic address is unique, dispatchable, =
and <br>
&gt;&gt;&gt; meets<br>
&gt;&gt;&gt; the requirements for the area). LoST provides the ability to d=
o <br>
&gt;&gt;&gt; both.<br>
&gt;&gt;&gt; NENA i3 (which defines NG9-1-1) makes extensive use of LoST. O=
ne <br>
&gt;&gt;&gt; thing<br>
&gt;&gt;&gt; NENA i3 does that was not originally contemplated when LoST wa=
s<br>
&gt;&gt;&gt; developed is to allow separation of the core mapping function =
of <br>
&gt;&gt;&gt; LoST<br>
&gt;&gt;&gt; from the validation function. NENA i3 allows (but does not req=
uire)<br>
&gt;&gt;&gt; these two services to be provided separately (with the motivat=
ion <br>
&gt;&gt;&gt; that<br>
&gt;&gt;&gt; mapping is a time-crucial service done during emergency call s=
etup,<br>
&gt;&gt;&gt; while validation is performed as data is provisioned into enti=
ties <br>
&gt;&gt;&gt; and<br>
&gt;&gt;&gt; is not time-crucial, so a provider might potentially provision=
 and<br>
&gt;&gt;&gt; operate these two services differently). LoST uses U-NAPTR <br=
>
&gt;&gt;&gt; Application<br>
&gt;&gt;&gt; Unique Strings rather than URIs to refer to other LoST servers=
. <br>
&gt;&gt;&gt; There is<br>
&gt;&gt;&gt; currently one U-NAPTR service tag for LoST (&quot;LoST&quot;).=
 In order to be <br>
&gt;&gt;&gt; able<br>
&gt;&gt;&gt; to separate service mapping from location validation, a second=
 <br>
&gt;&gt;&gt; service<br>
&gt;&gt;&gt; tag is needed. Otherwise an entity can&#39;t tell from an Appl=
ication <br>
&gt;&gt;&gt; Unique<br>
&gt;&gt;&gt; String which service is available and can&#39;t resolve an App=
lication<br>
&gt;&gt;&gt; Unique String into a URI for a LoST server that assuredly is w=
illing <br>
&gt;&gt;&gt; to<br>
&gt;&gt;&gt; perform location validation. We therefore propose to define<br=
>
&gt;&gt;&gt; &quot;LoST-Validation&quot; as a service tag. This will allow =
an entity to <br>
&gt;&gt;&gt; locate<br>
&gt;&gt;&gt; a LoST server willing to perform civic location validation, le=
aving<br>
&gt;&gt;&gt; &quot;LoST&quot; as the service tag for core service mapping.=
=C2=A0 (Of course, a <br>
&gt;&gt;&gt; LoST<br>
&gt;&gt;&gt; server located using the &#39;LoST&#39; service tag might offe=
r both mapping <br>
&gt;&gt;&gt; and<br>
&gt;&gt;&gt; validation, but the ability to use &#39;LoST-Validation&#39; i=
n NAPTR <br>
&gt;&gt;&gt; records<br>
&gt;&gt;&gt; makes explicit which LoST servers are willing to do validation=
.)<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; The Service Tags registry rules that require an RFC to add a t=
ag, so <br>
&gt;&gt;&gt; I<br>
&gt;&gt;&gt; have submitted a small RFC to do this:<br>
&gt;&gt;&gt; <a href=3D"https://www.ietf.org/internet-drafts/draft-gellens-=
lost-validation-00.txt" rel=3D"noreferrer" target=3D"_blank">https://www.ie=
tf.org/internet-drafts/draft-gellens-lost-validation-00.txt</a><br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Comments, feedback, etc. are appreciated.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; --Randall<br>
</blockquote></div>

--000000000000969c5d059d4cd52f--


From nobody Wed Jan 29 14:42:02 2020
Return-Path: <mnot@mnot.net>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF0C012001B; Wed, 29 Jan 2020 14:41:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=o8VdU91D; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=VSEKq2Kq
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 eZm5kJXp5IW8; Wed, 29 Jan 2020 14:41:53 -0800 (PST)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C79412004C; Wed, 29 Jan 2020 14:41:53 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id C1F5B21B1B; Wed, 29 Jan 2020 17:41:49 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Wed, 29 Jan 2020 17:41:49 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=from :content-type:content-transfer-encoding:reply-to:mime-version :subject:message-id:date:to; s=fm1; bh=Q3z700OD/S18QIepm+eFoHIuZ snEY2xqGgbeSlp8eiE=; b=o8VdU91DDd8GwTCNFE9S0qSn3kXQJkrsyPfEOhOE0 ++xRqTYl8Cad0JGux9r7Mjk0ub20j9fxMLwWCMYJ7sH3AHB0YBoWlnhj4nOChNMg 9V/zZdfVONF+SOOjHiw9DUNMeEAkIW+si41UCIfLq2MdxRUE35QDVwbOu+mOyQuT zMwzh3/b8yx5uy08CJoJnNzbvPkVZJAMx2maadcrhGrQzEdBrF3j6c4AznWUebRP 7zFEHrs74FK6SFWP4YRl2xdfbJLO8gPgmNe87IpnU/9WjaEA/ytjQOdplZkXArGD JqJ2nHAKQYDdihccjSMHS2RkNGdIi22oN75OmfrUtAz2A==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:reply-to:subject:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; bh=Q3z700OD/S18QIepm+eFoHIuZsnEY2xqGgbeSlp8eiE=; b=VSEKq2Kq kMp4yOoOD+nH4zk9y9QQ+rsEuw5IMpZY9GPrOCBINjOhu6wvjIfXMyqf9E4wEOl3 ZMp8i/b80KpAtiEhkHbgxi7JS2E7BNLEXNyvRbkIKTnVpDd82zA8jgv8Mjez/8O/ bUR/1mRmTVOK2fya2LNfh5WYQtUoiCGsej0EnsMS36WZX2QMfGSZ9ji2+Xl2v8NU Gxm8FKrmQJbDcGU44/8d+nOULmzrNrfWb7OM1whBRT1DWmGW3xQ4Mm2AFx8CHsl7 5G7Y9X9D/2XgvEgWSAy85vs7HmxNbktspOA4yp2fxxjsLktv9nKQ25v3hzPwCJFC pnqX+nwZWmwoHA==
X-ME-Sender: <xms:LQoyXia5ddFsPDXHTpSX15cJo7w7OTxXoAnMqW8Sf9N77JlUpkeSXQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrfeeigdduieduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephfgtgfhrggfukfffvffosehtqhhmtdhhtddvnecuhfhrohhmpeforghrkhcu pfhothhtihhnghhhrghmuceomhhnohhtsehmnhhothdrnhgvtheqnecuffhomhgrihhnpe hgihhthhhusgdrtghomhdprhhftgdqvgguihhtohhrrdhorhhgnecukfhppeduudelrddu jedrudehkedrvdehudenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrih hlfhhrohhmpehmnhhothesmhhnohhtrdhnvght
X-ME-Proxy: <xmx:LQoyXsJJQxkfYi4pLiQQbEq4x-YWmP9OxpSTVaB7nqPoz59r-wpliw> <xmx:LQoyXuuTdqPJklR97ZNKuyMgJXR6uIHeGXQSbnzDGTL06Nt9k_BplQ> <xmx:LQoyXgXyI9DfNohbaODixcmCojROhfePvK5Rk9WXMlxegBnQU6X_Hw> <xmx:LQoyXm8FV5ft4YodKQ5hdHmt6xWabsImR8EzMZVbvqaoG7leboA-dg>
Received: from macbook-pro.mnot.net (unknown [119.17.158.251]) by mail.messagingengine.com (Postfix) with ESMTPA id B7C493280059; Wed, 29 Jan 2020 17:41:47 -0500 (EST)
From: Mark Nottingham <mnot@mnot.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Reply-To: IETF QUIC WG <quic@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.40.2.2.4\))
Message-Id: <79D7CB95-3B81-4A65-A118-F5636F0899A4@mnot.net>
Date: Thu, 30 Jan 2020 09:41:45 +1100
To: IETF QUIC WG <quic@ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>, ART Area <art@ietf.org>, tsv-area@ietf.org
X-Mailer: Apple Mail (2.3608.40.2.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/rR74E2mFiTbjNaE55Wv3XSz65qs>
Subject: [art] DISPATCHing QUIC-related work in Vancouver
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2020 22:41:56 -0000

As discussed in the Transport Area meeting in Singapore, there are a =
number of proposals for extensions to QUIC, application protocols using =
QUIC, and other QUIC-related work items.

While the QUIC Working Group has discussed adopting a limited number of =
extensions in the near future, it was felt that a DISPATCH-like* forum =
might help to route QUIC-related work appropriately.

So, as an experiment, the QUIC Working Group will hold a third, =
hour-long session in Vancouver to discuss proposals for new QUIC =
extensions, applications, and related work not yet being considered for =
adoption in QUIC or another Working Group.

This session will enable people to raise their proposals, get feedback =
on them, and allow the appropriate Area Directors to get a sense of what =
work will be reasonable to continue. Such work might be adopted by the =
QUIC WG (when it has capacity to take on new work), another existing =
group, or it might require a BoF.

If you have a proposal, please list it here:
  https://github.com/quicwg/dispatch/wiki/IETF107
... by 2020-02-28.

Kind regards,

Lars, Lucas and Mark, QUIC WG Chairs

* See <https://www.rfc-editor.org/rfc/rfc7957#section-2> for a =
description of DISPATCH.=


From nobody Wed Jan 29 16:07:37 2020
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: art@ietf.org
Delivered-To: art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D7AB612004E; Wed, 29 Jan 2020 16:07:36 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <art@ietf.org>, <draft-nottingham-rfc7320bis@ietf.org>, <adam@nostrum.com>, <mt@lowentropy.net>, <mt@mozilla.com>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.116.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <158034285687.32109.12684137044171428381.idtracker@ietfa.amsl.com>
Date: Wed, 29 Jan 2020 16:07:36 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/_z8K1GLkZ892GOY-56peZaKheWM>
Subject: [art] Datatracker State Update Notice: <draft-nottingham-rfc7320bis-03.txt>
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jan 2020 00:07:37 -0000

IANA action state changed to "No IANA Actions"
Datatracker URL: https://datatracker.ietf.org/doc/draft-nottingham-rfc7320bis/


From nobody Thu Jan 30 15:44:15 2020
Return-Path: <rg+ietf@randy.pensive.org>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B96E2120013 for <art@ietfa.amsl.com>; Thu, 30 Jan 2020 15:44:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.898
X-Spam-Level: *
X-Spam-Status: No, score=1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FORGED_RELAY_MUA_TO_MX=3.799, SPF_PASS=-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 6z1RqGajCzdS for <art@ietfa.amsl.com>; Thu, 30 Jan 2020 15:44:12 -0800 (PST)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id 2B206120255 for <art@ietf.org>; Thu, 30 Jan 2020 15:44:12 -0800 (PST)
Received: from [99.111.97.181] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Thu, 30 Jan 2020 15:44:11 -0800
From: "Randall Gellens" <rg+ietf@randy.pensive.org>
To: "Ted Hardie" <ted.ietf@gmail.com>
Cc: "Applications and Real-Time Area Discussion" <art@ietf.org>, "Brian Rosen" <br@brianrosen.net>
Date: Thu, 30 Jan 2020 15:44:10 -0800
X-Mailer: MailMate (1.13.1r5671)
Message-ID: <3BE74F43-5037-421B-8161-5975C67DEB52@randy.pensive.org>
In-Reply-To: <CA+9kkMA_-dBg5gsGJJ2Tobr4Pon2B6YpoY80ugP3kBVvgSw2zw@mail.gmail.com>
References: <8B4763EE-63C2-448C-AB70-BC9EE5D91D7B@randy.pensive.org> <CA+9kkMA_-dBg5gsGJJ2Tobr4Pon2B6YpoY80ugP3kBVvgSw2zw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/dF4NH9GMDVZFQOSyuOU6ndn2qXU>
Subject: Re: [art] Please review: Registering the 'LoST-Validation' NAPTR Service Tag
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jan 2020 23:44:14 -0000

On 29 Jan 2020, at 12:03, Ted Hardie wrote:

> I don't see any major issues with this.  As a very minor nit, this 
> text:
>
>    In the absense of any NAPTR
>    records containing the 'LoST-Validation' service tag, the 'LoST'
>    service tag is used.  Fallback to the 'LoST' service tag may follow
>    if the 'Lost-Validation' service tag fails to result in a usable 
> LoST
>    server.  Using the 'LoST-Validation' service tag might result in 
> the
>    same URL as the 'LoST' service tag, or it may result in a different
>    URL.  The URLs might result in the same physical servers being
>    contacted, or different servers.
>
> is a bit confusing.  Changing:
>
>    Fallback to the 'LoST' service tag may follow
>    if the 'Lost-Validation' service tag fails to result in a usable 
> LoST
>    server.
>
> to something like:  "Clients MAY also fallback to the "LoST" service 
> tag
> if the "LoST-validation" service tag fails to resolve to a usable LoST 
> server"
>
> Would be slightly more readable to me.
>
> regards,
>
> Ted Hardie



Hi Ted,

Thanks for the comment.  What do you think of this wording:

    Because some servers might be configured to provide both mapping and
    validation functions, a server identified using the 'LoST' service
    tag might also perform the validation function (and resolving the 
two
    tags might result in the same URL).  Because the two functions might
    be separate, clients seeking a LoST server for location validation
    should first try U-NAPTR resolution using the 'Lost-Validation'
    service tag, and may fallback to the 'LoST' service tag if the 
'Lost-
    Validation' service tag cannot be resolved to a usable LoST server.


--Randall


> On Tue, Jan 28, 2020 at 4:51 PM Randall Gellens 
> <rg+ietf@randy.pensive.org>
> wrote:
>
>> Version -02 of the draft was uploaded today.  (Version -01 that
>> addressed Ted's comments and some glitches I noticed was published on
>> the 21st.)  This is a very short draft that registers a new NAPTR
>> service tag.  I appreciate any reviews.
>>
>> https://www.ietf.org/internet-drafts/draft-gellens-lost-validation-02.txt
>>
>> Thanks!
>>
>> On 21 Jan 2020, at 17:30, Randall Gellens wrote:
>>
>>> On 21 Jan 2020, at 9:29, Ted Hardie wrote:
>>>
>>>> Hi Randy, Brian,
>>>>
>>>> Thanks for the message.  I took a quick look at the document, and
>>>> there are
>>>> two things that might want consideration.  The first is this text,
>>>> which
>>>> tells you that the bursty validation traffic and the real-time
>>>> functions
>>>> may be performed by the same server:
>>>>
>>>>    A server identified using the 'LoST' service tag might
>>>>    also perform the validation function (and might resolve to the
>>>> same
>>>>    URL as a server identified using the 'LoST-Validation' service
>>>> tag),
>>>>    but the 'LoST-Validation' tag makes this explicit.
>>>>
>>>> The "tag makes this explicit." doesn't seem to quite cover what you
>>>> want to say here.  Maybe:
>>>>
>>>> Because some services are configured to provide
>>>> both real-time and validation functions, a server identified
>>>> using the 'LoST' service tag may also perform the validation
>>>> function.
>>>> The 'Lost-Validation' service tag should, however, always be used
>>>> first when seeking
>>>> the validation service, as the two functions may be separate.
>>>> Fallback to the 'LoST'
>>>>
>>>> may follow if the Lost-Validation service does not resolve.
>>>>
>>>>
>>>> Alternatively, you might cut this text and rely on the text in
>>>> section 3.
>>>
>>> I see the issue and I like your first suggested rewording, I think
>>> that makes it more clear.  Thank you.
>>>
>>>
>>>>
>>>> Second, the document's IANA considerations says this:
>>>>
>>>> IANA is requested to add 'LoST-Validation' to the S-NAPTR 
>>>> Application
>>>>    Service Tag registry created by [RFC3958]  This tag serves as a
>>>>    counter-part to the 'LoST' tag added by [RFC4848].
>>>>
>>>> 5.1.  U-NAPTR Registration
>>>>
>>>>    This document registers the following U-NAPTR application 
>>>> service
>>>>    tag:
>>>>
>>>>       Application Service Tag: LoST
>>>>
>>>>       Defining Publication: This document.
>>>>
>>>> Should this be S-NAPTR and LoST-Validation, respectively, or am I
>>>> missing
>>>> something?
>>>
>>> The tag name is definitely a typo, thank you very much for catching
>>> it.  The registry name I'm not sure about.  The reason for the
>>> mismatch is that IANA calls the registry "S-NAPTR Application 
>>> Service
>>> Tags" while RFC 5222 calls it "U-NAPTR application service tag" and
>>> RFC 3958 calls it "S-NAPTR Application Service Tags".  So, honestly, 
>>> I
>>> don't know what to call it.  I've changed the draft to consistently
>>> use "S-NAPTR" since that's what IANA calls it.
>>>
>>> The updated draft is at
>>>
>> https://www.ietf.org/internet-drafts/draft-gellens-lost-validation-01.txt
>>>
>>> (For some reason, the submit tool won't let me submit the .xml file,
>>> it insists the name is invalid.)
>>>
>>> --Randall
>>>
>>>>
>>>> regards,
>>>>
>>>> Ted
>>>>
>>>> On Sat, Jan 18, 2020 at 12:05 PM Randall Gellens
>>>> <rg+ietf@randy.pensive.org>
>>>> wrote:
>>>>
>>>>> Working in NENA, we've identified a need to register a new S-NAPTR
>>>>> service tag 'LoST-Validation'.
>>>>>
>>>>> Background: as some may recall, the key motivator for LoST was
>>>>> emergency
>>>>> services, primarily the ability to lookup a service URN for a
>>>>> location
>>>>> (i.e., map "URN:SERVICE:SOS" to a SIP URI for a PSAP for a 
>>>>> specific
>>>>> location), and secondarily the ability to validate a civic 
>>>>> location
>>>>> (i.e., validate that a civic address is unique, dispatchable, and
>>>>> meets
>>>>> the requirements for the area). LoST provides the ability to do
>>>>> both.
>>>>> NENA i3 (which defines NG9-1-1) makes extensive use of LoST. One
>>>>> thing
>>>>> NENA i3 does that was not originally contemplated when LoST was
>>>>> developed is to allow separation of the core mapping function of
>>>>> LoST
>>>>> from the validation function. NENA i3 allows (but does not 
>>>>> require)
>>>>> these two services to be provided separately (with the motivation
>>>>> that
>>>>> mapping is a time-crucial service done during emergency call 
>>>>> setup,
>>>>> while validation is performed as data is provisioned into entities
>>>>> and
>>>>> is not time-crucial, so a provider might potentially provision and
>>>>> operate these two services differently). LoST uses U-NAPTR
>>>>> Application
>>>>> Unique Strings rather than URIs to refer to other LoST servers.
>>>>> There is
>>>>> currently one U-NAPTR service tag for LoST ("LoST"). In order to 
>>>>> be
>>>>> able
>>>>> to separate service mapping from location validation, a second
>>>>> service
>>>>> tag is needed. Otherwise an entity can't tell from an Application
>>>>> Unique
>>>>> String which service is available and can't resolve an Application
>>>>> Unique String into a URI for a LoST server that assuredly is 
>>>>> willing
>>>>> to
>>>>> perform location validation. We therefore propose to define
>>>>> "LoST-Validation" as a service tag. This will allow an entity to
>>>>> locate
>>>>> a LoST server willing to perform civic location validation, 
>>>>> leaving
>>>>> "LoST" as the service tag for core service mapping.  (Of course, a
>>>>> LoST
>>>>> server located using the 'LoST' service tag might offer both 
>>>>> mapping
>>>>> and
>>>>> validation, but the ability to use 'LoST-Validation' in NAPTR
>>>>> records
>>>>> makes explicit which LoST servers are willing to do validation.)
>>>>>
>>>>> The Service Tags registry rules that require an RFC to add a tag, 
>>>>> so
>>>>> I
>>>>> have submitted a small RFC to do this:
>>>>>
>> https://www.ietf.org/internet-drafts/draft-gellens-lost-validation-00.txt
>>>>>
>>>>> Comments, feedback, etc. are appreciated.
>>>>>
>>>>> --Randall
>>


From nobody Thu Jan 30 16:02:43 2020
Return-Path: <ted.ietf@gmail.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDB861200FB for <art@ietfa.amsl.com>; Thu, 30 Jan 2020 16:02:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level: 
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 vkP2HRXaBzMg for <art@ietfa.amsl.com>; Thu, 30 Jan 2020 16:02:37 -0800 (PST)
Received: from mail-ot1-x335.google.com (mail-ot1-x335.google.com [IPv6:2607:f8b0:4864:20::335]) (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 060FA120074 for <art@ietf.org>; Thu, 30 Jan 2020 16:02:36 -0800 (PST)
Received: by mail-ot1-x335.google.com with SMTP id a15so4949049otf.1 for <art@ietf.org>; Thu, 30 Jan 2020 16:02:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=24YV2e/y1gKKOd/7dhB8C96q3vWLDGi87GMy06P1oN0=; b=mzxYf15NkzBfMXKA+51S2ST+gHKr1FqxC8D988SsykBz6v55GGJO0FitGf65d1FAwW v7JoDoqgNH2TMa361e0AaGHMQFqKqtS49RzQiv3NCHa/yl5kGv0SWCYZKliYRL/D5epr d6ESPwnJOdNyX2fqGXa/RnExzIpUWAOYf0Zf7jvlbtdB4eRflMaALy/4RMEr/xAfhKmC J5Sy6gyMkpER6Noqpt6G0iNMcmBHgQiQzssKY1vQFR8HFlhUC6GgQU8EWr60fwISW75Y xi1lKBseJHD9x5WVIKmisRCAxiGovGd9AeCTwY9JCnJtubOfkYIk7Koc5sLnoKYF1t9n cHlA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=24YV2e/y1gKKOd/7dhB8C96q3vWLDGi87GMy06P1oN0=; b=exjCjd+azBIozWIholPIJ6lpozS9n8lVsvJ0ZAXJ+iRd5HORGs6Z1ed+2rtiYbPeYP 6zaW00lbtkjY6NHUdE+sO5/lz2rB4XJ/JMpGJjiXH5bpzhA7YVtV08avaeJMSvb3WYiX +A8zORBphDmQIbQ4+daCkBHCT2VHs3bT7ld3ogHmp7QMmvBBmjwbdi3hLyaAtQYuy2Tu 4rDAVu09amaIftn7FXCNAhpJkJ6inBSBs8XF/3+QrFj9DHcf5F4psxbWbn9loExw1Rcs cMXWpnReJKdOrNEYceeluAj622meQ2kxAb3lwRFj74ZrB5u5cfam0JeoBbds+ULto79w BJUA==
X-Gm-Message-State: APjAAAUshGBuTwTsopR0fiyHtJxH5ARJC9M1t+m9+uOZ9UfWvg5UmG4/ wdG8eaLZeSGKqAbP1skv00o3reEFs7djE+4m2b4x9A==
X-Google-Smtp-Source: APXvYqzWd0uKI8QW2IR0uBZ6xU3yf9KjcOVQgHnqlFWc5//++hbrbWxJGSgNbHrW7uk1FzYjT8sxR6S0TVmhxfc08Bk=
X-Received: by 2002:a9d:6544:: with SMTP id q4mr5345763otl.269.1580428956009;  Thu, 30 Jan 2020 16:02:36 -0800 (PST)
MIME-Version: 1.0
References: <8B4763EE-63C2-448C-AB70-BC9EE5D91D7B@randy.pensive.org> <CA+9kkMA_-dBg5gsGJJ2Tobr4Pon2B6YpoY80ugP3kBVvgSw2zw@mail.gmail.com> <3BE74F43-5037-421B-8161-5975C67DEB52@randy.pensive.org>
In-Reply-To: <3BE74F43-5037-421B-8161-5975C67DEB52@randy.pensive.org>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Thu, 30 Jan 2020 16:02:09 -0800
Message-ID: <CA+9kkMB97UCDK_U=K0j9k71DwusP2wZrjcX2jY1N0XqGJvA8KQ@mail.gmail.com>
To: Randall Gellens <rg+ietf@randy.pensive.org>
Cc: Applications and Real-Time Area Discussion <art@ietf.org>, Brian Rosen <br@brianrosen.net>
Content-Type: multipart/alternative; boundary="000000000000840c32059d644acf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/Qg6QmWoA3GcoCTgIsu1dEKqTU6o>
Subject: Re: [art] Please review: Registering the 'LoST-Validation' NAPTR Service Tag
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Jan 2020 00:02:41 -0000

--000000000000840c32059d644acf
Content-Type: text/plain; charset="UTF-8"

Looks fine to me.

Ted
Mobile/Terse

On Thu, Jan 30, 2020 at 3:44 PM Randall Gellens <rg+ietf@randy.pensive.org>
wrote:

> On 29 Jan 2020, at 12:03, Ted Hardie wrote:
>
> > I don't see any major issues with this.  As a very minor nit, this
> > text:
> >
> >    In the absense of any NAPTR
> >    records containing the 'LoST-Validation' service tag, the 'LoST'
> >    service tag is used.  Fallback to the 'LoST' service tag may follow
> >    if the 'Lost-Validation' service tag fails to result in a usable
> > LoST
> >    server.  Using the 'LoST-Validation' service tag might result in
> > the
> >    same URL as the 'LoST' service tag, or it may result in a different
> >    URL.  The URLs might result in the same physical servers being
> >    contacted, or different servers.
> >
> > is a bit confusing.  Changing:
> >
> >    Fallback to the 'LoST' service tag may follow
> >    if the 'Lost-Validation' service tag fails to result in a usable
> > LoST
> >    server.
> >
> > to something like:  "Clients MAY also fallback to the "LoST" service
> > tag
> > if the "LoST-validation" service tag fails to resolve to a usable LoST
> > server"
> >
> > Would be slightly more readable to me.
> >
> > regards,
> >
> > Ted Hardie
>
>
>
> Hi Ted,
>
> Thanks for the comment.  What do you think of this wording:
>
>     Because some servers might be configured to provide both mapping and
>     validation functions, a server identified using the 'LoST' service
>     tag might also perform the validation function (and resolving the
> two
>     tags might result in the same URL).  Because the two functions might
>     be separate, clients seeking a LoST server for location validation
>     should first try U-NAPTR resolution using the 'Lost-Validation'
>     service tag, and may fallback to the 'LoST' service tag if the
> 'Lost-
>     Validation' service tag cannot be resolved to a usable LoST server.
>
>
> --Randall
>
>
> > On Tue, Jan 28, 2020 at 4:51 PM Randall Gellens
> > <rg+ietf@randy.pensive.org>
> > wrote:
> >
> >> Version -02 of the draft was uploaded today.  (Version -01 that
> >> addressed Ted's comments and some glitches I noticed was published on
> >> the 21st.)  This is a very short draft that registers a new NAPTR
> >> service tag.  I appreciate any reviews.
> >>
> >>
> https://www.ietf.org/internet-drafts/draft-gellens-lost-validation-02.txt
> >>
> >> Thanks!
> >>
> >> On 21 Jan 2020, at 17:30, Randall Gellens wrote:
> >>
> >>> On 21 Jan 2020, at 9:29, Ted Hardie wrote:
> >>>
> >>>> Hi Randy, Brian,
> >>>>
> >>>> Thanks for the message.  I took a quick look at the document, and
> >>>> there are
> >>>> two things that might want consideration.  The first is this text,
> >>>> which
> >>>> tells you that the bursty validation traffic and the real-time
> >>>> functions
> >>>> may be performed by the same server:
> >>>>
> >>>>    A server identified using the 'LoST' service tag might
> >>>>    also perform the validation function (and might resolve to the
> >>>> same
> >>>>    URL as a server identified using the 'LoST-Validation' service
> >>>> tag),
> >>>>    but the 'LoST-Validation' tag makes this explicit.
> >>>>
> >>>> The "tag makes this explicit." doesn't seem to quite cover what you
> >>>> want to say here.  Maybe:
> >>>>
> >>>> Because some services are configured to provide
> >>>> both real-time and validation functions, a server identified
> >>>> using the 'LoST' service tag may also perform the validation
> >>>> function.
> >>>> The 'Lost-Validation' service tag should, however, always be used
> >>>> first when seeking
> >>>> the validation service, as the two functions may be separate.
> >>>> Fallback to the 'LoST'
> >>>>
> >>>> may follow if the Lost-Validation service does not resolve.
> >>>>
> >>>>
> >>>> Alternatively, you might cut this text and rely on the text in
> >>>> section 3.
> >>>
> >>> I see the issue and I like your first suggested rewording, I think
> >>> that makes it more clear.  Thank you.
> >>>
> >>>
> >>>>
> >>>> Second, the document's IANA considerations says this:
> >>>>
> >>>> IANA is requested to add 'LoST-Validation' to the S-NAPTR
> >>>> Application
> >>>>    Service Tag registry created by [RFC3958]  This tag serves as a
> >>>>    counter-part to the 'LoST' tag added by [RFC4848].
> >>>>
> >>>> 5.1.  U-NAPTR Registration
> >>>>
> >>>>    This document registers the following U-NAPTR application
> >>>> service
> >>>>    tag:
> >>>>
> >>>>       Application Service Tag: LoST
> >>>>
> >>>>       Defining Publication: This document.
> >>>>
> >>>> Should this be S-NAPTR and LoST-Validation, respectively, or am I
> >>>> missing
> >>>> something?
> >>>
> >>> The tag name is definitely a typo, thank you very much for catching
> >>> it.  The registry name I'm not sure about.  The reason for the
> >>> mismatch is that IANA calls the registry "S-NAPTR Application
> >>> Service
> >>> Tags" while RFC 5222 calls it "U-NAPTR application service tag" and
> >>> RFC 3958 calls it "S-NAPTR Application Service Tags".  So, honestly,
> >>> I
> >>> don't know what to call it.  I've changed the draft to consistently
> >>> use "S-NAPTR" since that's what IANA calls it.
> >>>
> >>> The updated draft is at
> >>>
> >>
> https://www.ietf.org/internet-drafts/draft-gellens-lost-validation-01.txt
> >>>
> >>> (For some reason, the submit tool won't let me submit the .xml file,
> >>> it insists the name is invalid.)
> >>>
> >>> --Randall
> >>>
> >>>>
> >>>> regards,
> >>>>
> >>>> Ted
> >>>>
> >>>> On Sat, Jan 18, 2020 at 12:05 PM Randall Gellens
> >>>> <rg+ietf@randy.pensive.org>
> >>>> wrote:
> >>>>
> >>>>> Working in NENA, we've identified a need to register a new S-NAPTR
> >>>>> service tag 'LoST-Validation'.
> >>>>>
> >>>>> Background: as some may recall, the key motivator for LoST was
> >>>>> emergency
> >>>>> services, primarily the ability to lookup a service URN for a
> >>>>> location
> >>>>> (i.e., map "URN:SERVICE:SOS" to a SIP URI for a PSAP for a
> >>>>> specific
> >>>>> location), and secondarily the ability to validate a civic
> >>>>> location
> >>>>> (i.e., validate that a civic address is unique, dispatchable, and
> >>>>> meets
> >>>>> the requirements for the area). LoST provides the ability to do
> >>>>> both.
> >>>>> NENA i3 (which defines NG9-1-1) makes extensive use of LoST. One
> >>>>> thing
> >>>>> NENA i3 does that was not originally contemplated when LoST was
> >>>>> developed is to allow separation of the core mapping function of
> >>>>> LoST
> >>>>> from the validation function. NENA i3 allows (but does not
> >>>>> require)
> >>>>> these two services to be provided separately (with the motivation
> >>>>> that
> >>>>> mapping is a time-crucial service done during emergency call
> >>>>> setup,
> >>>>> while validation is performed as data is provisioned into entities
> >>>>> and
> >>>>> is not time-crucial, so a provider might potentially provision and
> >>>>> operate these two services differently). LoST uses U-NAPTR
> >>>>> Application
> >>>>> Unique Strings rather than URIs to refer to other LoST servers.
> >>>>> There is
> >>>>> currently one U-NAPTR service tag for LoST ("LoST"). In order to
> >>>>> be
> >>>>> able
> >>>>> to separate service mapping from location validation, a second
> >>>>> service
> >>>>> tag is needed. Otherwise an entity can't tell from an Application
> >>>>> Unique
> >>>>> String which service is available and can't resolve an Application
> >>>>> Unique String into a URI for a LoST server that assuredly is
> >>>>> willing
> >>>>> to
> >>>>> perform location validation. We therefore propose to define
> >>>>> "LoST-Validation" as a service tag. This will allow an entity to
> >>>>> locate
> >>>>> a LoST server willing to perform civic location validation,
> >>>>> leaving
> >>>>> "LoST" as the service tag for core service mapping.  (Of course, a
> >>>>> LoST
> >>>>> server located using the 'LoST' service tag might offer both
> >>>>> mapping
> >>>>> and
> >>>>> validation, but the ability to use 'LoST-Validation' in NAPTR
> >>>>> records
> >>>>> makes explicit which LoST servers are willing to do validation.)
> >>>>>
> >>>>> The Service Tags registry rules that require an RFC to add a tag,
> >>>>> so
> >>>>> I
> >>>>> have submitted a small RFC to do this:
> >>>>>
> >>
> https://www.ietf.org/internet-drafts/draft-gellens-lost-validation-00.txt
> >>>>>
> >>>>> Comments, feedback, etc. are appreciated.
> >>>>>
> >>>>> --Randall
> >>
>

--000000000000840c32059d644acf
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Looks fine to me.</div><div><br></div><div>Ted</div><=
div>Mobile/Terse<br></div></div><br><div class=3D"gmail_quote"><div dir=3D"=
ltr" class=3D"gmail_attr">On Thu, Jan 30, 2020 at 3:44 PM Randall Gellens &=
lt;<a href=3D"mailto:rg%2Bietf@randy.pensive.org">rg+ietf@randy.pensive.org=
</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:=
0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">=
On 29 Jan 2020, at 12:03, Ted Hardie wrote:<br>
<br>
&gt; I don&#39;t see any major issues with this.=C2=A0 As a very minor nit,=
 this <br>
&gt; text:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 In the absense of any NAPTR<br>
&gt;=C2=A0 =C2=A0 records containing the &#39;LoST-Validation&#39; service =
tag, the &#39;LoST&#39;<br>
&gt;=C2=A0 =C2=A0 service tag is used.=C2=A0 Fallback to the &#39;LoST&#39;=
 service tag may follow<br>
&gt;=C2=A0 =C2=A0 if the &#39;Lost-Validation&#39; service tag fails to res=
ult in a usable <br>
&gt; LoST<br>
&gt;=C2=A0 =C2=A0 server.=C2=A0 Using the &#39;LoST-Validation&#39; service=
 tag might result in <br>
&gt; the<br>
&gt;=C2=A0 =C2=A0 same URL as the &#39;LoST&#39; service tag, or it may res=
ult in a different<br>
&gt;=C2=A0 =C2=A0 URL.=C2=A0 The URLs might result in the same physical ser=
vers being<br>
&gt;=C2=A0 =C2=A0 contacted, or different servers.<br>
&gt;<br>
&gt; is a bit confusing.=C2=A0 Changing:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 Fallback to the &#39;LoST&#39; service tag may follow<br>
&gt;=C2=A0 =C2=A0 if the &#39;Lost-Validation&#39; service tag fails to res=
ult in a usable <br>
&gt; LoST<br>
&gt;=C2=A0 =C2=A0 server.<br>
&gt;<br>
&gt; to something like:=C2=A0 &quot;Clients MAY also fallback to the &quot;=
LoST&quot; service <br>
&gt; tag<br>
&gt; if the &quot;LoST-validation&quot; service tag fails to resolve to a u=
sable LoST <br>
&gt; server&quot;<br>
&gt;<br>
&gt; Would be slightly more readable to me.<br>
&gt;<br>
&gt; regards,<br>
&gt;<br>
&gt; Ted Hardie<br>
<br>
<br>
<br>
Hi Ted,<br>
<br>
Thanks for the comment.=C2=A0 What do you think of this wording:<br>
<br>
=C2=A0 =C2=A0 Because some servers might be configured to provide both mapp=
ing and<br>
=C2=A0 =C2=A0 validation functions, a server identified using the &#39;LoST=
&#39; service<br>
=C2=A0 =C2=A0 tag might also perform the validation function (and resolving=
 the <br>
two<br>
=C2=A0 =C2=A0 tags might result in the same URL).=C2=A0 Because the two fun=
ctions might<br>
=C2=A0 =C2=A0 be separate, clients seeking a LoST server for location valid=
ation<br>
=C2=A0 =C2=A0 should first try U-NAPTR resolution using the &#39;Lost-Valid=
ation&#39;<br>
=C2=A0 =C2=A0 service tag, and may fallback to the &#39;LoST&#39; service t=
ag if the <br>
&#39;Lost-<br>
=C2=A0 =C2=A0 Validation&#39; service tag cannot be resolved to a usable Lo=
ST server.<br>
<br>
<br>
--Randall<br>
<br>
<br>
&gt; On Tue, Jan 28, 2020 at 4:51 PM Randall Gellens <br>
&gt; &lt;<a href=3D"mailto:rg%2Bietf@randy.pensive.org" target=3D"_blank">r=
g+ietf@randy.pensive.org</a>&gt;<br>
&gt; wrote:<br>
&gt;<br>
&gt;&gt; Version -02 of the draft was uploaded today.=C2=A0 (Version -01 th=
at<br>
&gt;&gt; addressed Ted&#39;s comments and some glitches I noticed was publi=
shed on<br>
&gt;&gt; the 21st.)=C2=A0 This is a very short draft that registers a new N=
APTR<br>
&gt;&gt; service tag.=C2=A0 I appreciate any reviews.<br>
&gt;&gt;<br>
&gt;&gt; <a href=3D"https://www.ietf.org/internet-drafts/draft-gellens-lost=
-validation-02.txt" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.o=
rg/internet-drafts/draft-gellens-lost-validation-02.txt</a><br>
&gt;&gt;<br>
&gt;&gt; Thanks!<br>
&gt;&gt;<br>
&gt;&gt; On 21 Jan 2020, at 17:30, Randall Gellens wrote:<br>
&gt;&gt;<br>
&gt;&gt;&gt; On 21 Jan 2020, at 9:29, Ted Hardie wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Hi Randy, Brian,<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Thanks for the message.=C2=A0 I took a quick look at the d=
ocument, and<br>
&gt;&gt;&gt;&gt; there are<br>
&gt;&gt;&gt;&gt; two things that might want consideration.=C2=A0 The first =
is this text,<br>
&gt;&gt;&gt;&gt; which<br>
&gt;&gt;&gt;&gt; tells you that the bursty validation traffic and the real-=
time<br>
&gt;&gt;&gt;&gt; functions<br>
&gt;&gt;&gt;&gt; may be performed by the same server:<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 A server identified using the &#39;LoST&#39; =
service tag might<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 also perform the validation function (and mig=
ht resolve to the<br>
&gt;&gt;&gt;&gt; same<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 URL as a server identified using the &#39;LoS=
T-Validation&#39; service<br>
&gt;&gt;&gt;&gt; tag),<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 but the &#39;LoST-Validation&#39; tag makes t=
his explicit.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; The &quot;tag makes this explicit.&quot; doesn&#39;t seem =
to quite cover what you<br>
&gt;&gt;&gt;&gt; want to say here.=C2=A0 Maybe:<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Because some services are configured to provide<br>
&gt;&gt;&gt;&gt; both real-time and validation functions, a server identifi=
ed<br>
&gt;&gt;&gt;&gt; using the &#39;LoST&#39; service tag may also perform the =
validation<br>
&gt;&gt;&gt;&gt; function.<br>
&gt;&gt;&gt;&gt; The &#39;Lost-Validation&#39; service tag should, however,=
 always be used<br>
&gt;&gt;&gt;&gt; first when seeking<br>
&gt;&gt;&gt;&gt; the validation service, as the two functions may be separa=
te.<br>
&gt;&gt;&gt;&gt; Fallback to the &#39;LoST&#39;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; may follow if the Lost-Validation service does not resolve=
.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Alternatively, you might cut this text and rely on the tex=
t in<br>
&gt;&gt;&gt;&gt; section 3.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; I see the issue and I like your first suggested rewording, I t=
hink<br>
&gt;&gt;&gt; that makes it more clear.=C2=A0 Thank you.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Second, the document&#39;s IANA considerations says this:<=
br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; IANA is requested to add &#39;LoST-Validation&#39; to the =
S-NAPTR <br>
&gt;&gt;&gt;&gt; Application<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 Service Tag registry created by [RFC3958]=C2=
=A0 This tag serves as a<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 counter-part to the &#39;LoST&#39; tag added =
by [RFC4848].<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; 5.1.=C2=A0 U-NAPTR Registration<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 This document registers the following U-NAPTR=
 application <br>
&gt;&gt;&gt;&gt; service<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 tag:<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Application Service Tag: LoST<br=
>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Defining Publication: This docum=
ent.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Should this be S-NAPTR and LoST-Validation, respectively, =
or am I<br>
&gt;&gt;&gt;&gt; missing<br>
&gt;&gt;&gt;&gt; something?<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; The tag name is definitely a typo, thank you very much for cat=
ching<br>
&gt;&gt;&gt; it.=C2=A0 The registry name I&#39;m not sure about.=C2=A0 The =
reason for the<br>
&gt;&gt;&gt; mismatch is that IANA calls the registry &quot;S-NAPTR Applica=
tion <br>
&gt;&gt;&gt; Service<br>
&gt;&gt;&gt; Tags&quot; while RFC 5222 calls it &quot;U-NAPTR application s=
ervice tag&quot; and<br>
&gt;&gt;&gt; RFC 3958 calls it &quot;S-NAPTR Application Service Tags&quot;=
.=C2=A0 So, honestly, <br>
&gt;&gt;&gt; I<br>
&gt;&gt;&gt; don&#39;t know what to call it.=C2=A0 I&#39;ve changed the dra=
ft to consistently<br>
&gt;&gt;&gt; use &quot;S-NAPTR&quot; since that&#39;s what IANA calls it.<b=
r>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; The updated draft is at<br>
&gt;&gt;&gt;<br>
&gt;&gt; <a href=3D"https://www.ietf.org/internet-drafts/draft-gellens-lost=
-validation-01.txt" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.o=
rg/internet-drafts/draft-gellens-lost-validation-01.txt</a><br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; (For some reason, the submit tool won&#39;t let me submit the =
.xml file,<br>
&gt;&gt;&gt; it insists the name is invalid.)<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; --Randall<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; regards,<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Ted<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; On Sat, Jan 18, 2020 at 12:05 PM Randall Gellens<br>
&gt;&gt;&gt;&gt; &lt;<a href=3D"mailto:rg%2Bietf@randy.pensive.org" target=
=3D"_blank">rg+ietf@randy.pensive.org</a>&gt;<br>
&gt;&gt;&gt;&gt; wrote:<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Working in NENA, we&#39;ve identified a need to regist=
er a new S-NAPTR<br>
&gt;&gt;&gt;&gt;&gt; service tag &#39;LoST-Validation&#39;.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Background: as some may recall, the key motivator for =
LoST was<br>
&gt;&gt;&gt;&gt;&gt; emergency<br>
&gt;&gt;&gt;&gt;&gt; services, primarily the ability to lookup a service UR=
N for a<br>
&gt;&gt;&gt;&gt;&gt; location<br>
&gt;&gt;&gt;&gt;&gt; (i.e., map &quot;URN:SERVICE:SOS&quot; to a SIP URI fo=
r a PSAP for a <br>
&gt;&gt;&gt;&gt;&gt; specific<br>
&gt;&gt;&gt;&gt;&gt; location), and secondarily the ability to validate a c=
ivic <br>
&gt;&gt;&gt;&gt;&gt; location<br>
&gt;&gt;&gt;&gt;&gt; (i.e., validate that a civic address is unique, dispat=
chable, and<br>
&gt;&gt;&gt;&gt;&gt; meets<br>
&gt;&gt;&gt;&gt;&gt; the requirements for the area). LoST provides the abil=
ity to do<br>
&gt;&gt;&gt;&gt;&gt; both.<br>
&gt;&gt;&gt;&gt;&gt; NENA i3 (which defines NG9-1-1) makes extensive use of=
 LoST. One<br>
&gt;&gt;&gt;&gt;&gt; thing<br>
&gt;&gt;&gt;&gt;&gt; NENA i3 does that was not originally contemplated when=
 LoST was<br>
&gt;&gt;&gt;&gt;&gt; developed is to allow separation of the core mapping f=
unction of<br>
&gt;&gt;&gt;&gt;&gt; LoST<br>
&gt;&gt;&gt;&gt;&gt; from the validation function. NENA i3 allows (but does=
 not <br>
&gt;&gt;&gt;&gt;&gt; require)<br>
&gt;&gt;&gt;&gt;&gt; these two services to be provided separately (with the=
 motivation<br>
&gt;&gt;&gt;&gt;&gt; that<br>
&gt;&gt;&gt;&gt;&gt; mapping is a time-crucial service done during emergenc=
y call <br>
&gt;&gt;&gt;&gt;&gt; setup,<br>
&gt;&gt;&gt;&gt;&gt; while validation is performed as data is provisioned i=
nto entities<br>
&gt;&gt;&gt;&gt;&gt; and<br>
&gt;&gt;&gt;&gt;&gt; is not time-crucial, so a provider might potentially p=
rovision and<br>
&gt;&gt;&gt;&gt;&gt; operate these two services differently). LoST uses U-N=
APTR<br>
&gt;&gt;&gt;&gt;&gt; Application<br>
&gt;&gt;&gt;&gt;&gt; Unique Strings rather than URIs to refer to other LoST=
 servers.<br>
&gt;&gt;&gt;&gt;&gt; There is<br>
&gt;&gt;&gt;&gt;&gt; currently one U-NAPTR service tag for LoST (&quot;LoST=
&quot;). In order to <br>
&gt;&gt;&gt;&gt;&gt; be<br>
&gt;&gt;&gt;&gt;&gt; able<br>
&gt;&gt;&gt;&gt;&gt; to separate service mapping from location validation, =
a second<br>
&gt;&gt;&gt;&gt;&gt; service<br>
&gt;&gt;&gt;&gt;&gt; tag is needed. Otherwise an entity can&#39;t tell from=
 an Application<br>
&gt;&gt;&gt;&gt;&gt; Unique<br>
&gt;&gt;&gt;&gt;&gt; String which service is available and can&#39;t resolv=
e an Application<br>
&gt;&gt;&gt;&gt;&gt; Unique String into a URI for a LoST server that assure=
dly is <br>
&gt;&gt;&gt;&gt;&gt; willing<br>
&gt;&gt;&gt;&gt;&gt; to<br>
&gt;&gt;&gt;&gt;&gt; perform location validation. We therefore propose to d=
efine<br>
&gt;&gt;&gt;&gt;&gt; &quot;LoST-Validation&quot; as a service tag. This wil=
l allow an entity to<br>
&gt;&gt;&gt;&gt;&gt; locate<br>
&gt;&gt;&gt;&gt;&gt; a LoST server willing to perform civic location valida=
tion, <br>
&gt;&gt;&gt;&gt;&gt; leaving<br>
&gt;&gt;&gt;&gt;&gt; &quot;LoST&quot; as the service tag for core service m=
apping.=C2=A0 (Of course, a<br>
&gt;&gt;&gt;&gt;&gt; LoST<br>
&gt;&gt;&gt;&gt;&gt; server located using the &#39;LoST&#39; service tag mi=
ght offer both <br>
&gt;&gt;&gt;&gt;&gt; mapping<br>
&gt;&gt;&gt;&gt;&gt; and<br>
&gt;&gt;&gt;&gt;&gt; validation, but the ability to use &#39;LoST-Validatio=
n&#39; in NAPTR<br>
&gt;&gt;&gt;&gt;&gt; records<br>
&gt;&gt;&gt;&gt;&gt; makes explicit which LoST servers are willing to do va=
lidation.)<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; The Service Tags registry rules that require an RFC to=
 add a tag, <br>
&gt;&gt;&gt;&gt;&gt; so<br>
&gt;&gt;&gt;&gt;&gt; I<br>
&gt;&gt;&gt;&gt;&gt; have submitted a small RFC to do this:<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt; <a href=3D"https://www.ietf.org/internet-drafts/draft-gellens-lost=
-validation-00.txt" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.o=
rg/internet-drafts/draft-gellens-lost-validation-00.txt</a><br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Comments, feedback, etc. are appreciated.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; --Randall<br>
&gt;&gt;<br>
</blockquote></div>

--000000000000840c32059d644acf--


From nobody Thu Jan 30 16:50:07 2020
Return-Path: <rg+ietf@randy.pensive.org>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E621F1200FB for <art@ietfa.amsl.com>; Thu, 30 Jan 2020 16:50:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.9
X-Spam-Level: *
X-Spam-Status: No, score=1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FORGED_RELAY_MUA_TO_MX=3.799, 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 8xRNWX81Q7YA for <art@ietfa.amsl.com>; Thu, 30 Jan 2020 16:50:03 -0800 (PST)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id 41ABB120074 for <art@ietf.org>; Thu, 30 Jan 2020 16:50:03 -0800 (PST)
Received: from [99.111.97.181] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Thu, 30 Jan 2020 16:50:02 -0800
From: "Randall Gellens" <rg+ietf@randy.pensive.org>
To: "Ted Hardie" <ted.ietf@gmail.com>
Cc: "Applications and Real-Time Area Discussion" <art@ietf.org>, "Brian Rosen" <br@brianrosen.net>
Date: Thu, 30 Jan 2020 16:50:01 -0800
X-Mailer: MailMate (1.13.1r5671)
Message-ID: <1120A2F8-5FDC-48AB-AA42-AEEAD49F5A60@randy.pensive.org>
In-Reply-To: <CA+9kkMB97UCDK_U=K0j9k71DwusP2wZrjcX2jY1N0XqGJvA8KQ@mail.gmail.com>
References: <8B4763EE-63C2-448C-AB70-BC9EE5D91D7B@randy.pensive.org> <CA+9kkMA_-dBg5gsGJJ2Tobr4Pon2B6YpoY80ugP3kBVvgSw2zw@mail.gmail.com> <3BE74F43-5037-421B-8161-5975C67DEB52@randy.pensive.org> <CA+9kkMB97UCDK_U=K0j9k71DwusP2wZrjcX2jY1N0XqGJvA8KQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_0DE4A373-021D-444C-A206-15A2902350D9_="
Embedded-HTML: [{"HTML":[344, 12441], "plain":[47, 8472], "uuid":"BD272E91-2833-4FB8-9285-DDE77AA07579"}]
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/GUZ_1Qc9jkhr8nlhRKhp8OnjceY>
Subject: Re: [art] Please review: Registering the 'LoST-Validation' NAPTR Service Tag
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Jan 2020 00:50:06 -0000

--=_MailMate_0DE4A373-021D-444C-A206-15A2902350D9_=
Content-Type: text/plain

On 30 Jan 2020, at 16:02, Ted Hardie wrote:

> Looks fine to me.
>
> Ted
> Mobile/Terse
>
> On Thu, Jan 30, 2020 at 3:44 PM Randall Gellens <rg+ietf@randy.pensive.org>
> wrote:
>
>> On 29 Jan 2020, at 12:03, Ted Hardie wrote:
>>
>>> I don't see any major issues with this.  As a very minor nit, this
>>> text:
>>>
>>>    In the absense of any NAPTR
>>>    records containing the 'LoST-Validation' service tag, the 'LoST'
>>>    service tag is used.  Fallback to the 'LoST' service tag may follow
>>>    if the 'Lost-Validation' service tag fails to result in a usable
>>> LoST
>>>    server.  Using the 'LoST-Validation' service tag might result in
>>> the
>>>    same URL as the 'LoST' service tag, or it may result in a different
>>>    URL.  The URLs might result in the same physical servers being
>>>    contacted, or different servers.
>>>
>>> is a bit confusing.  Changing:
>>>
>>>    Fallback to the 'LoST' service tag may follow
>>>    if the 'Lost-Validation' service tag fails to result in a usable
>>> LoST
>>>    server.
>>>
>>> to something like:  "Clients MAY also fallback to the "LoST" service
>>> tag
>>> if the "LoST-validation" service tag fails to resolve to a usable LoST
>>> server"
>>>
>>> Would be slightly more readable to me.
>>>
>>> regards,
>>>
>>> Ted Hardie
>>
>>
>>
>> Hi Ted,
>>
>> Thanks for the comment.  What do you think of this wording:
>>
>>     Because some servers might be configured to provide both mapping and
>>     validation functions, a server identified using the 'LoST' service
>>     tag might also perform the validation function (and resolving the
>> two
>>     tags might result in the same URL).  Because the two functions might
>>     be separate, clients seeking a LoST server for location validation
>>     should first try U-NAPTR resolution using the 'Lost-Validation'
>>     service tag, and may fallback to the 'LoST' service tag if the
>> 'Lost-
>>     Validation' service tag cannot be resolved to a usable LoST server.
>>
>>
>> --Randall
>>
>>
>>> On Tue, Jan 28, 2020 at 4:51 PM Randall Gellens
>>> <rg+ietf@randy.pensive.org>
>>> wrote:
>>>
>>>> Version -02 of the draft was uploaded today.  (Version -01 that
>>>> addressed Ted's comments and some glitches I noticed was published on
>>>> the 21st.)  This is a very short draft that registers a new NAPTR
>>>> service tag.  I appreciate any reviews.
>>>>
>>>>
>> https://www.ietf.org/internet-drafts/draft-gellens-lost-validation-02.txt
>>>>
>>>> Thanks!
>>>>
>>>> On 21 Jan 2020, at 17:30, Randall Gellens wrote:
>>>>
>>>>> On 21 Jan 2020, at 9:29, Ted Hardie wrote:
>>>>>
>>>>>> Hi Randy, Brian,
>>>>>>
>>>>>> Thanks for the message.  I took a quick look at the document, and
>>>>>> there are
>>>>>> two things that might want consideration.  The first is this text,
>>>>>> which
>>>>>> tells you that the bursty validation traffic and the real-time
>>>>>> functions
>>>>>> may be performed by the same server:
>>>>>>
>>>>>>    A server identified using the 'LoST' service tag might
>>>>>>    also perform the validation function (and might resolve to the
>>>>>> same
>>>>>>    URL as a server identified using the 'LoST-Validation' service
>>>>>> tag),
>>>>>>    but the 'LoST-Validation' tag makes this explicit.
>>>>>>
>>>>>> The "tag makes this explicit." doesn't seem to quite cover what you
>>>>>> want to say here.  Maybe:
>>>>>>
>>>>>> Because some services are configured to provide
>>>>>> both real-time and validation functions, a server identified
>>>>>> using the 'LoST' service tag may also perform the validation
>>>>>> function.
>>>>>> The 'Lost-Validation' service tag should, however, always be used
>>>>>> first when seeking
>>>>>> the validation service, as the two functions may be separate.
>>>>>> Fallback to the 'LoST'
>>>>>>
>>>>>> may follow if the Lost-Validation service does not resolve.
>>>>>>
>>>>>>
>>>>>> Alternatively, you might cut this text and rely on the text in
>>>>>> section 3.
>>>>>
>>>>> I see the issue and I like your first suggested rewording, I think
>>>>> that makes it more clear.  Thank you.
>>>>>
>>>>>
>>>>>>
>>>>>> Second, the document's IANA considerations says this:
>>>>>>
>>>>>> IANA is requested to add 'LoST-Validation' to the S-NAPTR
>>>>>> Application
>>>>>>    Service Tag registry created by [RFC3958]  This tag serves as a
>>>>>>    counter-part to the 'LoST' tag added by [RFC4848].
>>>>>>
>>>>>> 5.1.  U-NAPTR Registration
>>>>>>
>>>>>>    This document registers the following U-NAPTR application
>>>>>> service
>>>>>>    tag:
>>>>>>
>>>>>>       Application Service Tag: LoST
>>>>>>
>>>>>>       Defining Publication: This document.
>>>>>>
>>>>>> Should this be S-NAPTR and LoST-Validation, respectively, or am I
>>>>>> missing
>>>>>> something?
>>>>>
>>>>> The tag name is definitely a typo, thank you very much for catching
>>>>> it.  The registry name I'm not sure about.  The reason for the
>>>>> mismatch is that IANA calls the registry "S-NAPTR Application
>>>>> Service
>>>>> Tags" while RFC 5222 calls it "U-NAPTR application service tag" and
>>>>> RFC 3958 calls it "S-NAPTR Application Service Tags".  So, honestly,
>>>>> I
>>>>> don't know what to call it.  I've changed the draft to consistently
>>>>> use "S-NAPTR" since that's what IANA calls it.
>>>>>
>>>>> The updated draft is at
>>>>>
>>>>
>> https://www.ietf.org/internet-drafts/draft-gellens-lost-validation-01.txt
>>>>>
>>>>> (For some reason, the submit tool won't let me submit the .xml file,
>>>>> it insists the name is invalid.)
>>>>>
>>>>> --Randall
>>>>>
>>>>>>
>>>>>> regards,
>>>>>>
>>>>>> Ted
>>>>>>
>>>>>> On Sat, Jan 18, 2020 at 12:05 PM Randall Gellens
>>>>>> <rg+ietf@randy.pensive.org>
>>>>>> wrote:
>>>>>>
>>>>>>> Working in NENA, we've identified a need to register a new S-NAPTR
>>>>>>> service tag 'LoST-Validation'.
>>>>>>>
>>>>>>> Background: as some may recall, the key motivator for LoST was
>>>>>>> emergency
>>>>>>> services, primarily the ability to lookup a service URN for a
>>>>>>> location
>>>>>>> (i.e., map "URN:SERVICE:SOS" to a SIP URI for a PSAP for a
>>>>>>> specific
>>>>>>> location), and secondarily the ability to validate a civic
>>>>>>> location
>>>>>>> (i.e., validate that a civic address is unique, dispatchable, and
>>>>>>> meets
>>>>>>> the requirements for the area). LoST provides the ability to do
>>>>>>> both.
>>>>>>> NENA i3 (which defines NG9-1-1) makes extensive use of LoST. One
>>>>>>> thing
>>>>>>> NENA i3 does that was not originally contemplated when LoST was
>>>>>>> developed is to allow separation of the core mapping function of
>>>>>>> LoST
>>>>>>> from the validation function. NENA i3 allows (but does not
>>>>>>> require)
>>>>>>> these two services to be provided separately (with the motivation
>>>>>>> that
>>>>>>> mapping is a time-crucial service done during emergency call
>>>>>>> setup,
>>>>>>> while validation is performed as data is provisioned into entities
>>>>>>> and
>>>>>>> is not time-crucial, so a provider might potentially provision and
>>>>>>> operate these two services differently). LoST uses U-NAPTR
>>>>>>> Application
>>>>>>> Unique Strings rather than URIs to refer to other LoST servers.
>>>>>>> There is
>>>>>>> currently one U-NAPTR service tag for LoST ("LoST"). In order to
>>>>>>> be
>>>>>>> able
>>>>>>> to separate service mapping from location validation, a second
>>>>>>> service
>>>>>>> tag is needed. Otherwise an entity can't tell from an Application
>>>>>>> Unique
>>>>>>> String which service is available and can't resolve an Application
>>>>>>> Unique String into a URI for a LoST server that assuredly is
>>>>>>> willing
>>>>>>> to
>>>>>>> perform location validation. We therefore propose to define
>>>>>>> "LoST-Validation" as a service tag. This will allow an entity to
>>>>>>> locate
>>>>>>> a LoST server willing to perform civic location validation,
>>>>>>> leaving
>>>>>>> "LoST" as the service tag for core service mapping.  (Of course, a
>>>>>>> LoST
>>>>>>> server located using the 'LoST' service tag might offer both
>>>>>>> mapping
>>>>>>> and
>>>>>>> validation, but the ability to use 'LoST-Validation' in NAPTR
>>>>>>> records
>>>>>>> makes explicit which LoST servers are willing to do validation.)
>>>>>>>
>>>>>>> The Service Tags registry rules that require an RFC to add a tag,
>>>>>>> so
>>>>>>> I
>>>>>>> have submitted a small RFC to do this:
>>>>>>>
>>>>
>> https://www.ietf.org/internet-drafts/draft-gellens-lost-validation-00.txt
>>>>>>>
>>>>>>> Comments, feedback, etc. are appreciated.
>>>>>>>
>>>>>>> --Randall
>>>>
>>


Thanks, Ted.  I'll upload -03 now.

--Randall

--=_MailMate_0DE4A373-021D-444C-A206-15A2902350D9_=
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html>
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"=
>
</head>
<body>
<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal"><=
p dir=3D"auto">On 30 Jan 2020, at 16:02, Ted Hardie wrote:</p>
</div>
<blockquote style=3D"border-left:2px solid #777; color:#777; margin:0 0 5=
px; padding-left:5px"><div id=3D"BD272E91-2833-4FB8-9285-DDE77AA07579"><d=
iv dir=3D"ltr"><div>Looks fine to me.</div><div><br></div><div>Ted</div><=
div>Mobile/Terse<br></div></div><br><div class=3D"gmail_quote"><div dir=3D=
"ltr" class=3D"gmail_attr">On Thu, Jan 30, 2020 at 3:44 PM Randall Gellen=
s &lt;<a href=3D"mailto:rg%2Bietf@randy.pensive.org">rg+ietf@randy.pensiv=
e.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-l=
eft:1ex">On 29 Jan 2020, at 12:03, Ted Hardie wrote:<br>
<br>
&gt; I don&#39;t see any major issues with this.=C2=A0 As a very minor ni=
t, this <br>
&gt; text:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 In the absense of any NAPTR<br>
&gt;=C2=A0 =C2=A0 records containing the &#39;LoST-Validation&#39; servic=
e tag, the &#39;LoST&#39;<br>
&gt;=C2=A0 =C2=A0 service tag is used.=C2=A0 Fallback to the &#39;LoST&#3=
9; service tag may follow<br>
&gt;=C2=A0 =C2=A0 if the &#39;Lost-Validation&#39; service tag fails to r=
esult in a usable <br>
&gt; LoST<br>
&gt;=C2=A0 =C2=A0 server.=C2=A0 Using the &#39;LoST-Validation&#39; servi=
ce tag might result in <br>
&gt; the<br>
&gt;=C2=A0 =C2=A0 same URL as the &#39;LoST&#39; service tag, or it may r=
esult in a different<br>
&gt;=C2=A0 =C2=A0 URL.=C2=A0 The URLs might result in the same physical s=
ervers being<br>
&gt;=C2=A0 =C2=A0 contacted, or different servers.<br>
&gt;<br>
&gt; is a bit confusing.=C2=A0 Changing:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 Fallback to the &#39;LoST&#39; service tag may follow<b=
r>
&gt;=C2=A0 =C2=A0 if the &#39;Lost-Validation&#39; service tag fails to r=
esult in a usable <br>
&gt; LoST<br>
&gt;=C2=A0 =C2=A0 server.<br>
&gt;<br>
&gt; to something like:=C2=A0 &quot;Clients MAY also fallback to the &quo=
t;LoST&quot; service <br>
&gt; tag<br>
&gt; if the &quot;LoST-validation&quot; service tag fails to resolve to a=
 usable LoST <br>
&gt; server&quot;<br>
&gt;<br>
&gt; Would be slightly more readable to me.<br>
&gt;<br>
&gt; regards,<br>
&gt;<br>
&gt; Ted Hardie<br>
<br>
<br>
<br>
Hi Ted,<br>
<br>
Thanks for the comment.=C2=A0 What do you think of this wording:<br>
<br>
=C2=A0 =C2=A0 Because some servers might be configured to provide both ma=
pping and<br>
=C2=A0 =C2=A0 validation functions, a server identified using the &#39;Lo=
ST&#39; service<br>
=C2=A0 =C2=A0 tag might also perform the validation function (and resolvi=
ng the <br>
two<br>
=C2=A0 =C2=A0 tags might result in the same URL).=C2=A0 Because the two f=
unctions might<br>
=C2=A0 =C2=A0 be separate, clients seeking a LoST server for location val=
idation<br>
=C2=A0 =C2=A0 should first try U-NAPTR resolution using the &#39;Lost-Val=
idation&#39;<br>
=C2=A0 =C2=A0 service tag, and may fallback to the &#39;LoST&#39; service=
 tag if the <br>
&#39;Lost-<br>
=C2=A0 =C2=A0 Validation&#39; service tag cannot be resolved to a usable =
LoST server.<br>
<br>
<br>
--Randall<br>
<br>
<br>
&gt; On Tue, Jan 28, 2020 at 4:51 PM Randall Gellens <br>
&gt; &lt;<a href=3D"mailto:rg%2Bietf@randy.pensive.org" target=3D"_blank"=
>rg+ietf@randy.pensive.org</a>&gt;<br>
&gt; wrote:<br>
&gt;<br>
&gt;&gt; Version -02 of the draft was uploaded today.=C2=A0 (Version -01 =
that<br>
&gt;&gt; addressed Ted&#39;s comments and some glitches I noticed was pub=
lished on<br>
&gt;&gt; the 21st.)=C2=A0 This is a very short draft that registers a new=
 NAPTR<br>
&gt;&gt; service tag.=C2=A0 I appreciate any reviews.<br>
&gt;&gt;<br>
&gt;&gt; <a href=3D"https://www.ietf.org/internet-drafts/draft-gellens-lo=
st-validation-02.txt" rel=3D"noreferrer" target=3D"_blank">https://www.ie=
tf.org/internet-drafts/draft-gellens-lost-validation-02.txt</a><br>
&gt;&gt;<br>
&gt;&gt; Thanks!<br>
&gt;&gt;<br>
&gt;&gt; On 21 Jan 2020, at 17:30, Randall Gellens wrote:<br>
&gt;&gt;<br>
&gt;&gt;&gt; On 21 Jan 2020, at 9:29, Ted Hardie wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Hi Randy, Brian,<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Thanks for the message.=C2=A0 I took a quick look at the=
 document, and<br>
&gt;&gt;&gt;&gt; there are<br>
&gt;&gt;&gt;&gt; two things that might want consideration.=C2=A0 The firs=
t is this text,<br>
&gt;&gt;&gt;&gt; which<br>
&gt;&gt;&gt;&gt; tells you that the bursty validation traffic and the rea=
l-time<br>
&gt;&gt;&gt;&gt; functions<br>
&gt;&gt;&gt;&gt; may be performed by the same server:<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 A server identified using the &#39;LoST&#39=
; service tag might<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 also perform the validation function (and m=
ight resolve to the<br>
&gt;&gt;&gt;&gt; same<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 URL as a server identified using the &#39;L=
oST-Validation&#39; service<br>
&gt;&gt;&gt;&gt; tag),<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 but the &#39;LoST-Validation&#39; tag makes=
 this explicit.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; The &quot;tag makes this explicit.&quot; doesn&#39;t see=
m to quite cover what you<br>
&gt;&gt;&gt;&gt; want to say here.=C2=A0 Maybe:<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Because some services are configured to provide<br>
&gt;&gt;&gt;&gt; both real-time and validation functions, a server identi=
fied<br>
&gt;&gt;&gt;&gt; using the &#39;LoST&#39; service tag may also perform th=
e validation<br>
&gt;&gt;&gt;&gt; function.<br>
&gt;&gt;&gt;&gt; The &#39;Lost-Validation&#39; service tag should, howeve=
r, always be used<br>
&gt;&gt;&gt;&gt; first when seeking<br>
&gt;&gt;&gt;&gt; the validation service, as the two functions may be sepa=
rate.<br>
&gt;&gt;&gt;&gt; Fallback to the &#39;LoST&#39;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; may follow if the Lost-Validation service does not resol=
ve.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Alternatively, you might cut this text and rely on the t=
ext in<br>
&gt;&gt;&gt;&gt; section 3.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; I see the issue and I like your first suggested rewording, I=
 think<br>
&gt;&gt;&gt; that makes it more clear.=C2=A0 Thank you.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Second, the document&#39;s IANA considerations says this=
:<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; IANA is requested to add &#39;LoST-Validation&#39; to th=
e S-NAPTR <br>
&gt;&gt;&gt;&gt; Application<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 Service Tag registry created by [RFC3958]=C2=
=A0 This tag serves as a<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 counter-part to the &#39;LoST&#39; tag adde=
d by [RFC4848].<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; 5.1.=C2=A0 U-NAPTR Registration<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 This document registers the following U-NAP=
TR application <br>
&gt;&gt;&gt;&gt; service<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 tag:<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Application Service Tag: LoST<=
br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Defining Publication: This doc=
ument.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Should this be S-NAPTR and LoST-Validation, respectively=
, or am I<br>
&gt;&gt;&gt;&gt; missing<br>
&gt;&gt;&gt;&gt; something?<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; The tag name is definitely a typo, thank you very much for c=
atching<br>
&gt;&gt;&gt; it.=C2=A0 The registry name I&#39;m not sure about.=C2=A0 Th=
e reason for the<br>
&gt;&gt;&gt; mismatch is that IANA calls the registry &quot;S-NAPTR Appli=
cation <br>
&gt;&gt;&gt; Service<br>
&gt;&gt;&gt; Tags&quot; while RFC 5222 calls it &quot;U-NAPTR application=
 service tag&quot; and<br>
&gt;&gt;&gt; RFC 3958 calls it &quot;S-NAPTR Application Service Tags&quo=
t;.=C2=A0 So, honestly, <br>
&gt;&gt;&gt; I<br>
&gt;&gt;&gt; don&#39;t know what to call it.=C2=A0 I&#39;ve changed the d=
raft to consistently<br>
&gt;&gt;&gt; use &quot;S-NAPTR&quot; since that&#39;s what IANA calls it.=
<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; The updated draft is at<br>
&gt;&gt;&gt;<br>
&gt;&gt; <a href=3D"https://www.ietf.org/internet-drafts/draft-gellens-lo=
st-validation-01.txt" rel=3D"noreferrer" target=3D"_blank">https://www.ie=
tf.org/internet-drafts/draft-gellens-lost-validation-01.txt</a><br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; (For some reason, the submit tool won&#39;t let me submit th=
e .xml file,<br>
&gt;&gt;&gt; it insists the name is invalid.)<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; --Randall<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; regards,<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Ted<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; On Sat, Jan 18, 2020 at 12:05 PM Randall Gellens<br>
&gt;&gt;&gt;&gt; &lt;<a href=3D"mailto:rg%2Bietf@randy.pensive.org" targe=
t=3D"_blank">rg+ietf@randy.pensive.org</a>&gt;<br>
&gt;&gt;&gt;&gt; wrote:<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Working in NENA, we&#39;ve identified a need to regi=
ster a new S-NAPTR<br>
&gt;&gt;&gt;&gt;&gt; service tag &#39;LoST-Validation&#39;.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Background: as some may recall, the key motivator fo=
r LoST was<br>
&gt;&gt;&gt;&gt;&gt; emergency<br>
&gt;&gt;&gt;&gt;&gt; services, primarily the ability to lookup a service =
URN for a<br>
&gt;&gt;&gt;&gt;&gt; location<br>
&gt;&gt;&gt;&gt;&gt; (i.e., map &quot;URN:SERVICE:SOS&quot; to a SIP URI =
for a PSAP for a <br>
&gt;&gt;&gt;&gt;&gt; specific<br>
&gt;&gt;&gt;&gt;&gt; location), and secondarily the ability to validate a=
 civic <br>
&gt;&gt;&gt;&gt;&gt; location<br>
&gt;&gt;&gt;&gt;&gt; (i.e., validate that a civic address is unique, disp=
atchable, and<br>
&gt;&gt;&gt;&gt;&gt; meets<br>
&gt;&gt;&gt;&gt;&gt; the requirements for the area). LoST provides the ab=
ility to do<br>
&gt;&gt;&gt;&gt;&gt; both.<br>
&gt;&gt;&gt;&gt;&gt; NENA i3 (which defines NG9-1-1) makes extensive use =
of LoST. One<br>
&gt;&gt;&gt;&gt;&gt; thing<br>
&gt;&gt;&gt;&gt;&gt; NENA i3 does that was not originally contemplated wh=
en LoST was<br>
&gt;&gt;&gt;&gt;&gt; developed is to allow separation of the core mapping=
 function of<br>
&gt;&gt;&gt;&gt;&gt; LoST<br>
&gt;&gt;&gt;&gt;&gt; from the validation function. NENA i3 allows (but do=
es not <br>
&gt;&gt;&gt;&gt;&gt; require)<br>
&gt;&gt;&gt;&gt;&gt; these two services to be provided separately (with t=
he motivation<br>
&gt;&gt;&gt;&gt;&gt; that<br>
&gt;&gt;&gt;&gt;&gt; mapping is a time-crucial service done during emerge=
ncy call <br>
&gt;&gt;&gt;&gt;&gt; setup,<br>
&gt;&gt;&gt;&gt;&gt; while validation is performed as data is provisioned=
 into entities<br>
&gt;&gt;&gt;&gt;&gt; and<br>
&gt;&gt;&gt;&gt;&gt; is not time-crucial, so a provider might potentially=
 provision and<br>
&gt;&gt;&gt;&gt;&gt; operate these two services differently). LoST uses U=
-NAPTR<br>
&gt;&gt;&gt;&gt;&gt; Application<br>
&gt;&gt;&gt;&gt;&gt; Unique Strings rather than URIs to refer to other Lo=
ST servers.<br>
&gt;&gt;&gt;&gt;&gt; There is<br>
&gt;&gt;&gt;&gt;&gt; currently one U-NAPTR service tag for LoST (&quot;Lo=
ST&quot;). In order to <br>
&gt;&gt;&gt;&gt;&gt; be<br>
&gt;&gt;&gt;&gt;&gt; able<br>
&gt;&gt;&gt;&gt;&gt; to separate service mapping from location validation=
, a second<br>
&gt;&gt;&gt;&gt;&gt; service<br>
&gt;&gt;&gt;&gt;&gt; tag is needed. Otherwise an entity can&#39;t tell fr=
om an Application<br>
&gt;&gt;&gt;&gt;&gt; Unique<br>
&gt;&gt;&gt;&gt;&gt; String which service is available and can&#39;t reso=
lve an Application<br>
&gt;&gt;&gt;&gt;&gt; Unique String into a URI for a LoST server that assu=
redly is <br>
&gt;&gt;&gt;&gt;&gt; willing<br>
&gt;&gt;&gt;&gt;&gt; to<br>
&gt;&gt;&gt;&gt;&gt; perform location validation. We therefore propose to=
 define<br>
&gt;&gt;&gt;&gt;&gt; &quot;LoST-Validation&quot; as a service tag. This w=
ill allow an entity to<br>
&gt;&gt;&gt;&gt;&gt; locate<br>
&gt;&gt;&gt;&gt;&gt; a LoST server willing to perform civic location vali=
dation, <br>
&gt;&gt;&gt;&gt;&gt; leaving<br>
&gt;&gt;&gt;&gt;&gt; &quot;LoST&quot; as the service tag for core service=
 mapping.=C2=A0 (Of course, a<br>
&gt;&gt;&gt;&gt;&gt; LoST<br>
&gt;&gt;&gt;&gt;&gt; server located using the &#39;LoST&#39; service tag =
might offer both <br>
&gt;&gt;&gt;&gt;&gt; mapping<br>
&gt;&gt;&gt;&gt;&gt; and<br>
&gt;&gt;&gt;&gt;&gt; validation, but the ability to use &#39;LoST-Validat=
ion&#39; in NAPTR<br>
&gt;&gt;&gt;&gt;&gt; records<br>
&gt;&gt;&gt;&gt;&gt; makes explicit which LoST servers are willing to do =
validation.)<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; The Service Tags registry rules that require an RFC =
to add a tag, <br>
&gt;&gt;&gt;&gt;&gt; so<br>
&gt;&gt;&gt;&gt;&gt; I<br>
&gt;&gt;&gt;&gt;&gt; have submitted a small RFC to do this:<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt; <a href=3D"https://www.ietf.org/internet-drafts/draft-gellens-lo=
st-validation-00.txt" rel=3D"noreferrer" target=3D"_blank">https://www.ie=
tf.org/internet-drafts/draft-gellens-lost-validation-00.txt</a><br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Comments, feedback, etc. are appreciated.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; --Randall<br>
&gt;&gt;<br>
</blockquote></div></div></blockquote>
<div style=3D"white-space:normal"><blockquote style=3D"border-left:2px so=
lid #777; color:#777; margin:0 0 5px; padding-left:5px">
</blockquote><p dir=3D"auto">Thanks, Ted.  I'll upload -03 now.</p>
<p dir=3D"auto">--Randall</p>
</div>
</div>
</body>
</html>

--=_MailMate_0DE4A373-021D-444C-A206-15A2902350D9_=--

