From nobody Fri May 5 08:53:36 2017 Return-Path: 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 ; 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 ; 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 ; 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 ; 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 ; Fri, 5 May 2017 12:53:27 -0300 (CLST) Date: Fri, 5 May 2017 12:53:26 -0300 From: Hugo =?iso-8859-1?Q?Salgado-Hern=E1ndez?= 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: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2017 15:53:35 -0000 --MzdA25v054BPvyZa Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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 --MzdA25v054BPvyZa Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBAgAGBQJZDJ/1AAoJELDuRLDm9OmtSiYP/RWbQ2TXM+f/wTcJWoxBJvU8 5GoxDSGJacLHt3zB8i86YM9F7ovXv6O9zQVssNEbqAWpjAbcc2pJ7RDB8n/ZxUY7 TZph2XTyWMaRRQwA8T7HEOJr2boolIDuRWyNRoiIqdgHToxEDZKgOYgsRRmKsL+P U5xrfbYynVfx5Bpsq9Kqq3+N/8Q8JyCQLgCSrPEAam8o+un71pBPZkDQ7xDfxHFn EJN3bU13IdTN9tXwmXVJNrcFJes+ikgI2n0JWXMr3Z/4Rz7FQWUwnDvxkRMl0hFm uMDPfJBRLManCvhhKvC5bGPR5zQbSgtG5oCdH/3vnf7M3FHa6uC9s5MnsuhGyMyg zOdQLtL6BJX0tq2p1kOz0dLe4KJV1lLKpB97q7prrPjFdjm79i+2Ja9GqOuVkqD9 LOrFGBuCTJhXMy7ku9Phr4i+ERONRICWjA8QmffIlMEM7MyOBRCySXhh9tyPVdCx LmBsmfGHI8+LDwLphmhC+sK0o7E4E51DLKXr9HlTWiCsbMCx/m54JVRcYf4arqPN 7fdO9yWmTq8HNHm3fztVgF5OwpQ/t+ogfl/7ayVw2WnGNhrBDCxBHfOlcg3SQ9nR cqeCr27wgh1U6PuktjUm+cyCT1GXPkj+CQBKRIzRBm3Ig1DEtPYzypWp6Ixob7sz T5blq3r7nczwhLferrIZ =PiCI -----END PGP SIGNATURE----- --MzdA25v054BPvyZa-- From nobody Fri May 5 09:18:19 2017 Return-Path: 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 ; 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 ; 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 ; 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: 5 May 2017 16:17:48 -0000 Message-ID: <20170505161748.7184.qmail@ary.lan> From: "John Levine" 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: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 From nobody Sun May 7 20:33:09 2017 Return-Path: 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 9020F126D74 for ; Sun, 7 May 2017 20:33:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.098 X-Spam-Level: X-Spam-Status: No, score=0.098 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_LOW=-0.7, 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 YtgEJ3u38nQC for ; Sun, 7 May 2017 20:33:04 -0700 (PDT) Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) (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 D08A412025C for ; Sun, 7 May 2017 20:33:04 -0700 (PDT) Received: from [192.168.1.18] (unknown [124.189.96.43]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 79D5922E256; Sun, 7 May 2017 23:33:03 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) From: Mark Nottingham In-Reply-To: <20170505161748.7184.qmail@ary.lan> Date: Mon, 8 May 2017 13:33:00 +1000 Cc: dispatch@ietf.org Content-Transfer-Encoding: quoted-printable Message-Id: <672B55E1-FC53-42C4-8618-9937BEDAFF0F@mnot.net> References: <20170505161748.7184.qmail@ary.lan> To: John Levine X-Mailer: Apple Mail (2.3273) Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 May 2017 03:33:08 -0000 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.=20 Cheers, > On 6 May 2017, at 2:17 am, John Levine wrote: >=20 > In article <20170505155326.GH14760@vulcano.intra.nic.cl> you write: >> -=3D-=3D-=3D-=3D-=3D- >>=20 >> 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. >=20 > 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. >=20 > R's, > John >=20 > _______________________________________________ > dispatch mailing list > dispatch@ietf.org > https://www.ietf.org/mailman/listinfo/dispatch -- Mark Nottingham https://www.mnot.net/ From nobody Tue May 9 18:39:43 2017 Return-Path: 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 ; 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 ; 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 ; 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, 9 May 2017 22:39:32 -0300 From: Hugo =?iso-8859-1?Q?Salgado-Hern=E1ndez?= To: Mark Nottingham Cc: John Levine , 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: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 May 2017 01:39:41 -0000 --ILuaRSyQpoVaJ1HG Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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. >=20 > I agree that a provisional registration would do that.=20 >=20 > Cheers, >=20 >=20 > > On 6 May 2017, at 2:17 am, John Levine wrote: > >=20 > > In article <20170505155326.GH14760@vulcano.intra.nic.cl> you write: > >> -=3D-=3D-=3D-=3D-=3D- > >>=20 > >> 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. > >=20 > > 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. > >=20 > > R's, > > John > >=20 > > _______________________________________________ > > dispatch mailing list > > dispatch@ietf.org > > https://www.ietf.org/mailman/listinfo/dispatch >=20 > -- > Mark Nottingham https://www.mnot.net/ >=20 > _______________________________________________ > dispatch mailing list > dispatch@ietf.org > https://www.ietf.org/mailman/listinfo/dispatch >=20 --ILuaRSyQpoVaJ1HG Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBAgAGBQJZEm9UAAoJELDuRLDm9Omt8iEQAI72eVGz40202fLC2MVIw8mD hXDn+cFJWFF/6oo0o2odhhQb73kEej2vispRZxxjM1vcgxkBYTr1imT5gw52ADhp vKFnyc1+adgOnmY+4Mhk4IzowPEhNJBEggYCA0W9j0p0UVU4WXBxUGcMo5ISTdgH LgDW5rGgov0hCpuHh+GizoNtJ9TM9mItXJHBDgEitZKFsk07HCiGq0yb+PRx+RHB 9EOxcpF68pIIJYmpHrprBYZppLUpq4DkjR+Wiej/YRUt6gZ2hcOZVtVAexDDjnwq BsGzEEr3yU5Kx38lGt85UzNIKOS08WN1YV8fdXS7KKMh/zkUIaaqGlE0DD8XpacV bi6ho4V1WUIcFq6/EgVkud/EaOLmGcrzNQhmlK5sxl3P1At3ABJ1lVBDQVw53f1e IKAOG0s8FutgX1gL2EeP1RQUs+ZRDduJStPprxlvY28jds6quHdDkmxMNDdILJDZ 66un+8NrnFBNGw4rG3rOyr1bKBdZS67XvZ37AU9efK13CkavjgCiBUY8lXMu4tkK qPlnFMx5K/ZIQtsEU7lk4KTn93/DLOIQihekaQtPBA9fc4RWWucUglhyihRc5Efi 6kfS6R+R6tekDf6y549UcW8zAg9JMETaIRDG+4bbQg3FiciCGGZCdEEXi+kHYQj6 3mtFdPiFzck9oVSvxOj0 =z8Pb -----END PGP SIGNATURE----- --ILuaRSyQpoVaJ1HG-- From nobody Tue May 9 19:21:50 2017 Return-Path: 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 ; 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 ; 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 ; 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: 10 May 2017 02:21:08 -0000 Message-ID: <20170510022108.27204.qmail@ary.lan> From: "John Levine" 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: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 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] >-=-=-=-=-=- From nobody Thu May 11 17:13:13 2017 Return-Path: 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 ; 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 ; 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 ; 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 ; 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 ; 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 In-Reply-To: <20170510022108.27204.qmail@ary.lan> Date: Thu, 11 May 2017 17:08:41 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20170510022108.27204.qmail@ary.lan> To: DISPATCH list X-Mailer: Apple Mail (2.3124) Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 wrote: >=20 > In article <20170510013932.GB21191@pepino> you write: >> -=3D-=3D-=3D-=3D-=3D- >>=20 >> 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. >=20 > You might as well grab hxxps too. >=20 > R's, > John >=20 >=20 >=20 >> 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. >>>=20 >>> I agree that a provisional registration would do that.=20 >>>=20 >>> Cheers, >>>=20 >>>=20 >>>> On 6 May 2017, at 2:17 am, John Levine wrote: >>>>=20 >>>> In article <20170505155326.GH14760@vulcano.intra.nic.cl> you write: >>>>> -=3D-=3D-=3D-=3D-=3D- >>>>>=20 >>>>> 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. >>>>=20 >>>> 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. >>>>=20 >>>> R's, >>>> John >>>>=20 >>>> _______________________________________________ >>>> dispatch mailing list >>>> dispatch@ietf.org >>>> https://www.ietf.org/mailman/listinfo/dispatch >>>=20 >>> -- >>> Mark Nottingham https://www.mnot.net/ >>>=20 >>> _______________________________________________ >>> dispatch mailing list >>> dispatch@ietf.org >>> https://www.ietf.org/mailman/listinfo/dispatch >>>=20 >>=20 >> -=3D-=3D-=3D-=3D-=3D- >> [Attachment type=3Dapplication/pgp-signature, name=3Dsignature.asc] >> -=3D-=3D-=3D-=3D-=3D- >=20 >=20 > _______________________________________________ > dispatch mailing list > dispatch@ietf.org > https://www.ietf.org/mailman/listinfo/dispatch From nobody Tue May 30 09:16:43 2017 Return-Path: X-Original-To: dispatch@ietf.org Delivered-To: dispatch@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 52F441294C4; Tue, 30 May 2017 09:16:42 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IETF Meeting Session Request Tool To: Cc: alexey.melnikov@isode.com, ben@nostrum.com, dispatch@ietf.org, dispatch-chairs@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.52.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <149616100224.14841.1492635956506407436.idtracker@ietfa.amsl.com> Date: Tue, 30 May 2017 09:16:42 -0700 Archived-At: Subject: [dispatch] dispatch - New Meeting Session Request for IETF 99 X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.22 List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 May 2017 16:16:42 -0000 A new meeting session request has just been submitted by Alexey Melnikov, a ART Area Director. --------------------------------------------------------- Working Group Name: Dispatch Area Name: Applications and Real-Time Area Session Requester: Alexey Melnikov Number of Sessions: 1 Length of Session(s): 1.5 Hours Number of Attendees: 100 Conflicts to Avoid: First Priority: core clue bfcpbis avtext avtcore ecrit insipid mmusic netvc payload rmcat rtcweb sipcore stir webpush xrblock jmap uta dmarc Second Priority: tram tsvwg tsvarea opsarea lmap People who must be present: Alexey Melnikov Mary Barnes Adam Roach Ben Campbell Cullen Jennings Murray Kucherawy Resources Requested: Special Requests: Please schedule in the 1st slot on Monday morning, list the meeting as coupled with ARTAREA, and avoid the same kind of conflicts with other area meetings and any Bofs and potential new ART WGs. --------------------------------------------------------- From nobody Tue May 30 12:00:48 2017 Return-Path: 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 3FB35129C5C; Tue, 30 May 2017 12:00:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.998 X-Spam-Level: X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 u9YKdaYXs1bz; Tue, 30 May 2017 12:00:43 -0700 (PDT) Received: from mail-qt0-x22f.google.com (mail-qt0-x22f.google.com [IPv6:2607:f8b0:400d:c0d::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D6B8129C32; Tue, 30 May 2017 12:00:38 -0700 (PDT) Received: by mail-qt0-x22f.google.com with SMTP id f55so77798167qta.3; Tue, 30 May 2017 12:00:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=PbLXpy3oBAwe7AdhJEIJ3y5gQFdejpBXUMBjOwW9LDg=; b=Ns0iaZZlc5CnXQmg9BmQODY1gcXGmC+mvVwS4iH9FuY1hecR6NOZkduCzvOHGOZNnN WR6H7ps6MpyMF/CEFai1uerkOsBD5mW0OQG0v2ZPhu8+cV45wqE/NJmjSeIHTE7Vjgad 3jDy8dTXuozb5zKSjfW0sSNLWezdNhOSLuL2hlcP/q69P78emPE/WxiSfjfb+loJ8tGz JyrOHUL0qzGvBtBFkZ2QtmT0QVJCnXCFqbx8ozRP0fkDCWPmgcJkSLpQ1RoPvOcIhwpA 39xW5RHgk/N4rbcUkPlT1bzopMzu7BmzblcEa3cR56ggpfqqEFSqJjsz3PkaZWg3r0fk WnBg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=PbLXpy3oBAwe7AdhJEIJ3y5gQFdejpBXUMBjOwW9LDg=; b=KFWJVP2HqCD6uAP35Rr5vY6sWlcgEmNu9biptQYfNpsgTYXNw6+B+e5+qT4JsdBkbx TIGOAWMBkqn5GbpUO30TC756wXnjuuaw2redzlzHQ6W/qQyZB6gbZVlOtF67BwWwvQf0 RtkA3cVhmoroH4XB3cujappXOrP4c0SuDXaGRUo08Xopxh22nPsyPS51eNx/8W46BXVz kJzmMWHmK1i83i2PIf2EYv+NI58qLy/6+iOzSc3f7BzRP0DfnYj0Pno8MjJgkOBPe2E0 0TOWm+YyMHp+N+j0pei1bAyEHKNPW6zv8v1DP5rZ8GvLmrMFg84/orwWEo16fKTRLGj7 yHRQ== X-Gm-Message-State: AODbwcAoRBjZ4mwNXUqhwG6N8gmsuJRt2wZgJHU1i2iGX69R/JiJkaqn NUk++GfpLP1YROIUXFM0ZRqQ+ivyx3do X-Received: by 10.237.53.205 with SMTP id d13mr26550398qte.149.1496170837056; Tue, 30 May 2017 12:00:37 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.43.37 with HTTP; Tue, 30 May 2017 12:00:36 -0700 (PDT) From: Mary Barnes Date: Tue, 30 May 2017 14:00:36 -0500 Message-ID: To: DISPATCH Cc: Cullen Jennings , "Murray S. Kucherawy" , ART ADs Content-Type: multipart/alternative; boundary="001a11c10d14441fdc0550c26b93" Archived-At: Subject: [dispatch] Reminder: DISPATCH WG deadlines for IETF-99 X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 May 2017 19:00:47 -0000 --001a11c10d14441fdc0550c26b93 Content-Type: text/plain; charset="UTF-8" As a reminder, the following deadlines for the DISPATCH WG for IETF-99 are coming up: - June 2, 2017: Cutoff date for BoF submissions - June 12, 2017: Cutoff date to notify the chairs/DISPATCH WG of plans to submit a proposal - June 18, 2017: Cutoff for charter proposals for topics - June 25, 2017: Announcement of topics that have been dispatched for IETF 99 - July 3, 2017: Draft submission deadline Further details: https://tools.ietf.org/wg/dispatch/trac/wiki As a reminder, *please* use the typical WG naming convention when submitting documents that you'd like to discuss during the DISPATCH WG session: draft-yoursurnamehere-dispatch-xyz It's very helpful to the chairs to be able to easily see relevant documents using the tracker. And, if the draft moves to another WG later, our handy dandy tools have an easy way to link the documents. Regards, Mary on behalf of DISPATCH WG chairs and ART ADs --001a11c10d14441fdc0550c26b93 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
As a reminder, the following deadlines for the DISPATCH WG= for IETF-99 are coming up:=C2=A0
  • June 2, 2017: Cutoff date for= BoF submissions
  • June 12, 2017: Cutoff date to notify the chairs/DI= SPATCH WG of plans to submit a proposal
  • June 18, 2017: Cutoff for c= harter proposals for topics=C2=A0
  • June 25, 2017: Announcement of to= pics that have been dispatched for IETF 99
  • July 3, 2017: Draft subm= ission deadline
Further details: https://tools.ietf.org/wg/dispatch/trac/wiki

As a reminder, *please* use the typical WG namin= g convention when submitting documents that you'd like to discuss durin= g the DISPATCH WG session: =C2=A0
=C2=A0 =C2=A0draft-yoursurnameh= ere-dispatch-xyz

It's very helpful to the chai= rs to be able to easily see relevant documents using the tracker.=C2=A0 And= , if the draft moves to another WG later, our handy dandy tools have an eas= y way to link the documents. =C2=A0
Regards,
Mary o= n behalf of DISPATCH WG chairs and ART ADs
--001a11c10d14441fdc0550c26b93--