https://twitter.com/LiosK/status/1588116287422877697
April Fools' Day Request for Comments - Wikipedia
A Request for Comments (RFC), in the context of Internet governance, is a type of publication from the Internet Engineering Task Force (IETF) and the Internet Society (ISOC), usually describing methods, behaviors, research, or innovations applicable to the working of the Internet and Internet-connected systems. Almost every April Fools' Day (1 April) since 1989, the Internet RFC Editor has publish
RFC 5841: TCP Option to Denote Packet Mood
This RFC was published on the Independent Submission stream. This RFC is not endorsed by the IETF and has no formal standing in the IETF standards process. Independent Submission R. Hay Request for Comments: 5841 W. Turkal Category: Informational Google Inc. ISSN: 2070-1721 1 April 2010 TCP Option to Denote Packet Mood Abstract This document proposes a new TCP option to denote packet mood. Status
RFC 792: Internet Control Message Protocol
Network Working Group J. Postel Request for Comments: 792 ISI September 1981 Updates: RFCs 777, 760 Updates: IENs 109, 128 INTERNET CONTROL MESSAGE PROTOCOL DARPA INTERNET PROGRAM PROTOCOL SPECIFICATION Introduction The Internet Protocol (IP) [1] is used for host-to-host datagram service in a system of interconnected networks called the Catenet [2]. The network connecting devices are called Gatewa
RFC 768: User Datagram Protocol
RFC 768 J. Postel ISI 28 August 1980 User Datagram Protocol ---------------------- Introduction ------------ This User Datagram Protocol (UDP) is defined to make available a datagram mode of packet-switched computer communication in the environment of an interconnected set of computer networks. This protocol assumes that the Internet Protocol (IP) [1] is used as the underlying protocol. This proto
RFC 5905: Network Time Protocol Version 4: Protocol and Algorithms Specification
Internet Engineering Task Force (IETF) D. Mills Request for Comments: 5905 U. Delaware Obsoletes: 1305, 4330 J. Martin, Ed. Category: Standards Track ISC ISSN: 2070-1721 J. Burbank W. Kasch JHU/APL June 2010 Network Time Protocol Version 4: Protocol and Algorithms Specification Abstract The Network Time Protocol (NTP) is widely used to synchronize computer clocks in the Internet. This document des
RFC 2460: Internet Protocol, Version 6 (IPv6) Specification
Network Working Group S. Deering Request for Comments: 2460 Cisco Obsoletes: 1883 R. Hinden Category: Standards Track Nokia December 1998 Internet Protocol, Version 6 (IPv6) Specification 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 the "I
RFC 7159: The JavaScript Object Notation (JSON) Data Interchange Format
Internet Engineering Task Force (IETF) T. Bray, Ed. Request for Comments: 7159 Google, Inc. Obsoletes: 4627, 7158 March 2014 Category: Standards Track ISSN: 2070-1721 The JavaScript Object Notation (JSON) Data Interchange Format Abstract JavaScript Object Notation (JSON) is a lightweight, text-based, language-independent data interchange format. It was derived from the ECMAScript Programming Langu
RFC 4180: Common Format and MIME Type for Comma-Separated Values (CSV) Files
Network Working Group Y. Shafranovich Request for Comments: 4180 SolidMatrix Technologies, Inc. Category: Informational October 2005 Common Format and MIME Type for Comma-Separated Values (CSV) Files Status of This Memo This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. Copyright Notice Copyright
RFC 4648: The Base16, Base32, and Base64 Data Encodings
Network Working Group S. Josefsson Request for Comments: 4648 SJD Obsoletes: 3548 October 2006 Category: Standards Track The Base16, Base32, and Base64 Data Encodings 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 the "Internet Official Prot
RFC 7231: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content
Internet Engineering Task Force (IETF) R. Fielding, Ed. Request for Comments: 7231 Adobe Obsoletes: 2616 J. Reschke, Ed. Updates: 2817 greenbytes Category: Standards Track June 2014 ISSN: 2070-1721 Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content Abstract The Hypertext Transfer Protocol (HTTP) is a stateless application- level protocol for distributed, collaborative, hypertext informa
RFC 6919: Further Key Words for Use in RFCs to Indicate Requirement Levels
Independent Submission R. Barnes Request for Comments: 6919 S. Kent Category: Experimental BBN ISSN: 2070-1721 E. Rescorla RTFM, Inc. 1 April 2013 Further Key Words for Use in RFCs to Indicate Requirement Levels Abstract RFC 2119 defines a standard set of key words for describing requirements of a specification. Many IETF documents have found that these words cannot accurately capture the nuanced
SPDY Protocol
This document is an Internet-Draft (I-D). Anyone may submit an I-D to the IETF. This I-D is not endorsed by the IETF and has no formal standing in the IETF standards process. Network Working Group M. Belshe Internet-Draft Twist Expires: August 4, 2012 R. Peon Google, Inc Feb 2012 SPDY Protocol draft-mbelshe-httpbis-spdy-00 Abstract This document describes SPDY, a protocol designed for low-latency
RFC 2119 - Key words for use in RFCs to Indicate Requirement Levels
Network Working Group S. Bradner Request for Comments: 2119 Harvard University BCP: 14 March 1997 Category: Best Current Practice Key words for use in RFCs to Indicate Requirement Levels 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. Abstract
RFC1035(DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION)
2. INTRODUCTION 2. 導入 2.1. Overview 2.1. 概観 The goal of domain names is to provide a mechanism for naming resources in such a way that the names are usable in different hosts, networks, protocol families, internets, and administrative organizations. ドメイン名の目的は、異なるホスト・ネットワーク・プロトコルファミリ・インターネット・管理組織において名前を利用できる方法で、リソースに名前を付けるメカニズムを提供することである。 From the user's point of view, domain names are useful as ar
RFC1034(DOMAIN NAMES - CONCEPTS AND FACILITIES)
トップページ - 翻訳ドキュメント - RFC 1034 原文：ftp://ftp.rfc-editor.org/in-notes/rfc1034.txt 原文との対訳として読みたい方へ：このページをローカルに保存して、スタイルシートの original クラスの display 属性を none から block に変更してみてください。 サイト内関連リンク：RFC 1035 DNS 実装と仕様 Network Working Group Request for Comments: 1034 Obsoletes: RFCs 882, 883, 973 DOMAIN NAMES - CONCEPTS AND FACILITIES ドメイン名- 概念と機能 1. STATUS OF THIS MEMO 1. この文書の位置付け This RFC is an introduction to t
RFC 1035: Domain names - implementation and specification
Updated by RFC 1101, RFC 1183, RFC 1348, RFC 8490, RFC 8482, RFC 8767, RFC 2308, RFC 2137, RFC 2181, RFC 1982, RFC 2136, RFC 1996, RFC 1995, RFC 1876, RFC 2065, RFC 4034, RFC 4035, RFC 4343, RFC 5966, RFC 6604, RFC 2535, RFC 2673, RFC 2845, RFC 5936, RFC 3425, RFC 3658, RFC 4033, RFC 7766, RFC 9619 Network Working Group P. Mockapetris Request for Comments: 1035 ISI November 1987 Obsoletes: RFCs 88
RFC 1034: Domain names - concepts and facilities
Network Working Group P. Mockapetris Request for Comments: 1034 ISI Obsoletes: RFCs 882, 883, 973 November 1987 DOMAIN NAMES - CONCEPTS AND FACILITIES 1. STATUS OF THIS MEMO This RFC is an introduction to the Domain Name System (DNS), and omits many details which can be found in a companion RFC, "Domain Names - Implementation and Specification" [RFC-1035]. That RFC assumes that the reader is famil
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Standards.REST