jspωiki
Web Blog_blogentry_100818_1

2018-08-10#

Ran Across Today#

Hu: The Missing Element#

When did the acronym PEBKAC become a commonly accepted trope in security? Blaming users for security failures may be a convenient out, but it is also misguided. Identity and access management, at the center of bringing people into the security equation, should be making things better. But all too often we suffer from the same bad habit of thinking technology can solve all problems - if only the users would listen and do as told. But times, and expectations, are changing. Shifting from “users” to “people” requires us to move security away from being a dark art, and transform it into something more approachable, more human.

Humorous RFCs#

  • Internet Toaster
  • RFC 527 — ARPAWOCKY
  • RFC 748 — Telnet randomly-lose option, M. Crispin, 4/1/1978, 2 pp.
  • RFC 968 — Twas the Night Before Start-up, V. Cerf, 12/1/1985, 2 pp.
  • RFC 1097 — Telnet subliminal-message option, B. Miller, 4/1/1989, 3 pp.
  • RFC 1121 — Act One - The Poems, J. Postel, L. Kleinrock, V. Cerf, B. Boehm, D. Waitzman , 9/1/1989, 6 pp.
  • RFC 1149 — A Standard for the Transmission of IP Datagrams on Avian Carriers, D. Waitzman, 4/1/1990, 2 pp.
  • RFC 1216 — Gigabit Network Economics and Paradigm Shifts, P. Kunikos, P. Richard, 3/30/1991, 4 pp.
  • RFC 1217 — Memo from the Consortium for Slow Commotion Research (CSCR), V. Cerf, 4/1/1991, 5 pp.
  • RFC 1300 — Remembrances of Things Past, S. Greenfield, 2/1/1992, 4 pp.
  • RFC 1313 — Today's Programming for KRFC AM 1313, Internet Talk Radio, C. Partridge, 4/1/1992, 3 pp.
  • RFC 1437 — The Extension of MIME Content-Types to a New Medium, N. Borenstein, M. Linimon, 4/1/1993, 6 pp.
  • RFC 1438 — Internet Engineering Task Force Statements Of Boredom (SOBs), L. Chapin, C. Huitema, 4/1/1993, 2 pp.
  • RFC 1605 — SONET to Sonnet Translation, W. Shakespeare, 4/1/1994, 3 pp.
  • RFC 1606 — A Historical Perspective On The Usage Of IP Version 9, J. Onions, 4/1/1994, 4 pp.
  • RFC 1607 — A View from the 21st Century, V. Cerf, 4/1/1994, 13 pp.
  • RFC 1776 — The Address is the Message, S. Crocker, 4/1/1995, 2 pp.
  • RFC 1882 — The 12-Days of Technology Before Christmas, B. Hancock, 12/1/1995, 5 pp.
  • RFC 1924 — A Compact Representation of IPv6 Addresses, R. Elz, 4/1/1996, 6 pp.
  • RFC 1925 — The Twelve Networking Truths, R. Callon, 4/1/1996, 3 pp.
  • RFC 1926 — An Experimental Encapsulation of IP Datagrams on Top of ATM, 4/1/1996, J. Eriksson, 2 pp.
  • RFC 1927 — Suggested Additional MIME Types for Associating Documents, C. Rogers, 4/1/1996, 3 pp.
  • RFC 2100 — The Naming of Hosts, J. Ashworth, 4/1/1997, 3 pp.
  • RFC 2324 — Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0), L. Masinter, 4/1/1998, 10 pp.
  • RFC 2325 — Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2, M. Slavitch, 4/1/1998, 8 pp.
  • RFC 2549 — IP over Avian Carriers with Quality of Service, D. Waitzman, 4/1/1999, 6 pp., updates RFC 1149.
  • RFC 2550 — Y10K and Beyond, S. Glassman, M. Manasse, J. Mogul, 4/1/1999, 14 pp.
  • RFC 2551 — The Roman Standards Process -- Revision III, S. Bradner, 4/1/1999, 37 pp.
  • RFC 2795 — The Infinite Monkey Protocol Suite, S. Christey, 4/1/2000, 20 pp.
  • RFC 3091 - Pi Digit Generation Protocol.
  • RFC 3092 - Etymology of "Foo".
  • RFC 3093 - Firewall Enhancement Protocol (FEP).
  • RFC 3251 - Electricity over IP
  • RFC 3252 - Binary Lexical Octet Ad-hoc Transport
  • RFC 3514 - The Security Flag in the IPv4 Header (Evil Bit)
  • RFC 3751 - Omniscience Protocol Requirements
  • RFC 4041 - Requirements for Morality Sections in Routing Area Drafts
  • RFC 4042 - UTF-9 and UTF-18 Efficient Transformation Formats of Unicode
  • RFC 4824 - The Transmission of IP Datagrams over the Semaphore Flag Signaling System (SFSS)
  • RFC 5241 - Naming Rights in IETF Protocols
  • RFC 5442 - A Generalized Unified Character Code: Western European and CJK Sections
  • RFC 5513 - IANA Considerations for Three Letter Acronyms
  • RFC 5514 - IPv6 over Social Networks
  • RFC 5841 - TCP Option to Denote Packet Mood
  • RFC 5984 - Increasing Throughput in IP Networks with ESP-Based Forwarding: ESPBasedForwarding
  • RFC 6214 _ Adaptation of RFC 1149 for IPv6
  • RFC 6217 - Regional Broadcast Using an Atmospheric Link Layer
  • RFC 6592 - The Null Packet

