lug-bg: Prosto niamam komentar ;-)!
- Subject: lug-bg: Prosto niamam komentar ;-)!
- From: ivo@xxxxxxxxxxxxxx (Ivaylo Toshev)
- Date: Tue, 10 Apr 2001 14:08:39 +0300
Ìîæå äà Âè èçãëåæäà ìàéòàï ðàáîòàòà, îáà÷å íå å!!!
Âèæòå â àòà÷ìåíòèòå, èìàò ñè äàæå è project-site.
--
***********************************************
Ivaylo Toshev < ivo@xxxxxxxxxxxxxx>
***********************************************
ITCE Ltd. Sofia, BULGARIA
http://www.itce.com
http://linux.itce.com
http://bootcamp.itce.com
+359 2 957 17 83
+359 2 957 17 84
***********************************************
This is a MIME digest forward. The content of the message is contained in the attachment(s).
--
--------------Boundary-01=_QMLKR3W2ZJ9ILYQD7YFD
Content-Type: MESSAGE/RFC822; CHARSET=us-ascii
Content-ID: <01041012422609.01734@xxxxxxxxxxxx>
Content-Description: Fwd: Implementation of RFC 1149: IP over avian carriers. (fwd)
Received: from guard.FIREWALL.ITCE.COM (GUARD [192.168.100.100]) by SRV02.ruvex.bg with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
id H65ACWG8; Tue, 10 Apr 2001 12:35:50 +0300
Received: from linux.itce.com ([192.168.100.60]) by guard.FIREWALL.ITCE.COM with Microsoft SMTPSVC(5.0.2195.1600);
Tue, 10 Apr 2001 12:30:43 +0300
Received: from ivo.itce.com (IDENT:root@xxxxxxxxxxxx [192.168.1.219])
by linux.itce.com (8.11.0/8.8.7) with SMTP id f3A8aCX26462
for <ITExperts@xxxxxxxx>; Tue, 10 Apr 2001 11:36:12 +0300
Message-Id: <200104100836.f3A8aCX26462@xxxxxxxxxxxxxx>
From: Ivaylo Toshev <ivo@xxxxxxxxxxxxxx>
Subject: Fwd: Implementation of RFC 1149: IP over avian carriers.
To: ITExperts@xxxxxxxx
Reply-To: ivo@xxxxxxxxxxxxxx
Date: Tue, 10 Apr 2001 12:35:18 +0300
Lines: 67
Organization: ITCE Ltd
User-Agent: KNode/0.4
MIME-Version: 1.0
Content-Type: text/plain;
charset=us-ascii
Content-Transfer-Encoding: 7Bit
Return-Path: ivo@xxxxxxxxxxxxxx
X-OriginalArrivalTime: 10 Apr 2001 09:30:43.0527 (UTC) FILETIME=[EA3E8D70:01C0C1A0]
Status: R
X-Status: N
,--------------- Forwarded message (begin)
Subject: Implementation of RFC 1149: IP over avian carriers.
From: Vegard Engen <vegard@xxxxxxxxxxxxxxxxxxxx>
Date: Fri, 6 Apr 2001 22:34:49 +0300
-----BEGIN PGP SIGNED MESSAGE-----
11 years ago, april 1st 1990, an important RFC was written, RFC 1149: IP
over
avian carriers. To this day, as far as we know, no person has implemented
this
RFC, yet it has been mentioned in numerous classes and networking courses.
That
time has come to an end, and RFC 1149 will finally get its first
implementation, brought to you by Bergen Linux User Group and Vesta
Pigeon Racing Club.
The CPIP WG was founded march 6th 2001, as a joint project between the two
mentioned groups. Since then, members of both clubs have been busy
with planning, experimentation and implementation. We're now so far into
the
project that we feel confident that the technology is ready, and the
implementation will be finished in time.
The tentative date for the demonstration of the first implementation and
the
transportation of the first packets over live pigeons is set to april 28th.
The place will be somewhere in Bergen, but due to risk of interference in
the
transmission, the actual sites will not be announced, at least not yet.
The WGs project web page is http://www.blug.linux.no/rfc1149/ - and on this
page, we'll put up minutes, plans, implementation details and in due time,
a
report from the project.
Vegard Engen
Representant for the CPIP WG
- --
This article has been digitally signed by the moderator, using PGP.
http://www.iki.fi/mjr/cola-public-key.asc has PGP key for validating
signature.
Send submissions for comp.os.linux.announce to:
linux-announce@xxxxxxxxxxxxx
PLEASE remember a short description of the software and the LOCATION.
This group is archived at http://www.iki.fi/mjr/linux/cola.html
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: latin1
iQCVAgUBOs4aWlrUI/eHXJZ5AQGxsgP+MhwwMJWFbCYVBKjQG53EplTExk1a8n+V
UPm5btuKRhHnt8xYOUcyC+ezYdJEadg+OKNZABSeNp2YnPqmkfYBMn+/9qeqlQlp
Co0zdiAXbfbp1/drs0rdtoCblK+p7Iyspoa0tDXExxgpMy6LKOdCmMoPGMfmmClr
F8VIMpy2c6s=
=8lTc
-----END PGP SIGNATURE-----
`--------------- Forwarded message (end)
--------------Boundary-01=_QMLKR3W2ZJ9ILYQD7YFD
Content-Type: MESSAGE/RFC822; CHARSET=
Content-ID: <0104101242260A.01734@xxxxxxxxxxxx>
Content-Description: rfc1149 - Maitap si mislite vie ama ... (fwd)
Received: from ivo.itce.com ([192.168.1.219]) by SRV02.ruvex.bg with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
id H65ACWHG; Tue, 10 Apr 2001 12:41:07 +0300
Received: by ivo.itce.com (Postfix, from userid 0)
id E276B3E360; Tue, 10 Apr 2001 12:40:35 +0300 (EEST)
To: itexperts@xxxxxxxx
Subject: rfc1149 - Maitap si mislite vie ama ...
Message-Id: <20010410094035.E276B3E360@xxxxxxxxxxxx>
Date: Tue, 10 Apr 2001 12:40:35 +0300 (EEST)
From: root@xxxxxxxxxxxx (root)
Content-Type:
Status: R
X-Status: N
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.
Frame Format
The IP datagram is printed, on a small scroll of paper, in
hexadecimal, with each octet separated by whitestuff and blackstuff.
The scroll of paper is wrapped around one leg of the avian carrier.
A band of duct tape is used to secure the datagram's edges. The
bandwidth is limited to the leg length. The MTU is variable, and
paradoxically, generally increases with increased carrier age. A
typical MTU is 256 milligrams. Some datagram padding may be needed.
Upon receipt, the duct tape is removed and the paper copy of the
datagram is optically scanned into a electronically transmittable
form.
Discussion
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-
Waitzman [Page 1]
RFC 1149 IP Datagrams on Avian Carriers 1 April 1990
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.
Security Considerations
Security is not generally a problem in normal operation, but special
measures must be taken (such as data encryption) when avian carriers
are used in a tactical environment.
Author's Address
David Waitzman
BBN Systems and Technologies Corporation
BBN Labs Division
10 Moulton Street
Cambridge, MA 02238
Phone: (617) 873-4323
EMail: dwaitzman@xxxxxxx
Waitzman [Page 2]
===========================================================================
A mail-list of Linux Users Group - Bulgaria (bulgarian linuxers)
http://www.linux-bulgaria.org/ Hosted by Internet Group Ltd. - Stara Zagora
|