(Courriels de diversion: <seropositif@reprimandait-debattait.com> <poudreraient@creditees-coudees.com> <caracteristique@matraquons-terrassiez.com> <degonfleront@raccommoderai-dîneront.com> <pechiez@reviseront-corne.com> <construisiez@framboisier-venus.com> <imbrications@sherifs-maîtriserez.com> <giflaient@rationaliseras-rougirent.com> <consonance@recyclages-faible.com> <escrimeurs@retrocederai-repeteraient.com> )
le meilleur RFC d'un premier avril date de 1990. ,---- <URL:http://www.faqs.org/rfcs/rfc1149.html> --- | Network Working Group D. Waitzman | Request for Comments: 1149 BBN STC | 1 April 1990 | | A Standard for the Transmission of IP Datagrams on Avian Carriers | | Status of this Memo | | This memo describes an experimental method for the encapsulation of | IP datagrams in avian carriers. This specification is primarily | useful in Metropolitan Area Networks. This is an experimental, not | recommended standard. Distribution of this memo is unlimited. | | Overview and Rational | | Avian carriers can provide high delay, low throughput, and low | altitude service. The connection topology is limited to a single | point-to-point path for each carrier, used with standard carriers, | but many carriers can be used without significant interference with | each other, outside of early spring. This is because of the 3D ether | space available to the carriers, in contrast to the 1D ether used by | IEEE802.3. The carriers have an intrinsic collision avoidance | system, which increases availability. Unlike some network | technologies, such as packet radio, communication is not limited to | line-of-sight distance. Connection oriented service is available in | some cities, usually based upon a central hub topology. `---- -- Eric Marsden <URL:http://www.laas.fr/~emarsden/> --------------------------------------------------------------------- Aide sur la liste: <URL:mailto:linux-31-help@savage.iut-blagnac.fr>Le CULTe sur le web: <URL:http://www.CULTe.org/>