<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 5246 - The Transport Layer Security (TLS) Protocol Version 1.2</cite>
(<time>2015-02-19 08:58:15 +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="http://tools.ietf.org/html/rfc5246#page-79">http://tools.ietf.org/html/rfc5246#page-79</anchor-external></p></figcaption><blockquote><p>client</p><p>The application entity that initiates a TLS connection to a</p><p>server.  This may or may not imply that the client initiated the</p><p>underlying transport connection.  The primary operational</p><p>difference between the server and client is that the server is</p><p>generally authenticated, while the client is only optionally</p><p>authenticated.</p></blockquote></figure><figure class="quote"><figcaption><p><anchor-end xmlns="urn:x-suika-fam-cx:markup:suikawiki:0:9:" a0:anchor="2" xmlns:a0="urn:x-suika-fam-cx:markup:suikawiki:0:9:">[2]</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>TLS client:  An entity that assumes the role of a client in a</p><p>Transport Layer Security <strong>[</strong>TLS<strong>]</strong> negotiation.  In this specification</p><p>we generally assume that the TLS client is an (interactive or</p><p>automated) application client; however, in application protocols</p><p>that enable server-to-server communication, the TLS client could</p><p>be a peer application service.</p></blockquote></figure></body></html>