| | podobné slovo | definícia |  
transmission control protocol/internet protocol (encz) | transmission control protocol/internet protocol,	n:		 |  
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] |  
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)
  |  
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)
  |  
serial line internet protocol (foldoc) | Serial Line Internet Protocol
 
     (SLIP) Software allowing the
    Internet Protocol (IP), normally used on Ethernet, to be
    used over a serial line, e.g. an EIA-232 serial port
    connected to a modem.  It is defined in RFC 1055.
 
    SLIP modifies a standard Internet datagram by appending a
    special SLIP END character to it, which allows datagrams to be
    distinguished as separate.  SLIP requires a port configuration
    of 8 data bits, no parity, and EIA or {hardware flow
    control}.  SLIP does not provide error detection, being
    reliant on other high-layer protocols for this.  Over a
    particularly error-prone dial-up link therefore, SLIP on its
    own would not be satisfactory.
 
    A SLIP connection needs to have its IP address configuration
    set each time before it is established whereas {Point-to-Point
    Protocol} (PPP) can determine it automatically once it has
    started.
 
    See also SLiRP.
 
    (1995-04-30)
  |  
  |