query: what port is used by the imapv4 protocol

pos: Internet Message Access Protocol Internet Message Access Protocol In computing, the Internet Message Access Protocol (IMAP) is an Internet standard protocol used by email clients to retrieve email messages from a mail server over a TCP/IP connection. IMAP is defined by RFC 3501. IMAP was designed with the goal of permitting complete management of an email box by multiple email clients, therefore clients generally leave messages on the server until the user explicitly deletes them. An IMAP server typically listens on port number 143. IMAP over SSL (IMAPS) is assigned the port number 993. Virtually all modern e-mail clients and servers support IMAP, which

neg: IceWarp Mail Server IceWarp Mail Server IceWarp Mail Server is a commercial mail and groupware server developed by IceWarp Ltd. It runs on Windows and Linux. In 2006 was known as Merak Mail Server. It incorporates groupware capabilities over SyncML protocol, as well as SMTP, IMAP and POP protocols. In 2009 it became a replacement for discontinued Groupware Server 6 developed by Software602. IceWarp Mail Server, sometimes called IceWarp eMail Server, is integrated with other modules, including the groupware, antispam and antivirus modules. Protocols include SMTP/ESMTP, IMAPv4 with PUSH via IDLE command, IMAP ACL, POP3/SPOP3, APOP, HTTP(S), FTP(S) with OTP/S-Key, OpenLDAP, SIP, SIP

neg: Discard Protocol discard server is built into the inetd (or xinetd) daemon. The discard service is usually not enabled by default. It may be enabled by adding the following lines to the file /etc/inetd.conf and reloading the configuration: The Discard Protocol is the TCP/UDP equivalent of the Unix filesystem node codice_1. Such a service is guaranteed to receive what is sent to it and can be used for debugging TCP and/or UDP code requiring a guaranteed reception of payload sent. On various routers, this TCP or UDP port 9 for the Discard Protocol (or port 7 for the Echo Protocol relaying ICMP

neg: Ephemeral port Ephemeral port An ephemeral port is a short-lived transport protocol port for Internet Protocol (IP) communications. Ephemeral ports are allocated automatically from a predefined range by the IP stack software. An ephemeral port is typically used by the Transmission Control Protocol (TCP), User Datagram Protocol (UDP), or the Stream Control Transmission Protocol (SCTP) as the port assignment for the client end of a client–server communication to a well-known port on a server. On servers, ephemeral ports may also be used as the port assignment on the server end of a communication. This is done to continue communications with a client

neg: ARPA Host Name Server Protocol all UNIX operating systems. The Domain Name System (DNS) has replaced the ARPA Host Name Server Protocol and the DARPA Trivial Name Server. ARPA Host Name Server Protocol The ARPA Host Name Server Protocol (NAMESERVER), is an obsolete network protocol used in translating a host name to an Internet address. IANA Transmission Control Protocol (TCP) and User Datagram Protocol (UDP) port 42 for NAMESERVER; this port is more commonly used by the Windows Internet Name Service (WINS) on Microsoft operating systems. The NAMESERVER protocol is used by the DARPA Trivial Name Server, a server process called tnamed that is provided

neg: ARPA Host Name Server Protocol ARPA Host Name Server Protocol The ARPA Host Name Server Protocol (NAMESERVER), is an obsolete network protocol used in translating a host name to an Internet address. IANA Transmission Control Protocol (TCP) and User Datagram Protocol (UDP) port 42 for NAMESERVER; this port is more commonly used by the Windows Internet Name Service (WINS) on Microsoft operating systems. The NAMESERVER protocol is used by the DARPA Trivial Name Server, a server process called tnamed that is provided in some implementations of UNIX. Support for the NAMESERVER protocol has been deprecated, and may not be available in the latest implementations of

neg: NetBIOS the type of resource, and can be used to tell other applications what type of services the system offers. In NBT, the name service operates on UDP port 137 (TCP port 137 can also be used, but rarely is). The name service primitives offered by NetBIOS are: NetBIOS name resolution is not supported by Microsoft for Internet Protocol Version 6 (IPv6). Datagram mode is connectionless; the application is responsible for error detection and recovery. In NBT, the datagram service runs on UDP port 138. The datagram service primitives offered by NetBIOS are: Session mode lets two computers establish a connection,

neg: Dynamic Trunking Protocol following switch port mode settings exist: The configured switch port mode setting is referred to as the port's "trunking administrative mode". The current behavior of a given port after negotiating with the neighboring port is referred to as the port's "trunking operational mode". Disabling Dynamic Trunking Protocol (DTP). Stretch, Jeremy. Retrieved 1 June 2016. Dynamic Trunking Protocol The Dynamic Trunking Protocol (DTP) is a proprietary networking protocol developed by Cisco Systems for the purpose of negotiating trunking on a link between two VLAN-aware switches, and for negotiating the type of trunking encapsulation to be used. It works on Layer 2

neg: Parallel Line Internet Protocol are also used to transfer files between two computers where a network is not necessary or available. Parallel Line Internet Protocol The Parallel Line Internet Protocol (PLIP) is a computer networking protocol for direct computer-to-computer communications using the parallel port normally used for connections to a printer. The Parallel Line Internet Protocol provides Link Layer services for the Internet Protocol, the protocol used for forming small local area networks and large computer networks, such as the Internet, enabling computers without standard dedicated networking hardware, such as Ethernet, but with older parallel port devices, to communicate. The Internet Protocol Suite is

neg: Stateful firewall packet against the firewall's rule set, which can be extensive. Additionally, in the case of a match with the state table, the firewall does not need to perform deep packet inspection. Packet filtering alone is not regarded as providing enough protection. In order to effectively block peer-to-peer-related network traffic, what is needed is a firewall that does "application filtering", which can be regarded as an extension to stateful packet inspection. Stateful packet inspection can determine what type of protocol is being sent over each port, but application-level filters look at what a protocol is being used for. For example, an

neg: Portmap and 2, is running, and can be reached at UDP port 644 or TCP port 645, depending on what transport protocol the client wants to use. The port mapper service was discovered to be used in Distributed Denial of Service (DDoS) attacks and Distributed Reflective Denial of Service (DRDoS) attacks in 2015. By using a spoofed port mapper request, an attacker can amplify the effects on a target because a portmap query will return many times more data than in the original request. Portmap The port mapper ("rpc.portmap" or just "portmap", or "rpcbind") is an Open Network Computing Remote Procedure

neg: Port Aggregation Protocol of packet ordering, while the latter assures no packet reordering to occur but limit a single transfer to the bandwidth of a single interface. Port Aggregation Protocol Port Aggregation Protocol (PAgP) is a Cisco Systems proprietary networking protocol, which is used for the automated, logical aggregation of Ethernet switch ports, known as an EtherChannel. The PAgP is proprietary to Cisco Systems. A similar protocol known as LACP — released by the IEEE and known as 802.3ad or 802.1ax recently — is an industry standard and is not tied to a specific vendor: PAgP can be configured on a Cisco switch

neg: Port Aggregation Protocol Port Aggregation Protocol Port Aggregation Protocol (PAgP) is a Cisco Systems proprietary networking protocol, which is used for the automated, logical aggregation of Ethernet switch ports, known as an EtherChannel. The PAgP is proprietary to Cisco Systems. A similar protocol known as LACP — released by the IEEE and known as 802.3ad or 802.1ax recently — is an industry standard and is not tied to a specific vendor: PAgP can be configured on a Cisco switch to operate in three different modes: On Cisco network devices running CatOS, a single switch module may only be configured to run in either

neg: Port forwarding UPnP defines the Internet Gateway Device Protocol (IGD) which is a network service by which an Internet gateway advertises its presence on a private network via the Simple Service Discovery Protocol (SSDP). An application that provides an Internet-based service may discover such gateways and use the UPnP IGD protocol to reserve a port number on the gateway and cause the gateway to forward packets to its listening socket. Port forwarding can be divided into the following specific types: local, remote, and dynamic port forwarding. Local port forwarding is the most common type of port forwarding. It is used to forward

neg: RFB protocol RFB protocol RFB (“remote framebuffer”) is an open simple protocol for remote access to graphical user interfaces. Because it works at the framebuffer level it is applicable to all windowing systems and applications, including Microsoft Windows, macOS and the X Window System. RFB is the protocol used in Virtual Network Computing (VNC) and its derivatives. By default, a viewer/client uses TCP port 5900 to connect to a server (or 5800 for browser access), but can also be set to use any other port. Alternatively, a server can connect to a viewer in "listening mode" (by default on port 5500). One

neg: RFB protocol RFB protocol RFB (“remote framebuffer”) is an open simple protocol for remote access to graphical user interfaces. Because it works at the framebuffer level it is applicable to all windowing systems and applications, including Microsoft Windows, macOS and the X Window System. RFB is the protocol used in Virtual Network Computing (VNC) and its derivatives. By default, a viewer/client uses TCP port 5900 to connect to a server (or 5800 for browser access), but can also be set to use any other port. Alternatively, a server can connect to a viewer in "listening mode" (by default on port 5500). One

neg: Comparison of file transfer protocols "Assigned by IANA" indicates whether the port is listed in the Service Name and Transport Protocol Port Number Registry, which is curated by the Internet Assigned Numbers Authority (IANA). IANA devotes each port number in the registry to a specific service with a specific transport protocol. The table below lists the transport protocol in the "Transport" column. The following protocols were designed for serial communication, mostly for the RS-232 standard. They are used for uploading and downloading computer files via modem or serial cable (e.g., by null modem or direct cable connection). UUCP is one protocol that can operate with

neg: TCP Port Service Multiplexer either by using the "HELP" command or by requesting a large number of services. This has the same effect as port scanning the host for available services iteratively. Because TCPMUX allows someone to use any service only by accessing port number 1, the protocol makes it difficult to apply traditional port-based firewall rules that block access from certain or all hosts to specific services. TCP Port Service Multiplexer The TCP Port Service Multiplexer (TCPMUX) is a little-used Internet protocol defined in RFC 1078. The specification describes a multiplexing service that may be accessed with a network protocol to contact any

neg: Parallel Line Internet Protocol Parallel Line Internet Protocol The Parallel Line Internet Protocol (PLIP) is a computer networking protocol for direct computer-to-computer communications using the parallel port normally used for connections to a printer. The Parallel Line Internet Protocol provides Link Layer services for the Internet Protocol, the protocol used for forming small local area networks and large computer networks, such as the Internet, enabling computers without standard dedicated networking hardware, such as Ethernet, but with older parallel port devices, to communicate. The Internet Protocol Suite is the standards-based networking model and software specification for forming small and large computer networks, from local area

neg: GPRS Tunnelling Protocol private networks, not directly connected to the Internet. This happens on UDP port 2152. The GTPv1-U protocol is used to exchange user data over GTP tunnels across the Sx interfaces. An IP packet for a UE is encapsulated in an GTPv1-U packet and tunneled between the P-GW and the eNodeB for transmission with respect to a UE over S1-U and S5/S8 interfaces. The GTP' protocol is used to transfer charging data to the Charging Gateway Function. GTP' uses TCP/UDP port 3386. GTP is the primary protocol used in the GPRS core network. It is the protocol which allows end users

neg: Bootstrap Protocol transport protocol, port number 67 is used by the (DHCP) server to receive client requests and port number 68 is used by the client to receive (DHCP) server responses. BOOTP operates only on IPv4 networks. Historically, BOOTP has also been used for Unix-like diskless workstations to obtain the network location of their boot image, in addition to the IP address assignment. Enterprises used it to roll out a pre-configured client (e.g., Windows) installation to newly installed PCs. Originally requiring the use of a boot floppy disk to establish the initial network connection, manufacturers of network cards later embedded the protocol

neg: RTP-MIDI own protocol, imposing all parameters related to synchronization like the sampling frequency. This session protocol is called "AppleMIDI" in Wireshark software. Session management with AppleMIDI protocol requires two UDP ports, the first one is called "Control Port", the second one is called "Data Port". When used within a multithread implementation, only the Data port requires a "real-time" thread, the other port can be controlled by a normal priority thread. These two ports must be located at two consecutive locations (n / n+1); the first one can be any of the 65536 possible ports. There is no constraint on the number

neg: Message Send Protocol a datagram-based application on UDP. A service listens for UDP datagrams on port 18. When a datagram is received by the receiver, an answering datagram is sent back to the sender containing exactly the same data. Message Send Protocol The Message Send Protocol (MSP) is an application layer protocol used to send a short message between nodes on a network. The original version of the protocol was published in 1990. It was updated as Message Send Protocol 2 in 1992. One message send service is defined as a connection-based application on TCP. A service listens for TCP connections on port

neg: Port (computer networking) server connection. An example for the use of ports is the Internet mail system. A server used for sending and receiving email generally needs two services. The first service is used to transport email to and from other servers. This is accomplished with the Simple Mail Transfer Protocol (SMTP). The SMTP service application usually listens on TCP port 25 for incoming requests. The second service is usually either the Post Office Protocol (POP) or the Internet Message Access Protocol (IMAP) which is used by e-mail client applications on users' personal computers to fetch email messages from the server. The POP

neg: Virtual LAN ports to VLANs dynamically based on information such as the source MAC address of the device connected to the port or the username used to log onto that device. As a device enters the network, the switch queries a database for the VLAN membership of the port that device is connected to. Protocol methods include Multiple VLAN Registration Protocol (MVRP) and the somewhat obsolete GARP VLAN Registration Protocol (GVRP). In a switch that supports protocol-based VLANs, traffic is handled on the basis of its protocol. Essentially, this segregates or forwards traffic from a port depending on the particular protocol of

neg: Session Initiation Protocol model. Each transaction consists of a client request that invokes a particular method or function on the server and at least one response. SIP reuses most of the header fields, encoding rules and status codes of HTTP, providing a readable text-based format. SIP can be carried by several transport layer protocols including Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and Stream Control Transmission Protocol (SCTP). SIP clients typically use TCP or UDP on port numbers 5060 or 5061 for SIP traffic to servers and other endpoints. Port 5060 is commonly used for non-encrypted signaling traffic whereas port 5061 is

neg: Dynamic Host Configuration Protocol address autoconfiguration. IPv6 hosts may also use link-local addressing to achieve operations restricted to the local network link. The DHCP employs a connectionless service model, using the User Datagram Protocol (UDP). It is implemented with two UDP port numbers for its operations which are the same as for the bootstrap protocol (BOOTP). UDP port number 67 is the destination port of a server, and UDP port number 68 is used by the client. DHCP operations fall into four phases: server discovery, IP lease offer, IP lease request, and IP lease acknowledgement. These stages are often abbreviated as DORA for discovery,

neg: TCP Port Service Multiplexer TCP Port Service Multiplexer The TCP Port Service Multiplexer (TCPMUX) is a little-used Internet protocol defined in RFC 1078. The specification describes a multiplexing service that may be accessed with a network protocol to contact any one of a number of available TCP services of a host on a single, well-known port number. The specification of TCPMUX, RFC 1078, was deprecated in 2016 by RFC 7805 for technical reasons and lack of use in the Internet. A host may connect to a server that supports the TCPMUX protocol on TCP port 1. The host then sends a name of the

neg: Ephemeral port which it uses the IANA range by default. Windows Server 2008 with Exchange Server 2007 installed has a default port range of 1025–60000. In addition to the default range, all versions of Windows since Windows 2000 have the option of specifying a custom range anywhere within 1025–65535. If certain server software is used, that uses non ephemeral custom port ranges for initiating some further connections, it needs to be ensured by configuration that this custom port range and the ephemeral port range do not overlap. Ephemeral port An ephemeral port is a short-lived transport protocol port for Internet Protocol (IP)

neg: Ukagaka data via the Internet. Additionally, if the user permits, they can talk according to a remote script (which is written in the language called “Sakura Script”). In that case, it is also possible that two or more users chat to each other using the Ukagaka system. The protocol it uses to communicate with other (local or remote) programs is called SSTP (Sakura Script Transfer Protocol). Ports 7743 and 9801 are officially assigned by IANA for SSTP. The port 7743 is not actually used for this protocol. The original Ukagaka listens to port 9801 while SSP (see below) uses the port

neg: Port (computer networking) number. Ports provide a multiplexing service for multiple services or multiple communication sessions at one network address. Specific port numbers are commonly reserved to identify specific services. The lowest numbered 1024 port numbers are called 43210 port numbers, and identify the historically most commonly used services. In the client–server model of application architecture, a multiplexing service is established, so that multiple simultaneous communication sessions may be initiated for the same service. The most commonly used protocols that use ports are the Transmission Control Protocol (TCP) and the User Datagram Protocol (UDP). Transport layer protocols, such as the Transmission Control Protocol

neg: Hypertext caching protocol network failures and delays. An HTCP agent should be prepared to act in useful ways when no response is forthcoming, or when responses are delayed or reordered or damaged. TCP is optional and is expected to be used only for protocol debugging. The IANA has assigned port 4827 as the standard TCP and UDP port number for HTCP. An HTCP Message has the following general format: Hypertext caching protocol Hypertext Caching Protocol (abbreviated to HTCP) is used for discovering HTTP caches and cached data, managing sets of HTTP caches and monitoring cache activity. It permits full request and response headers

neg: Simple Network Management Protocol All SNMP messages are transported via User Datagram Protocol (UDP). The SNMP agent receives requests on UDP port 161. The manager may send requests from any available source port to port 161 in the agent. The agent response is sent back to the source port on the manager. The manager receives notifications ("Traps" and "InformRequests") on port 162. The agent may generate notifications from any available port. When used with Transport Layer Security or Datagram Transport Layer Security, requests are received on port 10161 and notifications are sent to port 10162. SNMPv1 specifies five core protocol data units (PDUs). Two

neg: Communication protocol of standardization and an overview of protocols using this scheme is given in the article on OSI protocols. In networking equipment configuration, a term-of-art distinction is often drawn: The term "protocol" strictly refers to the transport layer, and the term "service" refers to protocols utilizing a "protocol" for transport. In the common case of the TCP and UDP "protocols", "services" are distinguished by their port numbers. Conformance to these port numbers is voluntary, so in content inspection systems the term "service" strictly refers to port numbers, and the term "application" is often used to refer to protocols identified through inspection

neg: Zone Routing Protocol reduces the control overhead for longer routes that would be necessary if using proactive routing protocols throughout the entire route, while eliminating the delays for routing within a zone that would be caused by the route-discovery processes of reactive routing protocols. What is called the Intra-zone Routing Protocol (IARP), or a proactive routing protocol, is used inside routing zones. What is called the Inter-zone Routing Protocol (IERP), or a reactive routing protocol, is used between routing zones. IARP uses a routing table. Since this table is already stored, this is considered a proactive protocol. IERP uses a reactive protocol. Any

neg: Portmap as a client would not be able to get the port number for the port mapper service from the port mapper itself. The port mapper must be started before any other RPC servers are started. The port mapper service first appeared in SunOS 2.0. This shows the different programs and their versions, and which ports they use. For example, it shows that NFS is running, both version 2 and 3, and can be reached at TCP port 2049 or UDP port 2049, depending on what transport protocol the client wants to use, and that the mount protocol, both version 1

neg: Direct Client-to-Client here to maintain compatibility with the error messages sent by the extended DCC CHAT. If the receiver declines the transfer, it sends the following CTCP reply: Other errors are reported in the same fashion. If the receiver is willing and capable of receiving the file, it will connect to the given address and port. What happens then depends on the protocol used. In the case of the "clear" protocol, the XMIT server will, upon receiving a connection, send a 32-bit time t in network byte order, representing the file's modification time. Presumably based on the modification time of the local

neg: Portmap Portmap The port mapper ("rpc.portmap" or just "portmap", or "rpcbind") is an Open Network Computing Remote Procedure Call (ONC RPC) service that runs on network nodes that provide other ONC RPC services. Version 2 of the port mapper protocol maps ONC RPC program number/version number pairs to the network port number for that version of that program. When an ONC RPC server is started, it will tell the port mapper, for each particular program number/version number pair it implements for a particular transport protocol (TCP or UDP), what port number it is using for that particular program number/version number pair

neg: Bluetooth and publicly available API on most operating systems. Additionally, applications that used a serial port to communicate can be quickly ported to use RFCOMM. The "Bluetooth Network Encapsulation Protocol" (BNEP) is used for transferring another protocol stack's data via an L2CAP channel. Its main purpose is the transmission of IP packets in the Personal Area Networking Profile. BNEP performs a similar function to SNAP in Wireless LAN. The "Audio/Video Control Transport Protocol" (AVCTP) is used by the remote control profile to transfer AV/C commands over an L2CAP channel. The music control buttons on a stereo headset use this protocol to

neg: Computer network suite provides a diverse set of networking capabilities. The protocols have a flat addressing scheme. They operate mostly at levels 1 and 2 of the OSI model. For example, MAC bridging (IEEE 802.1D) deals with the routing of Ethernet packets using a Spanning Tree Protocol. IEEE 802.1Q describes VLANs, and IEEE 802.1X defines a port-based Network Access Control protocol, which forms the basis for the authentication mechanisms used in VLANs (but it is also found in WLANs) – it is what the home user sees when the user has to enter a "wireless access key". Ethernet, sometimes simply called "LAN",

neg: Simple Service Discovery Protocol of SSDP also used port 5000 for this service. In 2014 it was discovered that SSDP was being used in DDoS attacks known as an "SSDP reflection attack with amplification". Many devices, including some residential routers, have a vulnerability in the UPnP software that allows an attacker to get replies from port number 1900 to a destination address of their choice. With a botnet of thousands of devices the attackers can generate sufficient packet rates and occupy bandwidth to saturate links, causing the denial of service. Simple Service Discovery Protocol The Simple Service Discovery Protocol (SSDP) is a network protocol

neg: Character Generator Protocol Character Generator Protocol The Character Generator Protocol (CHARGEN) is a service of the Internet Protocol Suite defined in in 1983 by Jon Postel. It is intended for testing, debugging, and measurement purposes. The protocol is rarely used, as its design flaws allow ready misuse. A host may connect to a server that supports the Character Generator Protocol on either Transmission Control Protocol (TCP) or User Datagram Protocol (UDP) port number 19. Upon opening a TCP connection, the server starts sending arbitrary characters to the connecting host and continues until the host closes the connection. In the UDP implementation of the

neg: Registered port to indicate an application or service. Registered port A registered port is a network port (a sub-address defined within the Internet Protocol, in the range 1024–49151) assigned by the Internet Assigned Numbers Authority (IANA) (or by Internet Corporation for Assigned Names and Numbers (ICANN) before March 21, 2001, or by USC/ISI before 1998) for use with a certain protocol or application. Ports with numbers 0–1023 are called "system or well-known ports"; ports with numbers 1024-49151 are called "user or registered ports", and ports with numbers 49152-65535 are called "dynamic and/or private ports". Both system and user ports are used by

neg: Registered port Registered port A registered port is a network port (a sub-address defined within the Internet Protocol, in the range 1024–49151) assigned by the Internet Assigned Numbers Authority (IANA) (or by Internet Corporation for Assigned Names and Numbers (ICANN) before March 21, 2001, or by USC/ISI before 1998) for use with a certain protocol or application. Ports with numbers 0–1023 are called "system or well-known ports"; ports with numbers 1024-49151 are called "user or registered ports", and ports with numbers 49152-65535 are called "dynamic and/or private ports". Both system and user ports are used by transport protocols (TCP, UDP, DCCP, SCTP)

neg: Simple Network Paging Protocol Simple Network Paging Protocol Simple Network Paging Protocol (SNPP) is a protocol that defines a method by which a pager can receive a message over the Internet. It is supported by most major paging providers, and serves as an alternative to the paging modems used by many telecommunications services. The protocol was most recently described in . It is a fairly simple protocol that may run over TCP port 444 and sends out a page using only a handful of well-documented commands. It is relatively easy to connect to a SNPP server only requiring a telnet client and the address

neg: File Service Protocol the root user can start a process that listens on a port under 1024.) The name "FSP" was originally created without a real expansion. In 1993, discussions were held about what to expand the acronym to; the ultimate result was "File Service Protocol". Other suggestions included "File Slurping Protocol", "FTP's Sexier Partner", and "Flaky Stream Protocol". Due to its inherent low performance, FSP was sometimes colloquially said to stand for "Fucking Slow Protocol" . File Service Protocol File Service Protocol (FSP) is a UDP-based replacement for the File Transfer Protocol, designed for anonymous access with lower hardware and network requirements

neg: Telecommunication used version of the Internet Protocol is version four but a move to version six is imminent. At the transport layer, most communication adopts either the Transmission Control Protocol (TCP) or the User Datagram Protocol (UDP). TCP is used when it is essential every message sent is received by the other computer whereas UDP is used when it is merely desirable. With TCP, packets are retransmitted if they are lost and placed in order before they are presented to higher layers. With UDP, packets are not ordered or retransmitted if lost. Both TCP and UDP packets carry port numbers with

neg: Cubesat Space Protocol the csp_new_packet function. CSP has been successfully tested with the following physical layers. The port range is divided into three adjustable segments. Ports 0 to 7 are used for general services such as ping and buffer status, and are implemented by the CSP service handler. The ports from 8 to 47 are used for subsystem specific services. All remaining ports, from 48 to 63, are ephemeral ports used for outgoing connections. The bits from 28 to 31 are used for marking packets with HMAC, XTEA encryption, RDP header and CRC32 checksum. Cubesat Space Protocol CubeSat Space Protocol (CSP) is a

neg: VISCA Protocol ATEM switchers that have RS-422 port and controlled by either ATEM 1M/E or ATEM 2M/E control panels are capable of controlling VISCA protocol compatible cameras as of November 2015 VISCA Protocol VISCA is a professional camera control protocol used with PTZ cameras. It was designed by Sony to be used on several of its surveillance and OEM block cameras. It is based on RS232 Serial communications at 9600 bit/s, 8N1, no flow control typically though a DE-9 connector, but can also be on 8-Pin DIN, RJ45 and RJ11 connectors use in daisy chain configurations. VISCA utilizes a serial repeater network

neg: Port (computer networking) (TCP) and the User Datagram Protocol (UDP), transfer data using protocol data units (PDUs). For TCP, the PDU is a segment, and a datagram for UDP. Both protocols use a header field for recording the source and destination port number. A port number is a 16-bit unsigned integer, thus ranging from 0 to 65535. For TCP, port number 0 is reserved and cannot be used, while for UDP, the source port is optional and a value of zero means no port. A process associates its input or output channels via an Internet socket, which is a type of file descriptor,

neg: Label Distribution Protocol state database. Label Distribution Protocol Label Distribution Protocol (LDP) is a protocol in which routers capable of Multiprotocol Label Switching (MPLS) exchange label mapping information. Two routers with an established session are called LDP peers and the exchange of information is bi-directional. LDP is used to build and maintain LSP databases that are used to forward traffic through MPLS networks. LDP can be used to distribute the inner label (VC/VPN/service label) and outer label (path label) in MPLS. For inner label distribution, targeted LDP (tLDP) is used. LDP and tLDP discovery runs on UDP port 646 and the session is

neg: Label Distribution Protocol Label Distribution Protocol Label Distribution Protocol (LDP) is a protocol in which routers capable of Multiprotocol Label Switching (MPLS) exchange label mapping information. Two routers with an established session are called LDP peers and the exchange of information is bi-directional. LDP is used to build and maintain LSP databases that are used to forward traffic through MPLS networks. LDP can be used to distribute the inner label (VC/VPN/service label) and outer label (path label) in MPLS. For inner label distribution, targeted LDP (tLDP) is used. LDP and tLDP discovery runs on UDP port 646 and the session is built on

neg: Bluetooth the SDP (Protocol used to find other Bluetooth devices within the communication range, also responsible for detecting the function of devices in range), RFCOMM (Protocol used to emulate serial port connections) and TCS (Telephony control protocol) interact with the baseband controller through the L2CAP Protocol (Logical Link Control and Adaptation Protocol). The L2CAP protocol is responsible for the segmentation and reassembly of the packets The hardware that makes up the Bluetooth device is made up of, logically, two parts; which may or may not be physically separate. A radio device, responsible for modulating and transmitting the signal; and a digital

neg: Internet Control Message Protocol the physical connection to the host does not exist (distance is infinite); the indicated protocol or port is not active; the data must be fragmented but the 'don't fragment' flag is on. Where: Internet Control Message Protocol The Internet Control Message Protocol (ICMP) is a supporting protocol in the Internet protocol suite. It is used by network devices, including routers, to send error messages and operational information indicating, for example, that a requested service is not available or that a host or router could not be reached. ICMP differs from transport protocols such as TCP and UDP in that it

neg: Message Session Relay Protocol port, an optional session identifier, the transport and additional optional parameters. For example: codice_1 MSRP can be used within a SIP session: MSRP session is set up through SIP's offer-answer model. The SDP m-line media type is "message" and the protocol is either "TCP/MSRP" for MSRP over TCP and "TCP/TLS/MSRP" for MSRP over secure TLS. Furthermore, the MSRP URI is specified in a "path" attribute. A full SDP example, as provided by the RFC: The fact that MSRP contains the address and port and at the same time the c-line holds the address and m-line contain the port is a

neg: Short Message Peer-to-Peer Message Service Center (SMSC) usually acts as a server, awaiting connections from ESMEs. When SMPP is used for SMS peering, the sending MC usually acts as a client. The protocol is based on pairs of request/response PDUs (protocol data units, or packets) exchanged over OSI layer 4 (TCP session or X.25 SVC3) connections. The well-known port assigned by the IANA for SMPP when operating over TCP is 2775, but multiple arbitrary port numbers are often used in messaging environments. Before exchanging any messages, a bind command must be sent and acknowledged. The bind command determines in which direction will be

neg: NAT Port Mapping Protocol NAT Port Mapping Protocol The NAT Port Mapping Protocol (NAT-PMP) is a network protocol for establishing network address translation (NAT) settings and port forwarding configurations automatically without user effort. The protocol automatically determines the external IPv4 address of a NAT gateway, and provides means for an application to communicate the parameters for communication to peers. NAT-PMP was introduced in 2005 by Apple as an alternative to the more common ISO Standard<ref name="ISO/IEC 29341"> ISO/IEC 29341, http://www.iso.org/iso/home/news_index/news_archive/news.htm?refid=Ref1185</ref> Internet Gateway Device Protocol implemented in many NAT routers. The protocol was published as an informational Request for Comments (RFC) by the Internet Engineering

neg: Simple Sensor Interface protocol source port and a 1-byte destination port number. The destination port number should be 0x28 for SSI messages. Simple Sensor Interface protocol The Simple Sensor Interface (SSI) protocol is a simple communications protocol designed for data transfer between computers or user terminals and smart sensors. The SSI protocol is an Application layer protocol as in the OSI model. The SSI protocol has been developed jointly by Nokia, Vaisala, Suunto, Ionific, Mermit and University of Oulu. Currently SSI is being developed within the Mimosa Project, part of the European Union Framework Programmes for Research and Technological Development. The SSI protocol is

neg: Port Control Protocol through PCP allow hosts to reduce the amount of generated traffic by eliminating workarounds in form of outgoing NAT keepalive messages, which are required for maintaining connections to servers and for various NAT traversal techniques such as TCP hole punching. At the same time, less generated traffic reduces the power consumption, directly improving the battery runtime for mobile devices. PCP was standardized in 2013 as a successor to the NAT Port Mapping Protocol (NAT-PMP), with which it shares similar protocol concepts and packet formats. In environments where a Universal Plug and Play Internet Gateway Device (UPnP IGD) is used in

neg: Port Control Protocol Port Control Protocol Port Control Protocol (PCP) is a computer networking protocol that allows hosts on IPv4 or IPv6 networks to control how the incoming IPv4 or IPv6 packets are translated and forwarded by an upstream router that performs network address translation (NAT) or packet filtering. By allowing hosts to create explicit port forwarding rules, handling of the network traffic can be easily configured to make hosts placed behind NATs or firewalls reachable from the rest of the Internet (so they can also act as network servers), which is a requirement for many applications. Additionally, explicit port forwarding rules available

neg: Real Time Streaming Protocol available. The default transport layer port number is 554 for both TCP and UDP, the latter being rarely used for the control requests. RTSP using RTP and RTCP allows for the implementation of rate adaptation. Real Time Streaming Protocol The Real Time Streaming Protocol (RTSP) is a network control protocol designed for use in entertainment and communications systems to control streaming media servers. The protocol is used for establishing and controlling media sessions between end points. Clients of media servers issue VCR-style commands, such as "play", "record" and "pause", to facilitate real-time control of the media streaming from the server

neg: Server Routing Protocol Server Routing Protocol Server Routing Protocol (SRP) is the proprietary network protocol used to transfer data between a BlackBerry Enterprise Server and the Research In Motion BlackBerry infrastructure. SRP communication takes place on TCP port 3101 by default. SRP work in two different part: 1. SRP ID 2. SRP Authorization Key During BlackBerry Enterprise Server installation, the unique Server Routing Protocol Identifier (SRP ID) and SRP Authentication Key must be entered. The SRP ID and SRP Authentication Key register and authenticate the BlackBerry Enterprise Server on the network. The work flow is same like any authentication process. The SRP ID

neg: HTTP tunnel proxy server and requests tunneling by specifying the port and the host computer it would like to connect to. The port is used to indicate the protocol being requested. If the connection was allowed and the proxy has connected to the specified host then the proxy will return a 2XX success response. The client is now being proxied to the remote host. Any data sent to the proxy server is now forwarded, unmodified, to the remote host and the client can communicate using any protocol accepted by the remote host. In the example below, the client is starting SSH communications

neg: Direct End to End Secure Chat Protocol Direct End to End Secure Chat Protocol The Internet Assigned Numbers Authority (IANA) officially assigned port 4605 to the SixChat End2End Direct secure messaging protocol created by Sixscape Communications, Pte. Ltd. The assignment was issued by IANA on 11 September 2014, and is listed in the official IANA resource registry at http://www.iana.org/assignments/service-names-port-numbers There are a very limited number of port numbers, which are assigned by IANA for protocols recognized as viable, complying with current protocol design standards, and not already covered by existing Internet standards. For example, port 25 was assigned to the SMTP email protocol many years ago. This

neg: Real-Time Object-Oriented Modeling via ports and bindings. To each port a unique "protocol" is assigned. A protocol in ROOM defines a set of outgoing and a set of incoming messages. Ports can be connected with a binding if they belong to the same protocol and are conjugate to each other. That means that one port is sending the outgoing messages of the protocol and receiving the incoming ones. This port is called the "regular" port. Its peer port, the "conjugated" port, receives the outgoing messages and sends the incoming ones of the protocol. In other words, a port is the combination of a

neg: Comparison of file transfer protocols "Encryption" column applies to transmitted data only, and not to the authentication system. The "Managed" column indicates whether the protocol is designed for managed file transfer (MFT). MFT protocols prioritise secure transmission in industrial applications that require such features as auditable transaction records, monitoring, and end-to-end data security. Such protocols may be preferred for electronic data interchange. In the table below, the "data port" is the network port or range of ports through which the protocol transmits file data. The "control port" is the port used for the dialogue of commands and status updates between client and server. The column

neg: Serial Attached SCSI one or more PHYs (such a connection is called a port whether it uses one or more PHYs, although the term "wide port" is sometimes used for a multi-PHY connection). The components known as "Serial Attached SCSI Expanders" (SAS Expanders) facilitate communication between large numbers of SAS devices. Expanders contain two or more external expander-ports. Each expander device contains at least one SAS Management Protocol target port for management and may contain SAS devices itself. For example, an expander may include a Serial SCSI Protocol target port for access to a peripheral device. An expander is "not necessary" to interface

neg: Geneva Agreement (1966) part to the treaty, has no participation in the comission) which within a period of 4 years would have to decide what could be the solution to the borderline problem, once this period has expires, the Protocol of Port Spain between Guyana, the United Kingdom, and Venezuela was signed in 1970 for which it was frozen, for a term of 12 years, part of the Geneva Agreement. In 1982, Venezuela decided not to ratify the Protocol of Port Spain and returned to what was established in the agreement. In 1983, Venezuela proposed direct negotiation with Guyana but Guyana does not

neg: Discard Protocol Discard Protocol The Discard Protocol is a service in the Internet Protocol Suite defined in RFC 863. It is intended for testing, debugging, measurement, or host management purposes. A host may send data to a host that supports the Discard Protocol on either Transmission Control Protocol (TCP) or User Datagram Protocol (UDP) port number 9. The data sent to the server is simply discarded. No response is returned. For this reason, UDP is usually used, but TCP allows the services to be accessible on session-oriented connections (for example via HTTP proxies or some VPN). On most Unix-like operating systems a

neg: Server Routing Protocol to send the message to the corresponding BlackBerry Enterprise Server for decryption and processing. Ref# Blackberry Server trial mentioning the technology Server Routing Protocol Server Routing Protocol (SRP) is the proprietary network protocol used to transfer data between a BlackBerry Enterprise Server and the Research In Motion BlackBerry infrastructure. SRP communication takes place on TCP port 3101 by default. SRP work in two different part: 1. SRP ID 2. SRP Authorization Key During BlackBerry Enterprise Server installation, the unique Server Routing Protocol Identifier (SRP ID) and SRP Authentication Key must be entered. The SRP ID and SRP Authentication Key register

neg: Port Control Protocol repeated. For example, result lifetimes can specify how long a failure condition is expected to persist, or how long the created mapping will last. Port Control Protocol Port Control Protocol (PCP) is a computer networking protocol that allows hosts on IPv4 or IPv6 networks to control how the incoming IPv4 or IPv6 packets are translated and forwarded by an upstream router that performs network address translation (NAT) or packet filtering. By allowing hosts to create explicit port forwarding rules, handling of the network traffic can be easily configured to make hosts placed behind NATs or firewalls reachable from the rest

neg: Reliability (computer networking) reliable multicast protocols. TCP, the main protocol used on the Internet, is a reliable unicast protocol. UDP, often used in computer games or in other situations where speed is an issue and the loss of a little data is not as important because of the transitory nature of the data, is an unreliable protocol. Often, a reliable unicast protocol is also connection-oriented. For example, TCP is connection-oriented, with the virtual-circuit ID consisting of source and destination IP addresses and port numbers. However, some unreliable protocols are connection-oriented, such as ATM and frame relay. In addition, some protocols are reliable-connectionless, such

neg: Smart meter a meter, mostly used in North American markets. The C12.18 standard is written specifically for meter communications via an ANSI Type 2 Optical Port, and specifies lower-level protocol details. ANSI C12.19 specifies the data tables that are used. ANSI C12.21 is an extension of C12.18 written for modem instead of optical communications, so it is better suited to automatic meter reading. IEC 61107 is a communication protocol for smart meters published by the IEC that is widely used for utility meters in the European Union. It is superseded by IEC 62056, but remains in wide use because it is simple

neg: Extensible User Interface Protocol Extensible User Interface Protocol The Extensible User Interface Protocol, or XUP, is a proposed web standard. XUP is a SOAP-based protocol for communicating events in a user interface, where the user interface is described by an XML document. The specification does not limit what format the XML document is in, or what event model is used for communicating over XUP. Examples given in the specification for possible user interface languages include XHTML, Wireless Markup Language, and XUL. The XUP specification was submitted to the World Wide Web Consortium (W3C) by Consortium member MartSoft Corporation in March 2002. , it is

neg: Port Control Protocol the local network, an interworking function between the UPnP IGD and PCP is required to be embedded in the IGD. The UPnP IGD-PCP IWF is specified in RFC6970. DHCP (IPv4 and IPv6) options to configure hosts with Port Control Protocol (PCP) server IP addresses are specified in RFC7291. The procedure to follow for selecting a server among a list of PCP server is discussed in RFC7488. In environments where NAT64 is deployed, PCP allows to learn the IPv6 prefix(es) used by a PCP-controlled NAT64 device to build IPv4-converted IPv6 addresses by the NAT64 (RFC7225). Many applications and network equipment deployments

neg: Identity Registration Protocol Identity Registration Protocol The Internet Assigned Numbers Authority (IANA) officially assigned TCP port 4604 to the Identity Registration Protocol (IRP) created by Sixscape Communications, Pte. Ltd. The assignment was issued by IANA on 17 March 2014, and is listed in the official IANA resource registry. There are a very limited number of port numbers, which are assigned by IANA for protocols recognized as viable, complying with current protocol design standards, and not already covered by existing Internet standards. For example, port 25 was assigned to the SMTP email protocol many years ago. This establishes a standard and eliminates conflicts with

neg: Communication protocol interest of the public. The need for protocol standards can be shown by looking at what happened to the bi-sync protocol (BSC) invented by IBM. BSC is an early link-level protocol used to connect two separate nodes. It was originally not intended to be used in a multinode network, but doing so revealed several deficiencies of the protocol. In the absence of standardization, manufacturers and organizations felt free to 'enhance' the protocol, creating incompatible versions on their networks. In some cases, this was deliberately done to discourage users from using equipment from other manufacturers. There are more than 50 variants

neg: NAT Port Mapping Protocol Task Force (IETF) in RFC 6886. NAT-PMP runs over the User Datagram Protocol (UDP) and uses port number 5351. It has no built-in authentication mechanisms because forwarding a port typically does not allow any activity that could not also be achieved using STUN methods. The benefit of NAT-PMP over STUN is that it does not require a STUN server and a NAT-PMP mapping has a known expiration time, allowing the application to avoid sending inefficient keep-alive packets. NAT-PMP is the predecessor to the Port Control Protocol (PCP). NAT Port Mapping Protocol The NAT Port Mapping Protocol (NAT-PMP) is a network

neg: Network Control Program the ARPANET changed its core networking protocols from NCP to the more flexible and powerful TCP/IP protocol suite, marking the start of the modern Internet. Network Control Program The Network Control Program (NCP) provided the middle layers of the protocol stack running on host computers of the ARPANET, the predecessor to the modern Internet. NCP preceded the Transmission Control Protocol (TCP) as a transport layer protocol used during the early ARPANET. NCP was a simplex protocol that utilized two port addresses, establishing two connections, for two-way communications. An odd and an even port were reserved for each application layer application

neg: Network Control Program Network Control Program The Network Control Program (NCP) provided the middle layers of the protocol stack running on host computers of the ARPANET, the predecessor to the modern Internet. NCP preceded the Transmission Control Protocol (TCP) as a transport layer protocol used during the early ARPANET. NCP was a simplex protocol that utilized two port addresses, establishing two connections, for two-way communications. An odd and an even port were reserved for each application layer application or protocol. The standardization of TCP and UDP reduced the need for the use of two simplex ports for each application down to one duplex

neg: STUN STUN Session Traversal Utilities for NAT (STUN) is a standardized set of methods, including a network protocol, for traversal of network address translator (NAT) gateways in applications of real-time voice, video, messaging, and other interactive communications. STUN is a tool used by other protocols, such as Interactive Connectivity Establishment (ICE), the Session Initiation Protocol (SIP), or WebRTC. It provides a tool for hosts to discover the presence of a network address translator, and to discover the mapped, usually public, Internet Protocol (IP) address and port number that the NAT has allocated for the application's User Datagram Protocol (UDP) flows to

neg: EForward EForward EForward is a file/document transport protocol to transfer files between computer systems with a guaranteed level of reliability. It belongs to the application layer of the Internet protocol suite. EForward uses a three-part (client-server-client) model, capable of handling any file type without further processing. Eforward was created in 1992 and in 1999 was assigned the IP port number 2181 by the Internet Assigned Numbers Authority (IANA). The protocol continues to be used under the Secure Easy IM (Seim) name. Originally the protocol was peer to peer but was changed to client server with peer to peer features. The protocol

neg: Dynamic Trunking Protocol Dynamic Trunking Protocol The Dynamic Trunking Protocol (DTP) is a proprietary networking protocol developed by Cisco Systems for the purpose of negotiating trunking on a link between two VLAN-aware switches, and for negotiating the type of trunking encapsulation to be used. It works on Layer 2 of the OSI model. VLAN trunks formed using DTP may utilize either IEEE 802.1Q or Cisco ISL trunking protocols. DTP should not be confused with VTP, as they serve different purposes. VTP communicates VLAN existence information between switches. DTP aids with trunk port establishment. Neither protocol transmits the data frames that trunks carry. The

neg: Message Send Protocol Message Send Protocol The Message Send Protocol (MSP) is an application layer protocol used to send a short message between nodes on a network. The original version of the protocol was published in 1990. It was updated as Message Send Protocol 2 in 1992. One message send service is defined as a connection-based application on TCP. A service listens for TCP connections on port 18. Once a connection is established, a short message is transmitted from the sender to the receiver over the connection. The sender closes the connection after sending the message. Another message send service is defined as

neg: Port Control Protocol for NAT64, NAT66, and NAT44; inclusion of PCP into IPv4 and IPv6 firewall devices is also supported. PCP is designed to be used on both large-scale aggregation points (for example, as part of carrier-grade NATs), and inside less expensive consumer-grade devices. Both long-term (for an IP camera or a temperature sensor acting as a server, for example) and short-term mappings (while playing an online computer game, for example) are supported. PCP supports transport layer protocols that use 16-bit port numbers (for example, TCP, UDP, Stream Control Transmission Protocol (SCTP) or Datagram Congestion Control Protocol (DCCP). Protocols that do not use

neg: Fast and Secure Protocol sending and receiving with the AES-128. To counteract attacks by monitoring the encrypted information during long transfers, the AES is operated in cipher feedback mode with a secret initialization vector for each block. In addition, an integrity check of each data block takes place, in which case, for example, a man-in-the-middle attack would be noticed. FASP's control Port is TCP port 22—the same port that SSH uses. For data transfer, it begins at UDP port 33001, which increments with each additional connection thread. Fast and Secure Protocol The Fast and Secure Protocol (FASP) is a proprietary data transfer protocol. FASP

neg: Multiple Spanning Tree Protocol of the core or of an island, this port self-configuration is done with very simple stipulations: if a port is not connected to another Abridge using a point-to-point link, it will turn itself an access port; on the other hand, ports directly connected to another Abridge are configured as core ports. This auto-configuration mechanism is pretty like the one used in RSTP. As any layer-two based protocol, ABridges uses ARP broadcasts to obtain the link layer address associated to an IP address at the same LAN or VLAN. That is the main cause why avoiding overflooding is a matter of

neg: Extensible User Interface Protocol a W3C "Note", meaning the W3C has not committed to developing the standard as a potential "Recommendation", and it is hosted for informational purposes only. Extensible User Interface Protocol The Extensible User Interface Protocol, or XUP, is a proposed web standard. XUP is a SOAP-based protocol for communicating events in a user interface, where the user interface is described by an XML document. The specification does not limit what format the XML document is in, or what event model is used for communicating over XUP. Examples given in the specification for possible user interface languages include XHTML, Wireless Markup Language,

neg: IEEE 802.1X the authentication server determines the credentials are valid, the supplicant (client device) is allowed to access resources located on the protected side of the network. EAPOL operates over the data link layer, and in Ethernet II framing protocol has an EtherType value of 0x888E. 802.1X-2001 defines two logical port entities for an authenticated port—the "controlled port" and the "uncontrolled port". The controlled port is manipulated by the 802.1X PAE (Port Access Entity) to allow (in the authorized state) or prevent (in the unauthorized state) network traffic ingress and egress to/from the controlled port. The uncontrolled port is used by the

neg: Nexus (standard) a packet-based protocol. This protocol can be JTAG (IEEE 1149.1); or, for high-speed systems, an auxiliary port can be used that supports full duplex, higher bandwidth transfers. Key Nexus functionality involves either JTAG-style request/response interactions, or packets transferred through the debug port, and includes: A low-level application programming interface (API) is also allowed for, to mask target specifics such as the host connection mechanism (such as an emulator or Calibration-instrument) and processor specific Nexus register details. This API is produced jointly by the tool and semiconductor vendor. IEEE-ISTO 5001-2003 is a scalable standard; there are currently four classes of compliance

neg: Firewall (computing) rules, the packet filter either drops (silently discards) the packet, or rejects the packet (discards it and generate an Internet Control Message Protocol notification for the sender) else it is allowed to pass. Packets may be filtered by source and destination network addresses, protocol, source and destination port numbers. The bulk of Internet communication in 20th and early 21st century used either Transmission Control Protocol (TCP) or User Datagram Protocol (UDP) in conjunction with well-known ports, enabling firewalls of that era to distinguish between, and thus control, specific types of traffic (such as web browsing, remote printing, email transmission, file

neg: Norton Internet Security objectionable sites, separated into 32 categories. The list is updated every two weeks by Norton LiveUpdate. Using the list alone, Norton only blocks sites present on the list. Consequently, Norton may not block sites until the next update. Parents can customize the list, adding or removing sites. A list of allowed sites can be created to restrict children to those specific sites. This version uses application blocking rather than protocol or port filtering to control Internet access. Children can be restricted in what applications they used to access the Internet. A parental controls profile can be set up for each

neg: Gopher (protocol) (i.e., the port number used by that server). The item type and display string are joined without a space; the other fields are separated by the tab character. Because of the simplicity of the Gopher protocol, tools such as netcat make it possible to download Gopher content easily from the command line: The protocol is also supported by cURL as of 7.21.2-DEV. Gopher menu items are defined by lines of tab-separated values in a text file. This file is sometimes called a "gophermap". As the source code to a gopher menu, a gophermap is roughly analogous to an HTML file

neg: On-Demand Mail Relay domain (or domains) using SMTP protocol, via the same TCP connection. Since connections are initiated by customers, this protocol works well for machines having dynamically assigned IPs and/or are firewall protected (i.e. your ISP may block incoming connection on port 25 or may use NAT). Only the ODMR server, referred as the "provider", must listen to SMTP connections on a fixed IP address. The design of ODMR allows the protocol to be used with an SMTP server that doesn't support it natively. A separate application can be used to do the initial ODMR protocol negotiation (EHLO, AUTH and ATRN), then

neg: RADIUS RADIUS Remote Authentication Dial-In User Service (RADIUS) is a networking protocol, operating on port 1812 that provides centralized Authentication, Authorization, and Accounting (AAA or Triple A) management for users who connect and use a network service. RADIUS was developed by Livingston Enterprises, Inc. in 1991 as an access server authentication and accounting protocol and later brought into the Internet Engineering Task Force (IETF) standards. Because of the broad support and the ubiquitous nature of the RADIUS protocol, it is often used by Internet service providers (ISPs) and enterprises to manage access to the Internet or internal networks, wireless networks, and

neg: Spanning Tree Protocol switches have been assigned a bridge ID and the protocol has chosen the root bridge switch, the best path to the root bridge is calculated based on port cost, path cost and port priority. Ultimately STP calculates the path cost on the basis of the bandwidth of a link, however links between switches may have the same bandwidth. Administrators can influence the protocol's choice of the preferred path by configuring the port cost, the lower the port cost the more likely it is that the protocol will choose the connected link as root port for the preferred path. Before the

neg: Time Protocol GMT, and closes the connection. Operation over UDP requires the sending of any datagram to the server port, as there is no connection setup for UDP. The fixed 32-bit data format means that the timestamp rolls over approximately every 136 years, with the first such occurrence on 7 February 2036. Programs that use the Time Protocol must be carefully designed to use context-dependent information to distinguish these dates from those in 1900. Many Unix-like operating systems used the Time Protocol to monitor or synchronize their clocks using the rdate utility, but this function was superseded by the Network Time Protocol

neg: Digital Audio Access Protocol other, Digital Photo Access Protocol (DPAP), is used by iPhoto for sharing images. They both rely on an underlying protocol, Digital Media Access Protocol (DMAP). Early versions of iTunes allowed users to connect to shares across the Internet, however, in recent versions only computers on the same subnet can share music (workarounds such as port tunneling are possible). "The Register" speculates that Apple made this move in response to pressure from the record labels. More recent versions of iTunes also limit the number of clients to 5 unique IP addresses within a 24-hour period. DAAP has also been implemented in

neg: Ident protocol Ident protocol The Ident Protocol (Identification Protocol, Ident), specified in RFC 1413, is an Internet protocol that helps identify the user of a particular TCP connection. One popular daemon program for providing the ident service is identd. The Ident Protocol is designed to work as a server daemon, on a user's computer, where it receives requests to a specified TCP port, generally 113. In the query, a client specifies a pair of TCP ports (a local and a remote port), encoded as ASCII decimals and separated by a comma (,). The server then sends a response that identifies the username

neg: Smart meter and well-accepted. It sends ASCII data using a serial port. The physical media are either modulated light, sent with an LED and received with a photodiode, or a pair of wires, usually modulated by EIA-485. The protocol is half-duplex. IEC 61107 is related to, and sometimes wrongly confused with, the FLAG protocol. Ferranti and Landis+Gyr were early proponents of an interface standard that eventually became a sub-set of IEC1107. The Open Smart Grid Protocol (OSGP) is a family of specifications published by the European Telecommunications Standards Institute (ETSI) used in conjunction with the ISO/IEC 14908 control networking standard for smart