<html xmlns="http://www.w3.org/1999/xhtml"><head></head><body><figure class="quote"><figcaption><p><anchor-end xmlns="urn:x-suika-fam-cx:markup:suikawiki:0:9:" a0:anchor="1" xmlns:a0="urn:x-suika-fam-cx:markup:suikawiki:0:9:">[1]</anchor-end> <cite xml:lang="en">RFC 6125 - Representation and Verification of Domain-Based Application Service Identity within Internet Public Key Infrastructure Using X.509 (PKIX) Certificates in the Context of Transport Layer Security (TLS)</cite>
(<time>2015-03-13 22:27:53 +09:00</time> 版)
<anchor-external xmlns="urn:x-suika-fam-cx:markup:suikawiki:0:9:" a0:resScheme="URI" xmlns:a0="urn:x-suika-fam-cx:markup:suikawiki:0:9:" a0:resParameter="https://tools.ietf.org/html/rfc6125#section-1.8">https://tools.ietf.org/html/rfc6125#section-1.8</anchor-external></p></figcaption><blockquote><p>source domain:  The fully qualified DNS domain name that a client</p><p>expects an application service to present in the certificate</p><p>(e.g., &quot;www.example.com&quot;), typically input by a human user,</p><p>configured into a client, or provided by reference such as in a</p><p>hyperlink.  The combination of a source domain and, optionally, an</p><p>application service type enables a client to construct one or more</p><p>reference identifiers.</p></blockquote></figure></body></html>