Factbites
 Where results make sense
About us   |   Why use us?   |   Reviews   |   PR   |   Contact us  

Topic: RFC 2549


Related Topics
Grr

  
  RFC 2549. Who is RFC 2549? What is RFC 2549? Where is RFC 2549? Definition of RFC 2549. Meaning of RFC 2549.
The RFCs issued by the Internet Engineering Task Force (IETF) and its predecessors are the most well-known series known as 'RFC', and is almost always what is meant by RFC without further qualification; however, other organizations have in the past also issued series called 'RFCs'.
The RFCs are unusual in that they are floated by technical experts acting on their own initiative and reviewed by the Internet at large, rather than formally promulgated through an institution such as ANSI.
RFC 1, entitled "Host Software", was issued on April 7 1969 by Steve Crocker.
www.knowledgerush.com /kr/encyclopedia/RFC_2549   (2428 words)

  
 Website dedicated to Recreation, Humor, Computer & RFCs   (Site not responding. Last check: 2007-10-16)
RFC 2795: The Infinite Monkey Protocol Suite (IMPS) - A protocol suite which supports an infinite number of monkeys that sit at an infinite number of typewriters in order to determine when they have either produced the entire works of William Shakespeare or a good television show.
RFC 2323: IETF Identification and Security Guidelines (FTP) - "This RFC is meant to represent a guideline by which the IETF conferences may run more efficiently with regards to identification and security protocols, with specific attention paid to a particular sub-group within the IETF: "facial hairius extremis".
RFC 1149: A Standard for the Transmission of IP Datagrams on Avian Carriers (FTP) - "This memo describes an experimental method for the encapsulation of IP datagrams in avian carriers.
www.findtutorials.com /internet/dir/Recreation/Humor/Computer/RFCs   (742 words)

  
 RFC 2549 (rfc2549) - IP over Avian Carriers with Quality of Service
Abstract This memo amends RFC 1149, "A Standard for the Transmission of IP Datagrams on Avian Carriers", with Quality of Service information.
References Waitzman, D., "A Standard for the Transmission of IP Datagrams on Avian Carriers", RFC 1149, 1 April 1990.
RFC 2549: I'm wondering about using un-powered contactless smart-card technology so that...
www.faqs.org /rfcs/rfc2549.html   (731 words)

  
 Request for Comments - Wikipedia, the free encyclopedia
RFCs can be obtained on the Internet from the RFC Editor [1], the IETF [2], or many other sites, principally using the Web, but also through anonymous FTP, gopher, and other Internet document-retrieval systems.
RFC 1, entitled "Host Software", was written by Steve Crocker from the University of California, Los Angeles, and published on April 7, 1969.
RFC 2047 specifies a standard way of encoding non US-ASCII characters into a string that identifies both the character set to use and the actual characters.
en.wikipedia.org /wiki/Request_for_Comments   (2380 words)

  
 April 1st RFC
RFC 1149 - Full text of RFC 1149 Standard for the transmission of IP datagrams on Avian Carriers.
RFC 2325 - Full text of RFC 2325 Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2.
RFC 2549 - Full text of RFC 2549 IP over Avian Carriers with Quality of Service.
www.sciencedaily.com /encyclopedia/april_1st_rfc   (677 words)

  
 RFC2549   (Site not responding. Last check: 2007-10-16)
RFC 2549 IP over Avian Carriers with QoS 1 April 1999 Weighted fair queueing (WFQ) MAY be implemented using scales, as shown: __ _____/-----\ / o\ <____ _____\_/ >-- +-----+ \ / /______/
RFC 2549 IP over Avian Carriers with QoS 1 April 1999 NATs are not recommended either -- as with many protocols, modifying the brain-embedded IP addresses is difficult, plus Avian Carriers MAY eat the NATs.
RFC 2549 IP over Avian Carriers with QoS 1 April 1999 STATUS current DESCRIPTION "Pulse rate of carrier, as measured in neck.
rfc.net /rfc2549.html   (758 words)

  
 RFC 2549: Definition and Links by Encyclopedian.com - All about RFC 2549