C. Pignataro, J. Clarke, G. Salgueiro (1 April 2012). Service Undiscovery Using Hide-and-Go-Seek for the Domain Pseudonym System (DPS). IETF. doi:10.17487/RFC6593. RFC 6593. 2013 R. Barnes, S. Kent, E. Rescorla (1 April 2013). Further Key Words for Use in RFCs to Indicate Requirement Levels. IETF. doi:10.17487/RFC6919. RFC 6919. R. Hinden (1 April 2013). Design Considerations for Faster-Than-Light (FTL) Communication. IETF. doi:10.17487/RFC6921. RFC 6921. 2014 I. Nazar (1 April 2014). The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA). IETF. doi:10.17487/RFC7168. RFC 7168. (see Hyper Text Coffee Pot Control Protocol) S. Turner (1 April 2014). The NSA (No Secrecy Afforded) Certificate Extension. IETF. doi:10.17487/RFC7169. RFC 7169. 2015 M. Wilhelm (1 April 2015). Scenic Routing for IPv6. IETF. doi:10.17487/RFC7511. RFC 7511. M. Luckie (1 April 2015). Really Explicit Congestion Notification (RECN). IETF. doi:10.17487/RFC7514. RFC 7514. 2016 An April 1st RFC was not published this year.[2] 2017 M. Danielson, M. Nilsson (1 April 2017). Complex Addressing in IPv6. IETF. doi:10.17487/RFC8135. RFC 8135. B. Carpenter (1 April 2017). Additional Transition Functionality for IPv6. IETF. doi:10.17487/RFC8136. RFC 8136. A. Farrel (1 April 2017). The Arte of ASCII: Or, An True and Accurate Representation of an Menagerie of Thynges Fabulous and Wonderful in Ye Forme of Character. IETF. doi:10.17487/RFC8140. RFC 8140. 2018 T. Mizrahi, J. Yallouz (1 April 2018). Wrongful Termination of Internet Protocol (IP) Packets. IETF. doi:10.17487/RFC8367. RFC 8367. H. Kaplan (1 April 2018). Internationalizing IPv6 Using 128-Bit Unicode. IETF. doi:10.17487/RFC8369. RFC 8369.

More Information#

There might be more information for this subject on one of the following: ...nobody