[precis] Fwd: [xmpp] 6122bis examples

Peter Saint-Andre <stpeter@stpeter.im> Tue, 05 November 2013 00:48 UTC

Return-Path: <stpeter@stpeter.im>
X-Original-To: precis@ietfa.amsl.com
Delivered-To: precis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0C4A11E825D for <precis@ietfa.amsl.com>; Mon, 4 Nov 2013 16:48:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.406
X-Spam-Level:
X-Spam-Status: No, score=-103.406 tagged_above=-999 required=5 tests=[AWL=1.193, BAYES_00=-2.599, GB_I_LETTER=-2, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zA-yJFik8fxS for <precis@ietfa.amsl.com>; Mon, 4 Nov 2013 16:48:09 -0800 (PST)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 3144711E8302 for <precis@ietf.org>; Mon, 4 Nov 2013 16:48:09 -0800 (PST)
Received: from ergon.local (unknown [128.107.239.234]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 8DA3E4032B; Mon, 4 Nov 2013 17:48:08 -0700 (MST)
Message-ID: <52784047.5090101@stpeter.im>
Date: Mon, 04 Nov 2013 16:48:07 -0800
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: "precis@ietf.org" <precis@ietf.org>
References: <52783A4C.5030102@stpeter.im>
In-Reply-To: <52783A4C.5030102@stpeter.im>
X-Enigmail-Version: 1.6
X-Forwarded-Message-Id: <52783A4C.5030102@stpeter.im>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: [precis] Fwd: [xmpp] 6122bis examples
X-BeenThere: precis@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Preparation and Comparison of Internationalized Strings <precis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/precis>, <mailto:precis-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/precis>
List-Post: <mailto:precis@ietf.org>
List-Help: <mailto:precis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/precis>, <mailto:precis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Nov 2013 00:48:22 -0000

Would examples be useful in the PRECIS documents, as well?

Peter


-------- Original Message --------
Subject: [xmpp] 6122bis examples
Date: Mon, 04 Nov 2013 16:22:36 -0800
From: Peter Saint-Andre <stpeter@stpeter.im>
To: XMPP <xmpp@ietf.org>

In the past, I have promised to add some examples to 6122bis. However, I
have also neglected to do so. Here is some proposed text. If folks would
like more examples, I'd be happy to add them.

###

3.5.  Examples

   The following examples illustrate a small number of JIDs that are
   consistent with the format defined above.

   Table 1: A sample of legal JIDs

   +---------------------------------+---------------------------------+
   | # | JID                         | Notes                           |
   +---------------------------------+---------------------------------+
   | 1 | juliet@example.com          | A "bare JID"                    |
   +---------------------------------+---------------------------------+
   | 2 | juliet@example.com/foo      | A "full JID"                    |
   +---------------------------------+---------------------------------+
   | 3 | juliet@example.com/foo bar  | Single space in resourcepart    |
   +---------------------------------+---------------------------------+
   | 4 | fussball@example.com        | Another bare JID                |
   +---------------------------------+---------------------------------+
   | 5 | fu&#xDF;ball@example.com    | The third character is LATIN    |
   |   |                             | SMALL LETTER SHARP S (U+00DF)   |
   +---------------------------------+---------------------------------+
   | 6 | &#x3C0;@example.com         | A localpart of GREEK SMALL      |
   |   |                             | LETTER PI (U+03C0)              |
   +---------------------------------+---------------------------------+
   | 7 | &#x3C0;@example.com/&#x3A3mp;#x3A3; | A resourcepart of GREEK CAPITAL |
   |   |                             | LETTER SIGMA (U+03A3)           |
   +---------------------------------+---------------------------------+
   | 8 | &#x3C0;@example.com/&#x3C3mp;#x3C3; | A resourcepart of GREEK SMALL   |
   |   |                             | LETTER SIGMA (U+03C3)           |
   +---------------------------------+---------------------------------+
   | 9 | &#x3C0;@example.com/&#x3C2mp;#x3C2; | A resourcepart of GREEK SMALL   |
   |   |                             | LETTER FINAL SIGMA (U+03C2)     |
   +---------------------------------+---------------------------------+
   | 10| henryiv@example.com/&#x265A;| A resourcepart of the Unicode   |
   |   |                             | character BLACK CHESS KING      |
   |   |                             | (U+265A)                        |
   +---------------------------------+---------------------------------+

   Several points might be worth noting here.  Regarding examples 4 and
   5: although in German the character esszett (LATIN SMALL LETTER SHARP
   S, U+00DF) can mostly be used interchangeably with the two characters
   "ss", the localparts in these examples are different and (if desired)
   a server would need to enforce a registration policy that disallows
   one of them if the other is registered.  Regarding examples 7, 8, and
   9: case-mapping of GREEK CAPITAL LETTER SIGMA (U+03A3) to lowercase
   (i.e., to GREEK SMALL LETTER SIGMA, U+03C3) during comparison would
   result in matching the JIDs in examples 7 and 8; PRECIS mapping rules
   do not account for the special status of GREEK SMALL LETTER FINAL
   SIGMA (U+03C2), so the JIDs in examples 8 and 9 would not be matched.
   Regarding example 10: symbol characters such as BLACK CHESS KING
   (U+265A) are allowed by the PRECIS FreeformClass.

   The following examples illustrate strings that are not JIDs because
   they violate the format defined above.

   Table 2: A sample of strings that violate the JID rules

   +---------------------------------+---------------------------------+
   | # | Non-JID string              | Notes                           |
   +---------------------------------+---------------------------------+
   | 1 | "juliet"@example.com        | Quotation marks (U+0022) are    |
   |   |                             | not allowed in the localpart    |
   +---------------------------------+---------------------------------+
   | 2 | foo bar@example.com         | Spaces are not allowed in the   |
   |   |                             | localpart                       |
   +---------------------------------+---------------------------------+
   | 3 | &#x265A@example.com         | Symbol characters (e.g., U+265A)|
   |   |                             | are not allowed in the localpart|
   +---------------------------------+---------------------------------+
   | 4 | juliet@example.com/ foo     | Leading spaces are not allowed  |
   |   |                             | in the resourcepart             |
   +---------------------------------+---------------------------------+
   | 5 | juliet@example.com/foo  bar | Double spaces are not allowed   |
   |   |                             | in the resourcepart             |
   +---------------------------------+---------------------------------+

###

_______________________________________________
xmpp mailing list
xmpp@ietf.org
https://www.ietf.org/mailman/listinfo/xmpp