IP over Avian Carriers with Quality of Service or RFC 2549 is a humorous Request For Comments by the internet engineering task force IETF.
It was written by D. Waitzman and released on April Fool's Day 1999; it is an April 1st RFC.
It updates Waitzman's earlier RFC 1149 about the transmission of IP traffic via carrier pigeons.
www.encyclopedian.com /rf/RFC-2549.html   (89 words)

  
 [No title]
Standards Track [Page 33] RFC 2459 Internet X.509 Public Key Infrastructure January 1999 Finally, the semantics of subject alternative names that include wildcard characters (e.g., as a placeholder for a set of names) are not addressed by this specification.
Standards Track [Page 52] RFC 2459 Internet X.509 Public Key Infrastructure January 1999 The goal of path validation is to verify the binding between a subject distinguished name or subject alternative name and subject public key, as represented in the "end entity" certificate, based on the public key of the "most-trusted CA".
Standards Track [Page 54] RFC 2459 Internet X.509 Public Key Infrastructure January 1999 (4) the subject and issuer names chain correctly (that is, the issuer of this certificate was the subject of the previous certificate.) (b) Verify that the subject name and subjectAltName extension (critical or noncritical) is consistent with the constrained subtrees state variables.
ietf.org /rfc/rfc2459.txt   (9282 words)

  
 Pantek - Expert Linux and Open Source Services: : RFC #2549: IP over Avian Carriers with Quality of Service. D. ...   (Site not responding. Last check: 2007-10-16)
RFC Archives: Library > General > Rfc > Rfc2549
Waitzman Experimental [Page 1] RFC 2549 IP over Avian Carriers with QoS 1 April 1999 Weighted fair queueing (WFQ) MAY be implemented using scales, as shown: __ _____/-----\ / o\ <____ _____\_/ >-- +-----+ \ / /______/
Waitzman Experimental [Page 2] RFC 2549 IP over Avian Carriers with QoS 1 April 1999 NATs are not recommended either -- as with many protocols, modifying the brain-embedded IP addresses is difficult, plus Avian Carriers MAY eat the NATs.
www.pantek.com /library/general/rfc/rfc2549.html   (743 words)

  
 RFC Index   (Site not responding. Last check: 2007-10-16)
This RFC explores mechanisms to prevent a remotely managed entity from burdening a manager or network with an unexpected amount of network management information, and to ensure delivery of "important" information.
This RFC defines a protocol to provide a mail checking service to be used between a client and server pair.
This RFC describes an open distance vector routing protocol for use at all levels of the internet, from isolated LANs to the major routers of an international commercial network provider.
www.potaroo.net /ietf/status_experimental.html   (4281 words)

  
 Recreation: Humor: Computer: RFCs   (Site not responding. Last check: 2007-10-16)
RFC 2549: IP over Avian Carriers with Quality of Service (FTP)
"This RFC is meant to represent a guideline by which the IETF conferences may run more efficiently with regards to identification and security protocols, with specific attention paid to a particular sub-group within the IETF: "facial hairius extremis".
RFC 1149: A Standard for the Transmission of IP Datagrams on Avian Carriers (FTP)
www.indianartcraft.com /dir.cgi/Recreation/Humor/Computer/RFCs   (621 words)

  
 Ip Over Avian Carriers   (Site not responding. Last check: 2007-10-16)
IP over Avian Carriers or RFC 1149 is a humorous Request for Comments document issued by the Internet Engineering Task Force.
It was written by D. Waitzman and released on April Fool's Day 1990, one of the April 1st RFCs.
RFC 1149 was actually implemented by the Bergen Linux User Group.
www.wikiverse.org /ip-over-avian-carriers   (145 words)

  
 Reactions to RFC 3514
In RFC 3514 you don't appear to discuss the conditions that will cause the so called evil bit to be set.
However, if we combine RFC 3514 with RFC 2549 (which updated RFC 1149), then a carrier with suitable conditioning can be made to detect evil intent and set the bit accordingly.
Another variation of 2549, using a K9 carrier can be made particularly effective by biting the attacker as well as setting the evil bit.
www.cs.columbia.edu /~smb/3514.html   (611 words)

  
 WYAE - Joke-RfCs
While a "normal" RfC (Request for Comments) usually defines internet standards and protocols, there are a number of RfCs and HowTos published on 1st of April - or for a similar purpose.
Well, some (RfC 1149 and 2322) in fact were implemented or are in practical use.
RfC 2322 actually is being used successfully at hacking camps like HIP (Hacking in Progress) or the CCCamp.
www.wyae.de /docs/joke-rfcs.php   (284 words)

  
 April Fools' Day RFC's   (Site not responding. Last check: 2007-10-16)
This RFC describes a protocol to dynamically hand out ip-numbers on field networks and small events that don't necessarily have a clear organisational body.
This memo amends RFC 1149 with Quality of Service information.
This memo describes a protocol suite which supports an infinite number of monkeys that sit at an infinite number of typewriters in order to determine when they have either produced the entire works of William Shakespeare or a good television show.
www.xinu.nl /unix/humour/april-1st-rfcs.html   (335 words)

  
 DomainsAreFree - Definition of Request For Comments
RFC are published by the RFC Editor who is under the general direction of the IAB.
RFCs can be obtained on the Internet from http://www.ietf.org/rfc.html or many other sites, using anonymous FTP, gopher, and other Internet document-retrieval systems.
RFC 2045 (http://www.rfc-editor.org/rfc/rfc2045.txt), RFC 2046 (http://www.rfc-editor.org/rfc/rfc2046.txt), RFC 2047 (http://www.rfc-editor.org/rfc/rfc2047.txt), RFC 2048 (http://www.rfc-editor.org/rfc/rfc2048.txt), RFC 2049 (http://www.rfc-editor.org/rfc/rfc2049.txt) (MIME)
www.domainsarefree.com /glossary/Request_for_Comments.html   (2593 words)

  
 Internet Entertainment (Linktionary term)
RFC 602 ('The Stockings Were Hung by the Chimney with Care,' Bob Metcalfe, December 1973)
RFC 1149 (A Standard for the Transmission of IP Datagrams on Avian Carriers, D. Waitzman, April 1990)
RFC 1437 (The Extension of MIME Content-Types to a New Medium, Borenstein and Linimon, April 1993)
www.linktionary.com /i/internet_ent.html   (467 words)

  
 April 1 RFCs   (Site not responding. Last check: 2007-10-16)
RFC 2322: Management of IP numbers by peg-dhcp
RFC 2325: Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2
RFC 1437: The Extension of MIME Content-Types to a New Medium
klubkev.org /~ksulliva/rfc-april1   (219 words)

  
 Marcel Waldvogel: Fun with RFCs
I thought you might be interested in RFC 2795, which contains a novel protocol that might be used in the video project.
If we want to go that way, then interoperation with the wireless communications standard (RFC 1149,* with the QoS extensions described in RFC 2549) is a definitive MUST.
If we plan on making our stuff into an Internet RFC, a good description of the standards process can be found in RFC 2551.
marcel.wanda.ch /Fun/RFC   (414 words)

  
 Nerdy Conservative: Warning! Nerd Humor: RFC 2549
Those of us who work in the technology industry, are aware that everything we do is under the watchful eyes of the IEEE, ISO, UL as well as the RFC documented standards.
Therefore, much of my work falls under the auspices of IEEE 802.1 and RFCs.
Yeah, it's been around for years, but I will still run into colleagues who don't believe me when I say that there is actually an RFC on...
nerdyconservative.blogspot.com /2004/11/warning-nerd-humor-rfc-2549.html   (181 words)

  
 IP over Avian Carriers : RFC 1149
IP over Avian Carriers or RFC 1149 is a humorous Request For Comments by the internet engineering taskforce IETF.
Waitzman released an improvement of his protocol on April 1, 1999: RFC 2549, IP over Avian Carriers with Quality of Service.
Full text of RFC 1149 (http://www.ietf.org/rfc/rfc1149.txt) Standard for the transmission of IP datagrams on avian carriers.
www.fastload.org /rf/RFC_1149.html   (178 words)

  
 RFC 2550 (rfc2550) - Y10K and Beyond
RFC 2550: As far as I se, the list of Open Issues (section 5) fails to list the problem of...
RFC 2550: With the possibility of space travel to the distant stars and possibly distant...
RFC 2550: Excellent :) Have you considered the :) implications for wristwatches ?
www.faqs.org /rfcs/rfc2550.html   (2873 words)

  
 RFC Archive
