The WebSocket protocol
Network Working Group I. Hickson Internet-Draft Google, Inc. Intended status: Standards Track May 6, 2010 Expires: November 7, 2010 The WebSocket protocol draft-hixie-thewebsocketprotocol-76 Abstract The WebSocket protocol enables two-way communication between a user agent running untrusted code running in a controlled environment to a remote host that has opted-in to communications from that code
RFC 2426: vCard MIME Directory Profile
Network Working Group F. Dawson Request for Comments: 2426 Lotus Development Corporation Category: Standards Track T. Howes Netscape Communications September 1998 vCard MIME Directory Profile Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of th
RFC 2425: A MIME Content-Type for Directory Information
Network Working Group T. Howes Request for Comments: 2425 M. Smith Category: Standards Track Netscape Communications Corp. F. Dawson Lotus Development Corporation September 1998 A MIME Content-Type for Directory Information Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please re
Stateless Automatic IPv4 over IPv6 Encapsulation / Decapsulation Technology: Specification
Network Working Group N. Matsuhira Internet-Draft Fujitsu Limited Intended status: Informational February 1, 2010 Expires: August 5, 2010 Stateless Automatic IPv4 over IPv6 Tunneling: Specification draft-matsuhira-sa46t-spec-00 Abstract This document specifies Stateless Automatic IPv4 over IPv6 Tunneling (SA46T) base specification. SA46T makes backbone network to IPv6 only. And also, SA46T can sta
RFC 5849: The OAuth 1.0 Protocol
Internet Engineering Task Force (IETF) E. Hammer-Lahav, Ed. Request for Comments: 5849 April 2010 Category: Informational ISSN: 2070-1721 The OAuth 1.0 Protocol Abstract OAuth provides a method for clients to access server resources on behalf of a resource owner (such as a different client or an end- user). It also provides a process for end-users to authorize third- party access to their server r
RFC 2606: Reserved Top Level DNS Names
Network Working Group D. Eastlake Request for Comments: 2606 A. Panitz BCP: 32 June 1999 Category: Best Current Practice Reserved Top Level DNS Names Status of this Memo This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet S
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
vCard Format Specification
RFC 5625: DNS Proxy Implementation Guidelines
vCard Format Specification
vCard Format Specification
The OAuth 2.0 Authorization Framework
RFC 3987: Internationalized Resource Identifiers (IRIs)
Stateless Automatic IPv4 over IPv6 Encapsulation / Decapsulation Technology: Global SA46T Address Format
RFC 1055: Nonstandard for transmission of IP datagrams over serial lines: SLIP
RFC 5721: POP3 Support for UTF-8
IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) -- Protocol Specification
IPv6 via IPv4 Service Provider Networks
IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) -- Protocol Specification
IPv6 via IPv4 Service Provider Networks
Emerging Service Provider Scenarios for IPv6 Deployment