ZebraWords.com - The Definition of 'Rfc 1985', Synonyms of 'Rfc 1985' & More on 'Rfc 1985'

No results could be found matching the exact term RFC 1985.

Try one of these suggestions:

rabbies rabbis rabies rabious raffish rappage ravage ravehook ravish raw rebec rebeck rebozo rebuke rebus reebok refix refuge refugee refuse rehboc reoppose repace repack repass repkie repose repouss'e revise revoice revoke rhebok rhebuck rheeboc ribes ribose ripsaw rivage rivose roebuck ropish rubbage rubbish rubiaceae rubies rubigo rubious rubus rufous raphus rbc reap rebecca rebekah reface rhapis rhibhus ribhus roof rooibos rubbishy raps rbac rbbs rboc rfc rfic rfog rfq rfs rips rpc rpc2 rpcs rpg rps rvc ravs r:base robex rpg-ii rufus reeves refugio ravia, rives roebuck, roff, ruby,

Consider searching for the individual words RFC, or 1985.

Dictionary Results for RFC:

1. V.E.R.A. -- Virtual Entity of Relevant Acronyms (February 2016)

RFC
       Remote Function Call (SAP, CPIC)

2. V.E.R.A. -- Virtual Entity of Relevant Acronyms (February 2016)

RFC
       Request For Change (PERL, ITIL)

3. V.E.R.A. -- Virtual Entity of Relevant Acronyms (February 2016)

RFC
       Request For Comments (Internet, RFC)

4. The Jargon File (version 4.4.7, 29 Dec 2003)

RFC
 /R?F?C/, n.

    [Request For Comment] One of a long-es?tab?lished series of numbered
    Internet informational documents and standards widely followed by
    commercial software and freeware in the Internet and Unix communities.
    Perhaps the single most influential one has been RFC-822 (the Internet
    mail-format standard). 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. For this reason, they remain known as RFCs even once adopted
    as standards.

    The RFC tradition of pragmatic, experience-driven, after-the-fact standard
    writing done by individuals or small working groups has important
    advantages over the more formal, committee-driven process typical of ANSI
    or ISO. Emblematic of some of these advantages is the existence of a
    flourishing tradition of ?joke? RFCs; usually at least one a year is
    published, usually on April 1st. Well-known joke RFCs have included 527 (?
    ARPAWOCKY?, R. Merryman, UCSD; 22 June 1973), 748 (?Telnet Randomly-Lose
    Option?, Mark R. Crispin; 1 April 1978), and 1149 (?A Standard for the
    Transmission of IP Datagrams on Avian Carriers?, D. Waitzman, BBN STC; 1
    April 1990). The first was a Lewis Carroll pastiche; the second a parody of
    the TCP-IP documentation style, and the third a deadpan skewering of
    standards-document legalese, describing protocols for transmitting Internet
    data packets by carrier pigeon (since actually implemented; see Appendix
    A). See also Infinite-Monkey Theorem.

    The RFCs are most remarkable for how well they work ? they frequently
    manage to have neither the ambiguities that are usually rife in informal
    specifications, nor the committee-perpetrated misfeatures that often haunt
    formal standards, and they define a network that has grown to truly
    worldwide proportions.

5. The Free On-line Dictionary of Computing (30 December 2018)

Request For Comments
RFC

    (RFC) One of a series, begun in 1969, of numbered
   Internet informational documents and standards widely
   followed by commercial software and freeware in the
   Internet and Unix communities.  Few RFCs are standards but
   all Internet standards are recorded in RFCs.  Perhaps the
   single most influential RFC has been RFC 822, the Internet
   electronic mail format standard.

   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.  For this reason, they remain
   known as RFCs even once adopted as standards.

   The RFC tradition of pragmatic, experience-driven,
   after-the-fact standard writing done by individuals or small
   working groups has important advantages over the more formal,
   committee-driven process typical of ANSI or ISO.

   Emblematic of some of these advantages is the existence of a
   flourishing tradition of "joke" RFCs; usually at least one a
   year is published, usually on April 1st.  Well-known joke RFCs
   have included 527 ("ARPAWOCKY", R. Merryman, UCSD; 22 June
   1973), 748 ("Telnet Randomly-Lose Option", Mark R. Crispin; 1
   April 1978), and 1149 ("A Standard for the Transmission of IP
   Datagrams on Avian Carriers", D. Waitzman, BBN STC; 1 April
   1990).  The first was a Lewis Carroll pastiche; the second a
   parody of the TCP/IP documentation style, and the third a
   deadpan skewering of standards-document legalese, describing
   protocols for transmitting Internet data packets by carrier
   pigeon.

   The RFCs are most remarkable for how well they work - they
   manage to have neither the ambiguities that are usually rife
   in informal specifications, nor the committee-perpetrated
   misfeatures that often haunt formal standards, and they
   define a network that has grown to truly worldwide
   proportions.

   <rfc.net>.
   <W3>.
   <JANET UK FTP>.
   <Imperial College, UK FTP>.
   <Nexor UK>.
   <Ohio State U>.

   See also For Your Information, STD.

   (1997-11-10)

Common Misspellings >