[B! RFC] ihagã®ãƒ–ãƒƒã‚¯ãƒžãƒ¼ã‚¯

ihag id:ihag

RFCã«é–¢ã™ã‚‹ihagã®ãƒ–ãƒƒã‚¯ãƒžãƒ¼ã‚¯ (13)

${{author_name}}$

{{{comment_expanded}}}

{{label}}

{{#is_bookmark}}ãƒªã‚¹ãƒˆ{{/is_bookmark}}{{^is_bookmark}}ãƒªãƒ³ã‚¯{{/is_bookmark}}

${{author_name}}$
{{author_name}}{{created}}
{{ #comment }}{{ comment }}{{ /comment }}
- {{ label }}

${{author_name}}$

{{{comment_expanded}}}

{{label}}

{{#is_bookmark}}ãƒªã‚¹ãƒˆ{{/is_bookmark}}{{^is_bookmark}}ãƒªãƒ³ã‚¯{{/is_bookmark}}

BGPã®æŒç¶šçš„ãªçµŒè·¯ã‚ªã‚·ãƒ¬ãƒ¼ã‚·ãƒ§ãƒ³ã®è§£æ±ºæ³• (RFC 7964)
ihag 2017/04/10
BGP

RFC

RFC7964
ãƒªãƒ³ã‚¯
RFC 6763: DNS-Based Service Discovery
Internet Engineering Task Force (IETF) S. Cheshire Request for Comments: 6763 M. Krochmal Category: Standards Track Apple Inc. ISSN: 2070-1721 February 2013 DNS-Based Service Discovery Abstract This document specifies how DNS resource records are named and structured to facilitate service discovery. Given a type of service that a client is looking for, and a domain in which the client is looking f
ihag 2014/06/02
mDNS

RFC
ãƒªãƒ³ã‚¯
ã‚µãƒ¼ãƒ“ã‚¹çµ‚äº†ã®ãŠçŸ¥ã‚‰ã›
ã‚µãƒ¼ãƒ“ã‚¹çµ‚äº†ã®ãŠçŸ¥ã‚‰ã› ã„ã¤ã‚‚Yahoo! JAPANã®ã‚µãƒ¼ãƒ“ã‚¹ã‚’ã”åˆ©ç”¨ã„ãŸã ãèª ã«ã‚ã‚ŠãŒã¨ã†ã”ã–ã„ã¾ã™ã€‚ ãŠå®¢æ§˜ãŒã‚¢ã‚¯ã‚»ã‚¹ã•ã‚ŒãŸã‚µãƒ¼ãƒ“ã‚¹ã¯æœ¬æ—¥ã¾ã§ã«ã‚µãƒ¼ãƒ“ã‚¹ã‚’çµ‚äº†ã„ãŸã—ã¾ã—ãŸã€‚ ä»Šå¾Œã¨ã‚‚Yahoo! JAPANã®ã‚µãƒ¼ãƒ“ã‚¹ã‚’ã”æ„›é¡§ãã ã•ã„ã¾ã™ã‚ˆã†ã€ã‚ˆã‚ã—ããŠé¡˜ã„ã„ãŸã—ã¾ã™ã€‚
ihag 2014/01/14
NTP

RFC

network
ãƒªãƒ³ã‚¯
RFC 4271: A Border Gateway Protocol 4 (BGP-4)
Network Working Group Y. Rekhter, Ed. Request for Comments: 4271 T. Li, Ed. Obsoletes: 1771 S. Hares, Ed. Category: Standards Track January 2006 A Border Gateway Protocol 4 (BGP-4) 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
ihag 2013/11/29
BGP4

RFC

RFC4271
ãƒªãƒ³ã‚¯
JSON ã®ç´¹ä»‹
JSON (JavaScript Object Notation)ã¯ã€è»½é‡ã®ãƒ‡ãƒ¼ã‚¿äº¤æ›ãƒ•ã‚©ãƒ¼ãƒžãƒƒãƒˆã§ã™ã€‚äººé–“ã«ã¨ã£ã¦èªã¿æ›¸ããŒå®¹æ˜“ã§ã€ãƒžã‚·ãƒ³ã«ã¨ã£ã¦ã‚‚ç°¡å˜ã«ãƒ‘ãƒ¼ã‚¹ã‚„ç”Ÿæˆã‚’è¡Œãªãˆã‚‹å½¢å¼ã§ã™ã€‚ JavaScriptãƒ—ãƒã‚°ãƒ©ãƒŸãƒ³ã‚°è¨€èªž ï¼ˆECMA-262æ¨™æº–ç¬¬3ç‰ˆ 1999å¹´12æœˆï¼‰ã®ä¸€éƒ¨ã‚’ãƒ™ãƒ¼ã‚¹ã«ä½œã‚‰ã‚Œã¦ã„ã¾ã™ã€‚ JSONã¯å®Œå…¨ã«è¨€èªžã‹ã‚‰ç‹¬ç«‹ã—ãŸãƒ†ã‚ã‚¹ãƒˆå½¢å¼ã§ã™ãŒã€Cã€C++ã€C#ã€Javaã€JavaScriptã€Perlã€Pythonã€ãã®ä»–å¤šãã®Cãƒ•ã‚¡ãƒŸãƒªãƒ¼ã®è¨€èªžã‚’ä½¿ç”¨ã™ã‚‹ãƒ—ãƒã‚°ãƒ©ãƒžã«ã¨ã£ã¦ã¯ã€é¦´æŸ“ã¿æ·±ã„è¦ç´„ãŒä½¿ã‚ã‚Œã¦ã„ã¾ã™ã€‚ã“ã‚Œã‚‰ã®æ€§è³ªãŒã€ JSONã‚’ç†æƒ³çš„ãªãƒ‡ãƒ¼ã‚¿äº¤æ›è¨€èªžã«ã—ã¦ã„ã¾ã™ã€‚ JSONã¯2ã¤ã®æ§‹é€ ã‚’åŸºã«ã—ã¦ã„ã¾ã™ã€‚ åå‰/å€¤ã®ãƒšã‚¢ã®é›†ã¾ã‚Šã€‚æ§˜ã€…ãªè¨€èªžã§ã€ã“ã‚Œã¯ã‚ªãƒ–ã‚¸ã‚§ã‚¯ãƒˆã€ãƒ¬ã‚³ãƒ¼ãƒ‰ã€æ§‹é€ ä½“ã€ãƒ‡ã‚£ã‚¯ã‚·ãƒ§ãƒŠãƒªã€ãƒãƒƒã‚·ãƒ¥ãƒ†ãƒ¼ãƒ–ãƒ«ã€ã‚ãƒ¼ã®ã‚ã‚‹ãƒªã‚¹ãƒˆã€é€£æƒ³é…åˆ—ã¨ã—ã¦å®Ÿç¾ã•ã‚Œã¦ã„ã¾ã™ã€‚
ihag 2008/02/04
Web

WebApp

JSON

research

standard

RFC
ãƒªãƒ³ã‚¯
studyinghttp.netÂ -Â ã“ã®ã‚¦ã‚§ãƒ–ã‚µã‚¤ãƒˆã¯è²©å£²ç”¨ã§ã™ï¼Â -Â è§£èª¬ ä»•æ§˜æ›¸ åˆ©ç”¨ æŠ€è¡“ ã§ã‚ã‚‹ æ‰‹æ³• æ—¥æœ¬èªžè¨³ ãƒ—ãƒã‚°ãƒ©ãƒŸãƒ³ã‚° ãƒªã‚½ãƒ¼ã‚¹ãŠã‚ˆã³æƒ…å ±
ã“ã®ã‚¦ã‚§ãƒ–ã‚µã‚¤ãƒˆã¯è²©å£²ç”¨ã§ã™ï¼ studyinghttp.net ã¯ã€ã‚ãªãŸãŒãŠæŽ¢ã—ã®æƒ…å ±ã®å…¨ã¦ã®æœ€æ–°ã‹ã¤æœ€é©ãªã‚½ãƒ¼ã‚¹ã§ã™ã€‚ä¸€èˆ¬ãƒˆãƒ”ãƒƒã‚¯ã‹ã‚‰ã“ã“ã‹ã‚‰æ¤œç´¢ã§ãã‚‹å†…å®¹ã¯ã€studyinghttp.netãŒå…¨ã¦ã¨ãªã‚Šã¾ã™ã€‚ã‚ãªãŸãŒãŠæŽ¢ã—ã®å†…å®¹ãŒè¦‹ã¤ã‹ã‚‹ã“ã¨ã‚’é¡˜ã£ã¦ã„ã¾ã™ï¼
ihag 2008/02/03
HTTP 1.1ã®å·®åˆ†GETã¨ã‹

RFC

standard

HTTP

Web

WebApp

research
ãƒªãƒ³ã‚¯
RFC2616: ãƒã‚¤ãƒ‘ãƒ¼ãƒ†ã‚ã‚¹ãƒˆè»¢é€ãƒ—ãƒãƒˆã‚³ãƒ« -- HTTP/1.1
This webpage was generated by the domain owner using SedoÂ Domain Parking. Disclaimer: Sedo maintains no relationship with third party advertisers. Reference to any specific service or trade mark is not controlled by Sedo nor does it constitute or imply its association, endorsement or recommendation.
ihag 2008/02/03
è¨€ã‚ãšã¨çŸ¥ã‚ŒãŸRFC2616

HTTP

Web

WebApp

RFC

standard

research
ãƒªãƒ³ã‚¯
studyinghttp.netÂ -Â
ihag 2008/02/03
Web

WebApp

HTTP

standard

RFC

research
ãƒªãƒ³ã‚¯
RFC2965: HTTP çŠ¶æ…‹ç®¡ç†ãƒ¡ã‚«ãƒ‹ã‚ºãƒ
Studying HTTP > RFC-Translations related HTTP ã“ã®æ–‡æ›¸ã¯ã€ D. Kristol, L. Montulli: HTTP State Management Mechanism (RFC 2965), October 2000. ã‚’ æ©‹æœ¬è‹±å½¦ ãŒæ—¥æœ¬èªžè¨³ã—ãŸç‰©ã§ã™ã€‚ ã“ã®æ–‡æ›¸ã®å–ã‚Šæ‰±ã„ã«ã¤ã„ã¦ã¯ã€[Studying HTTP] ã® RFC æ—¥æœ¬èªžè¨³ã‚’åˆ©ç”¨ã™ã‚‹ã«ã‚ãŸã£ã¦ã«å¾“ã£ã¦ä¸‹ã•ã„ã€‚ Network Working Group Request for Comments: 2965 Obsoletes: 2109 Category: Standards Track D. Kristol Bell Laboratories, Lucent Techno logies L. Montulli Epinions.com, Inc. October 2000
ihag 2008/02/03
HTTP Cookieã®ä»•æ§˜(RFC)

research

HTTP

WebApp

Web

Cookie

RFC

standard
ãƒªãƒ³ã‚¯
[Studying HTTP] RFC-Translations related HTTP
ã“ã®ã‚¦ã‚§ãƒ–ã‚µã‚¤ãƒˆã¯è²©å£²ç”¨ã§ã™ï¼ studyinghttp.net ã¯ã€ã‚ãªãŸãŒãŠæŽ¢ã—ã®æƒ…å ±ã®å…¨ã¦ã®æœ€æ–°ã‹ã¤æœ€é©ãªã‚½ãƒ¼ã‚¹ã§ã™ã€‚ä¸€èˆ¬ãƒˆãƒ”ãƒƒã‚¯ã‹ã‚‰ã“ã“ã‹ã‚‰æ¤œç´¢ã§ãã‚‹å†…å®¹ã¯ã€studyinghttp.netãŒå…¨ã¦ã¨ãªã‚Šã¾ã™ã€‚ã‚ãªãŸãŒãŠæŽ¢ã—ã®å†…å®¹ãŒè¦‹ã¤ã‹ã‚‹ã“ã¨ã‚’é¡˜ã£ã¦ã„ã¾ã™ï¼
ihag 2008/02/03
HTTPé–¢é€£ã®RFCï¼Ž2005å¹´æœ«é ƒã¾ã§ã®RFC(RFC4229)ã‚’ã‚«ãƒãƒ¼ã—ã¦ã„ã‚‹ï¼Ž

RFC

standard

HTTP

research

Web

WebApp
ãƒªãƒ³ã‚¯
ã‚½ãƒ•ãƒˆã‚¦ã‚§ã‚¢åˆ†é‡Žã®ç ”ç©¶é–‹ç™º / RFC 5023 Atom Publishing Protocol æ—¥æœ¬èªžè¨³ | Ricoh Japan
ã“ã®æ–‡æ›¸ã¯ RFC 5023 The Atom Publishing Protocol ã‚’, BCP78ã«ã‚ˆã£ã¦ä»˜è¨—ã•ã‚ŒãŸæ¨©åˆ©ã«åŸºã¥ã„ã¦æ—¥æœ¬èªžã«ç¿»è¨³ã—ãŸã‚‚ã®ã§ã™ã€‚ ç¿»è¨³ã«ã¯èª¤ã‚ŠãŒã‚ã‚‹å¯èƒ½æ€§ãŒã‚ã‚Šã¾ã™ã€‚ã“ã®ç¿»è¨³ã®æ£ç¢ºæ€§ã¯ä¿è¨¼ã—ã¾ã›ã‚“ã€‚ ç¿»è¨³ã«ã¤ã„ã¦ã®ãŠå•åˆã›å…ˆï¼šï¼ˆSSLå¯¾å¿œãƒ•ã‚©ãƒ¼ãƒ ï¼‰ ï¼ˆéžSSLå¯¾å¿œãƒ•ã‚©ãƒ¼ãƒ ï¼‰ ç¿»è¨³è€…ä¸€è¦§ æ ªå¼ä¼šç¤¾ãƒªã‚³ãƒ¼ å±±æœ¬é™½å¹³ æ—¥é‡ŽåŽŸå¯› é«˜æ¡‘å¯¿ä¸€ ä¸å·å‹æ¨¹ æ²–ç”°é‚¦å¤« äº•ä¸Šæµ©ä¸€ å…µæ¸…å¼˜ ãƒªã‚³ãƒ¼ã‚½ãƒ•ãƒˆã‚¦ã‚¨ã‚¢æ ªå¼ä¼šç¤¾ ç¦ç”°æœ‹ç´€ æ›´æ–°å±¥æ´ 2008-01-07 æ—¥å¤–ã‚¢ã‚½ã‚·ã‚¨ãƒ¼ãƒ„æ ªå¼ä¼šç¤¾ ä¹…æˆ‘æ§˜ã®æŒ‡æ‘˜ã‚’å—ã‘ 9.7 ã®è¨³æ–‡ã‚’ã‚ã‹ã‚Šã‚„ã™ãã€11.2 ã®æŠœã‘ã‚’ä¿®æ£ 2007-12-06 9.6ã€9.7.1ã€9.7.2ã€10 ã®èª¤è¨˜ã€è¡¨è¨˜ã¶ã‚Œã‚’ä¿®æ£ 2007-11-08 ã‚¨ãƒŒãƒ»ãƒ†ã‚£ãƒ»ãƒ†ã‚£ãƒ»ã‚³ãƒŸãƒ¥ãƒ‹ã‚±ãƒ¼ã‚·ãƒ§ãƒ³ã‚ºæ ªå¼ä¼šç¤¾ æœå€‰æ§˜ã®æŒ‡æ‘˜ã‚’å—ã‘ 9.3/9.4 ã®èª¤è¨³ã‚’ä¿®æ£ 2007-11-0
ihag 2007/10/13
atompub

protocol

reference

rfc
ãƒªãƒ³ã‚¯
http://www.openspf.org/svn/project/specs/rfc4408.txt
ihag 2007/05/15
Sender Policy Framework

RFC

SPF
ãƒªãƒ³ã‚¯
RFC793 - Transmission Control Protocol
TRANSMISSION CONTROL PROTOCOL DARPA INTERNET PROGRAM PROTOCOL SPECIFICATION September 1981 prepared for Defense Advanced Research Projects Agency Information Processing Techniques Office 1400 Wilson Boulevard Arlington, Virginia 22209 by Information Sciences Institute University of Southern California 4676 Admiralty Way Marina del Rey, California 90291 TABLE OF CONTENTS åºç« 1. å°Žå…¥ 1.1 å‹•æ©Ÿ 1.2 æ¦‚è¦ 1.3
ihag 2005/08/03
network

RFC
ãƒªãƒ³ã‚¯
1