slovodefinícia
rfc
(encz)
RFC,Request For Comments [zkr.]
rfc
(foldoc)
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 (http://rfc.net/).
{W3
(http://w3.org/hypertext/DataSources/Archives/RFC_sites.html)}.
JANET UK FTP (ftp://nic.ja.net/pub/newsfiles/JIPS/rfc).
Imperial College, UK FTP (ftp://src.doc.ic.ac.uk/rfc/).
Nexor UK (http://nexor.com/public/rfc/index/rfc.html).
{Ohio State U
(http://cis.ohio-state.edu/hypertext/faq/usenet/top.html)}.

See also For Your Information, STD.

(1997-11-10)
rfc
(jargon)
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.
rfc
(vera)
RFC
Remote Function Call (SAP, CPIC)
rfc
(vera)
RFC
Request For Change (PERL, ITIL)
rfc
(vera)
RFC
Request For Comments (Internet, RFC)
podobné slovodefinícia
reference concentration (rfc)
(encz)
reference concentration (RfC),referenční koncentrace [eko.] Stanovená
koncentrace (odhadnutá v rozpětí až jednoho řádu), která při celoživotní
inhalační expozici populace (včetně citlivých podskupin) pravděpodobně
nezpůsobí poškození zdraví. RNDr. Pavel Piskač
rfc
(encz)
RFC,Request For Comments [zkr.]
rfcm
(encz)
RFCM,Radio Frequency Countermeasure [zkr.] [voj.] Zdeněk Brož a
automatický překlad
sirfc
(encz)
SIRFC,Suite of Integrated Radar Frequency Countermeasures (Army) [zkr.]
[voj.] Zdeněk Brož a automatický překlad
rfc
(foldoc)
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 (http://rfc.net/).
{W3
(http://w3.org/hypertext/DataSources/Archives/RFC_sites.html)}.
JANET UK FTP (ftp://nic.ja.net/pub/newsfiles/JIPS/rfc).
Imperial College, UK FTP (ftp://src.doc.ic.ac.uk/rfc/).
Nexor UK (http://nexor.com/public/rfc/index/rfc.html).
{Ohio State U
(http://cis.ohio-state.edu/hypertext/faq/usenet/top.html)}.

See also For Your Information, STD.

(1997-11-10)
rfc 1014
(foldoc)
RFC 1014

The RFC defining
eXternal Data Representation.

(rfc:1014).

(1994-12-13)
rfc 1034
(foldoc)
RFC 1034

One of the RFCs defining the {Domain
Name System}.

(rfc:1034).

(1997-12-15)
rfc 1035
(foldoc)
RFC 1035

One of the RFCs defining the {Domain
Name System}.

(rfc:1035).

(1997-12-15)
rfc 1057
(foldoc)
RFC 1057

The RFC defining Sun RPC.

(rfc:1057).

(2003-06-04)
rfc 1058
(foldoc)
RFC 1058

The RFC defining {Routing Information
Protocol}. Updated by RFC 1388.

(rfc:1058).

(1994-11-30)
rfc 1081
(foldoc)
RFC 1081

The RFC defining POP3, {Post Office
Protocol} version 3.

(rfc:1081).

(1994-12-12)
rfc 1094
(foldoc)
RFC 1094

The RFC defining {Sun
Microsystems}'s Network File System (NFS).

(rfc:1094).

(1994-12-12)
rfc 1112
(foldoc)
RFC 1112

The RFC describing MBONE.

(rfc:1112).

(1994-11-11)
rfc 1119
(foldoc)
RFC 1119

The RFC defining {Network Time
Protocol}.

(rfc:1119).

(1994-11-30)
rfc 1123
(foldoc)
RFC 1123

The RFC "Requirements for Internet
Hosts Application and Support" which clarifies or changes the
specification of protocols given in earlier RFCs.

RFC 1123 defines the terms "MUST", "SHOULD", "MAY",
"unconditionally compliant", "conditionally compliant".
Capitals are used to emphasise that the official definition of
the word is being used.

MUST or REQUIRED means an absolute requirement for
conformance.

SHOULD or RECOMMENDED means the item can be ignored under
certain circumstances, although the full implications should
be understood.

MAY or OPTIONAL means the implementor can choose, usually
depending on whether it is needed or not.

Something "unconditionally compliant" meets all the MUST and
SHOULD requirements, "conditionally compliant" meets all the
MUST requirements and "not compliant" - does not meet some
MUST requirement.

For example, RFC 1123 amends RFC952 to say software MUST
handle either a letter or a digit as the first character of a
hostname.

(rfc:1123).

(1996-01-13)
rfc 1156
(foldoc)
RFC 1156

The RFC which established the MIB I {Management
Information Base} standard.

(rfc:1156).

(1994-11-14)
rfc 1157
(foldoc)
RFC 1157

The RFC defining {Simple Network
Management Protocol}.

(rfc:1157).

(1994-11-14)
rfc 1171
(foldoc)
RFC 1171

The RFC defining the {Point-to-Point
Protocol}.

(rfc:1171).

(1994-12-13)
rfc 1208
(foldoc)
RFC 1208

The RFC defining many of the
network-related terms in this dictionary.

(rfc:1208).

["A Glossary of Networking Terms", Jacobsen, O., and D. Lynch,
RFC 1208, Interop, Inc., March 1991.]

(1996-08-06)
rfc 1213
(foldoc)
RFC 1213

The RFC which definied the MIB II
Management Information Base.

(rfc:1213).

(1994-11-14)
rfc 1267
(foldoc)
RFC 1267

One of the RFCs describing {Border
Gateway Protocol}.

(rfc:1267).
rfc 1268
(foldoc)
RFC 1268

One of the RFCs describing {Border
Gateway Protocol}.

(rfc:1268).
rfc 1304
(foldoc)
RFC 1304

One of the RFCs describing {SMDS
Interface Protocol}.

(rfc:1304).

(2000-09-02)
rfc 1321
(foldoc)
RFC 1321

The RFC defining the {Message Digest
5} algorithm.

(rfc:1321).

(1996-08-04)
rfc 1334
(foldoc)
RFC 1334

The RFC defining
Challenge-Handshake Authentication Protocol and {Password
Authentication Protocol}.

(rfc:1334).

(1996-03-23)
rfc 1341
(foldoc)
RFC 1341

The June 1992 RFC defining
Multipurpose Internet Mail Extensions (MIME). This RFC
has been obsoleted by RFC 2045, RFC 2046, RFC 2047, {RFC
2048}, RFC 2049, and BCP0013.

(rfc:1341).

(1997-08-30)
rfc 1347
(foldoc)
RFC 1347

One of the RFCs describing the TUBA
protocol.

(rfc:1347).

(1997-08-30)
rfc 1350
(foldoc)
RFC 1350

The RFC defining TFTP.

(rfc:1350).

(1997-08-30)
rfc 1388
(foldoc)
RFC 1388

An update to RFC 1058, the RFC
defining Routing Information Protocol.

(rfc:1388).

(1994-11-30)
rfc 1436
(foldoc)
RFC 1436

The RFC defining the Internet
Gopher protocol.

(rfc:1436).

(1995-11-16)
rfc 1441
(foldoc)
RFC 1441

The RFC introducing SNMP v2.

(rfc:1441).

(1997-11-23)
rfc 1442
(foldoc)
RFC 1442

The RFC defining SMI for SNMP v2.

(rfc:1442).

(1997-11-23)
rfc 1443
(foldoc)
RFC 1443

The RFC defining textual conventions
for SNMP v2.

(rfc:1443).

(1997-11-23)
rfc 1444
(foldoc)
RFC 1444

The RFC defining conformance
statements for SNMP v2.

(rfc:1444).

(1997-11-23)
rfc 1445
(foldoc)
RFC 1445

The RFC defining the administrative
model for SNMP v2.

(rfc:1445).

(1997-11-23)
rfc 1446
(foldoc)
RFC 1446

The RFC defining security protocols
for SNMP v2.

(rfc:1446).

(1997-11-23)
rfc 1447
(foldoc)
RFC 1447

The RFC defining Party MIB for
SNMP v2.

(rfc:1447).

(1997-11-23)
rfc 1448
(foldoc)
RFC 1448

The RFC defining protocol operations
for SNMP v2.

(rfc:1448).

(1997-11-23)
rfc 1449
(foldoc)
RFC 1449

The RFC defining transport mappings
for SNMP v2.

(rfc:1449).

(1997-11-23)
rfc 1450
(foldoc)
RFC 1450

The RFC defining MIB for SNMP v2.

(rfc:1450).

(1997-11-23)
rfc 1451
(foldoc)
RFC 1451

The RFC defining {Manager to Manger
MIB}.

(rfc:1451).

(1997-11-23)
rfc 1452
(foldoc)
RFC 1452

The RFC describing coexistance
between SNMP v1 and SNMP v2.

(rfc:1452).

(1995-02-15)
rfc 1475
(foldoc)
RFC 1475

The RFC describing the TP/IX
protocol.

(rfc:1475).

(1995-04-03)
rfc 1508
(foldoc)
RFC 1508

One of the RFCs defining GSS-API.

(rfc:1508).

(1996-05-19)
rfc 1509
(foldoc)
RFC 1509

One of the RFCs defining GSS-API.

(rfc:1509).

(1996-05-19)
rfc 1520
(foldoc)
RFC 1520

The RFC defining {Classless
Inter-Domain Routing}.

(rfc:1520).

(1996-10-01)
rfc 1521
(foldoc)
RFC 1521

An RFC defining {Multipurpose Internet
Mail Extensions} (MIME). This RFC has been obsoleted by
RFC 2045, RFC 2046, RFC 2047, RFC 2048, RFC 2049,
and BCP0013.

(rfc:1521).

(1997-11-23)
rfc 1526
(foldoc)
RFC 1526

One of the RFCs describing the TUBA
protocol.

(rfc:1526).

(1997-11-23)
rfc 1531
(foldoc)
RFC 1531

The original RFC defining DHCP,
obsoleted by RFC 2131.

(rfc:1531).

(1998-11-20)
rfc 1550
(foldoc)
RFC 1550

An RFC white paper on IPng.

(rfc:1550).

(1995-04-03)
rfc 1561
(foldoc)
RFC 1561

One of the RFCs describing the TUBA
protocol.

(rfc:1561).

(1997-11-23)
rfc 1568
(foldoc)
RFC 1568

An RFC defining the {Simple Network
Paging Protocol} (SNPP) which is designed to support
Internet access to paging services such as those based on
the Telocator Alphanumeric Protocol. See also RFC 1861.

(rfc:1568).

(1996-06-24)
rfc 1591
(foldoc)
RFC 1591

The RFC defining the {Domain Name
System}. Written by J. Postel in March 1994.

(2001-05-14)
rfc 1630
(foldoc)
RFC 1630

The RFC defining the {Universal
Resource Identifier}.

(rfc:1630).

(1995-01-13)
rfc 1661
(foldoc)
RFC 1661

The RFC defining {Point-to-Point
Protocol}.

(rfc:1661).

(1997-02-05)
rfc 1700
(foldoc)
RFC 1700

The original RFC defining "Assigned
Numbers" such as standard "well-known" TCP and UDP port
numbers, now superseded by RFC 3232.

(rfc:1700).

(2001-04-08)
rfc 1701
(foldoc)
RFC 1701

The RFC defining {Generic Routing
Encapsulation}.

See also RFC 1702.

(rfc:1701).

(1997-04-02)
rfc 1702
(foldoc)
RFC 1702

The RFC defining {Generic Routing
Encapsulation} over IP.

(rfc:1702).

(1997-04-02)
rfc 1707
(foldoc)
RFC 1707

The RFC defining CATNIP.

(rfc:1707).

(1996-03-23)
rfc 1730
(foldoc)
RFC 1730

An old RFC defining IMAP, obsoleted
by RFC 2060, RFC 2061 and others.

(rfc:1730).

(1996-03-11)
rfc 1756
(foldoc)
RFC 1756

The RFC describing Remote Write Protocol.

(rfc:1756).

(1996-09-08)
rfc 1760
(foldoc)
RFC 1760

The RFC describing the S/KEY One-Time Password
system.

(rfc:1760).

(2000-01-31)
rfc 1777
(foldoc)
RFC 1777

The RFC defining {Lightweight
Directory Access Protocol}.

(rfc:1777).

(1996-08-23)
rfc 1778
(foldoc)
RFC 1778

The RFC that defines the requirements
that must be satisfied by encoding rules used to render X.500
Directory attribute syntaxes into a form suitable for use in
LDAP.

(rfc:1778).

(2002-03-02)
rfc 1795
(foldoc)
RFC 1795

The RFC that defines {Data Link
Switching}.

(rfc:1795).

(2008-01-11)
rfc 1823
(foldoc)
RFC 1823

The RFC defining the C language
application program interface to the {Lightweight Directory
Access Protocol}.

(rfc:1823).

(1996-11-28)
rfc 1825
(foldoc)
RFC 1825

The RFC describing security
mechanisms for Internet Protocol version 4 and {IP version
6} and the services that they provide.

(rfc:1825).

(1997-07-09)
rfc 1831
(foldoc)
RFC 1831

The RFC describing ONC RPC.

(2003-06-04)
rfc 1861
(foldoc)
RFC 1861

The RFC defining {Simple Network
Paging Protocol}. See also RFC 1568.

(rfc:1861).

(1997-04-25)
rfc 1938
(foldoc)
RFC 1938

The RFC describing a proposed
standard for a One-Time Password system, obsoleted by {RFC
2289}.

["A One-Time Password System.", N. Haller & C. Metz].

(rfc:1938).

(2000-03-05)
rfc 1951
(foldoc)
RFC 1951

The RFC describing deflate compression.

(rfc:1951).

(1997-06-21)
rfc 1959
(foldoc)
RFC 1959

The RFC defining a URL format for
the Lightweight Directory Access Protocol.

(rfc:1959).

(1996-11-28)
rfc 1960
(foldoc)
RFC 1960

The RFC defining the human-readable
format of search filters used with the {Lightweight Directory
Access Protocol}.

(rfc:1960).

(2002-03-02)
rfc 2045
(foldoc)
RFC 2045

One of the RFCs defining MIME.

(rfc:2045).

(1999-10-29)
rfc 2046
(foldoc)
RFC 2046

One of the RFCs defining MIME.

(rfc:2046).

(1999-10-29)
rfc 2047
(foldoc)
RFC 2047

One of the RFCs defining MIME.

(rfc:2047).

(1999-10-29)
rfc 2048
(foldoc)
RFC 2048

The RFC explaining
registration of MIME types.

(rfc:2048).

(1998-02-11)
rfc 2049
(foldoc)
RFC 2049

One of the RFCs defining MIME.

(rfc:2049).

(1999-10-29)
rfc 2060
(foldoc)
RFC 2060

One of the RFCs describing IMAP.

(rfc:2060).

(1999-03-14)
rfc 2061
(foldoc)
RFC 2061

One of the RFCs describing IMAP.

(rfc:2061).

(1999-03-14)
rfc 2068
(foldoc)
RFC 2068

The RFC defining HTTP version 1.1.

(rfc:2068).

(1997-05-03)

Nenašli ste slovo čo ste hľadali ? Doplňte ho do slovníka.

na vytvorenie tejto webstránky bol pužitý dictd server s dátami z sk-spell.sk.cx a z iných voľne dostupných dictd databáz. Ak máte klienta na dictd protokol (napríklad kdict), použite zdroj slovnik.iz.sk a port 2628.

online slovník, sk-spell - slovníkové dáta, IZ Bratislava, Malé Karpaty - turistika, Michal Páleník, správy, údaje o okresoch V4