From nobody Mon Dec 1 17:31:47 2014 Return-Path: X-Original-To: xmpp@ietfa.amsl.com Delivered-To: xmpp@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9444F1ACE01 for ; Mon, 1 Dec 2014 17:31:46 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.6 X-Spam-Level: X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 HPlszbcZ5FDK for ; Mon, 1 Dec 2014 17:31:42 -0800 (PST) Received: from mail-ie0-f179.google.com (mail-ie0-f179.google.com [209.85.223.179]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB7071ACE00 for ; Mon, 1 Dec 2014 17:31:41 -0800 (PST) Received: by mail-ie0-f179.google.com with SMTP id rp18so10312963iec.24 for ; Mon, 01 Dec 2014 17:31:41 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=tFzMSE2gxjFMNU36wjh5wwwhPrhBu843ssnM1X7Yj6c=; b=RlJ6giOemobh0XpEiFp+W+q1/WqdGjbCET5Lneqq7in219KSdWPJ5WUAx/LzVoKvgo apJRzi25zq/3pxHFbR9Yz81YUEKfToD25UzaAt3kuDt+AN/p34twIZlagKcKZ7NfaGAH W75nNZI31sMcxm2zEFDWdc2gSPHCgJO4rlvDTZMb4Bv58cqQJNpueeJjLUrFadJd20MJ CAenSduBcBRF3sZhvF9E/oY+aW5lrffJDW6fdAc1cSX1T9llgQoYBcy1MYvGGGYZ2iRQ j2ijKX5yKVg0Ld9k9yBb6kI6yRQKWQd2MSnhiFIcEp+c8xcpahDeR2WpksduPxCqjkcT mShg== X-Gm-Message-State: ALoCoQkwpPVZ3vU3IcIyV9vsRMZPwlAc6F0M+MGEH5xfEJp/+n+9zR4vOGKyHCx5rQLKMhDDeE8K X-Received: by 10.42.61.130 with SMTP id u2mr592692ich.61.1417483901353; Mon, 01 Dec 2014 17:31:41 -0800 (PST) Received: from aither.local (c-73-34-202-214.hsd1.co.comcast.net. [73.34.202.214]) by mx.google.com with ESMTPSA id ga11sm5830958igd.4.2014.12.01.17.31.40 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 01 Dec 2014 17:31:40 -0800 (PST) Message-ID: <547D167B.2020700@andyet.net> Date: Mon, 01 Dec 2014 18:31:39 -0700 From: Peter Saint-Andre - &yet User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Dave Cridland References: <20141112033353.13684.68712.idtracker@ietfa.amsl.com> <5462D556.8040400@andyet.net> <54653A03.5010206@andyet.net> In-Reply-To: <54653A03.5010206@andyet.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Archived-At: http://mailarchive.ietf.org/arch/msg/xmpp/EhobeksRXinN3c9-SJ7bdWo4o4A Cc: XMPP Working Group Subject: Re: [xmpp] Fwd: New Version Notification for draft-ietf-uta-xmpp-03.txt X-BeenThere: xmpp@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: XMPP Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Dec 2014 01:31:46 -0000 BTW version -04 was intended to address this feedback: https://datatracker.ietf.org/doc/draft-ietf-uta-xmpp/ On 11/13/14, 4:08 PM, Peter Saint-Andre - &yet wrote: > Hi Dave, thanks for the feedback. > > On 11/12/14, 4:47 AM, Dave Cridland wrote: >> Lightning review: >> >> 1) §3.3 - I don't understand why session tickets would be bad compared >> to session ids? > > I freely admit that I don't understand the effective difference between > session IDs and session tickets for XMPP (or for TLS session resumption > in general). To my meager brain, the differences are not explained well > in the RFCs. Enlightenment would be appreciated. :-) > >> 2) Should there be a discussion about recommended SAN types? RFC 6120 >> currently says the only MTI is xmppAddr; RFC 6125 gives no MTI as I >> understand it. > > This is covered in §13.7.1.2.1 of RFC 6120. Perhaps a pointer to that > section would be helpful? > >> 3) If so, should we discuss wildcard resolution? Or not? RFC 5280 says >> wildcard resolution is within the scope of the application rather than >> TLS/PKIX itself. > > That's also covered in the aforementioned section of RFC 6120. However, > do we feel that it's time to revisit the text there? (BTW, Jeff Hodges > and I tried to kill off wildcard certs entirely in RFC 6125 but weren't > successful.) > >> 4) Finally, there's two different protocols in XMPP - C2S and S2S. It >> might be good to explicitly note the different requirements on these >> (the draft says C2S clients MUST authenticate servers, for example). > > And it doesn't say that servers need to authenticate peer servers over > s2s, which implies that unauthenticated s2s connections are allowed. > This is consistent with current practice. Are you suggesting that we > change the recommendation (e.g., SHOULD or MUST authenticate for s2s) or > at least make it explicit that unauthenticated s2s connections are allowed? > > Peter > From nobody Tue Dec 2 18:45:01 2014 Return-Path: X-Original-To: xmpp@ietfa.amsl.com Delivered-To: xmpp@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AC561A8996 for ; Tue, 2 Dec 2014 18:44:58 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.601 X-Spam-Level: X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 J4QbjLb-8FlQ for ; Tue, 2 Dec 2014 18:44:57 -0800 (PST) Received: from mail-ie0-f169.google.com (mail-ie0-f169.google.com [209.85.223.169]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 72C861A8994 for ; Tue, 2 Dec 2014 18:44:57 -0800 (PST) Received: by mail-ie0-f169.google.com with SMTP id y20so13036749ier.0 for ; Tue, 02 Dec 2014 18:44:56 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=EZzXksAcecttHyOCnUro2Aq55kspNfqRlWl4BA2o7ac=; b=QcNXHvKyfUsR6zUTU/9vjcB2gHx0FJ/TfxlP3GxBdWDRx89oAPDsaxvifhBjmv6Cmu K5gNWSPp2OXwBOcXgmU4j04OHwIkXe0VuSGD10qtsO2vBBF6nvy6r6U9BjHT9nOAoji7 WyCQN2oV07BoPXY/xFP3h4bXdhwPJ8YBfzSK3ShCN4lc9eMBeDzG0fxDUKtSo2JAa3hL lc+iwObXYqxMpy3TTksfxF5+W4XoYaoMnZB/YqcDMcgADU3ZBM8HwXh3sWD6Bc7FzQH+ m6VdvZK/dmDN4hFscJcaKVHE2vmISPuAKvtfSExwvx2QBVYXHV4S8/9MMNFlNPfp0uxH 8K4Q== X-Gm-Message-State: ALoCoQm45pkCdUQJZBOhjRKUDiCKdvdp3jyxJiaM0JqhOF9+WQyLUFORUnMqNAjT/Yj6Sj5jcqmY X-Received: by 10.107.17.79 with SMTP id z76mr2491010ioi.27.1417574696894; Tue, 02 Dec 2014 18:44:56 -0800 (PST) Received: from aither.local (c-73-34-202-214.hsd1.co.comcast.net. [73.34.202.214]) by mx.google.com with ESMTPSA id o72sm10720641ioo.14.2014.12.02.18.44.56 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 02 Dec 2014 18:44:56 -0800 (PST) Message-ID: <547E7927.7030203@andyet.net> Date: Tue, 02 Dec 2014 19:44:55 -0700 From: Peter Saint-Andre - &yet User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: "precis@ietf.org" , XMPP Working Group References: <547BDAA7.2030601@andyet.net> In-Reply-To: <547BDAA7.2030601@andyet.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Archived-At: http://mailarchive.ietf.org/arch/msg/xmpp/5kH0etio1RXGSz4N0yxut9LQiRQ Subject: Re: [xmpp] consolidating FreeformClass profiles? X-BeenThere: xmpp@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: XMPP Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2014 02:44:58 -0000 Seeing no objections, I'm going to make this change. On 11/30/14, 8:04 PM, Peter Saint-Andre - &yet wrote: > I think we've done a pretty good job of consolidating some of the > IdentiferClass profiles, thanks to prodding from John Klensin. > > Now I'm wondering if we can prune the list of FreeformClass profiles. > Currently we have: > > Password (draft-ietf-precis-saslprepbis) > Resourcepart (draft-ietf-xmpp-6122bis) > Nickname (draft-ietf-precis-nickname) > > The Password and Resourcepart profiles are similar: the main differences > are use of the Bidi Rule and removal of leading and trailing whitespace > in Resourcepart (the latter is more of a UI consideration and probably > doesn't belong in the Resourcepart profile in the first place). I think > we *might* be able to point to the Password profile from 6122bis and > remove the Resourcepart profile (I'll need to post to the XMPP WG list > about that). The "Password" name feels a bit strange in this context (I > might prefer a more generic name like "OpaqueString"), but that's a nit. > > The Nickname profile is different enough in purpose and function that I > think we'll need to keep it. > > Peter > From nobody Tue Dec 2 19:42:52 2014 Return-Path: X-Original-To: xmpp@ietfa.amsl.com Delivered-To: xmpp@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3744D1A0067; Tue, 2 Dec 2014 19:42:50 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 LTFhbGMLalYW; Tue, 2 Dec 2014 19:42:49 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id F2A151A0041; Tue, 2 Dec 2014 19:42:48 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 5.7.4 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20141203034248.23689.45669.idtracker@ietfa.amsl.com> Date: Tue, 02 Dec 2014 19:42:48 -0800 Archived-At: http://mailarchive.ietf.org/arch/msg/xmpp/1Q1dSsY8vR8fB9EVuiKvwpFc8wg Cc: xmpp@ietf.org Subject: [xmpp] I-D Action: draft-ietf-xmpp-6122bis-18.txt X-BeenThere: xmpp@ietf.org X-Mailman-Version: 2.1.15 List-Id: XMPP Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2014 03:42:50 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Extensible Messaging and Presence Protocol Working Group of the IETF. Title : Extensible Messaging and Presence Protocol (XMPP): Address Format Author : Peter Saint-Andre Filename : draft-ietf-xmpp-6122bis-18.txt Pages : 25 Date : 2014-12-02 Abstract: This document defines the address format for the Extensible Messaging and Presence Protocol (XMPP), including support for code points outside the ASCII range. This document obsoletes RFC 6122. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-xmpp-6122bis/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-xmpp-6122bis-18 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-xmpp-6122bis-18 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Wed Dec 3 05:07:39 2014 Return-Path: X-Original-To: xmpp@ietfa.amsl.com Delivered-To: xmpp@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 855311A1AAA for ; Wed, 3 Dec 2014 05:07:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.378 X-Spam-Level: X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 xdx9i-_GI2Ox for ; Wed, 3 Dec 2014 05:07:33 -0800 (PST) Received: from mail-ob0-x22f.google.com (mail-ob0-x22f.google.com [IPv6:2607:f8b0:4003:c01::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3EFD51A1AA6 for ; Wed, 3 Dec 2014 05:07:23 -0800 (PST) Received: by mail-ob0-f175.google.com with SMTP id wp4so982622obc.6 for ; Wed, 03 Dec 2014 05:07:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=+GTYK8TUjSdPnI4sIxvgoEamO/afBo50goc1tZhpG8o=; b=OZI9UIH0HWtFK+2xBlASNsxUNWT1f/bNyuJJ5M5SJXZkfUCR3PBMBle2pKwnHX3KHZ jsodNtdAyVtrFyuSwrrmx29UZ1t+a9BgjS1wvCbmjeGktnhWHuriejSEAh3fpp+xg/F1 63Hw5hFQXYX77GyNIpHpj/VmPCwT5BHhHO/kA= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=+GTYK8TUjSdPnI4sIxvgoEamO/afBo50goc1tZhpG8o=; b=l3VmHPtAnxpvvCqdJthpVuu+QkHp/e9JD4Gt75IsLDaFbkLdIsOy1EYoGoEEaTwB3H VB8nvIfEtY10Wg2+/YDZYI/Ozngh1JI1Zx7kcurrcMG0qyRQdR+RBBvqQfQankXZfiMk D1HlmBJ4uQere5cM2wFwGzdxkXZPdbWFJe5ljHo1MYEwMEEuiiJQ1HSMsaMhZ3Bz+TDr rGxw/Kjo50pPTI0P2/SW6OKpDZntPfzy50N5AVQ5ryPdmzRl89jXkwC6ooHkv1XlRUK1 Hm4mHfULtoYPaJxF1Vvxo2wjgztrBgZoyX8MsRAh6zLH42yh7EIT7GK8fDH4R7+GTBAt F8Jg== X-Gm-Message-State: ALoCoQlp/kbxFZ0bMye05UcELEhavB93O8oj9Yr51cvM3xeulMAm51z4/DwQM5BejN1nSRiLovWj MIME-Version: 1.0 X-Received: by 10.202.220.87 with SMTP id t84mr2890150oig.86.1417612042542; Wed, 03 Dec 2014 05:07:22 -0800 (PST) Received: by 10.60.227.199 with HTTP; Wed, 3 Dec 2014 05:07:22 -0800 (PST) In-Reply-To: <547E7927.7030203@andyet.net> References: <547BDAA7.2030601@andyet.net> <547E7927.7030203@andyet.net> Date: Wed, 3 Dec 2014 13:07:22 +0000 Message-ID: From: Dave Cridland To: "Peter Saint-Andre - &yet" Content-Type: multipart/alternative; boundary=001a113d30b239bcb105094f8620 Archived-At: http://mailarchive.ietf.org/arch/msg/xmpp/fph44hjFcNaYDIzaoowB2Lru7ow Cc: "precis@ietf.org" , XMPP Working Group Subject: Re: [xmpp] consolidating FreeformClass profiles? X-BeenThere: xmpp@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: XMPP Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2014 13:07:34 -0000 --001a113d30b239bcb105094f8620 Content-Type: text/plain; charset=UTF-8 On 3 December 2014 at 02:44, Peter Saint-Andre - &yet wrote: > Seeing no objections, I'm going to make this change. I'm not wholly sure I fully understand the change you're proposing, which is why I've not commented. I suspect I need to spend some time getting to grips with Precis, and what the distinction is between Precis and Stringprep. Help here - such as a discussion at the XMPP Summit at the end of January - would be very welcome. The only thing I feel qualified to comment on is that resources in XMPP shouldn't have spaces stripped; I think that'd be a surprising change in a handful of cases. --001a113d30b239bcb105094f8620 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

On 3= December 2014 at 02:44, Peter Saint-Andre - &yet <= ;peter@andyet.net= > wrote:

Seeing no objections, = I'm going to make this change.

I'm = not wholly sure I fully understand the change you're proposing, which i= s why I've not commented.

I suspect I need to = spend some time getting to grips with Precis, and what the distinction is b= etween Precis and Stringprep. Help here - such as a discussion at the XMPP = Summit at the end of January - would be very welcome.

<= div>The only thing I feel qualified to comment on is that resources in XMPP= shouldn't have spaces stripped; I think that'd be a surprising cha= nge in a handful of cases.

--001a113d30b239bcb105094f8620-- From nobody Wed Dec 3 11:38:49 2014 Return-Path: X-Original-To: xmpp@ietfa.amsl.com Delivered-To: xmpp@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7EE71A8AE8 for ; Wed, 3 Dec 2014 11:38:46 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.601 X-Spam-Level: X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable 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 FkN3-jPjgtTs for ; Wed, 3 Dec 2014 11:38:45 -0800 (PST) Received: from mail-ie0-f169.google.com (mail-ie0-f169.google.com [209.85.223.169]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 488371A90EC for ; Wed, 3 Dec 2014 11:38:35 -0800 (PST) Received: by mail-ie0-f169.google.com with SMTP id y20so14514469ier.0 for ; Wed, 03 Dec 2014 11:38:34 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=WiOla1ZSoF/X/HmGOO1SdvrUW7razGNUF13FPtwIPXg=; b=NVz0PVxTM1sIot1QeuqT4f3Cgp7DSHcuTbnX343glH+T0SM3iooL/gAWM7/NF6FN0c WIrEfjJWpPnfT3Jwbm4+mkPPZmTObd8tRor/NzP5D/sbHYyDDQu4KYg/ZNzQ3cnXAOTE E+i8fiKS6Tprncfpr8cppixGebVPEN8p+5uPLwR0TGmEAnPpw6YEasMhf99s6rkgnfnz O8P/HeqOvq0RYs697GRcY61dYriARC9HyQtzoDJUd+pz80RX7LgTUGLBf9L9Podn8dK0 alkeiKKupjhSHFFLY7925rLfClXPpu/okNuQFgKSDEjiNrqeQc084dRhT1FSsXD9Prqu UoCg== X-Gm-Message-State: ALoCoQk4J5V6oJNqwZOLkyR+xiEsK/w1TeQwcOEFJvdEuspGXXmq5rziWKIBD6V7riogwnbLz8mZ X-Received: by 10.107.128.87 with SMTP id b84mr6340779iod.42.1417635514148; Wed, 03 Dec 2014 11:38:34 -0800 (PST) Received: from aither.local (c-73-34-202-214.hsd1.co.comcast.net. [73.34.202.214]) by mx.google.com with ESMTPSA id fk8sm19096716igb.9.2014.12.03.11.38.33 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 03 Dec 2014 11:38:33 -0800 (PST) Message-ID: <547F66B8.10001@andyet.net> Date: Wed, 03 Dec 2014 12:38:32 -0700 From: Peter Saint-Andre - &yet User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Dave Cridland References: <547BDAA7.2030601@andyet.net> <547E7927.7030203@andyet.net> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Archived-At: http://mailarchive.ietf.org/arch/msg/xmpp/EsxRWjWhfT5yHJlyV3loZlCsPbk Cc: "precis@ietf.org" , XMPP Working Group Subject: Re: [xmpp] consolidating FreeformClass profiles? X-BeenThere: xmpp@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: XMPP Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2014 19:38:46 -0000 On 12/3/14, 6:07 AM, Dave Cridland wrote: > On 3 December 2014 at 02:44, Peter Saint-Andre - &yet > wrote: > > Seeing no objections, I'm going to make this change. > > > I'm not wholly sure I fully understand the change you're proposing, > which is why I've not commented. The change is to not define a separate profile but instead point to the OpaqueString profile from draft-ietf-precis-saslprepbis. We are working hard to reduce the number of profiles, since multiplication of profiles beyond necessity will increase the possibility of user confusion. http://tools.ietf.org/html/draft-ietf-precis-framework-20#section-5.1 > I suspect I need to spend some time getting to grips with Precis, and > what the distinction is between Precis and Stringprep. Help here - such > as a discussion at the XMPP Summit at the end of January - would be very > welcome. Unfortunately, now is the time to understand it, because we are pushing hard to finish this work in both PRECIS WG and XMPP WG. This overview might be useful: https://stpeter.im/files/i18n-tutorial.pdf I might even have time to make a few updates to that soon so that it addresses your questions. The following readings might prove useful: http://tools.ietf.org/html/draft-ietf-precis-framework-20#section-1 http://tools.ietf.org/html/rfc4690 http://tools.ietf.org/html/rfc6885 > The only thing I feel qualified to comment on is that resources in XMPP > shouldn't have spaces stripped; I think that'd be a surprising change in > a handful of cases. I'm proposing that we use this profile for resourceparts: http://tools.ietf.org/html/draft-ietf-precis-saslprepbis-12#section-4.2 There is no space-stripping there, but there is conversion of non-ASCII spaces to ASCII space. Peter -- Peter Saint-Andre https://andyet.com/