Slashdot Mirror

← Back to Domains

Domain: faqs.org

Stories and comments across the archive that link to faqs.org.

Comments · 2,078

  1. Re:Makes sense by SEWilco · · Score: 2 · on Hailstorm: Changing Society's Privacy Infrastructure

    The standard for a nonexistent address is "example.com", "example.net", or "example.org". RFC 2606

  2. Private addresses should be hidden. by fwc · · Score: 4 · on Will ISP Use of 10.0.0.0 Addresses Cause Problems?
    RFC1918 addresses can only be used in a few circumstances.

    These can be summarized as follows:

    If packets from the IP address will never reach the public internet without it being re-written (NAT'd) to a public address, then it is ok.

    Some ISP's think that it's ok to use RFC1918 addresses on their internal point-to-point links. It is not. The reason why is that many ISP's filter anything coming from or going to a RFC1918 address because they generally are bogus packets anyways. However, if the RFC1918 addresses are used on internet visible interfaces, this causes things to break.

    A good example of this is MTU path discovery. Basically this works by sending a packet from point a to point b with the don't fragment bit set. If the packet reaches a router which can't handle a packet of that size, the router sends back an ICMP packet which basically tells the "Discovering" machine that it couldn't forward the packet because it was too big for it's MTU setting. If the IP address of the offending router's interface happens to be an RFC1918 address, then you might never see the ICMP back and as such you will have weird problems going on.

    Note: This is also why you shouldn't just filter ICMP packets.

    In the case above, it sounds like the ISP is using the 10.0.0.0 address internally. As they also had the customer using the 10.0.0.0 address range, this could get weird really fast.

  3. Wrong? by CrayDrygu · · Score: 4 · on Will ISP Use of 10.0.0.0 Addresses Cause Problems?
    Which version of the RFC are you looking at? I'm looking at one dated February 1996...

    10.0.0.0/8 -- You got that one right.

    172.16.0.0/12 -- That right, too

    You messed up on the other one, though. It's 192.168.0.0/16. That's right, the full 192.168.0.0 - 192.168.255.255 range is open.

    Ref: RCF1918

    --

  4. Criminal Law=victims with injury by ip4noman · · Score: 1 · on Schwartz Case Upheld on Appeal

    Implict in this case is a troubling concept. But if you follow the mental experiment, it could shake some fundamental principles of how the Western economy works.

    There are 2 main branches of law, Criminal and Civil. The defining characteristic of Criminal law is "victims with injury"; civil law (a/k/a "equity law") deals with contracts.

    Now Randal was an employee of Intel, and all employment arangements are contractual in nature. Please see my page relating to employment drug testing for information about employment contracts: http://www.ip4noman.org/principles.html

    Now what Randal did was perhaps a violation a of professional conduct (certainly), or a breech of his contract w/Intel (although I doubt it), and subject to cancelation of it, or even the pursuit of civil remedies, but this is claimed to be a CRINMINAL case...

    The Lawful Arrest FAQ points out that the objective proof that a crime occured is called "corpus delicti", which requires
    • a victim who has injury, and
    • a criminal cause (as opposed to an accident, or act of god)

    Now this brings up a question: What is the name of the victim? Is it Intel Corportation? Can a corporation be a crime victim? And the nature of the injury? Certainly a person can receive a broken arm, or loss of life, but how exactly can a corporation be injured?

    You see, corporations are defined under the law as an "Artifical Person" for these reasons:
    • "persons" can own property,
    • "persons" have rights,
    • "persons" can engage in contracts,
    • "persons" can sue and be sued, and presumably
    • "persons" can be injured, "persons" can be crime victims

    I personally question the notion that these "artifical persons", or "corpses" as Dave Ratcliffe calls them, these human constructions which own most of the property in America, which have more political clout than any natural person, which have more financial resources than any of us, I question whether these soulless abstractions without a moral consciousness can be considered an honorable creature (honor is requirement to being a party to a contract). I question what it means for a corporation to own land or TV stations, and wonder where the present system will take us. I especially question the notion that corporations can be injured, or can be crime victims.

    The case of Randal Schwartz is extremely important, and is related to many cases of late (mafiaboy, Emmanual Goldstein/2600, Kevin Mitnick, Oprah Winfrey's free-speech case against the cattle industry, etc.) ... all against alleged "corporate crime victims".

    If we don't protest this, soon we all will/could be accuesd of some non-crimes like "uttering a trademarked expression without paying propery royalty, and in a disparaging fashion leading to loss of the profit that a corporation rightly deserves" or some such foolishness...

    We live in interesting times, this year of our lord, nineteen hundred eighty four...

    Implict in this case is a troubling concept. But if you follow the mental experiment, it could shake some fundamental principles of how the Western economy works.

    There are 2 main branches of law, Criminal and Civil. The defining characteristic of Criminal law is "victims with injury"; civil law (a/k/a "equity law") deals with contracts.

    Now Randal was an employee of Intel, and all employment arangements are contractual in nature. Please see my FAQ relating to employment drug testing for information about contracts: http://www.ip4noman.org/principles.html

    Now what Randal did was perhaps a violation a of professional conduct (certainly), or a breech of his contract w/Intel (although I doubt it), and subject to cancelation of it even the pursuit of civil remedies, but this is claimed to be a CRINMINAL case...

    The Lawful Arrest FAQ points out that the objective proof that a crime occured is called "corpus delicti", which requires
    • a victim who has injury, and
    • a criminal cause (as opposed to an accident

    Now this brings up a question: What is the name of the victim? Is it Intel Corportation? Can a corporation be a crime victim? And the nature of the injury? Certainly a person can receive a broken arm, or loss of life, but how exactly can a corporation be injured?

    You see, corporations are defined under the law as an "Artifical Person" for these reasons:
    • "persons" can own property,
    • "persons" have rights,
    • "persons" can engage in contracts,
    • "persons" can sue and be sued, and presumably
    • "persons" can be injured, "persons" can be crime victims

    I personally question the notion that these "artifical persons", or "corpses" as Dave Ratcliffe calls them, these human constructions which own most of the property in America, which have more political clout than any natural person, which have more financial resources than any of us, I question whether these soulless abstractions without a moral consciousness can be considered an honorable creature (honor is requirement to being a party to a contract). I question what it means for a corporation to own land or TV stations, and wonder where the present system will take us. I especially question the notion that corporations can be injured, or can be crime victims.

    The case of Randal Schwartz is extremely important, and is related to many cases of late (mafiaboy, Emmanual Goldstein/2600, Kevin Mitnick, Oprah Winfrey's free-speech case against the cattle industry, etc. ... all against alleged "corporate crime victims".

    If we don't protest this, soon we all will/could be accuesd of some non-crimes like "uttering a trademarked expression without paying propery royalty, and in a disparaging fashion leading to loss of the profit that a corporation rightly deserves" or some such foolishness...

    We live in interesting times, this year of our lord, nineteen hundred eighty four...

  5. Criminal Law=victims with injury by ip4noman · · Score: 1 · on Schwartz Case Upheld on Appeal

    Implict in this case is a troubling concept. But if you follow the mental experiment, it could shake some fundamental principles of how the Western economy works.

    There are 2 main branches of law, Criminal and Civil. The defining characteristic of Criminal law is "victims with injury"; civil law (a/k/a "equity law") deals with contracts.

    Now Randal was an employee of Intel, and all employment arangements are contractual in nature. Please see my page relating to employment drug testing for information about employment contracts: http://www.ip4noman.org/principles.html

    Now what Randal did was perhaps a violation a of professional conduct (certainly), or a breech of his contract w/Intel (although I doubt it), and subject to cancelation of it, or even the pursuit of civil remedies, but this is claimed to be a CRINMINAL case...

    The Lawful Arrest FAQ points out that the objective proof that a crime occured is called "corpus delicti", which requires
    • a victim who has injury, and
    • a criminal cause (as opposed to an accident, or act of god)

    Now this brings up a question: What is the name of the victim? Is it Intel Corportation? Can a corporation be a crime victim? And the nature of the injury? Certainly a person can receive a broken arm, or loss of life, but how exactly can a corporation be injured?

    You see, corporations are defined under the law as an "Artifical Person" for these reasons:
    • "persons" can own property,
    • "persons" have rights,
    • "persons" can engage in contracts,
    • "persons" can sue and be sued, and presumably
    • "persons" can be injured, "persons" can be crime victims

    I personally question the notion that these "artifical persons", or "corpses" as Dave Ratcliffe calls them, these human constructions which own most of the property in America, which have more political clout than any natural person, which have more financial resources than any of us, I question whether these soulless abstractions without a moral consciousness can be considered an honorable creature (honor is requirement to being a party to a contract). I question what it means for a corporation to own land or TV stations, and wonder where the present system will take us. I especially question the notion that corporations can be injured, or can be crime victims.

    The case of Randal Schwartz is extremely important, and is related to many cases of late (mafiaboy, Emmanual Goldstein/2600, Kevin Mitnick, Oprah Winfrey's free-speech case against the cattle industry, etc.) ... all against alleged "corporate crime victims".

    If we don't protest this, soon we all will/could be accuesd of some non-crimes like "uttering a trademarked expression without paying propery royalty, and in a disparaging fashion leading to loss of the profit that a corporation rightly deserves" or some such foolishness...

    We live in interesting times, this year of our lord, nineteen hundred eighty four...

    Implict in this case is a troubling concept. But if you follow the mental experiment, it could shake some fundamental principles of how the Western economy works.

    There are 2 main branches of law, Criminal and Civil. The defining characteristic of Criminal law is "victims with injury"; civil law (a/k/a "equity law") deals with contracts.

    Now Randal was an employee of Intel, and all employment arangements are contractual in nature. Please see my FAQ relating to employment drug testing for information about contracts: http://www.ip4noman.org/principles.html

    Now what Randal did was perhaps a violation a of professional conduct (certainly), or a breech of his contract w/Intel (although I doubt it), and subject to cancelation of it even the pursuit of civil remedies, but this is claimed to be a CRINMINAL case...

    The Lawful Arrest FAQ points out that the objective proof that a crime occured is called "corpus delicti", which requires
    • a victim who has injury, and
    • a criminal cause (as opposed to an accident

    Now this brings up a question: What is the name of the victim? Is it Intel Corportation? Can a corporation be a crime victim? And the nature of the injury? Certainly a person can receive a broken arm, or loss of life, but how exactly can a corporation be injured?

    You see, corporations are defined under the law as an "Artifical Person" for these reasons:
    • "persons" can own property,
    • "persons" have rights,
    • "persons" can engage in contracts,
    • "persons" can sue and be sued, and presumably
    • "persons" can be injured, "persons" can be crime victims

    I personally question the notion that these "artifical persons", or "corpses" as Dave Ratcliffe calls them, these human constructions which own most of the property in America, which have more political clout than any natural person, which have more financial resources than any of us, I question whether these soulless abstractions without a moral consciousness can be considered an honorable creature (honor is requirement to being a party to a contract). I question what it means for a corporation to own land or TV stations, and wonder where the present system will take us. I especially question the notion that corporations can be injured, or can be crime victims.

    The case of Randal Schwartz is extremely important, and is related to many cases of late (mafiaboy, Emmanual Goldstein/2600, Kevin Mitnick, Oprah Winfrey's free-speech case against the cattle industry, etc. ... all against alleged "corporate crime victims".

    If we don't protest this, soon we all will/could be accuesd of some non-crimes like "uttering a trademarked expression without paying propery royalty, and in a disparaging fashion leading to loss of the profit that a corporation rightly deserves" or some such foolishness...

    We live in interesting times, this year of our lord, nineteen hundred eighty four...

  6. Re:enough with the april fools humor! by Brian+Feldman · · Score: 1 · on Slashdot Moving To FreeBSD
    Huh? Did you not see RFC 3092, Etymology of "Foo"? It was posted a few days earlier, but it's still dated properly =)

    --

  7. Re:A lot more, actually :) by demo · · Score: 2 · on TCP/IP Over HTTP

    Hmm.. Seems I forgot

    RFC748 - Telnet randomly-lose option.

    *sigh*

  8. A lot more, actually :) by demo · · Score: 5 · on TCP/IP Over HTTP
    Just to sum up most of the April Fools RFCs over the years...
    • RFC3093 - Firewall Enhancement Protocol (FEP).
    • RFC3092 - Etymology of "Foo".
    • RFC3091 - Pi Digit Generation Protocol.
    • RFC2795 - The Infinite Monkey Protocol Suite (IMPS).
    • RFC2551 - The Roman Standards Process -- Revision III.
    • RFC2550 - Y10K and Beyond.
    • RFC2549 - IP over Avian Carriers with Quality of Service.
    • RFC2325 - Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2
    • RFC2324 - Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0).
    • RFC2323 - IETF Identification and Security Guidelines.
    • RFC2322 - Management of IP numbers by peg-dhcp.
    • RFC2321 - RITA -- The Reliable Internetwork Troubleshooting Agent.
    • RFC2100 - The Naming of Hosts.
    • RFC1927 - Suggested Additional MIME Types for Associating Documents.
    • RFC1926 - An Experimental Encapsulation of IP Datagrams on Top of ATM.
    • RFC1925 - The Twelve Networking Truths.
    • RFC1924 - A Compact Representation of IPv6 Addresses.
    • RFC1776 - The Address is the Message. S. Crocker.
    • RFC1607 - A VIEW FROM THE 21ST CENTURY. V. Cerf.
    • RFC1606 - A Historical Perspective On The Usage Of IP Version 9.
    • RFC1605 - SONET to Sonnet Translation.
    • RFC1438 - Internet Engineering Task Force Statements Of Boredom (SOBs).
    • RFC1437 - The Extension of MIME Content-Types to a New Medium.
    • RFC1313 - Today's Programming for KRFC AM 1313 Internet Talk Radio.
    • RFC1217 - Memo from the Consortium for Slow Commotion Research (CSCR).
    • RFC1216 - Gigabit network economics and paradigm shifts.
    • RFC1149 - Standard for the transmission of IP datagrams on avian carriers.
    • RFC1097 - Telnet subliminal-message option.
    Did I miss any?
  9. A lot more, actually :) by demo · · Score: 5 · on TCP/IP Over HTTP
    Just to sum up most of the April Fools RFCs over the years...
    • RFC3093 - Firewall Enhancement Protocol (FEP).
    • RFC3092 - Etymology of "Foo".
    • RFC3091 - Pi Digit Generation Protocol.
    • RFC2795 - The Infinite Monkey Protocol Suite (IMPS).
    • RFC2551 - The Roman Standards Process -- Revision III.
    • RFC2550 - Y10K and Beyond.
    • RFC2549 - IP over Avian Carriers with Quality of Service.
    • RFC2325 - Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2
    • RFC2324 - Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0).
    • RFC2323 - IETF Identification and Security Guidelines.
    • RFC2322 - Management of IP numbers by peg-dhcp.
    • RFC2321 - RITA -- The Reliable Internetwork Troubleshooting Agent.
    • RFC2100 - The Naming of Hosts.
    • RFC1927 - Suggested Additional MIME Types for Associating Documents.
    • RFC1926 - An Experimental Encapsulation of IP Datagrams on Top of ATM.
    • RFC1925 - The Twelve Networking Truths.
    • RFC1924 - A Compact Representation of IPv6 Addresses.
    • RFC1776 - The Address is the Message. S. Crocker.
    • RFC1607 - A VIEW FROM THE 21ST CENTURY. V. Cerf.
    • RFC1606 - A Historical Perspective On The Usage Of IP Version 9.
    • RFC1605 - SONET to Sonnet Translation.
    • RFC1438 - Internet Engineering Task Force Statements Of Boredom (SOBs).
    • RFC1437 - The Extension of MIME Content-Types to a New Medium.
    • RFC1313 - Today's Programming for KRFC AM 1313 Internet Talk Radio.
    • RFC1217 - Memo from the Consortium for Slow Commotion Research (CSCR).
    • RFC1216 - Gigabit network economics and paradigm shifts.
    • RFC1149 - Standard for the transmission of IP datagrams on avian carriers.
    • RFC1097 - Telnet subliminal-message option.
    Did I miss any?
  10. A lot more, actually :) by demo · · Score: 5 · on TCP/IP Over HTTP
    Just to sum up most of the April Fools RFCs over the years...
    • RFC3093 - Firewall Enhancement Protocol (FEP).
    • RFC3092 - Etymology of "Foo".
    • RFC3091 - Pi Digit Generation Protocol.
    • RFC2795 - The Infinite Monkey Protocol Suite (IMPS).
    • RFC2551 - The Roman Standards Process -- Revision III.
    • RFC2550 - Y10K and Beyond.
    • RFC2549 - IP over Avian Carriers with Quality of Service.
    • RFC2325 - Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2
    • RFC2324 - Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0).
    • RFC2323 - IETF Identification and Security Guidelines.
    • RFC2322 - Management of IP numbers by peg-dhcp.
    • RFC2321 - RITA -- The Reliable Internetwork Troubleshooting Agent.
    • RFC2100 - The Naming of Hosts.
    • RFC1927 - Suggested Additional MIME Types for Associating Documents.
    • RFC1926 - An Experimental Encapsulation of IP Datagrams on Top of ATM.
    • RFC1925 - The Twelve Networking Truths.
    • RFC1924 - A Compact Representation of IPv6 Addresses.
    • RFC1776 - The Address is the Message. S. Crocker.
    • RFC1607 - A VIEW FROM THE 21ST CENTURY. V. Cerf.
    • RFC1606 - A Historical Perspective On The Usage Of IP Version 9.
    • RFC1605 - SONET to Sonnet Translation.
    • RFC1438 - Internet Engineering Task Force Statements Of Boredom (SOBs).
    • RFC1437 - The Extension of MIME Content-Types to a New Medium.
    • RFC1313 - Today's Programming for KRFC AM 1313 Internet Talk Radio.
    • RFC1217 - Memo from the Consortium for Slow Commotion Research (CSCR).
    • RFC1216 - Gigabit network economics and paradigm shifts.
    • RFC1149 - Standard for the transmission of IP datagrams on avian carriers.
    • RFC1097 - Telnet subliminal-message option.
    Did I miss any?
  11. A lot more, actually :) by demo · · Score: 5 · on TCP/IP Over HTTP
    Just to sum up most of the April Fools RFCs over the years...
    • RFC3093 - Firewall Enhancement Protocol (FEP).
    • RFC3092 - Etymology of "Foo".
    • RFC3091 - Pi Digit Generation Protocol.
    • RFC2795 - The Infinite Monkey Protocol Suite (IMPS).
    • RFC2551 - The Roman Standards Process -- Revision III.
    • RFC2550 - Y10K and Beyond.
    • RFC2549 - IP over Avian Carriers with Quality of Service.
    • RFC2325 - Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2
    • RFC2324 - Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0).
    • RFC2323 - IETF Identification and Security Guidelines.
    • RFC2322 - Management of IP numbers by peg-dhcp.
    • RFC2321 - RITA -- The Reliable Internetwork Troubleshooting Agent.
    • RFC2100 - The Naming of Hosts.
    • RFC1927 - Suggested Additional MIME Types for Associating Documents.
    • RFC1926 - An Experimental Encapsulation of IP Datagrams on Top of ATM.
    • RFC1925 - The Twelve Networking Truths.
    • RFC1924 - A Compact Representation of IPv6 Addresses.
    • RFC1776 - The Address is the Message. S. Crocker.
    • RFC1607 - A VIEW FROM THE 21ST CENTURY. V. Cerf.
    • RFC1606 - A Historical Perspective On The Usage Of IP Version 9.
    • RFC1605 - SONET to Sonnet Translation.
    • RFC1438 - Internet Engineering Task Force Statements Of Boredom (SOBs).
    • RFC1437 - The Extension of MIME Content-Types to a New Medium.
    • RFC1313 - Today's Programming for KRFC AM 1313 Internet Talk Radio.
    • RFC1217 - Memo from the Consortium for Slow Commotion Research (CSCR).
    • RFC1216 - Gigabit network economics and paradigm shifts.
    • RFC1149 - Standard for the transmission of IP datagrams on avian carriers.
    • RFC1097 - Telnet subliminal-message option.
    Did I miss any?
  12. A lot more, actually :) by demo · · Score: 5 · on TCP/IP Over HTTP
    Just to sum up most of the April Fools RFCs over the years...
    • RFC3093 - Firewall Enhancement Protocol (FEP).
    • RFC3092 - Etymology of "Foo".
    • RFC3091 - Pi Digit Generation Protocol.
    • RFC2795 - The Infinite Monkey Protocol Suite (IMPS).
    • RFC2551 - The Roman Standards Process -- Revision III.
    • RFC2550 - Y10K and Beyond.
    • RFC2549 - IP over Avian Carriers with Quality of Service.
    • RFC2325 - Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2
    • RFC2324 - Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0).
    • RFC2323 - IETF Identification and Security Guidelines.
    • RFC2322 - Management of IP numbers by peg-dhcp.
    • RFC2321 - RITA -- The Reliable Internetwork Troubleshooting Agent.
    • RFC2100 - The Naming of Hosts.
    • RFC1927 - Suggested Additional MIME Types for Associating Documents.
    • RFC1926 - An Experimental Encapsulation of IP Datagrams on Top of ATM.
    • RFC1925 - The Twelve Networking Truths.
    • RFC1924 - A Compact Representation of IPv6 Addresses.
    • RFC1776 - The Address is the Message. S. Crocker.
    • RFC1607 - A VIEW FROM THE 21ST CENTURY. V. Cerf.
    • RFC1606 - A Historical Perspective On The Usage Of IP Version 9.
    • RFC1605 - SONET to Sonnet Translation.
    • RFC1438 - Internet Engineering Task Force Statements Of Boredom (SOBs).
    • RFC1437 - The Extension of MIME Content-Types to a New Medium.
    • RFC1313 - Today's Programming for KRFC AM 1313 Internet Talk Radio.
    • RFC1217 - Memo from the Consortium for Slow Commotion Research (CSCR).
    • RFC1216 - Gigabit network economics and paradigm shifts.
    • RFC1149 - Standard for the transmission of IP datagrams on avian carriers.
    • RFC1097 - Telnet subliminal-message option.
    Did I miss any?
  13. A lot more, actually :) by demo · · Score: 5 · on TCP/IP Over HTTP
    Just to sum up most of the April Fools RFCs over the years...
    • RFC3093 - Firewall Enhancement Protocol (FEP).
    • RFC3092 - Etymology of "Foo".
    • RFC3091 - Pi Digit Generation Protocol.
    • RFC2795 - The Infinite Monkey Protocol Suite (IMPS).
    • RFC2551 - The Roman Standards Process -- Revision III.
    • RFC2550 - Y10K and Beyond.
    • RFC2549 - IP over Avian Carriers with Quality of Service.
    • RFC2325 - Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2
    • RFC2324 - Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0).
    • RFC2323 - IETF Identification and Security Guidelines.
    • RFC2322 - Management of IP numbers by peg-dhcp.
    • RFC2321 - RITA -- The Reliable Internetwork Troubleshooting Agent.
    • RFC2100 - The Naming of Hosts.
    • RFC1927 - Suggested Additional MIME Types for Associating Documents.
    • RFC1926 - An Experimental Encapsulation of IP Datagrams on Top of ATM.
    • RFC1925 - The Twelve Networking Truths.
    • RFC1924 - A Compact Representation of IPv6 Addresses.
    • RFC1776 - The Address is the Message. S. Crocker.
    • RFC1607 - A VIEW FROM THE 21ST CENTURY. V. Cerf.
    • RFC1606 - A Historical Perspective On The Usage Of IP Version 9.
    • RFC1605 - SONET to Sonnet Translation.
    • RFC1438 - Internet Engineering Task Force Statements Of Boredom (SOBs).
    • RFC1437 - The Extension of MIME Content-Types to a New Medium.
    • RFC1313 - Today's Programming for KRFC AM 1313 Internet Talk Radio.
    • RFC1217 - Memo from the Consortium for Slow Commotion Research (CSCR).
    • RFC1216 - Gigabit network economics and paradigm shifts.
    • RFC1149 - Standard for the transmission of IP datagrams on avian carriers.
    • RFC1097 - Telnet subliminal-message option.
    Did I miss any?
  14. A lot more, actually :) by demo · · Score: 5 · on TCP/IP Over HTTP
    Just to sum up most of the April Fools RFCs over the years...
    • RFC3093 - Firewall Enhancement Protocol (FEP).
    • RFC3092 - Etymology of "Foo".
    • RFC3091 - Pi Digit Generation Protocol.
    • RFC2795 - The Infinite Monkey Protocol Suite (IMPS).
    • RFC2551 - The Roman Standards Process -- Revision III.
    • RFC2550 - Y10K and Beyond.
    • RFC2549 - IP over Avian Carriers with Quality of Service.
    • RFC2325 - Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2
    • RFC2324 - Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0).
    • RFC2323 - IETF Identification and Security Guidelines.
    • RFC2322 - Management of IP numbers by peg-dhcp.
    • RFC2321 - RITA -- The Reliable Internetwork Troubleshooting Agent.
    • RFC2100 - The Naming of Hosts.
    • RFC1927 - Suggested Additional MIME Types for Associating Documents.
    • RFC1926 - An Experimental Encapsulation of IP Datagrams on Top of ATM.
    • RFC1925 - The Twelve Networking Truths.
    • RFC1924 - A Compact Representation of IPv6 Addresses.
    • RFC1776 - The Address is the Message. S. Crocker.
    • RFC1607 - A VIEW FROM THE 21ST CENTURY. V. Cerf.
    • RFC1606 - A Historical Perspective On The Usage Of IP Version 9.
    • RFC1605 - SONET to Sonnet Translation.
    • RFC1438 - Internet Engineering Task Force Statements Of Boredom (SOBs).
    • RFC1437 - The Extension of MIME Content-Types to a New Medium.
    • RFC1313 - Today's Programming for KRFC AM 1313 Internet Talk Radio.
    • RFC1217 - Memo from the Consortium for Slow Commotion Research (CSCR).
    • RFC1216 - Gigabit network economics and paradigm shifts.
    • RFC1149 - Standard for the transmission of IP datagrams on avian carriers.
    • RFC1097 - Telnet subliminal-message option.
    Did I miss any?
  15. A lot more, actually :) by demo · · Score: 5 · on TCP/IP Over HTTP
    Just to sum up most of the April Fools RFCs over the years...
    • RFC3093 - Firewall Enhancement Protocol (FEP).
    • RFC3092 - Etymology of "Foo".
    • RFC3091 - Pi Digit Generation Protocol.
    • RFC2795 - The Infinite Monkey Protocol Suite (IMPS).
    • RFC2551 - The Roman Standards Process -- Revision III.
    • RFC2550 - Y10K and Beyond.
    • RFC2549 - IP over Avian Carriers with Quality of Service.
    • RFC2325 - Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2
    • RFC2324 - Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0).
    • RFC2323 - IETF Identification and Security Guidelines.
    • RFC2322 - Management of IP numbers by peg-dhcp.
    • RFC2321 - RITA -- The Reliable Internetwork Troubleshooting Agent.
    • RFC2100 - The Naming of Hosts.
    • RFC1927 - Suggested Additional MIME Types for Associating Documents.
    • RFC1926 - An Experimental Encapsulation of IP Datagrams on Top of ATM.
    • RFC1925 - The Twelve Networking Truths.
    • RFC1924 - A Compact Representation of IPv6 Addresses.
    • RFC1776 - The Address is the Message. S. Crocker.
    • RFC1607 - A VIEW FROM THE 21ST CENTURY. V. Cerf.
    • RFC1606 - A Historical Perspective On The Usage Of IP Version 9.
    • RFC1605 - SONET to Sonnet Translation.
    • RFC1438 - Internet Engineering Task Force Statements Of Boredom (SOBs).
    • RFC1437 - The Extension of MIME Content-Types to a New Medium.
    • RFC1313 - Today's Programming for KRFC AM 1313 Internet Talk Radio.
    • RFC1217 - Memo from the Consortium for Slow Commotion Research (CSCR).
    • RFC1216 - Gigabit network economics and paradigm shifts.
    • RFC1149 - Standard for the transmission of IP datagrams on avian carriers.
    • RFC1097 - Telnet subliminal-message option.
    Did I miss any?
  16. A lot more, actually :) by demo · · Score: 5 · on TCP/IP Over HTTP
    Just to sum up most of the April Fools RFCs over the years...
    • RFC3093 - Firewall Enhancement Protocol (FEP).
    • RFC3092 - Etymology of "Foo".
    • RFC3091 - Pi Digit Generation Protocol.
    • RFC2795 - The Infinite Monkey Protocol Suite (IMPS).
    • RFC2551 - The Roman Standards Process -- Revision III.
    • RFC2550 - Y10K and Beyond.
    • RFC2549 - IP over Avian Carriers with Quality of Service.
    • RFC2325 - Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2
    • RFC2324 - Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0).
    • RFC2323 - IETF Identification and Security Guidelines.
    • RFC2322 - Management of IP numbers by peg-dhcp.
    • RFC2321 - RITA -- The Reliable Internetwork Troubleshooting Agent.
    • RFC2100 - The Naming of Hosts.
    • RFC1927 - Suggested Additional MIME Types for Associating Documents.
    • RFC1926 - An Experimental Encapsulation of IP Datagrams on Top of ATM.
    • RFC1925 - The Twelve Networking Truths.
    • RFC1924 - A Compact Representation of IPv6 Addresses.
    • RFC1776 - The Address is the Message. S. Crocker.
    • RFC1607 - A VIEW FROM THE 21ST CENTURY. V. Cerf.
    • RFC1606 - A Historical Perspective On The Usage Of IP Version 9.
    • RFC1605 - SONET to Sonnet Translation.
    • RFC1438 - Internet Engineering Task Force Statements Of Boredom (SOBs).
    • RFC1437 - The Extension of MIME Content-Types to a New Medium.
    • RFC1313 - Today's Programming for KRFC AM 1313 Internet Talk Radio.
    • RFC1217 - Memo from the Consortium for Slow Commotion Research (CSCR).
    • RFC1216 - Gigabit network economics and paradigm shifts.
    • RFC1149 - Standard for the transmission of IP datagrams on avian carriers.
    • RFC1097 - Telnet subliminal-message option.
    Did I miss any?
  17. A lot more, actually :) by demo · · Score: 5 · on TCP/IP Over HTTP
    Just to sum up most of the April Fools RFCs over the years...
    • RFC3093 - Firewall Enhancement Protocol (FEP).
    • RFC3092 - Etymology of "Foo".
    • RFC3091 - Pi Digit Generation Protocol.
    • RFC2795 - The Infinite Monkey Protocol Suite (IMPS).
    • RFC2551 - The Roman Standards Process -- Revision III.
    • RFC2550 - Y10K and Beyond.
    • RFC2549 - IP over Avian Carriers with Quality of Service.
    • RFC2325 - Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2
    • RFC2324 - Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0).
    • RFC2323 - IETF Identification and Security Guidelines.
    • RFC2322 - Management of IP numbers by peg-dhcp.
    • RFC2321 - RITA -- The Reliable Internetwork Troubleshooting Agent.
    • RFC2100 - The Naming of Hosts.
    • RFC1927 - Suggested Additional MIME Types for Associating Documents.
    • RFC1926 - An Experimental Encapsulation of IP Datagrams on Top of ATM.
    • RFC1925 - The Twelve Networking Truths.
    • RFC1924 - A Compact Representation of IPv6 Addresses.
    • RFC1776 - The Address is the Message. S. Crocker.
    • RFC1607 - A VIEW FROM THE 21ST CENTURY. V. Cerf.
    • RFC1606 - A Historical Perspective On The Usage Of IP Version 9.
    • RFC1605 - SONET to Sonnet Translation.
    • RFC1438 - Internet Engineering Task Force Statements Of Boredom (SOBs).
    • RFC1437 - The Extension of MIME Content-Types to a New Medium.
    • RFC1313 - Today's Programming for KRFC AM 1313 Internet Talk Radio.
    • RFC1217 - Memo from the Consortium for Slow Commotion Research (CSCR).
    • RFC1216 - Gigabit network economics and paradigm shifts.
    • RFC1149 - Standard for the transmission of IP datagrams on avian carriers.
    • RFC1097 - Telnet subliminal-message option.
    Did I miss any?
  18. A lot more, actually :) by demo · · Score: 5 · on TCP/IP Over HTTP
    Just to sum up most of the April Fools RFCs over the years...
    • RFC3093 - Firewall Enhancement Protocol (FEP).
    • RFC3092 - Etymology of "Foo".
    • RFC3091 - Pi Digit Generation Protocol.
    • RFC2795 - The Infinite Monkey Protocol Suite (IMPS).
    • RFC2551 - The Roman Standards Process -- Revision III.
    • RFC2550 - Y10K and Beyond.
    • RFC2549 - IP over Avian Carriers with Quality of Service.
    • RFC2325 - Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2
    • RFC2324 - Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0).
    • RFC2323 - IETF Identification and Security Guidelines.
    • RFC2322 - Management of IP numbers by peg-dhcp.
    • RFC2321 - RITA -- The Reliable Internetwork Troubleshooting Agent.
    • RFC2100 - The Naming of Hosts.
    • RFC1927 - Suggested Additional MIME Types for Associating Documents.
    • RFC1926 - An Experimental Encapsulation of IP Datagrams on Top of ATM.
    • RFC1925 - The Twelve Networking Truths.
    • RFC1924 - A Compact Representation of IPv6 Addresses.
    • RFC1776 - The Address is the Message. S. Crocker.
    • RFC1607 - A VIEW FROM THE 21ST CENTURY. V. Cerf.
    • RFC1606 - A Historical Perspective On The Usage Of IP Version 9.
    • RFC1605 - SONET to Sonnet Translation.
    • RFC1438 - Internet Engineering Task Force Statements Of Boredom (SOBs).
    • RFC1437 - The Extension of MIME Content-Types to a New Medium.
    • RFC1313 - Today's Programming for KRFC AM 1313 Internet Talk Radio.
    • RFC1217 - Memo from the Consortium for Slow Commotion Research (CSCR).
    • RFC1216 - Gigabit network economics and paradigm shifts.
    • RFC1149 - Standard for the transmission of IP datagrams on avian carriers.
    • RFC1097 - Telnet subliminal-message option.
    Did I miss any?
  19. A lot more, actually :) by demo · · Score: 5 · on TCP/IP Over HTTP
    Just to sum up most of the April Fools RFCs over the years...
    • RFC3093 - Firewall Enhancement Protocol (FEP).
    • RFC3092 - Etymology of "Foo".
    • RFC3091 - Pi Digit Generation Protocol.
    • RFC2795 - The Infinite Monkey Protocol Suite (IMPS).
    • RFC2551 - The Roman Standards Process -- Revision III.
    • RFC2550 - Y10K and Beyond.
    • RFC2549 - IP over Avian Carriers with Quality of Service.
    • RFC2325 - Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2
    • RFC2324 - Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0).
    • RFC2323 - IETF Identification and Security Guidelines.
    • RFC2322 - Management of IP numbers by peg-dhcp.
    • RFC2321 - RITA -- The Reliable Internetwork Troubleshooting Agent.
    • RFC2100 - The Naming of Hosts.
    • RFC1927 - Suggested Additional MIME Types for Associating Documents.
    • RFC1926 - An Experimental Encapsulation of IP Datagrams on Top of ATM.
    • RFC1925 - The Twelve Networking Truths.
    • RFC1924 - A Compact Representation of IPv6 Addresses.
    • RFC1776 - The Address is the Message. S. Crocker.
    • RFC1607 - A VIEW FROM THE 21ST CENTURY. V. Cerf.
    • RFC1606 - A Historical Perspective On The Usage Of IP Version 9.
    • RFC1605 - SONET to Sonnet Translation.
    • RFC1438 - Internet Engineering Task Force Statements Of Boredom (SOBs).
    • RFC1437 - The Extension of MIME Content-Types to a New Medium.
    • RFC1313 - Today's Programming for KRFC AM 1313 Internet Talk Radio.
    • RFC1217 - Memo from the Consortium for Slow Commotion Research (CSCR).
    • RFC1216 - Gigabit network economics and paradigm shifts.
    • RFC1149 - Standard for the transmission of IP datagrams on avian carriers.
    • RFC1097 - Telnet subliminal-message option.
    Did I miss any?
  20. A lot more, actually :) by demo · · Score: 5 · on TCP/IP Over HTTP
    Just to sum up most of the April Fools RFCs over the years...
    • RFC3093 - Firewall Enhancement Protocol (FEP).
    • RFC3092 - Etymology of "Foo".
    • RFC3091 - Pi Digit Generation Protocol.
    • RFC2795 - The Infinite Monkey Protocol Suite (IMPS).
    • RFC2551 - The Roman Standards Process -- Revision III.
    • RFC2550 - Y10K and Beyond.
    • RFC2549 - IP over Avian Carriers with Quality of Service.
    • RFC2325 - Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2
    • RFC2324 - Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0).
    • RFC2323 - IETF Identification and Security Guidelines.
    • RFC2322 - Management of IP numbers by peg-dhcp.
    • RFC2321 - RITA -- The Reliable Internetwork Troubleshooting Agent.
    • RFC2100 - The Naming of Hosts.
    • RFC1927 - Suggested Additional MIME Types for Associating Documents.
    • RFC1926 - An Experimental Encapsulation of IP Datagrams on Top of ATM.
    • RFC1925 - The Twelve Networking Truths.
    • RFC1924 - A Compact Representation of IPv6 Addresses.
    • RFC1776 - The Address is the Message. S. Crocker.
    • RFC1607 - A VIEW FROM THE 21ST CENTURY. V. Cerf.
    • RFC1606 - A Historical Perspective On The Usage Of IP Version 9.
    • RFC1605 - SONET to Sonnet Translation.
    • RFC1438 - Internet Engineering Task Force Statements Of Boredom (SOBs).
    • RFC1437 - The Extension of MIME Content-Types to a New Medium.
    • RFC1313 - Today's Programming for KRFC AM 1313 Internet Talk Radio.
    • RFC1217 - Memo from the Consortium for Slow Commotion Research (CSCR).
    • RFC1216 - Gigabit network economics and paradigm shifts.
    • RFC1149 - Standard for the transmission of IP datagrams on avian carriers.
    • RFC1097 - Telnet subliminal-message option.
    Did I miss any?
  21. A lot more, actually :) by demo · · Score: 5 · on TCP/IP Over HTTP
    Just to sum up most of the April Fools RFCs over the years...
    • RFC3093 - Firewall Enhancement Protocol (FEP).
    • RFC3092 - Etymology of "Foo".
    • RFC3091 - Pi Digit Generation Protocol.
    • RFC2795 - The Infinite Monkey Protocol Suite (IMPS).
    • RFC2551 - The Roman Standards Process -- Revision III.
    • RFC2550 - Y10K and Beyond.
    • RFC2549 - IP over Avian Carriers with Quality of Service.
    • RFC2325 - Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2
    • RFC2324 - Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0).
    • RFC2323 - IETF Identification and Security Guidelines.
    • RFC2322 - Management of IP numbers by peg-dhcp.
    • RFC2321 - RITA -- The Reliable Internetwork Troubleshooting Agent.
    • RFC2100 - The Naming of Hosts.
    • RFC1927 - Suggested Additional MIME Types for Associating Documents.
    • RFC1926 - An Experimental Encapsulation of IP Datagrams on Top of ATM.
    • RFC1925 - The Twelve Networking Truths.
    • RFC1924 - A Compact Representation of IPv6 Addresses.
    • RFC1776 - The Address is the Message. S. Crocker.
    • RFC1607 - A VIEW FROM THE 21ST CENTURY. V. Cerf.
    • RFC1606 - A Historical Perspective On The Usage Of IP Version 9.
    • RFC1605 - SONET to Sonnet Translation.
    • RFC1438 - Internet Engineering Task Force Statements Of Boredom (SOBs).
    • RFC1437 - The Extension of MIME Content-Types to a New Medium.
    • RFC1313 - Today's Programming for KRFC AM 1313 Internet Talk Radio.
    • RFC1217 - Memo from the Consortium for Slow Commotion Research (CSCR).
    • RFC1216 - Gigabit network economics and paradigm shifts.
    • RFC1149 - Standard for the transmission of IP datagrams on avian carriers.
    • RFC1097 - Telnet subliminal-message option.
    Did I miss any?
  22. A lot more, actually :) by demo · · Score: 5 · on TCP/IP Over HTTP
    Just to sum up most of the April Fools RFCs over the years...
    • RFC3093 - Firewall Enhancement Protocol (FEP).
    • RFC3092 - Etymology of "Foo".
    • RFC3091 - Pi Digit Generation Protocol.
    • RFC2795 - The Infinite Monkey Protocol Suite (IMPS).
    • RFC2551 - The Roman Standards Process -- Revision III.
    • RFC2550 - Y10K and Beyond.
    • RFC2549 - IP over Avian Carriers with Quality of Service.
    • RFC2325 - Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2
    • RFC2324 - Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0).
    • RFC2323 - IETF Identification and Security Guidelines.
    • RFC2322 - Management of IP numbers by peg-dhcp.
    • RFC2321 - RITA -- The Reliable Internetwork Troubleshooting Agent.
    • RFC2100 - The Naming of Hosts.
    • RFC1927 - Suggested Additional MIME Types for Associating Documents.
    • RFC1926 - An Experimental Encapsulation of IP Datagrams on Top of ATM.
    • RFC1925 - The Twelve Networking Truths.
    • RFC1924 - A Compact Representation of IPv6 Addresses.
    • RFC1776 - The Address is the Message. S. Crocker.
    • RFC1607 - A VIEW FROM THE 21ST CENTURY. V. Cerf.
    • RFC1606 - A Historical Perspective On The Usage Of IP Version 9.
    • RFC1605 - SONET to Sonnet Translation.
    • RFC1438 - Internet Engineering Task Force Statements Of Boredom (SOBs).
    • RFC1437 - The Extension of MIME Content-Types to a New Medium.
    • RFC1313 - Today's Programming for KRFC AM 1313 Internet Talk Radio.
    • RFC1217 - Memo from the Consortium for Slow Commotion Research (CSCR).
    • RFC1216 - Gigabit network economics and paradigm shifts.
    • RFC1149 - Standard for the transmission of IP datagrams on avian carriers.
    • RFC1097 - Telnet subliminal-message option.
    Did I miss any?
  23. A lot more, actually :) by demo · · Score: 5 · on TCP/IP Over HTTP
    Just to sum up most of the April Fools RFCs over the years...
    • RFC3093 - Firewall Enhancement Protocol (FEP).
    • RFC3092 - Etymology of "Foo".
    • RFC3091 - Pi Digit Generation Protocol.
    • RFC2795 - The Infinite Monkey Protocol Suite (IMPS).
    • RFC2551 - The Roman Standards Process -- Revision III.
    • RFC2550 - Y10K and Beyond.
    • RFC2549 - IP over Avian Carriers with Quality of Service.
    • RFC2325 - Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2
    • RFC2324 - Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0).
    • RFC2323 - IETF Identification and Security Guidelines.
    • RFC2322 - Management of IP numbers by peg-dhcp.
    • RFC2321 - RITA -- The Reliable Internetwork Troubleshooting Agent.
    • RFC2100 - The Naming of Hosts.
    • RFC1927 - Suggested Additional MIME Types for Associating Documents.
    • RFC1926 - An Experimental Encapsulation of IP Datagrams on Top of ATM.
    • RFC1925 - The Twelve Networking Truths.
    • RFC1924 - A Compact Representation of IPv6 Addresses.
    • RFC1776 - The Address is the Message. S. Crocker.
    • RFC1607 - A VIEW FROM THE 21ST CENTURY. V. Cerf.
    • RFC1606 - A Historical Perspective On The Usage Of IP Version 9.
    • RFC1605 - SONET to Sonnet Translation.
    • RFC1438 - Internet Engineering Task Force Statements Of Boredom (SOBs).
    • RFC1437 - The Extension of MIME Content-Types to a New Medium.
    • RFC1313 - Today's Programming for KRFC AM 1313 Internet Talk Radio.
    • RFC1217 - Memo from the Consortium for Slow Commotion Research (CSCR).
    • RFC1216 - Gigabit network economics and paradigm shifts.
    • RFC1149 - Standard for the transmission of IP datagrams on avian carriers.
    • RFC1097 - Telnet subliminal-message option.
    Did I miss any?
  24. A lot more, actually :) by demo · · Score: 5 · on TCP/IP Over HTTP
    Just to sum up most of the April Fools RFCs over the years...
    • RFC3093 - Firewall Enhancement Protocol (FEP).
    • RFC3092 - Etymology of "Foo".
    • RFC3091 - Pi Digit Generation Protocol.
    • RFC2795 - The Infinite Monkey Protocol Suite (IMPS).
    • RFC2551 - The Roman Standards Process -- Revision III.
    • RFC2550 - Y10K and Beyond.
    • RFC2549 - IP over Avian Carriers with Quality of Service.
    • RFC2325 - Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2
    • RFC2324 - Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0).
    • RFC2323 - IETF Identification and Security Guidelines.
    • RFC2322 - Management of IP numbers by peg-dhcp.
    • RFC2321 - RITA -- The Reliable Internetwork Troubleshooting Agent.
    • RFC2100 - The Naming of Hosts.
    • RFC1927 - Suggested Additional MIME Types for Associating Documents.
    • RFC1926 - An Experimental Encapsulation of IP Datagrams on Top of ATM.
    • RFC1925 - The Twelve Networking Truths.
    • RFC1924 - A Compact Representation of IPv6 Addresses.
    • RFC1776 - The Address is the Message. S. Crocker.
    • RFC1607 - A VIEW FROM THE 21ST CENTURY. V. Cerf.
    • RFC1606 - A Historical Perspective On The Usage Of IP Version 9.
    • RFC1605 - SONET to Sonnet Translation.
    • RFC1438 - Internet Engineering Task Force Statements Of Boredom (SOBs).
    • RFC1437 - The Extension of MIME Content-Types to a New Medium.
    • RFC1313 - Today's Programming for KRFC AM 1313 Internet Talk Radio.
    • RFC1217 - Memo from the Consortium for Slow Commotion Research (CSCR).
    • RFC1216 - Gigabit network economics and paradigm shifts.
    • RFC1149 - Standard for the transmission of IP datagrams on avian carriers.
    • RFC1097 - Telnet subliminal-message option.
    Did I miss any?
  25. A lot more, actually :) by demo · · Score: 5 · on TCP/IP Over HTTP
    Just to sum up most of the April Fools RFCs over the years...
    • RFC3093 - Firewall Enhancement Protocol (FEP).
    • RFC3092 - Etymology of "Foo".
    • RFC3091 - Pi Digit Generation Protocol.
    • RFC2795 - The Infinite Monkey Protocol Suite (IMPS).
    • RFC2551 - The Roman Standards Process -- Revision III.
    • RFC2550 - Y10K and Beyond.
    • RFC2549 - IP over Avian Carriers with Quality of Service.
    • RFC2325 - Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2
    • RFC2324 - Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0).
    • RFC2323 - IETF Identification and Security Guidelines.
    • RFC2322 - Management of IP numbers by peg-dhcp.
    • RFC2321 - RITA -- The Reliable Internetwork Troubleshooting Agent.
    • RFC2100 - The Naming of Hosts.
    • RFC1927 - Suggested Additional MIME Types for Associating Documents.
    • RFC1926 - An Experimental Encapsulation of IP Datagrams on Top of ATM.
    • RFC1925 - The Twelve Networking Truths.
    • RFC1924 - A Compact Representation of IPv6 Addresses.
    • RFC1776 - The Address is the Message. S. Crocker.
    • RFC1607 - A VIEW FROM THE 21ST CENTURY. V. Cerf.
    • RFC1606 - A Historical Perspective On The Usage Of IP Version 9.
    • RFC1605 - SONET to Sonnet Translation.
    • RFC1438 - Internet Engineering Task Force Statements Of Boredom (SOBs).
    • RFC1437 - The Extension of MIME Content-Types to a New Medium.
    • RFC1313 - Today's Programming for KRFC AM 1313 Internet Talk Radio.
    • RFC1217 - Memo from the Consortium for Slow Commotion Research (CSCR).
    • RFC1216 - Gigabit network economics and paradigm shifts.
    • RFC1149 - Standard for the transmission of IP datagrams on avian carriers.
    • RFC1097 - Telnet subliminal-message option.
    Did I miss any?
  26. A lot more, actually :) by demo · · Score: 5 · on TCP/IP Over HTTP
    Just to sum up most of the April Fools RFCs over the years...
    • RFC3093 - Firewall Enhancement Protocol (FEP).
    • RFC3092 - Etymology of "Foo".
    • RFC3091 - Pi Digit Generation Protocol.
    • RFC2795 - The Infinite Monkey Protocol Suite (IMPS).
    • RFC2551 - The Roman Standards Process -- Revision III.
    • RFC2550 - Y10K and Beyond.
    • RFC2549 - IP over Avian Carriers with Quality of Service.
    • RFC2325 - Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2
    • RFC2324 - Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0).
    • RFC2323 - IETF Identification and Security Guidelines.
    • RFC2322 - Management of IP numbers by peg-dhcp.
    • RFC2321 - RITA -- The Reliable Internetwork Troubleshooting Agent.
    • RFC2100 - The Naming of Hosts.
    • RFC1927 - Suggested Additional MIME Types for Associating Documents.
    • RFC1926 - An Experimental Encapsulation of IP Datagrams on Top of ATM.
    • RFC1925 - The Twelve Networking Truths.
    • RFC1924 - A Compact Representation of IPv6 Addresses.
    • RFC1776 - The Address is the Message. S. Crocker.
    • RFC1607 - A VIEW FROM THE 21ST CENTURY. V. Cerf.
    • RFC1606 - A Historical Perspective On The Usage Of IP Version 9.
    • RFC1605 - SONET to Sonnet Translation.
    • RFC1438 - Internet Engineering Task Force Statements Of Boredom (SOBs).
    • RFC1437 - The Extension of MIME Content-Types to a New Medium.
    • RFC1313 - Today's Programming for KRFC AM 1313 Internet Talk Radio.
    • RFC1217 - Memo from the Consortium for Slow Commotion Research (CSCR).
    • RFC1216 - Gigabit network economics and paradigm shifts.
    • RFC1149 - Standard for the transmission of IP datagrams on avian carriers.
    • RFC1097 - Telnet subliminal-message option.
    Did I miss any?
  27. A lot more, actually :) by demo · · Score: 5 · on TCP/IP Over HTTP
    Just to sum up most of the April Fools RFCs over the years...
    • RFC3093 - Firewall Enhancement Protocol (FEP).
    • RFC3092 - Etymology of "Foo".
    • RFC3091 - Pi Digit Generation Protocol.
    • RFC2795 - The Infinite Monkey Protocol Suite (IMPS).
    • RFC2551 - The Roman Standards Process -- Revision III.
    • RFC2550 - Y10K and Beyond.
    • RFC2549 - IP over Avian Carriers with Quality of Service.
    • RFC2325 - Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2
    • RFC2324 - Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0).
    • RFC2323 - IETF Identification and Security Guidelines.
    • RFC2322 - Management of IP numbers by peg-dhcp.
    • RFC2321 - RITA -- The Reliable Internetwork Troubleshooting Agent.
    • RFC2100 - The Naming of Hosts.
    • RFC1927 - Suggested Additional MIME Types for Associating Documents.
    • RFC1926 - An Experimental Encapsulation of IP Datagrams on Top of ATM.
    • RFC1925 - The Twelve Networking Truths.
    • RFC1924 - A Compact Representation of IPv6 Addresses.
    • RFC1776 - The Address is the Message. S. Crocker.
    • RFC1607 - A VIEW FROM THE 21ST CENTURY. V. Cerf.
    • RFC1606 - A Historical Perspective On The Usage Of IP Version 9.
    • RFC1605 - SONET to Sonnet Translation.
    • RFC1438 - Internet Engineering Task Force Statements Of Boredom (SOBs).
    • RFC1437 - The Extension of MIME Content-Types to a New Medium.
    • RFC1313 - Today's Programming for KRFC AM 1313 Internet Talk Radio.
    • RFC1217 - Memo from the Consortium for Slow Commotion Research (CSCR).
    • RFC1216 - Gigabit network economics and paradigm shifts.
    • RFC1149 - Standard for the transmission of IP datagrams on avian carriers.
    • RFC1097 - Telnet subliminal-message option.
    Did I miss any?
  28. A lot more, actually :) by demo · · Score: 5 · on TCP/IP Over HTTP
    Just to sum up most of the April Fools RFCs over the years...
    • RFC3093 - Firewall Enhancement Protocol (FEP).
    • RFC3092 - Etymology of "Foo".
    • RFC3091 - Pi Digit Generation Protocol.
    • RFC2795 - The Infinite Monkey Protocol Suite (IMPS).
    • RFC2551 - The Roman Standards Process -- Revision III.
    • RFC2550 - Y10K and Beyond.
    • RFC2549 - IP over Avian Carriers with Quality of Service.
    • RFC2325 - Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2
    • RFC2324 - Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0).
    • RFC2323 - IETF Identification and Security Guidelines.
    • RFC2322 - Management of IP numbers by peg-dhcp.
    • RFC2321 - RITA -- The Reliable Internetwork Troubleshooting Agent.
    • RFC2100 - The Naming of Hosts.
    • RFC1927 - Suggested Additional MIME Types for Associating Documents.
    • RFC1926 - An Experimental Encapsulation of IP Datagrams on Top of ATM.
    • RFC1925 - The Twelve Networking Truths.
    • RFC1924 - A Compact Representation of IPv6 Addresses.
    • RFC1776 - The Address is the Message. S. Crocker.
    • RFC1607 - A VIEW FROM THE 21ST CENTURY. V. Cerf.
    • RFC1606 - A Historical Perspective On The Usage Of IP Version 9.
    • RFC1605 - SONET to Sonnet Translation.
    • RFC1438 - Internet Engineering Task Force Statements Of Boredom (SOBs).
    • RFC1437 - The Extension of MIME Content-Types to a New Medium.
    • RFC1313 - Today's Programming for KRFC AM 1313 Internet Talk Radio.
    • RFC1217 - Memo from the Consortium for Slow Commotion Research (CSCR).
    • RFC1216 - Gigabit network economics and paradigm shifts.
    • RFC1149 - Standard for the transmission of IP datagrams on avian carriers.
    • RFC1097 - Telnet subliminal-message option.
    Did I miss any?
  29. A lot more, actually :) by demo · · Score: 5 · on TCP/IP Over HTTP
    Just to sum up most of the April Fools RFCs over the years...
    • RFC3093 - Firewall Enhancement Protocol (FEP).
    • RFC3092 - Etymology of "Foo".
    • RFC3091 - Pi Digit Generation Protocol.
    • RFC2795 - The Infinite Monkey Protocol Suite (IMPS).
    • RFC2551 - The Roman Standards Process -- Revision III.
    • RFC2550 - Y10K and Beyond.
    • RFC2549 - IP over Avian Carriers with Quality of Service.
    • RFC2325 - Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2
    • RFC2324 - Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0).
    • RFC2323 - IETF Identification and Security Guidelines.
    • RFC2322 - Management of IP numbers by peg-dhcp.
    • RFC2321 - RITA -- The Reliable Internetwork Troubleshooting Agent.
    • RFC2100 - The Naming of Hosts.
    • RFC1927 - Suggested Additional MIME Types for Associating Documents.
    • RFC1926 - An Experimental Encapsulation of IP Datagrams on Top of ATM.
    • RFC1925 - The Twelve Networking Truths.
    • RFC1924 - A Compact Representation of IPv6 Addresses.
    • RFC1776 - The Address is the Message. S. Crocker.
    • RFC1607 - A VIEW FROM THE 21ST CENTURY. V. Cerf.
    • RFC1606 - A Historical Perspective On The Usage Of IP Version 9.
    • RFC1605 - SONET to Sonnet Translation.
    • RFC1438 - Internet Engineering Task Force Statements Of Boredom (SOBs).
    • RFC1437 - The Extension of MIME Content-Types to a New Medium.
    • RFC1313 - Today's Programming for KRFC AM 1313 Internet Talk Radio.
    • RFC1217 - Memo from the Consortium for Slow Commotion Research (CSCR).
    • RFC1216 - Gigabit network economics and paradigm shifts.
    • RFC1149 - Standard for the transmission of IP datagrams on avian carriers.
    • RFC1097 - Telnet subliminal-message option.
    Did I miss any?
  30. A lot more, actually :) by demo · · Score: 5 · on TCP/IP Over HTTP
    Just to sum up most of the April Fools RFCs over the years...
    • RFC3093 - Firewall Enhancement Protocol (FEP).
    • RFC3092 - Etymology of "Foo".
    • RFC3091 - Pi Digit Generation Protocol.
    • RFC2795 - The Infinite Monkey Protocol Suite (IMPS).
    • RFC2551 - The Roman Standards Process -- Revision III.
    • RFC2550 - Y10K and Beyond.
    • RFC2549 - IP over Avian Carriers with Quality of Service.
    • RFC2325 - Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2
    • RFC2324 - Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0).
    • RFC2323 - IETF Identification and Security Guidelines.
    • RFC2322 - Management of IP numbers by peg-dhcp.
    • RFC2321 - RITA -- The Reliable Internetwork Troubleshooting Agent.
    • RFC2100 - The Naming of Hosts.
    • RFC1927 - Suggested Additional MIME Types for Associating Documents.
    • RFC1926 - An Experimental Encapsulation of IP Datagrams on Top of ATM.
    • RFC1925 - The Twelve Networking Truths.
    • RFC1924 - A Compact Representation of IPv6 Addresses.
    • RFC1776 - The Address is the Message. S. Crocker.
    • RFC1607 - A VIEW FROM THE 21ST CENTURY. V. Cerf.
    • RFC1606 - A Historical Perspective On The Usage Of IP Version 9.
    • RFC1605 - SONET to Sonnet Translation.
    • RFC1438 - Internet Engineering Task Force Statements Of Boredom (SOBs).
    • RFC1437 - The Extension of MIME Content-Types to a New Medium.
    • RFC1313 - Today's Programming for KRFC AM 1313 Internet Talk Radio.
    • RFC1217 - Memo from the Consortium for Slow Commotion Research (CSCR).
    • RFC1216 - Gigabit network economics and paradigm shifts.
    • RFC1149 - Standard for the transmission of IP datagrams on avian carriers.
    • RFC1097 - Telnet subliminal-message option.
    Did I miss any?
  31. A lot more, actually :) by demo · · Score: 5 · on TCP/IP Over HTTP
    Just to sum up most of the April Fools RFCs over the years...
    • RFC3093 - Firewall Enhancement Protocol (FEP).
    • RFC3092 - Etymology of "Foo".
    • RFC3091 - Pi Digit Generation Protocol.
    • RFC2795 - The Infinite Monkey Protocol Suite (IMPS).
    • RFC2551 - The Roman Standards Process -- Revision III.
    • RFC2550 - Y10K and Beyond.
    • RFC2549 - IP over Avian Carriers with Quality of Service.
    • RFC2325 - Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2
    • RFC2324 - Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0).
    • RFC2323 - IETF Identification and Security Guidelines.
    • RFC2322 - Management of IP numbers by peg-dhcp.
    • RFC2321 - RITA -- The Reliable Internetwork Troubleshooting Agent.
    • RFC2100 - The Naming of Hosts.
    • RFC1927 - Suggested Additional MIME Types for Associating Documents.
    • RFC1926 - An Experimental Encapsulation of IP Datagrams on Top of ATM.
    • RFC1925 - The Twelve Networking Truths.
    • RFC1924 - A Compact Representation of IPv6 Addresses.
    • RFC1776 - The Address is the Message. S. Crocker.
    • RFC1607 - A VIEW FROM THE 21ST CENTURY. V. Cerf.
    • RFC1606 - A Historical Perspective On The Usage Of IP Version 9.
    • RFC1605 - SONET to Sonnet Translation.
    • RFC1438 - Internet Engineering Task Force Statements Of Boredom (SOBs).
    • RFC1437 - The Extension of MIME Content-Types to a New Medium.
    • RFC1313 - Today's Programming for KRFC AM 1313 Internet Talk Radio.
    • RFC1217 - Memo from the Consortium for Slow Commotion Research (CSCR).
    • RFC1216 - Gigabit network economics and paradigm shifts.
    • RFC1149 - Standard for the transmission of IP datagrams on avian carriers.
    • RFC1097 - Telnet subliminal-message option.
    Did I miss any?
  32. A lot more, actually :) by demo · · Score: 5 · on TCP/IP Over HTTP
    Just to sum up most of the April Fools RFCs over the years...
    • RFC3093 - Firewall Enhancement Protocol (FEP).
    • RFC3092 - Etymology of "Foo".
    • RFC3091 - Pi Digit Generation Protocol.
    • RFC2795 - The Infinite Monkey Protocol Suite (IMPS).
    • RFC2551 - The Roman Standards Process -- Revision III.
    • RFC2550 - Y10K and Beyond.
    • RFC2549 - IP over Avian Carriers with Quality of Service.
    • RFC2325 - Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2
    • RFC2324 - Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0).
    • RFC2323 - IETF Identification and Security Guidelines.
    • RFC2322 - Management of IP numbers by peg-dhcp.
    • RFC2321 - RITA -- The Reliable Internetwork Troubleshooting Agent.
    • RFC2100 - The Naming of Hosts.
    • RFC1927 - Suggested Additional MIME Types for Associating Documents.
    • RFC1926 - An Experimental Encapsulation of IP Datagrams on Top of ATM.
    • RFC1925 - The Twelve Networking Truths.
    • RFC1924 - A Compact Representation of IPv6 Addresses.
    • RFC1776 - The Address is the Message. S. Crocker.
    • RFC1607 - A VIEW FROM THE 21ST CENTURY. V. Cerf.
    • RFC1606 - A Historical Perspective On The Usage Of IP Version 9.
    • RFC1605 - SONET to Sonnet Translation.
    • RFC1438 - Internet Engineering Task Force Statements Of Boredom (SOBs).
    • RFC1437 - The Extension of MIME Content-Types to a New Medium.
    • RFC1313 - Today's Programming for KRFC AM 1313 Internet Talk Radio.
    • RFC1217 - Memo from the Consortium for Slow Commotion Research (CSCR).
    • RFC1216 - Gigabit network economics and paradigm shifts.
    • RFC1149 - Standard for the transmission of IP datagrams on avian carriers.
    • RFC1097 - Telnet subliminal-message option.
    Did I miss any?
  33. A lot more, actually :) by demo · · Score: 5 · on TCP/IP Over HTTP
    Just to sum up most of the April Fools RFCs over the years...
    • RFC3093 - Firewall Enhancement Protocol (FEP).
    • RFC3092 - Etymology of "Foo".
    • RFC3091 - Pi Digit Generation Protocol.
    • RFC2795 - The Infinite Monkey Protocol Suite (IMPS).
    • RFC2551 - The Roman Standards Process -- Revision III.
    • RFC2550 - Y10K and Beyond.
    • RFC2549 - IP over Avian Carriers with Quality of Service.
    • RFC2325 - Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2
    • RFC2324 - Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0).
    • RFC2323 - IETF Identification and Security Guidelines.
    • RFC2322 - Management of IP numbers by peg-dhcp.
    • RFC2321 - RITA -- The Reliable Internetwork Troubleshooting Agent.
    • RFC2100 - The Naming of Hosts.
    • RFC1927 - Suggested Additional MIME Types for Associating Documents.
    • RFC1926 - An Experimental Encapsulation of IP Datagrams on Top of ATM.
    • RFC1925 - The Twelve Networking Truths.
    • RFC1924 - A Compact Representation of IPv6 Addresses.
    • RFC1776 - The Address is the Message. S. Crocker.
    • RFC1607 - A VIEW FROM THE 21ST CENTURY. V. Cerf.
    • RFC1606 - A Historical Perspective On The Usage Of IP Version 9.
    • RFC1605 - SONET to Sonnet Translation.
    • RFC1438 - Internet Engineering Task Force Statements Of Boredom (SOBs).
    • RFC1437 - The Extension of MIME Content-Types to a New Medium.
    • RFC1313 - Today's Programming for KRFC AM 1313 Internet Talk Radio.
    • RFC1217 - Memo from the Consortium for Slow Commotion Research (CSCR).
    • RFC1216 - Gigabit network economics and paradigm shifts.
    • RFC1149 - Standard for the transmission of IP datagrams on avian carriers.
    • RFC1097 - Telnet subliminal-message option.
    Did I miss any?
  34. A lot more, actually :) by demo · · Score: 5 · on TCP/IP Over HTTP
    Just to sum up most of the April Fools RFCs over the years...
    • RFC3093 - Firewall Enhancement Protocol (FEP).
    • RFC3092 - Etymology of "Foo".
    • RFC3091 - Pi Digit Generation Protocol.
    • RFC2795 - The Infinite Monkey Protocol Suite (IMPS).
    • RFC2551 - The Roman Standards Process -- Revision III.
    • RFC2550 - Y10K and Beyond.
    • RFC2549 - IP over Avian Carriers with Quality of Service.
    • RFC2325 - Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2
    • RFC2324 - Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0).
    • RFC2323 - IETF Identification and Security Guidelines.
    • RFC2322 - Management of IP numbers by peg-dhcp.
    • RFC2321 - RITA -- The Reliable Internetwork Troubleshooting Agent.
    • RFC2100 - The Naming of Hosts.
    • RFC1927 - Suggested Additional MIME Types for Associating Documents.
    • RFC1926 - An Experimental Encapsulation of IP Datagrams on Top of ATM.
    • RFC1925 - The Twelve Networking Truths.
    • RFC1924 - A Compact Representation of IPv6 Addresses.
    • RFC1776 - The Address is the Message. S. Crocker.
    • RFC1607 - A VIEW FROM THE 21ST CENTURY. V. Cerf.
    • RFC1606 - A Historical Perspective On The Usage Of IP Version 9.
    • RFC1605 - SONET to Sonnet Translation.
    • RFC1438 - Internet Engineering Task Force Statements Of Boredom (SOBs).
    • RFC1437 - The Extension of MIME Content-Types to a New Medium.
    • RFC1313 - Today's Programming for KRFC AM 1313 Internet Talk Radio.
    • RFC1217 - Memo from the Consortium for Slow Commotion Research (CSCR).
    • RFC1216 - Gigabit network economics and paradigm shifts.
    • RFC1149 - Standard for the transmission of IP datagrams on avian carriers.
    • RFC1097 - Telnet subliminal-message option.
    Did I miss any?
  35. A lot more, actually :) by demo · · Score: 5 · on TCP/IP Over HTTP
    Just to sum up most of the April Fools RFCs over the years...
    • RFC3093 - Firewall Enhancement Protocol (FEP).
    • RFC3092 - Etymology of "Foo".
    • RFC3091 - Pi Digit Generation Protocol.
    • RFC2795 - The Infinite Monkey Protocol Suite (IMPS).
    • RFC2551 - The Roman Standards Process -- Revision III.
    • RFC2550 - Y10K and Beyond.
    • RFC2549 - IP over Avian Carriers with Quality of Service.
    • RFC2325 - Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2
    • RFC2324 - Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0).
    • RFC2323 - IETF Identification and Security Guidelines.
    • RFC2322 - Management of IP numbers by peg-dhcp.
    • RFC2321 - RITA -- The Reliable Internetwork Troubleshooting Agent.
    • RFC2100 - The Naming of Hosts.
    • RFC1927 - Suggested Additional MIME Types for Associating Documents.
    • RFC1926 - An Experimental Encapsulation of IP Datagrams on Top of ATM.
    • RFC1925 - The Twelve Networking Truths.
    • RFC1924 - A Compact Representation of IPv6 Addresses.
    • RFC1776 - The Address is the Message. S. Crocker.
    • RFC1607 - A VIEW FROM THE 21ST CENTURY. V. Cerf.
    • RFC1606 - A Historical Perspective On The Usage Of IP Version 9.
    • RFC1605 - SONET to Sonnet Translation.
    • RFC1438 - Internet Engineering Task Force Statements Of Boredom (SOBs).
    • RFC1437 - The Extension of MIME Content-Types to a New Medium.
    • RFC1313 - Today's Programming for KRFC AM 1313 Internet Talk Radio.
    • RFC1217 - Memo from the Consortium for Slow Commotion Research (CSCR).
    • RFC1216 - Gigabit network economics and paradigm shifts.
    • RFC1149 - Standard for the transmission of IP datagrams on avian carriers.
    • RFC1097 - Telnet subliminal-message option.
    Did I miss any?
  36. Hell, I've got wireless already by Saint+Aardvark · · Score: 3 · on Free Wireless For Fun And / Or No Profit
    And you're all welcome to join. Just check out RFC 2549, IP over Avian Carriers with Quality of Service. After all, those wireless LAN cards can be pretty pricey...

  37. RFC2324! by TGandalf · · Score: 2 · on First Ever Webcam to Come Offline

    RFC2324: Hyper Text Coffee Pot Control Protocol. My favourite response code is "418 I'm a teapot". Oddly though, Apache refused to accept this config. Maybe, I'll have to send a bug report.

  38. WHAT "old limits" on .org???? by mattdm · · Score: 5 · on VeriSign Usurps .com

    There are also apparently plans to reinstate the old limits on .org domains - if you aren't a non-profit corporation, you won't be permitted to register or keep a .org domain.

    There never were any such limits. Read RFC 1591

    ORG - This domain is intended as the miscellaneous TLD for organizations that didn't fit anywhere else. Some non- government organizations may fit here.

    In fact, although I can't find into on the IANA website anymore (it's all been "updated"), .org used to be specifically recommended as the place for individuals who wanted their own domain.

    Anything more limiting than this wouldn't be old rules -- it'd be something completely new. If new TLDs are created which serve as functional replacements (something for personal and family domains, something for software projects, etc., etc.), that's all well and good for the future, but it's ridiculous and unfair to take away existing .org domains.


    --

  39. Re: JPEG Specs by Rabenwolf · · Score: 2 · on Does Cracking Encryption Involve Some Precognition?
    How does your computer know that a jpeg is a jpeg?

    A good place to start for this question would be the Usenet JPEG FAQ; the question is answered here.

  40. Re: JPEG Specs by Rabenwolf · · Score: 2 · on Does Cracking Encryption Involve Some Precognition?
    How does your computer know that a jpeg is a jpeg?

    A good place to start for this question would be the Usenet JPEG FAQ; the question is answered here.

  41. A little education about the law by ip4noman · · Score: 2 · on New York ISP Held Liable For Newsgroup Content

    Please see the Lawful Arrest FAQ for the defintion of "crime", "cause of action", and "probable cause". For your reference:

    A crime (corpus delecti) must have:
    • An Injury
    • A criminal cause (not an accident or act-of-god)
    Cause of Action requires:
    • A right
    • An Injury
    • A petition for restitution
    Probable Cause is : Reason to believe that the accused caused the injury to the victim
    Probable Cause requires :Connection between the accused and the victim's injury

    Look, no one is denying that forcing a child to pose for nude photos (or worse) is a crime. And let's say some sicko scans them and posts them to Usenet. And let's say that Fred O. Phile likes to look at such pictures for erotic pleasure and downloads them from his ISP.

    Ok, Fred is a pervert. But did he produce an injury to the child? No. The ISP is in the business of passing bits around. Did anyone at the ISP cause an injury to a child? No.

    I'm going to go out on a limb here and assert that not every photo of a nude child actually produces an injury! BUT: if there was an injury produced, perhaps it was the guy that took the photo, and NOT the ISP, and not the guy that pulled it from a.b.p.k-p

    And as my friend Jimmy Pineapple would say, "End of fucking story" -- Bill Hicks
  42. Underscores in tripod names by marnanel · · Score: 1 · on LOTR Internet-Only Trailer

    Unfortunately, Tripod allows users to pick names which contain underscores, and then uses them as labels within the DNS; this is in contravention of RFC 1034 sec 3.5, which states:

    The labels must follow the rules for ARPANET host names. They must start with a letter, end with a letter or digit, and have as interior characters only letters, digits, and hyphen. (my emphasis)

    This doesn't often cause much of a problem for most people, since most systems are properly "liberal in what they accept, and conservative in what they send" ; however, in my experience, some systems have problems with the broken names, notably some firewall software.

    I suppose somebody should point this out to Tripod, really.

    M

  43. Capability (theoretically) already exists... by RapaNui · · Score: 2 · on Yahoo Geographically Targeting Users

    There is (theoretically, at least), already the capability to do some of this stuff, as outlined in

    RFC1712-DNS Encoding of Geographical Location
    and
    RFC1876-A Means for Expressing Location Information in the Domain Name System

  44. Capability (theoretically) already exists... by RapaNui · · Score: 2 · on Yahoo Geographically Targeting Users

    There is (theoretically, at least), already the capability to do some of this stuff, as outlined in

    RFC1712-DNS Encoding of Geographical Location
    and
    RFC1876-A Means for Expressing Location Information in the Domain Name System

  45. Why isn't this stored at www.faqs.org? by glanois · · Score: 1 · on comp.os.linux.security FAQ
    Or rtfm.mit.edu?

    I know why. It's because the author hasn't bothered to format his FAQ according to the standard, nor has he bothered to get it approved for posting to news.answers et al.

    This link tells you what you need to know to know to get a Usenet FAQ document posted to news.answers.

    -Gerard

  46. Coffee! by sachachua · · Score: 1 · on Ideas For High School Electronics Class?
    Looks like a perfect opportunity to adhere to the following RFCs:

    • RFC2325 - Slavitch - 1 Apr 1998
      Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2
      This memo defines an extension to the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for the management of coffee-brewing and maintenance devices.

    • RFC2324 - Masinter - 1 Apr 1998
      Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0)
      This document describes HTCPCP, a protocol for controlling, monitoring, and diagnosing coffee pots.
  47. Coffee! by sachachua · · Score: 1 · on Ideas For High School Electronics Class?
    Looks like a perfect opportunity to adhere to the following RFCs:

    • RFC2325 - Slavitch - 1 Apr 1998
      Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2
      This memo defines an extension to the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for the management of coffee-brewing and maintenance devices.

    • RFC2324 - Masinter - 1 Apr 1998
      Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0)
      This document describes HTCPCP, a protocol for controlling, monitoring, and diagnosing coffee pots.
  48. Re:This is actually pretty cool. by Benley · · Score: 1 · on GNOME ORBit Ported To Linux Kernel

    While this may not be exactly what you're looking for, you might try DS3 for modem sharing. Or, something that I suspect is more what you're after is MSREDIR, a serial port redirector that is designed to let multiple people share multiple modems (an implementation of RFC 2217).

    As for sound card sharing, while I haven't looked into this very much, it is probably not difficult to do it using the EsounD daemon. I think I may have tried this before using xmms to play across the network to a remote host. Quite cool if you ask me.

  49. Re:Something I missed? by andrewt · · Score: 1 · on Ozone Hole Will Heal, Say British Scientists
    These questions and others are answered in Robert Parsons' Ozone Depletion FAQ

    Andrew Taylor

  50. Re:The 555-xxxx of ip's? by tycage · · Score: 1 · on Phone Numbers Instead of URLs?
    I think this would suffice, Address Allocatioin for Private Internets

    :)

    --Ty