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

"John Levine" <johnl@taugh.com> Wed, 10 May 2017 02:21 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 95CE312EBBC for <dispatch@ietfa.amsl.com>; Tue, 9 May 2017 19:21:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.779
X-Spam-Level:
X-Spam-Status: No, score=0.779 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, SPF_NEUTRAL=0.779, 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 zgARNJbecOiV for <dispatch@ietfa.amsl.com>; Tue, 9 May 2017 19:21:33 -0700 (PDT)
Received: from miucha.iecc.com (www.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 3B51412EBB6 for <dispatch@ietf.org>; Tue, 9 May 2017 19:21:32 -0700 (PDT)
Received: (qmail 24952 invoked from network); 10 May 2017 02:21:30 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 10 May 2017 02:21:30 -0000
Date: Wed, 10 May 2017 02:21:08 -0000
Message-ID: <20170510022108.27204.qmail@ary.lan>
From: John Levine <johnl@taugh.com>
To: dispatch@ietf.org
In-Reply-To: <20170510013932.GB21191@pepino>
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/3UaJSUq7QfPf2fnC2Ov_devEs5A>
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: Wed, 10 May 2017 02:21:38 -0000

In article <20170510013932.GB21191@pepino> you write:
>-=-=-=-=-=-
>
>Thanks John and Mark.
>Fair enough. I've asked and received the provisional registration,
>with the draft as reference. In case its needed, it can be upgraded
>to permanent in the future.

You might as well grab hxxps too.

R's,
John



>On 13:33 08/05, Mark Nottingham wrote:
>> I think it's worth having a registry entry if this is widespread practice, if only to prevent accidental use.
>> 
>> I agree that a provisional registration would do that. 
>> 
>> Cheers,
>> 
>> 
>> > On 6 May 2017, at 2:17 am, John Levine <johnl@taugh.com> wrote:
>> > 
>> > 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
>> > 
>> > _______________________________________________
>> > dispatch mailing list
>> > dispatch@ietf.org
>> > https://www.ietf.org/mailman/listinfo/dispatch
>> 
>> --
>> Mark Nottingham   https://www.mnot.net/
>> 
>> _______________________________________________
>> dispatch mailing list
>> dispatch@ietf.org
>> https://www.ietf.org/mailman/listinfo/dispatch
>> 
>
>-=-=-=-=-=-
>[Attachment type=application/pgp-signature, name=signature.asc]
>-=-=-=-=-=-