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

Hugo Salgado-Hernández <hsalgado@nic.cl> Wed, 10 May 2017 01:39 UTC

Return-Path: <hsalgado@nic.cl>
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 74B6612EBA9 for <dispatch@ietfa.amsl.com>; Tue, 9 May 2017 18:39:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.798
X-Spam-Level:
X-Spam-Status: No, score=0.798 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-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 awsVZ30i7E7o for <dispatch@ietfa.amsl.com>; Tue, 9 May 2017 18:39:37 -0700 (PDT)
Received: from mail.nic.cl (mail.nic.cl [IPv6:2001:1398:1::6008]) (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 76ADC12EBA6 for <dispatch@ietf.org>; Tue, 9 May 2017 18:39:37 -0700 (PDT)
Received: from mail.nic.cl (localhost [127.0.0.1]) by mail.nic.cl (Postfix) with ESMTP id 1E82E800246; Tue, 9 May 2017 22:39:34 -0300 (CLST)
Received: from pepino (hsalgado-vpn.intra.nic.cl [172.30.14.17]) (using TLSv1.2 with cipher AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.nic.cl (Postfix) with ESMTPSA id EDAD3800213; Tue, 9 May 2017 22:39:33 -0300 (CLST)
Date: Tue, 09 May 2017 22:39:32 -0300
From: Hugo Salgado-Hernández <hsalgado@nic.cl>
To: Mark Nottingham <mnot@mnot.net>
Cc: John Levine <johnl@taugh.com>, dispatch@ietf.org
Message-ID: <20170510013932.GB21191@pepino>
References: <20170505161748.7184.qmail@ary.lan> <672B55E1-FC53-42C4-8618-9937BEDAFF0F@mnot.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="ILuaRSyQpoVaJ1HG"
Content-Disposition: inline
In-Reply-To: <672B55E1-FC53-42C4-8618-9937BEDAFF0F@mnot.net>
User-Agent: Mutt/1.8.0 (2017-02-23)
X-Virus-Scanned: ClamAV using ClamSMTP on Tue May 9 22:39:34 2017 -0300 (CLST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/TbIqOsT3SG0QE6vQ8XnZwysDsrE>
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 01:39:41 -0000

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.

Hugo

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
>