Within the RFCs is there several very amusing RFCs of more or less serious nature.
Here is a small index that I hope will bring a smile to your face and possibly understand some more bizzare elements of the network peoples odd nature.
This compiled list of such RFCs is called FYE - For Your Enjoyment by myself and there is no "official" name for it to my knowledge.
home.swipnet.se /cfmd/rfc/dir/fye.html   (155 words)

  
 BGPexpert.com archive for 2002 second quarter
Probably the most famous of all is RFC 1149, which was updated in RFC 2549:
It took some time, but in 2001 the Bergen Linux User Group implemented RFC 1149 and carried out some tests.
Here are more April first RFCs: RFC 1097, RFC 1217, RFC 1313, RFC 1437, RFC 1438, RFC 1605, RFC 1606, RFC 1607, RFC 1776, RFC 1924, RFC 1925, RFC 1926, RFC 1927, RFC 2100, RFC 2321, RFC 2323, RFC 2324, RFC 2550, RFC 2551, RFC 2795.
www.bgpexpert.com /archive2002q2.php   (582 words)

  
 Request for comment - Questionz.net , answers to all your questions   (Site not responding. Last check: 2007-10-16)
(Format: TXT=109200 bytes) (Obsoletes RFC 0733) (Obsoleted by RFC 2822) (Updated by RFC 1123, RFC 1138, RFC 1148, RFC 1327, RFC 2156) (Status: HISTORIC) This is an important early RFC from the IETF that specified the format of e-mail messages exchanged between computers on the Internet.
(Format: TXT=110695 bytes) (Obsoletes RFC 0822) (Status: PROPOSED STANDARD) This standard specifies a syntax for text messages that are sent between computer users, within the framework of electronic mail messages.
There are some mail clients that are not RFC 2047 Compliant, if you are using one of this clients you are strongly encuraged to change your mail client or to update it to a compliant version: Eudora 4: Double quote characters are encoded with a Windows codpage and are eight-bit characters.
www.questionz.net /History_of_the_Internet/RFC.html   (2076 words)

  
 Josh Simon's Fun Information: Funny RFCs   (Site not responding. Last check: 2007-10-16)
RFC 1149--A Standard for the Transmission of IP Datagrams on Avian Carriers
RFC 2325--Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2
RFC 2549--IP over Avian Carriers with Quality of Service
www.clock.org /~jss/play/rfc.html   (42 words)

  
 hjp: doc: RFC 2549: IP over Avian Carriers with Quality of Service
RFC 2549 IP over Avian Carriers with QoS 1 April 1999
NATs are not recommended either -- as with many protocols, modifying the brain-embedded IP addresses is difficult, plus Avian Carriers MAY eat the NATs.
There is ongoing litigation about which is the prior art: carrier or egg.
www.hjp.at /doc/rfc/rfc2549.html   (795 words)

  
 rfc 2549 reference for Network Programming in .NET with C# & Visual Basic .NET (VB.NET)
rfc 2549 reference for Network Programming in.NET with C# & Visual Basic.NET (VB.NET)
If you wish, you can use the navigation bar on the left hand side, to view other articles.
Waitzman Experimental [Page 1] RFC 2549 IP over Avian Carriers with QoS 1 April 1999 Weighted fair queueing (WFQ) MAY be implemented using scales, as shown: __ _____/-----\ / o\
www.webtropy.com /articles/rfc.aspx?rfc=2549   (781 words)

Try your search on: Qwika (all wikis)

Factbites
  About us   |   Why use us?   |   Reviews   |   Press   |   Contact us  
Copyright © 2005-2007 www.factbites.com Usage implies agreement with terms.