This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task
Force (IETF). Note that other groups may also distribute working
documents as Internet-Drafts. The list of current Internet-Drafts is
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 27 October 2020.¶
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided without
warranty as described in the Simplified BSD License.¶
This document contains test vectors for several Preparation,
Enforcement, and Comparison of Internationalized Strings (PRECIS) [RFC8264] profiles.¶
Two sets of vectors exist for profiles of the base classes.
The first set tests the enforcement step.
It takes the form of a table that contains an input string, an output
string and an optional error.
If the error column has a value of "ctx" it indicates that the context
rule was violated, "empty" means that an empty string was disallowed,
"rune" means that a disallowed code point (rune) was encountered, and
"bidi" indicates that the BIDI Rule was violated.
The second set tests the PRECIS comparison step.
It takes the form of a table that contains two strings, a boolean that
is TRUE if the two strings should be considered equal and FALSE
otherwise, and an optional comment.¶
The test vectors in this document have been verified by three
An implementation that concurs with the results provided in this
document should be interoperable with other implementations.¶
Input and output strings are expressed as UTF-8 and hexidecimal encoded
This document is intended to provide test vectors for the PRECIS framework
and its profiles.
No assertion of the security of the PRECIS framework or its profiles for
any particular use is intended.
The reader is referred to [RFC8264] for a
discussion of the general security of the PRECIS framework.¶
Saint-Andre, P. and M. Blanchet, "PRECIS Framework: Preparation, Enforcement, and Comparison of Internationalized Strings in Application Protocols", RFC 8264, DOI 10.17487/RFC8264, , <https://www.rfc-editor.org/info/rfc8264>.
The author would like to thank Marcel van Lohuizen of Google for his help
and code reviews on the Go programming language implementation of PRECIS
for which these tests were designed and for contributing many of the tests
Also, Peter Saint-Andre for his encouragement on this document.¶