Alexey Melnikov wrote: > Nicolas Williams wrote: > >> A domain-based name consists of three required elements: >> >> o a service name >> >> o a domain name >> >> o a hostname >> >> + For the purposes of domain-based names a "domain" is defined by the >> + applications that use domain-based names. An application protocol >> + might use a simple DNS domainname, such as "example.com" for naming, >> + while another it might use the DNS domainname of the SRV RRs it >> + queries (e.g., "_tcp._foo.example.com"), and yet another may use >> + something that does not resemble a DNS domainname. Application >> + protocol specifications that provide for use of domain-based service >> + names MUST define the domain-portion of their domain-based names. >> >> > I like the suggested changes, except for the last sentence quoted above. > Here you are trying to put requirements on application protocols, which > is probably Ok. But you are effectively declaring all existing > application layer protocols non compliant with this MUST. Was this the > intent? The way I read this is that the MUST does not apply to existing application protocols because they do not "provide for the use of domain-based service names". Only new application protocols that specify the use of domain-based service names will need to define what a "domain" is for that application. Jeffrey Altman
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature