[dispatch] Registration of "hxxp" URI scheme
Hugo Salgado-Hernández <hsalgado@nic.cl> Fri, 05 May 2017 15:53 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 8C8741298A1 for <dispatch@ietfa.amsl.com>; Fri, 5 May 2017 08:53:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.797
X-Spam-Level:
X-Spam-Status: No, score=0.797 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-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 Viv06N0gmixd for <dispatch@ietfa.amsl.com>; Fri, 5 May 2017 08:53:32 -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 E3BBB129572 for <dispatch@ietf.org>; Fri, 5 May 2017 08:53:28 -0700 (PDT)
Received: from mail.nic.cl (localhost [127.0.0.1]) by mail.nic.cl (Postfix) with ESMTP id 39A028004F6 for <dispatch@ietf.org>; Fri, 5 May 2017 12:53:27 -0300 (CLST)
Received: from vulcano.intra.nic.cl (unknown [IPv6:2001:1398:4:6:a986:59d3:cbbf:59e5]) (using TLSv1.2 with cipher AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.nic.cl (Postfix) with ESMTPS id 22D668004D0 for <dispatch@ietf.org>; Fri, 5 May 2017 12:53:27 -0300 (CLST)
Date: Fri, 05 May 2017 12:53:26 -0300
From: Hugo Salgado-Hernández <hsalgado@nic.cl>
To: dispatch@ietf.org
Message-ID: <20170505155326.GH14760@vulcano.intra.nic.cl>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="MzdA25v054BPvyZa"
Content-Disposition: inline
User-Agent: Mutt/1.8.0 (2017-02-23)
X-Virus-Scanned: ClamAV using ClamSMTP on Fri May 5 12:53:27 2017 -0300 (CLST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/e046TSRxM4k8vwxbAE3LIWwA-xg>
Subject: [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 15:53:35 -0000
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. I wrote a short draft but I'm not sure of the path forward. I know I can ask for a "provisional" registration, but I can't find any description or document to point as a reference. So maybe will be an opportunity to publish an spec as an Informational RFC and point to it, being a provisional or permanent registration. Draft is here https://datatracker.ietf.org/doc/draft-salgado-hxxp/ What do you think? Best, Hugo
- [dispatch] Registration of "hxxp" URI scheme Hugo Salgado-Hernández
- Re: [dispatch] Registration of "hxxp" URI scheme John Levine
- Re: [dispatch] Registration of "hxxp" URI scheme Mark Nottingham
- Re: [dispatch] Registration of "hxxp" URI scheme Hugo Salgado-Hernández
- Re: [dispatch] Registration of "hxxp" URI scheme John Levine
- Re: [dispatch] Registration of "hxxp" URI scheme Cullen Jennings