As per Relevance of the word carriers, we have this rfc below:
Network Working Group D.
Request for Comments: 2549 IronBridge
Updates: 1149 1 April 1999
Category:
IP over Avian Carriers with Quality of
Status of this
This memo defines an Experimental Protocol for the
community. It does not specify an Internet standard of any kind
Discussion and suggestions for improvement are requested
Distribution of this memo is unlimited
Copyright
Copyright (C) The Internet Society (1999). All Rights Reserved
This memo amends RFC 1149, "A Standard for the Transmission of
Datagrams on Avian Carriers", with Quality of Service information
This is an experimental, not recommended standard
Overview and
The following quality of service levels are available: Concorde
First, Business, and Coach. Concorde class offers expedited
delivery. One major benefit to using Avian Carriers is that this
the only networking technology that earns frequent flyer miles,
the Concorde and First classes of service earn 50% bonus miles
packet. Ostriches are an alternate carrier that have much
bulk transfer capability but provide slower delivery, and require
use of bridges between domains
The service level is indicated on a per-carrier basis by bar-
markings on the wing. One implementation strategy is for a bar-
reader to scan each carrier as it enters the router and then
it in the proper queue, gated to prevent exit until the proper time
The carriers may sleep while enqueued
For secure networks, carriers may have classes Prime or Choice
Prime carriers are self-keying when using public key encryption
Some distributors have been known to falsely classify Choice
as Prime
Packets MAY be marked for deletion using RED paint while enqueued
Waitzman Experimental [Page 1]
RFC 2549 IP over Avian Carriers with QoS 1 April 1999
Weighted fair queueing (WFQ) MAY be implemented using scales,
shown
__
_____/-----\ / o
<____ _____\_/ >--
+-----+ \ / /______/
| 10g | /|:||/
+-----+ /____/|
| 10g | |
+-----+ ..
===============================
^
|
=========
Carriers in the queue too long may leave log entries, as shown on
scale
The following is a plot of traffic shaping, from coop-erative
sites
Alt | Plot of Traffic Shaping showing carriers in
|
2k | ....................
| . .
| . .
1k | . .
| +---+ +---+
| | A | | B |
| +---+ +---+
|_____________________________________________
Avian carriers normally bypass bridges and tunnels but will seek
worm hole tunnels. When carrying web traffic, the carriers
digest the spiders, leaving behind a more compact representation
The carriers may be confused by mirrors
Round-robin queueing is not recommended. Robins make for well-
networks but do not support the necessary auto-homing feature
A BOF was held at the last IETF but only Avian Carriers were
entry, so we don't know the results other than we're sure they
MPLS is great. Our attempts at attaching labels to the carriers
been met with resistance
Waitzman Experimental [Page 2]
RFC 2549 IP over Avian Carriers with QoS 1 April 1999
NATs are not recommended either -- as with many protocols,
the brain-embedded IP addresses is difficult, plus Avian Carriers
eat the NATs
Encapsulation may be done with saran wrappers.
encapsulation in hawks has been known to occur, with
being messy and the packets mangled
Loose source routes are a viable evolutionary alternative
standards-based MSWindows-compliant technology, but strict
routes MUST NOT be used, as they are a choke-point
The ITU has offered the IETF formal alignment with its
technology, Penguins, but that won't fly
Multicasting is supported, but requires the implementation of a
device. Carriers may be lost if they are based on a tree as it
being pruned. The carriers propagate via an inheritance tree.
carriers have an average TTL of 15 years, so their use in
ring searches is limited
Additional quality of service discussion can be found in a Michelin'
guide
MIB and Management
AvCarrier2 OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS can't-
STATUS
DESCRIPTION "Definition of an avian carrier
::= { life eukaryotes mitochondrial_eukaryotes crown_
metazoa chordata craniata vertebrata
sarcopterygii terrestrial_vertebrates amniota
archosauromorpha archosauria dinosauria aves
columbiformes columbidae columba livia }
AvCarrier OBJECT-
SYNTAX SET OF
MAX-ACCESS not-
STATUS
DESCRIPTION "Definition of an avian carrier
::= { life animalia chordata vertebrata
columbiformes columbidae columba livia }
PulseRate OBJECT-
SYNTAX Gauge(0..300)
MAX-ACCESS read-
Waitzman Experimental [Page 3]
RFC 2549 IP over Avian Carriers with QoS 1 April 1999
STATUS
DESCRIPTION "Pulse rate of carrier, as measured in neck
Frequent sampling is disruptive to operations."
::= { AvCarrier 1}
The carriers will not line up in lexigraphic order but
naturally order in a large V shape. Bulk retrieval is
using the Powerful Get-Net operator
Specification of
In this document, several words are used to signify the
of the specification. These words are often capitalized
MUST Usually
MUST NOT Usually not
SHOULD Only when Marketing insists
MAY Only if it doesn't cost extra
Security
There are privacy issues with stool pigeons
Agoraphobic carriers are very insecure in operation
Patent
There is ongoing litigation about which is the prior art: carrier
egg
Waitzman, D., "A Standard for the Transmission of IP Datagrams
Avian Carriers", RFC 1149, 1 April 1990.
Jim.Carlson.Ibnets.com > Jon.Saperia . ack 32 win 123 (DF
Ross Callon, Scott Bradner, Charlie Lynn ...
Waitzman Experimental [Page 4]
RFC 2549 IP over Avian Carriers with QoS 1 April 1999
Author's
David
IronBridge
55 Hayden
Lexington, MA 02421
Phone: (781) 372-8161
EMail: djw@vineyard.
Waitzman Experimental [Page 5]
RFC 2549 IP over Avian Carriers with QoS 1 April 1999
Full Copyright
Copyright (C) The Internet Society (1999). All Rights Reserved
This document and translations of it may be copied and furnished
others, and derivative works that comment on or otherwise explain
or assist in its implementation may be prepared, copied,
and distributed, in whole or in part, without restriction of
kind, provided that the above copyright notice and this paragraph
included on all such copies and derivative works. However,
document itself may not be modified in any way, such as by
the copyright notice or references to the Internet Society or
Internet organizations, except as needed for the purpose
developing Internet standards in which case the procedures
copyrights defined in the Internet Standards process must
followed, or as required to translate it into languages other
English
The limited permissions granted above are perpetual and will not
revoked by the Internet Society or its successors or assigns
This document and the information contained herein is provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Waitzman Experimental [Page 6]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
