IETF Datatracker
Groups By area/parent Apps & Realtime General Internet Ops & Management Routing Security Web and Internet Transport IAB IRTF IETF LLC RFC Editor Other Active AGs Active Areas Active Directorates Active IAB Workshops Active Programs Active RAGs Active Teams New work Chartering groups BOFs BOF Requests Other groups Concluded groups Non-WG lists Documents Search Recent I-Ds I-D submission IESG dashbo
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 2616: Hypertext Transfer Protocol -- HTTP/1.1
Network Working Group R. Fielding Request for Comments: 2616 UC Irvine Obsoletes: 2068 J. Gettys Category: Standards Track Compaq/W3C J. Mogul Compaq H. Frystyk W3C/MIT L. Masinter Xerox P. Leach Microsoft T. Berners-Lee W3C/MIT June 1999 Hypertext Transfer Protocol -- HTTP/1.1 Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests
RFC 8375: Special-Use Domain 'home.arpa.'
Internet Engineering Task Force (IETF) P. Pfister Request for Comments: 8375 Cisco Systems Updates: 7788 T. Lemon Category: Standards Track Nibbhaya Consulting ISSN: 2070-1721 May 2018 Special-Use Domain 'home.arpa.' Abstract This document specifies the behavior that is expected from the Domain Name System with regard to DNS queries for names ending with '.home.arpa.' and designates this domain as
RFC 4791: Calendaring Extensions to WebDAV (CalDAV)
Network Working Group C. Daboo Request for Comments: 4791 Apple Category: Standards Track B. Desruisseaux Oracle L. Dusseault CommerceNet March 2007 Calendaring Extensions to WebDAV (CalDAV) 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
Using Early Data in HTTP
httpbis M. Thomson Internet-Draft Mozilla Intended status: Standards Track M. Nottingham Expires: December 24, 2017 true W. Tarreau HAProxy Technologies June 22, 2017 Using Early Data in HTTP draft-thomson-http-replay-00 Abstract This document explains the risks of using early data for HTTP and describes techniques for reducing them. In particular, it defines a mechanism that enables clients to co
RFC 5545: Internet Calendaring and Scheduling Core Object Specification (iCalendar)
Network Working Group B. Desruisseaux, Ed. Request for Comments: 5545 Oracle Obsoletes: 2445 September 2009 Category: Standards Track Internet Calendaring and Scheduling Core Object Specification (iCalendar) Abstract This document defines the iCalendar data format for representing and exchanging calendaring and scheduling information such as events, to-dos, journal entries, and free/busy informati
RFC 8369: Internationalizing IPv6 Using 128-Bit Unicode
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 H. Kaplan Request for Comments: 8369 128 Technology Category: Informational 1 April 2018 ISSN: 2070-1721 Internationalizing IPv6 Using 128-Bit Unicode Abstract It is clear that Unicode will eventually exhaust its supply o
RFC 8367: Wrongful Termination of Internet Protocol (IP) Packets
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 T. Mizrahi Request for Comments: 8367 Marvell Category: Informational J. Yallouz ISSN: 2070-1721 Intel 1 April 2018 Wrongful Termination of Internet Protocol (IP) Packets Abstract Routers and middleboxes terminate packets
Ballot for draft-ietf-tls-tls13-28
Thank you for a surprisingly (because of the technical density) readable document - I may use this as an example of a well written but dense document... Also, thanks to the doc shepherd for a good write-up. I'm balloting NoObj instead of Yes only because I don't think I have enough background/expertise in the topic. Thanks to the many pages of people who worked on this document. The result is surp
RFC 3875: The Common Gateway Interface (CGI) Version 1.1
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. Network Working Group D. Robinson Request for Comments: 3875 K. Coar Category: Informational The Apache Software Foundation October 2004 The Common Gateway Interface (CGI) Version 1.1 Status of this Memo This memo provides information for the I
RFC 7662: OAuth 2.0 Token Introspection
Internet Engineering Task Force (IETF) J. Richer, Ed. Request for Comments: 7662 October 2015 Category: Standards Track ISSN: 2070-1721 OAuth 2.0 Token Introspection Abstract This specification defines a method for a protected resource to query an OAuth 2.0 authorization server to determine the active state of an OAuth 2.0 token and to determine meta-information about this token. OAuth 2.0 deploym
RFC 8297: An HTTP Status Code for Indicating Hints
Internet Engineering Task Force (IETF) K. Oku Request for Comments: 8297 Fastly Category: Experimental December 2017 ISSN: 2070-1721 An HTTP Status Code for Indicating Hints Abstract This memo introduces an informational HTTP status code that can be used to convey hints that help a client make preparations for processing the final response. Status of This Memo This document is not an Internet Stan
RFC 8314: Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access
Internet Engineering Task Force (IETF) K. Moore Request for Comments: 8314 Windrock, Inc. Updates: 1939, 2595, 3501, 5068, 6186, 6409 C. Newman Category: Standards Track Oracle ISSN: 2070-1721 January 2018 Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access Abstract This specification outlines current recommendations for the use of Transport Layer S
RFC 7664: Dragonfly Key Exchange
Internet Research Task Force (IRTF) D. Harkins, Ed. Request for Comments: 7664 Aruba Networks Category: Informational November 2015 ISSN: 2070-1721 Dragonfly Key Exchange Abstract This document specifies a key exchange using discrete logarithm cryptography that is authenticated using a password or passphrase. It is resistant to active attack, passive attack, and offline dictionary attack. This doc
SRv6 for Mobile User-Plane
SRv6 for Mobile User- Plane draft-matsushima-spring-dmm-srv6-mobile-uplane-03 IETF100 S.Matsushima, C.Filsfils, M.Kohno, D.Voyer Feedbacks after IETF99 • Many people asked: System Impacts? • To current control-plane protocol. • To current RAN. • People really care degree of system impact to change U-plane protocol from current one. • Benefits? • What is able to do with SRv6? • Isn’t that possible
ietf100-cache-digest
Cache Digest (IETF 100) Cache Digests for HTTP/2 Kazuho Oku Cache Digest (IETF 100) • proposes: – SENDING_CACHE_DIGEST SETTINGS Parameter – switch to Cuckoo Filters – thanks to Yoav Weiss for the proposal Pull Request #413 Cache Digest (IETF 100) • a SETTINGS parameter sent by client – “I’m going to send CACHE_DIGEST, so the server should decide what to push after seeing the digest” • client strat
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Web PKI OPS (wpkops)
https://datatracker.ietf.org/meeting/101/materials/slides-101-dnsop-sessa-the-dns-camel-01
https://datatracker.ietf.org/meeting/100/materials/slides-100-tls-sessa-tls13/