"Eric A. Hall" wrote:
> A trickier problem is finding the encapsulation substrate. Do we specify > encodings for protocols, or for data formats? In the latter case, do we > define TES for every registered MIME charset/encoding? I mean, do we > really want to define transfer encodings for ISO-2022-JP (including > all of the charset switching stuff)? I would point out here that the DNS message is also a data format which has its own peculiarities, in that it provides the octet encoding syntax for domain names, and which has to be recognized and supported as an application-specific encoding. This is an example that shows how there will be application-specific encodings, but that this WG does not have to explicitly define every such encoding (DNSEXT owns this one, for example). -- Eric A. Hall http://www.ehsco.com/ Internet Core Protocols http://www.oreilly.com/catalog/coreprot/
