From nobody Fri Feb 5 08:40:57 2016 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E12451B3B30 for ; Fri, 5 Feb 2016 08:40:56 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.52 X-Spam-Level: X-Spam-Status: No, score=0.52 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, SPF_PASS=-0.001] autolearn=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 JulBpK159Wuf for ; Fri, 5 Feb 2016 08:40:55 -0800 (PST) Received: from mail-qg0-x22f.google.com (mail-qg0-x22f.google.com [IPv6:2607:f8b0:400d:c04::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 B24BB1B3B2C for ; Fri, 5 Feb 2016 08:40:55 -0800 (PST) Received: by mail-qg0-x22f.google.com with SMTP id o11so71516054qge.2 for ; Fri, 05 Feb 2016 08:40:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=samwhited.com; s=swgoo; h=mime-version:from:date:message-id:subject:to:cc:content-type; bh=dVHY7mRdZFL8e97m16uoDYuzHJOVWlxgDtunr0VNe4c=; b=RyAn0xJJ9wo5o+zQv6t9zzOuIEntYIwtSnbkOj7HEoLE5bKigzWE8XezhLwJWMD4u6 vGlfupzgQoZPr1Jh6iwcx0NCC4nZy2RDM1ZaZvVKmfwlsZE/becehVE7adBHFw4COJA8 TNprWin7Acn61Fq3I2Fx5BO51jhI6xPXEZrNc= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc :content-type; bh=dVHY7mRdZFL8e97m16uoDYuzHJOVWlxgDtunr0VNe4c=; b=Pb2Rl63X/K9IJxaPNjNak7uglE8E17rhmHdQ68ycTwfr5dJp2APSxmu3eQ/GK0q+Bd vUWFdoVPKGQkutMctEqylT6amgjXvMe3lSGEK2It8UtgIGtLruPzCrSDmYot7z4MsmoC LtusuJfwCPxST3QOaUCfjj/IEsqqHBJuMjvdI1nszgi/gjSvN/wPHuCyqEJ+Gac7WRQu +nysIzCpDzEsFvdWbW+Ort/hPNPCFHY/JychYOTT0sbjpuq+/ieiIxnx3/dCevZhBCDL kq1VDgvViV73YBMkS4bxW7iQHN+3uIDPJkR2LDYjq7S7AYwqYW9K5oUMe/1/DG1GrSkS ks1w== X-Gm-Message-State: AG10YORk8oh3jE1NBB6e8p545TW7EMI/Heo909ltihP8TYYBcsV1bNwnXs9ikgU7Jbprdk5aC61GazEXROLEFw== X-Received: by 10.140.92.111 with SMTP id a102mr17596627qge.92.1454690454827; Fri, 05 Feb 2016 08:40:54 -0800 (PST) MIME-Version: 1.0 Received: by 10.55.79.82 with HTTP; Fri, 5 Feb 2016 08:40:15 -0800 (PST) X-Originating-IP: [72.48.156.244] From: Sam Whited Date: Fri, 5 Feb 2016 10:40:15 -0600 Message-ID: To: precis@ietf.org Content-Type: text/plain; charset=UTF-8 Archived-At: Cc: Peter Saint-Andre Subject: [precis] PRECIS Go implementation X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Preparation and Comparison of Internationalized Strings List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Feb 2016 16:40:57 -0000 Hi all, I've mentioned that I was working on a Golang implementation of PRECIS on this list before, and now that it's been merged into the experimental part of the Go standard library I wanted to provide an update and announce it's availability: https://godoc.org/golang.org/x/text/secure/precis There are still a few hiccups and TODO's, mostly due to the fact that there's not currently a Go implementation of the BIDI rule, but those should be smoothed out over time and I'm convinced that it's mostly compatible with other PRECIS implementations like Christian Schedt's recent Java version (from which I stole many tests, thanks Christian). The source can be found here, for anyone who is interested: https://github.com/golang/text/tree/master/secure/precis An interesting thing to note about this implementation is that we decided that it is fast enough to NOT implement the prepare step. Instead, clients and servers alike are expected perform enforcement. To give a quick example, here is a benchmark of enforcing the string "Malvolio" (including setup and teardown, not reusing constructed profiles): PASS BenchmarkUsernameCaseMapped-8 300000 5727 ns/op 14064 B/op 20 allocs/op BenchmarkUsernameCasePreserved-8 300000 5428 ns/op 14064 B/op 20 allocs/op BenchmarkOpaqueString-8 300000 4736 ns/op 9888 B/op 19 allocs/op BenchmarkNickname-8 300000 4874 ns/op 9888 B/op 19 allocs/op ok _/home/sam/src/golang-x-text/secure/precis 6.452s While this doesn't look great at first glance, it's worth noting that this is a naive implementation with minimal optimizations beyond pre-generating a trie of derived properties. It will be quite easy to go back and get those 20 allocations per operation down to a more reasonable number (even after adding BIDI support), which should increase the speed per operation significantly. Best, Sam -- Sam Whited pub 4096R/54083AE104EA7AD3 https://blog.samwhited.com From nobody Thu Feb 18 04:50:59 2016 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51C7C1A01A5 for ; Thu, 18 Feb 2016 04:50:58 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.008 X-Spam-Level: X-Spam-Status: No, score=-0.008 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RP_MATCHES_RCVD=-0.006, SPF_PASS=-0.001] autolearn=ham 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 3hJmA6PsVacN for ; Thu, 18 Feb 2016 04:50:57 -0800 (PST) Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 26FB81A0151 for ; Thu, 18 Feb 2016 04:50:57 -0800 (PST) Received: from [192.168.1.111] (modemcable093.65-160-184.mc.videotron.ca [184.160.65.93]) by jazz.viagenie.ca (Postfix) with ESMTPSA id A3CB8476D3 for ; Thu, 18 Feb 2016 07:50:56 -0500 (EST) From: "Marc Blanchet" To: precis@ietf.org Date: Thu, 18 Feb 2016 07:50:56 -0500 Message-ID: <60B10F55-51AE-4EEB-A825-C5FBFD8245E9@viagenie.ca> MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-Mailer: MailMate (1.9.3r5187) Archived-At: Subject: [precis] no meeting in BA X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Preparation and Comparison of Internationalized Strings List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Feb 2016 12:50:58 -0000 Hello, co-chairs do not think we need a meeting in BA, so we did not request a slot. Regards, Marc. From nobody Mon Feb 29 15:35:17 2016 Return-Path: X-Original-To: precis@ietfa.amsl.com Delivered-To: precis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82F461A004E; Mon, 29 Feb 2016 15:35:14 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.908 X-Spam-Level: X-Spam-Status: No, score=-101.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.006, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham 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 Nb2gu9ESpFxX; Mon, 29 Feb 2016 15:35:13 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6648E1A0367; Mon, 29 Feb 2016 15:35:09 -0800 (PST) Received: by rfc-editor.org (Postfix, from userid 30) id 4CD74180206; Mon, 29 Feb 2016 15:34:18 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20160229233418.4CD74180206@rfc-editor.org> Date: Mon, 29 Feb 2016 15:34:18 -0800 (PST) Archived-At: Cc: precis@ietf.org, rfc-editor@rfc-editor.org Subject: [precis] RFC 7790 on Mapping Characters for Classes of the Preparation, Enforcement, and Comparison of Internationalized Strings (PRECIS) X-BeenThere: precis@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Preparation and Comparison of Internationalized Strings List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Feb 2016 23:35:14 -0000 A new Request for Comments is now available in online RFC libraries. RFC 7790 Title: Mapping Characters for Classes of the Preparation, Enforcement, and Comparison of Internationalized Strings (PRECIS) Author: Y. Yoneya, T. Nemoto Status: Informational Stream: IETF Date: February 2016 Mailbox: yoshiro.yoneya@jprs.co.jp, t.nemo10@kmd.keio.ac.jp Pages: 10 Characters: 20806 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-precis-mappings-12.txt URL: https://www.rfc-editor.org/info/rfc7790 DOI: http://dx.doi.org/10.17487/RFC7790 The framework for the preparation, enforcement, and comparison of internationalized strings (PRECIS) defines several classes of strings for use in application protocols. Because many protocols perform case-sensitive or case-insensitive string comparison, it is necessary to define methods for case mapping. In addition, both the Internationalized Domain Names in Applications (IDNA) and the PRECIS problem statement describe mappings for internationalized strings that are not limited to case, but include width mapping and mapping of delimiters and other special characters that can be taken into consideration. This document provides guidelines for designers of PRECIS profiles and describes several mappings that can be applied between receiving user input and passing permitted code points to internationalized protocols. In particular, this document describes both locale-dependent and context-depending case mappings as well as additional mappings for delimiters and special characters. This document is a product of the Preparation and Comparison of Internationalized Strings Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC