| podobné slovo | definícia |
protocol
(mass) | protocol
- protokol |
protocols
(mass) | protocols
- protokoly |
file transfer protocol
(msas) | File Transfer Protocol
- FTP |
file transfer protocol
(msasasci) | File Transfer Protocol
- FTP |
communications protocol
(encz) | communications protocol, n: |
file transfer protocol
(encz) | file transfer protocol, n: |
helsinki protocol.
(encz) | Helsinki Protocol.,Helsinský protokol [eko.] RNDr. Pavel Piskač |
hypertext transfer protocol
(encz) | hypertext transfer protocol, n: |
montreal protocol.
(encz) | Montreal Protocol.,Montrealský protokol [eko.] RNDr. Pavel Piskač |
protocol
(encz) | protocol,protokol n: |
protocols
(encz) | protocols,protokoly n: pl. Zdeněk Brož |
transmission control protocol
(encz) | transmission control protocol, n: |
transmission control protocol/internet protocol
(encz) | transmission control protocol/internet protocol, n: |
file-transfer protocol
(czen) | file-transfer protocol,FTP Zdeněk Brož |
simple mail transfer protocol
(czen) | Simple Mail Transfer Protocol,SMTP[zkr.] |
system monitoring display protocol
(czen) | System Monitoring Display Protocol,SMDP[zkr.] |
file transfer protocol
(gcide) | ftp \ftp\, FTP \FTP\([e^]f`t[=e]*p[=e]"), n. [acronym from File
Transfer Protocol.] (Computers)
An acronym for file transfer protocol, a standardized
protocol used to allow transmission of files between
computers; as, send me the file by ftp. It consists of a set
of coded signals which are transmitted between computers, and
which inform the receiving computer of the nature of a packet
of information to be transmitted, and inform the transmitting
computer when a packet has been successfully received.
[acronym]
[PJC] ftp |
Protocolist
(gcide) | Protocolist \Pro"to*col`ist\, n.
One who draughts protocols.
[1913 Webster] |
anonymous file transfer protocol
(wn) | anonymous file transfer protocol
n 1: a common way to make software available; users are allowed
to log in as `guest' without a password and copy whatever
has been made available [syn: anonymous ftp, {anonymous
file transfer protocol}] |
communications protocol
(wn) | communications protocol
n 1: (computer science) rules determining the format and
transmission of data [syn: protocol, {communications
protocol}] |
file transfer protocol
(wn) | file transfer protocol
n 1: protocol that allows users to copy files between their
local system and any system they can reach on the network
[syn: file transfer protocol, FTP] |
hypertext transfer protocol
(wn) | hypertext transfer protocol
n 1: a protocol (utilizing TCP) to transfer hypertext requests
and information between servers and browsers [syn:
hypertext transfer protocol, HTTP] |
protocol
(wn) | protocol
n 1: (computer science) rules determining the format and
transmission of data [syn: protocol, {communications
protocol}]
2: forms of ceremony and etiquette observed by diplomats and
heads of state
3: code of correct conduct; "safety protocols"; "academic
protocol" |
transmission control protocol
(wn) | transmission control protocol
n 1: a protocol developed for the internet to get data from one
network device to another; "TCP uses a retransmission
strategy to insure that data will not be lost in
transmission" [syn: transmission control protocol, TCP] |
transmission control protocol/internet protocol
(wn) | transmission control protocol/internet protocol
n 1: a set of protocols (including TCP) developed for the
internet in the 1970s to get data from one network device
to another [syn: {transmission control protocol/internet
protocol}, TCP/IP] |
address resolution protocol
(foldoc) | Address Resolution Protocol
ARP
(ARP) A method for finding a host's
Ethernet address from its Internet address. The sender
broadcasts an ARP packet containing the Internet address
of another host and waits for it (or some other host) to send
back its Ethernet address. Each host maintains a cache of
address translations to reduce delay and loading. ARP allows
the Internet address to be independent of the Ethernet address
but it only works if all hosts support it.
ARP is defined in RFC 826.
The alternative for hosts that do not do ARP is {constant
mapping}.
See also proxy ARP, reverse ARP.
(1995-03-20)
|
advanced data communications control protocol
(foldoc) | Advanced Data Communications Control Protocol
ADCCP
An ANSI standard bit-oriented data link
control protocol.
(1997-05-07)
|
alternating bit protocol
(foldoc) | Alternating bit protocol
(ABP) A simple data link layer protocol that
retransmits lost or corrupted messages.
Messages are sent from transmitter A to receiver B. Assume
that the channel from A to B is initialised and that there are
no messages in transit. Each message contains a data part, a
checksum, and a one-bit sequence number, i.e. a value that
is 0 or 1.
When A sends a message, it sends it continuously, with the
same sequence number, until it receives an acknowledgment
(ACK) from B that contains the same sequence number. When
that happens, A complements (flips) the sequence number and
starts transmitting the next message.
When B receives a message from A, it checks the checksum. If
the message is not corrupted B sends back an ACK with the same
sequence number. If it is the first message with that
sequence number then it is sent for processing. Subsequent
messages with the same sequence bit are simply acknowledged.
If the message is corrupted B sends back an negative/error
acknowledgment (NAK). This is optional, as A will continue
transmitting until it receives the correct ACK.
A treats corrupted ACK messages, and NAK messages in the same
way. The simplest behaviour is to ignore them all and
continue transmitting.
(2000-10-28)
|
apple address resolution protocol
(foldoc) | Apple Address Resolution Protocol
AARP
(AARP) Apple's system to allow AppleTalk
protocol to work over networks other than LocalTalk, such
as Ethernet or Token Ring. AppleTalk nodes announce
their presence to the network so that other nodes can address
messages to them. AARP maps between AppleTalk addresses and
other schemes. It is actually a general address mapping
protocol that can be used to map between addresses at any
protocol level.
[G. Sidhu, R. Andrews, and A. Oppenheimer, "Inside AppleTalk",
Addison Wesley, 1990].
(2006-04-18)
|
appletalk data stream protocol
(foldoc) | AppleTalk Data Stream Protocol
ADSP
(ADSP) A protocol which provides a simple
transport method for data accross a network.
(1996-06-18)
|
appletalk filing protocol
(foldoc) | AppleTalk Filing Protocol
(AFP) A client/server protocol used in
AppleTalk communications networks. In order for non-Apple
networks to access data in an AppleShare server, their
protocols must translate into the AFP language.
See also: Columbia AppleTalk Package.
(1998-06-28)
|
application configuration access protocol
(foldoc) | Application Configuration Access Protocol
ACAP
(ACAP) A protocol which enhances IMAP by
allowing the user to set up address books, user options, and
other data for universal access. Currently (Feb 1997) no
Internet proprietary products have implemented ACAP because
the Internet Engineering Task Force has not yet approved the
final specification. This was expected early in 1997.
["Your E-Mail Is Obsolete", Byte, Feb 1997].
(1997-05-03)
|
application protocol data unit
(foldoc) | Application Protocol Data Unit
(APDU) A packet of data exchanged between two
application programs across a network. This is the
highest level view of communication in the OSI {seven layer
model} and a single packet exchanged at this level may
actually be transmitted as several packets at a lower layer as
well as having extra information (headers) added for routing
etc.
(1995-12-19)
|
border gateway protocol
(foldoc) | Border Gateway Protocol
BGP
(BGP) An Exterior Gateway Protocol defined in
RFC 1267 and RFC 1268. BGP's design is based on
experience gained with Exterior Gateway Protocol (EGP), as
defined in STD 18, RFC 904 and EGP usage in the NSFNet
backbone, as described in RFC 1092 and RFC 1093.
(1994-11-29)
|
challenge-handshake authentication protocol
(foldoc) | Challenge-Handshake Authentication Protocol
CHAP
(CHAP) An
authentication scheme used by PPP servers to validate the
identity of the originator of the connection upon connection
or any time later.
CHAP applies a three-way handshaking procedure. After the
link is established, the server sends a "challenge" message to
the originator. The originator responds with a value
calculated using a one-way hash function. The server checks
the response against its own calculation of the expected hash
value. If the values match, the authentication is
acknowledged; otherwise the connection is usually terminated.
CHAP provides protection against playback attack through the
use of an incrementally changing identifier and a variable
challenge value. The authentication can be repeated any time
while the connection is open limiting the time of exposure to
any single attack, and the server is in control of the
frequency and timing of the challenges. As a result, CHAP
provides greater security then PAP.
CHAP is defined in RFC 1334.
(1996-03-05)
|
client to client protocol
(foldoc) | Client To Client Protocol
(CTCP) A type of protocol created to allow
structured data such as font information to be exchanged
between users on IRC. It is also used to send a query to a
user. The available CTCP commands include VERSION, FINGER,
DCC CHAT, DCC SEND, TIME, PING, ECHO, CLIENTINFO. Some
commands are not available on some IRC client software.
(1995-04-12)
|
common architecture for next generation internet protocol
(foldoc) | Common Architecture for Next Generation Internet Protocol
CATNIP
(CATNIP, originally Common Architecture
Technology for Next-generation Internet Protocol)
A network architecture designed to provide a compressed form
of the existing network layer protocols and to integrate
CLNP, IP, and IPX. It provides for any of the
transport layer protocols in use, including TP4, CLTP,
TCP, UDP, IPX, and SPX, to run over any of the network
layer protocol formats: CLNP, IP (version 4), IPX and CATNIP.
CATNIP was originally proposed by Robert L. Ullmann of {Lotus
Development Corporation} on 1993-12-22. It was published as
RFC 1707 in October 1994 but it is not an Internet
standard of any kind.
(1996-03-23)
|
common management information protocol
(foldoc) | Common Management Information Protocol
CMIP
(CMIP) Part of the OSI body of standards
specifying protocol elements that may be used to provide the
operation and notification services described in the related
standard, CMIS (Common Management Information Services).
Document: ISO/IEC 9596, or equivalent ITU X.711.
(1997-12-07)
|
connectionless protocol
(foldoc) | connectionless protocol
The data communication method in which communication
occurs between hosts with no previous setup. Packets sent
between two hosts may take different routes.
UDP is a connectionless protocol. Also called {packet
switching}. Contrast circuit switching, connection-oriented.
(2014-05-04)
|
core protocol stack
(foldoc) | Core Protocol Stack
1. A portion of the Web Services architecture for
defining and describing various Web Services.
2. The architectural protocol layers of a Bluetooth
wireless communication system, comprising the {Host
Control Interface} (HCI), {Logical Link Control and Adaptation
Protocol} (L2CAP), RS232 Serial Cable Emulation Profile
(RFCOMM), Service Discovery Protocol (SDP), and {Object
Exchange} (OBEX).
(2002-06-28)
|
direct client to client protocol
(foldoc) | Direct Client to Client Protocol
(DCC) An IRC protocol created to allow users
to chat privately and to send and receive files directly
instead of having to go thorugh the IRC servers. DCC protects
users from being monitored by IRC Server operators that have
enabled conversation logging. It also allows much more
efficient use of available bandwidth as the data does not
need to be broadcast all over the world just to reach a
specific user.
The available DCC commands include DCC CHAT (direct user to
user chat), DCC SEND (direct user to user file send) and DCC
GET (file acknowledgement from a receiver).
(1995-04-12)
|
directory access protocol
(foldoc) | Directory Access Protocol
X.500 protocol used for communication between a Directory User
Agent and a Directory System Agent.
|
dynamic host configuration protocol
(foldoc) | Dynamic Host Configuration Protocol
DHCP
(DHCP) A protocol that provides a means to
dynamically allocate IP addresses to computers on a {local
area network}. The system administrator assigns a range of
IP addresses to DHCP and each client computer on the LAN has
its TCP/IP software configured to request an IP address from
the DHCP server. The request and grant process uses a lease
concept with a controllable time period.
DHCP is defined in RFC 2131.
Microsoft introduced DHCP on their NT server with version
3.5 in late 1994.
(http://dhcp.org/).
(1998-11-22)
|
exterior gateway protocol
(foldoc) | Exterior Gateway Protocol
EGP
(EGP) A protocol which distributes routing
information to the routers which connect {autonomous
systems}.
The term "gateway" is historical, and "router" is currently
the preferred term.
There is also a routing protocol called EGP defined in {STD
18}, RFC 904.
See also Border Gateway Protocol, {Interior Gateway
Protocol}.
|
file service protocol
(foldoc) | File Service Protocol
FSP
(FSP) A protocol, similar to FTP, for copying
files between computers. It's designed for {anonymous
archives}, and has protection against server and network
overloading. It doesn't use connections so it can survive
interruptions in service.
Until 1993-08-12, FSP didn't stand for anything. Wen-King
was responsible for the initials and Michael Grubb
for their eventual expansion. Other
suggestions were "File Slurping Protocol", "Flaky Stream
Protocol" and "FTP's Sexier Partner".
{FAQ
(ftp://ftp.germany.eu.net/pub/networking/inet/fsp/fsp-faq/)}.
[fsp-faq, 1993-08-12].
(1997-12-07)
|
file transfer protocol
(foldoc) | File Transfer Protocol
FTP
(FTP) A client-server protocol which allows a user on one
computer to transfer files to and from another computer over a
TCP/IP network. Also the client program the user executes
to transfer files. It is defined in STD 9, RFC 959.
See also anonymous FTP, FSP, TFTP.
Unix manual page: ftp(1).
(1994-12-01)
|
home network administration protocol
(foldoc) | Home Network Administration Protocol
HNAP
HNAP1
(HNAP) A network protocol using SOAP over
HTTP that lets manufacturers and administrtors to configure
devices remotely. HNAP is typically used by ISPs to update
Internet routers in customers' homes or workplaces.
Because it runs on many devices on the Internet, HNAP is a
target for remote attacks or probes. These may start by
attempting to fetch the URL "/HNAP1/" on the remote device.
[{Cisco whitepaper
(https://www.cisco.com/web/partners/downloads/guest/hnap_protocol_whitepaper.pdf)}]
[{SANS vulnerability post
(https://isc.sans.edu/forums/diary/More+on+HNAP+What+is+it+How+to+Use+it+How+to+Find+it/17648/)}]
(2018-08-09)
|
hot standby routing protocol
(foldoc) | Hot Standby Routing Protocol
HSRP
(HSRP) A CISCO standard, defined in RFC 2281,
that calls for a mirrored router in passive mode to send
hello packets, wait for a lead router to die and, without
dropping a packet, take over from that router.
Note: "standby", not "swappable" (and certainly not
"swapable").
(2005-01-26)
|
hot swapable routing protocol
(foldoc) | Hot Swapable Routing Protocol
Incorrect spelling of incorrect expansion of HSRP -
Hot Standby Routing Protocol.
(2005-01-26)
|
hot swappable routing protocol
(foldoc) | Hot Swappable Routing Protocol
Incorrect expansion of HSRP - {Hot Standby Routing
Protocol}.
(2005-01-26)
|
hypertext transfer protocol
(foldoc) | Hypertext Transfer Protocol
HTTP
(HTTP) The client-server TCP/IP protocol used
on the web for the exchange of HTML documents.
It conventionally uses port 80.
See also Uniform Resource Locator.
(1994-10-27)
|
hypertext transmission protocol, secure
(foldoc) | HyperText Transmission Protocol, Secure
HTTPS
(HTTPS) A variant of HTTP used by Netscape for
handling secure transactions.
The Netscape Navigator supports a URL access method,
"https", for connecting to HTTP servers using SSL.
"https" is a unique protocol that is simply SSL underneath
HTTP. You need to use "https://" for HTTP URLs with
SSL, whereas you continue to use "http://" for HTTP URLs
without SSL. The default "https" port number is 443, as
assigned by the Internet Assigned Numbers Authority.
(http://netscape.com/info/security-doc.html).
(1995-01-16)
|
icmp router discovery protocol
(foldoc) | ICMP Router Discovery Protocol
IRDP
(IRDP) A routing protocol used by {Microsoft
Windows} DHCP clients and various Unix flavors.
{Vulnerability
(http://securiteam.com/securitynews/Most_DHCP_clients_are_vulnerable_to_an_IRDP_attack.html)}.
[Details? Reference?]
(1999-10-31)
|
interior gateway protocol
(foldoc) | Interior Gateway Protocol
IGP
(IGP) An Internet protocol which distributes
routing information to the routers within an {autonomous
system}.
The term "gateway" is historical, "router" is currently the
preferred term.
See also Exterior Gateway Protocol, {Open Shortest Path
First}, Routing Information Protocol.
(1994-11-09)
|
internet control message protocol
(foldoc) | Internet Control Message Protocol
ICMP
(ICMP) An extension to the Internet Protocol (IP)
that allows for the generation of error messages, test
packets, and informational messages related to IP. It is
defined in STD 5, RFC 792.
(1999-09-18)
|
internet group management protocol
(foldoc) | Internet Group Management Protocol
IGMP
(IGMP) An extension to the Internet Protocol,
used by IP hosts to report their host group memberships to
immediately-neighbouring multicast routers.
See also MBONE.
Version 1 of IGMP is defined in Appendix 1 of RFC 1112.
Version 2 is proposed in RFC 2236.
(1999-11-08)
|
internet inter-orb protocol
(foldoc) | Internet Inter-ORB Protocol
IIOP
(IIOP) A protocol which will be mandatory
for all CORBA 2.0 compliant platforms. The initial phase
of the project is to build an infrastructure consisting of: an
IIOP to HTTP gateway which allows CORBA clients to
access WWW resources; an HTTP to IIOP gateway to let WWW
clients access CORBA resources; a web server which makes
resources available by both IIOP and HTTP; web browsers which
can use IIOP as their native protocol.
(http://ansa.co.uk/ANSA/ISF/wwwCorba_1.html).
(1996-04-01)
|
internet message access protocol
(foldoc) | Internet Message Access Protocol
IMAP
(IMAP) A protocol allowing a client
to access and manipulate electronic mail messages on a
server. It permits manipulation of remote message folders
(mailboxes), in a way that is functionally equivalent to
local mailboxes.
IMAP includes operations for creating, deleting, and renaming
mailboxes; checking for new messages; permanently removing
messages; searching; and selective fetching of message
attributes, texts, and portions thereof. It does not specify
a means of posting mail; this function is handled by a mail
transfer protocol such as SMTP.
See RFC 2060, RFC 2061, and others.
Compare: POP.
(1999-03-14)
|
internet open trading protocol
(foldoc) | Internet Open Trading Protocol
Open Trading Protocol
(IOTP, Formerly "Open Trading Protocol",
OTP) A specification that provides an interoperable framework
for Internet commerce. It is optimised for the case where the
buyer and the merchant do not have a prior acquaintance and is
payment system independent. It will be able to encapsulate
and support payment systems such as SET, Mondex,
CyberCash's CyberCoin, DigiCash's e-cash, GeldKarte, etc.
IOTP is able to handle cases where such merchant roles as the
shopping site, the payment handler, the deliverer of goods or
services, and the provider of customer support are performed
by different Internet sites.
The IOTP specification is maintained by the IETF {Internet
Open Trading Protocol (trade) Working Group
(http://ietf.org/html.charters/trade-charter.html)}.
(http://otp.org/).
(2001-09-22)
|
internet protocol
(foldoc) | Internet Protocol
IP
(IP) The network layer for the TCP/IP
protocol suite widely used on Ethernet networks, defined
in STD 5, RFC 791. IP is a connectionless,
best-effort packet switching protocol. It provides
packet routing, fragmentation and re-assembly through
the data link layer.
IPv4 is the version in widespread use and IPv6 was just
beginning to come into use in 2000 but is still not widespread
by 2008.
[Other versions? Dates?]
(2000-12-19)
|
internet protocol control protocol
(foldoc) | Internet Protocol Control Protocol
IPCP
(IPCP) The Control Protocol for {Internet
Protocol}.
[Details?]
(2002-06-29)
|
internet protocol version 4
(foldoc) | Internet Protocol version 4
IPv4
The version of Internet Protocol in
widespread use in 2000.
(2000-12-19)
|
internet protocol version 6
(foldoc) | Internet Protocol version 6
IPv6
(IPv6, IPng, IP next generation) The
most viable candidate to replace the current {Internet
Protocol}. The primary purpose of IPv6 is to solve the
problem of the shortage of IP addresses.
The following features have been purposed: 16-byte addresses
instead of the current four bytes; embedded encryption - a
32-bit Security Association ID (SAID) plus a variable length
initialisation vector in packet headers; user
authentication (a 32-bit SAID plus variable length
authentication data in headers); autoconfiguration
(currently partly handled by {Dynamic Host Configuration
Protocol}); support for delay-sensitive traffic - a 24 bit
flow ID field in headers to denote voice or video, etc.
One possible solution is based on the TUBA protocol (RFC
1347, 1526, 1561) which is itself based on the OSI
Connectionless Network Protocol (CNLP). Another is TP/IX
(RFC 1475) which changes TCP and UDP headers to give a
64-bit IP address, a 32-bit port number, and a 64-bit
sequence number.
RFC 1550 is a white paper on IPng.
IPv6.org (http://ipv6.org/).
["Doubts About IPng could create TCP/IP chaos", Johna Till
Johnson, Data Communications, Nov 1994].
(2004-06-17)
|
internet security association and key management protocol
(foldoc) | Internet Security Association and Key Management Protocol
ISAKMP
(ISAKMP) The definitions and procedures
for authenticating communication between 2 peers. This
includes the creation and management of {Security
Associations}, key generation techniques, and {threat
mitigation}. ISAKMP is proposed in RFC 2408.
(2000-02-08)
|
inverse address resolution protocol
(foldoc) | Inverse Address Resolution Protocol
InARP
(InARP) Additions to ARP typically
used for Frame Relay. [Any other examples of its use?]
Frame Relay stations route frames of a higher level
protocol between LANs, across a Permanent Virtual Circuit.
These stations are identified by their {Data Link Control
Identifier} (DLCI), equivalent to an Ethernet address in a
LAN itself.
InARP allows a station to determine a protocol address (e.g.
IP address) from a DLCI. This is useful if a new {virtual
circuit} becomes available. Signalling messages announce its
DLCI, but without the corresponding protocol address it is
unusable: no frames can be routed to it.
Reverse ARP (RARP) performs a similar task on an Ethernet
LAN, however RARP answers the question "What is my IP
Address?" whereas InARP answers the question "What is your
protocol address?".
See RFC 2390.
(2000-01-15)
|
java remote method protocol
(foldoc) | Java Remote Method Protocol
JRMP
(JRMP) A proprietary wire-level protocol designed
by Sun Microsystems to transport Java RMI.
JRMP serves the same function as IIOP, but also supports
object passing. Sun plans to offer IIOP as an alternative
to JRMP.
Sun do not appear to use this term any longer, simply
referring to the "RMI transport protocol".
(http://java.sun.com/j2se/1.3.0/docs/guide/rmi/spec/rmi-protocol3.html).
Comparison (http://execpc.com/~gopalan/misc/compare.html).
(2001-07-21)
|
layer two tunneling protocol
(foldoc) | Layer Two Tunneling Protocol
L2TP
(L2TP) An IETF standard protocol for creating
Virtual Private Networks. L2TP is an open standard with
mutlivendor interoperability and acceptance.
Compare: PPTP.
[Sponsored by Cisco Systems, Inc.?]
(1998-09-24)
|
lightweight directory access protocol
(foldoc) | Lightweight Directory Access Protocol
LDAP
(LDAP) A protocol for accessing on-line
directory services.
LDAP was defined by the IETF in order to encourage adoption
of X.500 directories. The Directory Access Protocol (DAP)
was seen as too complex for simple internet clients to use.
LDAP defines a relatively simple protocol for updating and
searching directories running over TCP/IP.
LDAP is gaining support from vendors such as Netscape,
Novell, Sun, HP, IBM/Lotus, SGI, AT&T, and
Banyan
An LDAP directory entry is a collection of attributes with a
name, called a distinguished name (DN). The DN refers to the
entry unambiguously. Each of the entry's attributes has a
type and one or more values. The types are typically
mnemonic strings, like "cn" for common name, or "mail" for
e-mail address. The values depend on the type. For
example, a mail attribute might contain the value
"donald.duck@disney.com". A jpegPhoto attribute would contain
a photograph in binary JPEG/JFIF format.
LDAP directory entries are arranged in a hierarchical
structure that reflects political, geographic, and/or
organisational boundaries. Entries representing countries
appear at the top of the tree. Below them are entries
representing states or national organisations. Below them
might be entries representing people, organisational units,
printers, documents, or just about anything else.
RFC 1777, RFC 1778, RFC 1959, RFC 1960, RFC 1823.
{LDAP v3
(http://kingsmountain.com/LDAPRoadmap/CurrentState.html)}.
[Difference v1, v2, v3?]
(2003-09-27)
|
link access protocol balanced
(foldoc) | Link Access Protocol Balanced
LAPB
(LAPB) X.25 layer 2 (data link layer)
protocol.
[Details?]
(1996-01-22)
|
link access protocol for modems
(foldoc) | Link Access Protocol for Modems
LAPM
(LAPM) The Automatic Repeat Request system used in the
V.42 protocol.
|
link control protocol
(foldoc) | Link Control Protocol
LCP
A protocol used to automatically agree upon
encapsulation format options, handle varying packet size
limits, authenticate the identity of its peer on the link,
determine when a link is functioning properly and when it is
defunct, detect a looped-back link and other common
misconfiguration errors, and terminate the link.
[RFC 1570].
(1997-05-10)
|
link state routing protocol
(foldoc) | Link State Routing Protocol
A routing protocol such as
OSPF which permits routers to exchange information with one
another about the reachability of other networks and the cost
or metric to reach the other networks.
The cost/metric is based on number of hops, link speeds,
traffic congestion, and other factors as determined by the
network designer. Link state routers use {Dijkstra's
algorithm} to calculate shortest (lowest cost) paths, and
normally update other routers with whom they are connected
only when their own routing tables change.
Link state routing is an improvement over {distance-vector
routing} protocols such as RIP which normally use only a
single metric (such as hop count) and which exchange all of
their table information with all other routers on a regular
schedule. Link state routing normally requires more
processing but less transmission overhead.
(2000-03-14)
|
local mail transfer protocol
(foldoc) | Local Mail Transfer Protocol
LMTP
(LMTP) A protocol designed as an
alternative to ESMTP for cases where the mail receiver does
not manage a queue. LMTP is an application level protocol
that runs on top of TCP/IP. It was initially defined in
RFC 2033, and uses (with a few changes) the syntax and
semantics of ESMTP. It should be used only by specific
prior arrangement and configuration, and it must not be used
on TCP port 25 (the SMTP port).
(2002-03-09)
|
logical link control and adaptation protocol
(foldoc) | Logical Link Control and Adaptation Protocol
L2CAP
(L2CAP) A Bluetooth protocol in the {Core
Protocol Stack} providing data services to higher layer
Bluetooth protocols.
{L2CAP Layer Tutorial
(http://palowireless.com/infotooth/tutorial/l2cap.asp)}.
(2002-06-28)
|
lower layer protocol
(foldoc) | Lower Layer Protocol
LLP
(LLP, or lower-layer protocol)
Any protocol residing in OSI layers one to four.
These protocols package, route, verify and transmit
datagrams. A prime example would be TCP/IP. Lower layer
protocols support the upper layer protocols.
(1999-02-17)
|
manufacturers automation protocol
(foldoc) | Manufacturing Automation Protocol
Manufacturers Automation Protocol
(MAP) A set of protocols developed by General
Motors based on Token Bus (IEEE 802.4) and giving
predictable real-time response.
(1994-10-21)
|
manufacturing automation protocol
(foldoc) | Manufacturing Automation Protocol
Manufacturers Automation Protocol
(MAP) A set of protocols developed by General
Motors based on Token Bus (IEEE 802.4) and giving
predictable real-time response.
(1994-10-21)
|
media gateway control protocol
(foldoc) | Media Gateway Control Protocol
MGCP
(MGCP) A protocol used within a
Voice over IP system. MGCP is an IETF work in progress,
it superseded SGCP.
MGCP is an internal protocol used within a distributed
system that appears to the outside world as a single VoIP
gateway.
This system is composed of a Call Agent, and a set of
gateways, including at least one "media gateway" that performs
the conversion of media signals between circuits and
packets, and at least one "signalling gateway" when
connected to an SS7 controlled network.
{IETF MGCP draft
(http://ietf.org/internet-drafts/draft-huitema-megaco-mgcp-v0r1-05.txt)}.
(1999-03-17)
|
mesi protocol
(foldoc) | MESI protocol
Modified, Exclusive, Shared, Invalid.
A cache coherency protocol where each cache line is
marked with one of the four states.
The MESI protocol is used by the Pentium processor.
(1995-05-05)
|
microcom networking protocol
(foldoc) | Microcom Networking Protocol
MNP
(MNP) One of the most common modem protocols with
compression. Also the name of a product.
[Details? On-line spec?]
(1995-01-31)
|
multiprotocol label switching
(foldoc) | Multiprotocol Label Switching
MPLS
(MPLS) A packet switching protocol developed
by the IETF. Initially developed to improve switching
speed, other benefits are now seen as being more important.
MPLS adds a 32-bit label to each packet to improve
network efficiency and to enable routers to direct
packets along predefined routes in accordance with the
required quality of service. The label is added when the
packet enters the MPLS network, and is based on an
analysis of the packet header. The label contains
information on the route along which the packet may travel,
and the forwarding equivalence class (FEC) of the packet.
Packets with the same FEC are routed through the network
in the same way.
Routers make forwarding decisions based purely on the contents
of the label. This simplifies the work done by the router,
leading to an increase in speed. At each router, the label
is replaced with a new label, which tells the next router
how to forward the packet. The label is removed when the
packet leaves the MPLS network.
Modern ASIC-based routers can look up routes fast enough to
make the speed increase less important. However, MPLS still
has some benefits. The use of FECs allows QoS levels to
be guaranteed, and MPLS allows IP tunnels to be created
through a network, so that VPNs can be implemented without
encryption.
MPLS Resource Center (http://mplsrc.com/).
[RFC 3031]
(2002-04-14)
|