Re: [xmpp] WGLC of draft-ietf-xmpp-6122bis-11
Matt Miller <mamille2@cisco.com> Tue, 25 March 2014 20:26 UTC
Return-Path: <mamille2@cisco.com>
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 9E0811A0239 for <xmpp@ietfa.amsl.com>; Tue, 25 Mar 2014 13:26:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.511
X-Spam-Level:
X-Spam-Status: No, score=-9.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 5Sje8NAJuGY8 for <xmpp@ietfa.amsl.com>; Tue, 25 Mar 2014 13:26:01 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) by ietfa.amsl.com (Postfix) with ESMTP id 7DDDD1A0245 for <xmpp@ietf.org>; Tue, 25 Mar 2014 13:26:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3408; q=dns/txt; s=iport; t=1395779159; x=1396988759; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=eNjlsc6HI1C2FYBxSyWBAIBMrTZfOPg5jJuNCd2TMhg=; b=lgbE7/Nzu6laYlmDcuk9Ihf+uxNU0dlm67lgS/HjPtDkmehONg90MB86 xCs7sOOpKHGXGh14JOdX+OhMoEGE/2cyxL1WoXo+rJE8Poxkocx5KCSV4 4+Ef2itWeFcq+tFfjz9G9Is1qrciiVwtxcUH50kPyi0DzWS+42WzdXec0 w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUJABnmMVOtJV2a/2dsb2JhbABZgwY7V6lXBJkRgR0WdIIlAQEBAwF4EQsYCQ8HDwkDAgECAUUGAQwGAgEBh20Iz3oXjjs6GIQgAQOJGjiOe5Iyg02CDA
X-IronPort-AV: E=Sophos;i="4.97,730,1389744000"; d="scan'208";a="30311042"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by alln-iport-2.cisco.com with ESMTP; 25 Mar 2014 20:25:46 +0000
Received: from xhc-rcd-x05.cisco.com (xhc-rcd-x05.cisco.com [173.37.183.79]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s2PKPkpu021506 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 25 Mar 2014 20:25:46 GMT
Received: from MAMILLE2-M-T03K.local (64.101.72.44) by xhc-rcd-x05.cisco.com (173.37.183.79) with Microsoft SMTP Server (TLS) id 14.3.123.3; Tue, 25 Mar 2014 15:25:46 -0500
Message-ID: <5331E64A.5080909@cisco.com>
Date: Tue, 25 Mar 2014 14:25:46 -0600
From: Matt Miller <mamille2@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>, XMPP Working Group <xmpp@ietf.org>
References: <68FA58CE-C00A-4281-8B7E-5C96A0B3B835@nostrum.com> <35972936-21C6-4F35-92EF-4435C3F85C63@nostrum.com> <5331DFEC.4030900@cisco.com> <5331E42D.6020501@stpeter.im>
In-Reply-To: <5331E42D.6020501@stpeter.im>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [64.101.72.44]
Archived-At: http://mailarchive.ietf.org/arch/msg/xmpp/gv4Js1JR3VYzGN0zuC2ueKUBM5E
Subject: Re: [xmpp] WGLC of draft-ietf-xmpp-6122bis-11
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp/>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Mar 2014 20:26:04 -0000
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 3/25/14, 2:16 PM, Peter Saint-Andre wrote: > On 3/25/14, 1:58 PM, Matt Miller wrote: >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 >> >> I've finished reviewing draft-ietf-xmpp-6122bis-11. I mostly >> think this document is ready to be published. I think it deals >> with the internationalization issues at hand as well as can be >> expected. >> >> However, in 3.2. Domainpart, I wonder about the following: >> >> 4. So-called "additional mappings" MAY be applied to the >> domainpart, such as those defined in [I-D.ietf-precis-mappings] >> or [RFC5895]. >> >> As far as I can tell, just about all of the suggested mappings >> from RFC5895 are already required here. But for any that are >> not, I worry about the potential for interoperability problems if >> say two servers communicating with each other apply different >> mappings. It might be best to strike this bullet from the list. > > Yes, I think you are right that it would be best to remove this > step. While updating draft-ietf-precis-saslprepbis last night, I > removed any mention of additional mappings from the password > algorithm, for similar reasons. > >> Less concerning to me is in 3.3. Localpart: >> >> 2. So-called "additional mappings" MAY be applied, such as >> those defined in [I-D.ietf-precis-mappings]. >> >> I think there is less concern about interoperability problems >> here, but I wonder if it is of any real utility. > > In saslprepbis, we've changed the username text to read: > > 3. So-called additional mappings MAY be applied, such as mapping > of delimiters (e.g., characters such as '@', ':', '/', '+', and > '-') and special handling of certain characters or classes of > characters (e.g., mapping of non-ASCII spaces to ASCII space or > mapping of control characters to nothing); the PRECIS mappings > document [I-D.ietf-precis-mappings] describes such mappings in more > detail. > > However, that kind of mapping doesn't apply to XMPP localparts > because we profile the PRECIS IdentifierClass, which prohibits > punctuation and space characters outside the ASCII7 range, control > characters, etc. So IMHO it's unnecessary for localparts. > Agreed. >> The similar language in 3.4. Resourcepart is not concerning to me >> at all; there are some cases where additional mappings are >> desirable (e.g., MUC nicknames), and I think the language makes >> it clear that anything beyond "it's opaque" is to be approached >> with care. > > Agreed, although I'd change the bullet to mostly or entirely match > what I added to draft-ietf-precis-saslprepbis. > That works for me. - -- - - m&m Matt Miller < mamille2@cisco.com > Cisco Systems, Inc. -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: GPGTools - https://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCgAGBQJTMeZKAAoJEDWi+S0W7cO1cdUIALStFgXG1uuizVckpgGMpalQ WKc9WU5OcIdvUBk9NuPjHP8J18wx9nvKCqpEp+yN4CznvurF/g8gJZxZsRdBD0mV HtO8OxhqqH3v0q+CQmWoGxx9VSmFzgR+4BKXbjsJrWec2BU8oSpouagk01moFJIe F46ZeVsU+TZYhxxGrnvnljsUEv7YFHevkeFO6cd22Jo35ikU/NjkBLMEEpR2+9mk Xw3N0eNmkucZ8xILVVtRbLIq3L6AcZNo0Gr3MeKI/SSxcJYm4bBYxnnQa3jOZJXA WkvnGnUEECIQ58hu60DHmH60HS2OHH7WwfPvutwvf8cBJmnVx4AWP69MtnRH+is= =3whQ -----END PGP SIGNATURE-----
- Re: [xmpp] WGLC of draft-ietf-xmpp-6122bis-11 Matt Miller
- [xmpp] WGLC of draft-ietf-xmpp-6122bis-11 Ben Campbell
- Re: [xmpp] WGLC of draft-ietf-xmpp-6122bis-11 Ben Campbell
- Re: [xmpp] WGLC of draft-ietf-xmpp-6122bis-11 Peter Saint-Andre
- Re: [xmpp] WGLC of draft-ietf-xmpp-6122bis-11 Matt Miller
- Re: [xmpp] WGLC of draft-ietf-xmpp-6122bis-11 Peter Saint-Andre
- Re: [xmpp] WGLC of draft-ietf-xmpp-6122bis-11 Ben Campbell