Re: [DNSOP] Minor editorial change to draft-ietf-dnsop-sutld-ps

John C Klensin <john-ietf@jck.com> Fri, 07 July 2017 03:36 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1ECA912741D; Thu, 6 Jul 2017 20:36:32 -0700 (PDT)
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, RP_MATCHES_RCVD=-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 RrKXrtlQN8Dz; Thu, 6 Jul 2017 20:36:30 -0700 (PDT)
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 427B61317B0; Thu, 6 Jul 2017 20:36:30 -0700 (PDT)
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 1dTK4A-000AWp-Sb; Thu, 06 Jul 2017 23:36:26 -0400
Date: Thu, 06 Jul 2017 23:36:21 -0400
From: John C Klensin <john-ietf@jck.com>
To: Mark Andrews <marka@isc.org>
cc: "Roy T. Fielding" <fielding@gbiv.com>, dnsop <dnsop@ietf.org>, IETF Rinse Repeat <ietf@ietf.org>
Message-ID: <707A073EEBAE4B87504AB9B4@PSB>
In-Reply-To: <20170707004259.541A17DB62A2@rock.dv.isc.org>
References: <CAHw9_iJQ31wqLavOhtMpPOBhGP4j6CLk45KHGdX5vOA+qj4nQA@mail.gmail.com> <m2a84kzm4y.wl-randy@psg.com> <F98FEA1C-3F3F-4344-8B07-996AAD899CC2@fugue.com> <m2shicxr0h.wl-randy@psg.com> <A70FD34B-000A-4748-B1B2-BF6DF66C7D6C@fugue.com> <m2podgxq97.wl-randy@psg.com> <5F120298-CD66-4CB6-9DC5-0C5DF6F02CC7@fugue.com> <CACfw2hhx+-Z=7ZnnaOkToc+Bd7aKDpBFt+nFUxkt9sKqLn4D8Q@mail.gmail.com> <2DF1AFC7-643B-4610-8EB8-0616D3D0B024@fugue.com> <20170705000229.5918D7D8457F@rock.dv.isc.org> <CACweHNCAi7JcOW9CX=6FViv1wUoe5fhn7deJ2eieP2-D_FhaSA@mail.gmail.com> <20170705031957.834B97D8FBDD@rock.dv.isc.org> <CACweHNCAmZPOUmat5ruh6qkYrECM2fh15n49P+zDcJ0gfoEGvg@mail.gmail.com> <765A15BF-8505-4470-9628-70CE9665BC16@gbiv.com> <20170705231101.E23E77D9B7A1@rock.dv.isc.org> <901C29488D8446E4176CF83E@PSB> <20170707004259.541A17DB62A2@rock.dv.isc.org>
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/dnsop/TxaKg1mtHsssD470O-AjQ9msr3w>
Subject: Re: [DNSOP] Minor editorial change to draft-ietf-dnsop-sutld-ps
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jul 2017 03:36:32 -0000


--On Friday, July 7, 2017 10:42 +1000 Mark Andrews
<marka@isc.org>; wrote:

>> The same subsection of RFC 3986 also uses the term "host
>> subcomponent" for what you are referring to as a name and
>> allows it to be a "registered name" (or <reg-name>) that
>> might not be a DNS name or reference at all -- whether it is
>> or not is scheme-dependent. 
>...

> Which really should never have been allowed.  Beyound the UI
> everything should be absolute.  Relative names in URI really
> don't work in practice because search lists are not
> constistent even inside a single organisation.

Mark, it is no secret that I'm not a fan of relative URIs or of
3986 generally.  But the latter is, for better or worse, a full
standard that went through the IETF process.   If you think it
is seriously flawed, I'd encourage you to write in I-D to fix it
and see if you can get it through the system.  My experience
predicts that any attempt to do such a thing will produce an
outcry about the astronomical number of web pages that contain
and depend on such references and the only slightly smaller
number of them that are used every day, but maybe you will do
better than I did when I tried to get something with far
narrower scope through the system.

> I had my ISP hand me a relative link for their support pages.
> IT DID NOT WORK.  There support line got a call complaining
> about it.

With the above in mind, so?  The number of links most of us see
a week that don't work --whether the references are relative or
absolute-- is rather too large to view one failure as horrible
breakage in the model.

    john