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

Cullen Jennings <fluffy@iii.ca> Fri, 12 May 2017 00:13 UTC

Return-Path: <fluffy@iii.ca>
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 C825E124234 for <dispatch@ietfa.amsl.com>; Thu, 11 May 2017 17:13:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.802
X-Spam-Level:
X-Spam-Status: No, score=-2.802 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, 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 zqYABlGFY07A for <dispatch@ietfa.amsl.com>; Thu, 11 May 2017 17:13:06 -0700 (PDT)
Received: from smtp112.iad3a.emailsrvr.com (smtp112.iad3a.emailsrvr.com [173.203.187.112]) (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 EB06E12EABF for <dispatch@ietf.org>; Thu, 11 May 2017 17:08:43 -0700 (PDT)
Received: from smtp15.relay.iad3a.emailsrvr.com (localhost [127.0.0.1]) by smtp15.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id 11AFE5291 for <dispatch@ietf.org>; Thu, 11 May 2017 20:08:43 -0400 (EDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp15.relay.iad3a.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id CE525526D for <dispatch@ietf.org>; Thu, 11 May 2017 20:08:42 -0400 (EDT)
X-Sender-Id: fluffy@iii.ca
Received: from [10.92.108.188] (184-23-135-130.dedicated.static.sonic.net [184.23.135.130]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:587 (trex/5.7.12); Thu, 11 May 2017 20:08:43 -0400
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <20170510022108.27204.qmail@ary.lan>
Date: Thu, 11 May 2017 17:08:41 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <BD1F84B0-04EB-4CB4-9D3D-F3317DF8DA7F@iii.ca>
References: <20170510022108.27204.qmail@ary.lan>
To: DISPATCH list <dispatch@ietf.org>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/nmad_7xDP6dVOiLGULMupCyBqD0>
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, 12 May 2017 00:13:11 -0000

It sounds like this has dispatched itself so from a chair point of view, I don't think we need to do much more here. Let us know if you think we need to so something else.

Thanks, Cullen (one of the chairs)



> On May 9, 2017, at 7:21 PM, John Levine <johnl@taugh.com> wrote:
> 
> 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]
>> -=-=-=-=-=-
> 
> 
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch