TCP/IP

DNS, NetBIOS, LDAP, FTP, TFTP, Finger, HTTP

 Idi na Hrvatsku Stranicu  Specific



 To the Beginning   |   1   |   2   |   3   |   4   |   5   |   6   |   7   |   8   |   9   |   Towards the End

BGMP

Border Gateway Multicast Protocol - maintains a group-prefix state in response to messages from BGMP peers and notifications from M-IGP components. Group-shared trees are rooted at the domain advertising the group prefixes covering those groups. When a receiver joins a specific group address, the border router towards the root domain generates a group-specific Join message, which is then forwarded Border-Router-by-Border-Router towards the root domain. BGMP Join and Prune messages are sent over TCP connections between BGMP peers, and the BGMP protocol state is refreshed by KEEP ALIVE messages periodically sent over TCP.

  0   1   2   3  
  0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
0 Length Type Reserved

Diameter

Diameter - provides an Authentication, Authorization and Accounting (AAA) framework for applications such as network access or IP mobility. Diameter also works in both local AAA and roaming situations. Diameter runs over reliable transport mechanisms (TCP, SCTP) as defined in [AAATRANS].

  0   1   2   3  
  0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
0 Version Message length
4 Command Flags Command-Code
8 Application-ID
12 Hop-by-Hop Identifier
16 End-to-End Identifier
  AVPs ...

DIS

Distributed Interactive Simulation - is a government/industry initiative to define an infrastructure for linking simulations of various types at multiple locations to create realistic, complex, virtual worlds for the simulation of highly interactive activities. This infrastructure brings together systems built for separate purposes, technologies from different eras, products from various vendors, and platforms from various services, and permits them to interoperate.

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Octets
Protocol Version
8-bit enumeration
Exercise ID
8-bit unsigned integer
1
2
PDU Type
8-bit enumeration
Protocol Family
8-bit enumeration
3
4
Timestamp
32-bit unsigned integer
5
6
7
8
Length
16-bit unsigned integer
9
10
Padding
16 bits unused
11
12

DNS

Domain Name Service - searches for resources using a database distributed among different name servers.

16 21 25 28 32
ID Q Query A T R V B Rcode
Question count Answer count
Authority count Additional count
Structure of the DNS header in 32 bit lines.

ISAKMP / IKE

Internet Security Association and Key Management Protocol / Internet Key Exchange - defines a framework for security association management and cryptographic key establishment for the Internet. It combines the security concepts of authentication, key management, and security associations to establish the required security for government, commercial, and private communications on the Internet.

  0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
0
4
Initiator
Cookie
8
12
Responder
Cookie
16 Next Payload MjVer MnVer Exchange Type Flags
20 Message ID
24 Length

iSCSI

Internet Small Computer Systems Interface - is a mapping of the SCSI remote procedure invocation model over the TCP protocol. SCSI commands are carried by iSCSI requests and SCSI responses and status are carried by iSCSI responses. iSCSI also uses the request response mechanism for iSCSI protocol mechanisms.

  0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
0   I Opcode F Opcode-specific fields
4 TotalAHSLength DataSegmentLength
8 LUN or Opcode-specific fields
12
16 Initiator Task Tag
20 Opcode - specific fields
48

FANP

Flow Attribute Notification Protocol - is a protocol between neighbor modes which manages cut-through packet forwarding functionalities. In cut-through packet forwarding, a router doesn’t perform conventional IP packet processing for received packets. FANP indicates mapping information between a datalink connection and a packet flow to the neighbor node. It helps a pair of nodes manage mapping information.

8 16 24 32
Version OpCode Checksum
VCID type Flow ID Reserved or
Refresh int. or
Error code
VCID
Flow ID
Structure of the FANP protocol.

NetBIOS / IP

Net Basic Input-Output System / over Internet Protocol - is a standard protocol to support NetBIOS services in a TCP / IP environment. Both local network and Internet operations are supported. Various node types are defined to accommodate local and Internet topologies and to allow operation with or without the use of IP broadcast.

16 21 28 32
Name_trn_id Opcode Nm_flags Rcode
Qdcount Ancount
Nscount Arcount
Structure of the NetBIOS / IP header in 32 bit lines.

LDAP

Lightweight Directory Access Protocol - provides access to X.500 directories without using the DAP (Directory Access Protocol). It is used for simple management applications and browser applications that provide simple read/write interactive access to the X.500 directory and should complement the DAP. X.500 technology has proved to be highly popular, and therefore led to efforts to reduce the high ?cost of entry? associated with it. Until now methods suggested were based on specific applications and, as such, were limited. The LDAP is also a directory protocol alternative, but it is not dependant on a particular application. As such it is intended to be simpler and less expensive than existing ones.


MZAP

Multicast-scope Zone Announcement Protocol - is used to discover the multicast administrative scope zones that are relevant at a particular location. MZAP also provides mechanisms whereby common misconfigurations of administrative scope zones can be discovered.

  0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
0 Version B PTYPE Address Family NameCount
4 Message Origin
8 Zone ID Address
12 Zone Start Address
16 Zone End Address
  Encoded Zone Name-1 (variable length)
    ......
    Encoded Zone Name-N (variable length)
    Padding (if needed)

COPS

Common Open Policy Service - describes a simple query and response protocol that can be used to exchange policy information between a policy server (Policy Decision Point or PDP) and its clients (Policy Enforcement Points or PEPs). It is designed to be extensible so that other kinds of policy clients may be supported in the future. The model does not make any assumptions about the methods of the policy server, but is based on the server returning decisions to policy requests.

4 8 16 32
Version Flags Op Code Client-type
Message Length
Structure of the COPS header in 32 bit lines.

After the COPS header comes all encapsulated objects that follow the same object format.

16 32
Length (octets) C-Num C-Type
(Object contents)
Structure of the COPS object format in 32 bit lines.

FTP

File Transfer Protocol - provides the basic elements of file sharing between hosts. FTP uses TCP to create a virtual connection for control information and then creates a separate TCP connection for data transfers. The control connection uses an image of the TELNET protocol to exchange commands and messages between hosts.


TFTP

Trivial File Transfer Protocol - uses UDP. TFTP supports file writing and reading; it does not support directory service of user authorization.


Finger

Finger - user information protocol is a simple protocol which provides an interface to a remote user information program. It is a protocol for the exchange of user information. based on the Transmission Control Protocol, using TCP port 79 decimal (117 octal).


HTTP

HyperText Transfer Protocol - is an application-level protocol with the lightness and speed necessary for distributed, collaborative, hypermedia information systems. Messages are passed in a format similar to that used by Internet Mail and the Multipurpose Internet Mail Extensions (MIME).

The format of the Request packet header is shown in the following illustration:

 
Method Request-URI HTTP version
Structure of the HTTP request header.

The format of the Response packet header is shown in the following illustration:

 
HTTP version Status-code Reason-phrase
Structure of the HTTP response header.

S-HTTP

Secure HTTP - provides secure communication mechanisms between an HTTP client-server pair in order to enable spontaneous commercial transactions for a wide range of applications. S-HTTP provides a flexible protocol that supports multiple orthogonal operation modes, key management mechanisms, trust models, cryptographic algorithms and encapsulation formats through option negotiation between parties for each transaction.


 To the Beginning   |   1   |   2   |   3   |   4   |   5   |   6   |   7   |   8   |   9   |   Towards the End

 Back
 Search
 Next

Citing of this page:
Radic, Drago. " Informatics Alphabet " Split-Croatia.
{Date of access}; https://informatics.buzdo.com/specific/file.
Copyright © by Drago Radic. All rights reserved.  |  Disclaimer
 TCP/IP - Start
 TCP/IP  Informatics Alphabet