Hi Peter, On Mon, Mar 05, 2012 at 09:34:31AM -0700, Peter Saint-Andre wrote: > 2. case preservation > > The problem statement document mentions the need to specify whether an > application protocol preserves case. However, the framework document > does not require profile documents to specify whether they preserve > case, nor does it provide guidelines or mechanisms for doing so.
This came up more than once in discussion, however, so I presume people still think it's important. > 3. mapped to nothing > > The problem statement document mentions the possibility of mapping > characters to nothing, as was done in some stringprep profiles. However, > the framework document does not provide guidelines or mechanisms for > doing so. Some of the reviews indicated that there are existing stringprep profiles in use that map to nothing. If we're going to say that this is deprecated, we need to state it outright. > 4. string classes > > The problem statement document mentions five possible string classes, > corresponding roughly to (a) domain names, (b) usernames, (c) secrets, > (d) protocol strings, and (e) string blobs. Clearly, (a) is covered by > IDNA2008. However, the framework document now covers only (b) via the > NameClass and (d) via the FreeClass, because it removed the SecretClass > and never included a blob-class of some sort. Do we need to bring these > into alignment? The working copy text that Marc and I are working on has DomainClass, NameClass, and FreeClass in it. NameClass is defined to be like IDNA2008, which means that framework shouldn't have it. The other two are in framework-01 (I just checked). > 5. blobs > > Following up on (4), do we need to define a BlobClass, or would such a > class be an absolute identifier requiring only byte-for-byte comparison > (and thus not need PRECIS-based comparison rules)? We concluded previously that we did not need it. Best, A -- Andrew Sullivan [email protected] _______________________________________________ precis mailing list [email protected] https://www.ietf.org/mailman/listinfo/precis
