Re: [dispatch] Registration of "hxxp" URI scheme

"John Levine" <johnl@taugh.com> Fri, 05 May 2017 16:18 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EADF9129ACD for <dispatch@ietfa.amsl.com>; Fri, 5 May 2017 09:18:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.579
X-Spam-Level: *
X-Spam-Status: No, score=1.579 tagged_above=-999 required=5 tests=[BAYES_50=0.8, SPF_NEUTRAL=0.779] 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 YCJPsNMbIwgZ for <dispatch@ietfa.amsl.com>; Fri, 5 May 2017 09:18:14 -0700 (PDT)
Received: from miucha.iecc.com (w6.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C9E4812941C for <dispatch@ietf.org>; Fri, 5 May 2017 09:18:12 -0700 (PDT)
Received: (qmail 89618 invoked from network); 5 May 2017 16:18:10 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 5 May 2017 16:18:10 -0000
Date: Fri, 05 May 2017 16:17:48 -0000
Message-ID: <20170505161748.7184.qmail@ary.lan>
From: John Levine <johnl@taugh.com>
To: dispatch@ietf.org
In-Reply-To: <20170505155326.GH14760@vulcano.intra.nic.cl>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/6xCxl4J5d_9z_LEs8xxF-OH52Q0>
Subject: Re: [dispatch] Registration of "hxxp" URI scheme
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 May 2017 16:18:18 -0000

In article <20170505155326.GH14760@vulcano.intra.nic.cl> you write:
>-=-=-=-=-=-
>
>Dear dispatch WG.
>I recently realized there's no registration for the "hxxp"
>scheme in the IANA table. This scheme had become a de-facto
>standard from many years, inside the security community,
>to obfuscate malicious urls. I think it deserves to be
>registered for block and documentation matters.

Since the whole point of hxxp is to prevent interoperation, I don't
understand what problem a permanent registration would solve.  It
doesn't seem very likely that anyone would use those four letters to
mean anything else. but if you want a placeholder to prevent that, a
provisional FCFS registration would do the trick.

R's,
John