| Author |
Topic: IPoAC |
b0b
From:
Cloverdale, CA, USA
|
|
|
|
Michael Maddex
From:
Northern New Mexico, USA
|
Posted 18 Mar 2009 5:46 pm Rfc 1149 |
|
From RFC 1149 (Discussing IPoAC):
<tt>Multiple types of service can be provided with a prioritized pecking order. An additional property is built-in worm detection and eradication. Because IP only guarantees best effort delivery, loss of a carrier can be tolerated. With time, the carriers are self-regenerating. While broadcasting is not specified, storms can cause data loss. There is persistent delivery retry, until the carrier drops. Audit trails are automatically generated, and can often be found on logs and cable trays.</tt>
Sounds like a step up from my first modem.
_________________
"For every expert, there is an equal and opposite expert." -- Arthur C. Clarke |
|
|
|
John Cipriano
From:
San Francisco
|
Posted 25 Mar 2009 9:53 pm
|
|
Other good ones are the Infinite Monkey protocol, electricity over IP, and the AM Talk Radio schedule:
http://tools.ietf.org/html/rfc1313
http://tools.ietf.org/html/rfc3251
http://tools.ietf.org/html/rfc2795
But nothing will ever come close to topping this:
http://www.ietf.org/rfc/rfc3514.txt
| Code: |
Currently-assigned values are defined as follows:
0x0 If the bit is set to 0, the packet has no evil intent. Hosts,
network elements, etc., SHOULD assume that the packet is
harmless, and SHOULD NOT take any defensive measures. (We note
that this part of the spec is already implemented by many common
desktop operating systems.)
0x1 If the bit is set to 1, the packet has evil intent. Secure
systems SHOULD try to defend themselves against such packets.
Insecure systems MAY chose to crash, be penetrated, etc.
|
|
|
|
|
