llm-wiki/raw/official-docs/rfc6455-websocket.md

title, source_type, url, archive_url, related_branches, related_projects, tags, created, last_reviewed

title	source_type	url	archive_url	related_branches	related_projects	tags	created	last_reviewed
official-doc / IETF RFC 6455 — The WebSocket Protocol	official-doc	https://www.rfc-editor.org/rfc/rfc6455.html		feature-streaming-response-contract	ca-skeleton	websocket rfc6455 ietf full-duplex tcp http-upgrade streaming protocol bidirectional	2026-06-02	2026-06-02

IETF RFC 6455 — The WebSocket Protocol

Layer: raw/official-docs/ — IETF RFC 6455 (December 2011, Standards Track) 핵심 섹션 발췌. Strength 분류: official-standard — IETF Standards Track RFC. 검증된 요약은 /ingest 후 wiki/concepts/ 에 별도 작성.

Parent / 활용 branch (필수)

Branch	이 자료가 정당화하는 결정
raw/branch-notes/feature-streaming-response-contract	WebSocket alternative 의 프로토콜 명세 근거 — full-duplex, HTTP Upgrade handshake, frame 구조, TCP 관계, 보안 요구사항 (client masking)

출처 / Source

• 원본 URL: https://www.rfc-editor.org/rfc/rfc6455.html
• Datatracker URL: https://datatracker.ietf.org/doc/html/rfc6455
• 아카이브 URL: (미수집)
• 저자 / 조직: IETF — I. Fette (Google), A. Melnikov (Isode Ltd)
• 발행일: 2011-12 (December 2011, Proposed Standard / Standards Track)
• 마지막 확인일: 2026-06-02

왜 저장했는지 / Why archived

feature-streaming-response-contract 에서 WebSocket 은 SSE 와 함께 핵심 비교 alternative. RFC 6455 는 WebSocket 의 유일한 normative specification. full-duplex 특성, HTTP → WebSocket upgrade 메커니즘, 클라이언트 프레임 masking 요구사항, TCP 와의 관계를 claim 수준으로 확인하기 위해 보관. 특히 "HTTP 와 독립된 TCP-based 프로토콜" 정의가 ca-skeleton 의 reverse proxy 설정 부담 claim 의 근거.

핵심 인용 / Key quotes (verbatim)

[Abstract] "The WebSocket Protocol enables two-way communication between a client running untrusted code in a controlled environment to a remote host that has opted-in to communications from that code. The security model used for this is the origin-based security model commonly used by web browsers. The protocol consists of an opening handshake followed by basic message framing, layered over TCP."

[Abstract] "The goal of this technology is to provide a mechanism for browser-based applications that need two-way communication with servers that does not rely on opening multiple HTTP connections (e.g., using XMLHttpRequest or