The Experts below are selected from a list of 2601 Experts worldwide ranked by ideXlab platform

Quantum Corporation - One of the best experts on this subject based on the ideXlab platform.

  • Changed name to Network ADT (iADT).
    2008
    Co-Authors: From Paul, A. Suhler, Quantum Corporation
    Abstract:

    Added Registered Port number. Allowed iADT Ports to use any Port number. Removed iADT-specific baud rate and TimeoutACK. 2 Second revision (11 April 2008) Deleted the ABORT service request and the ABORTED service indication. Added analysis of existing state machines, link services, and frame header fields. Added analysis of physical layer connections. 3 Third revision (30 April 2008) Added discussion of including legacy ADT signals in new Custom Connector section. Added proposed connector signal name and pinout. 4 Fourth revision (29 May 2008) Separated the concept of an “ADT Port ” from an “ADT interconnect Port.” Added link layer protocol services generic to all physical layers, as well as mappings to RS-422, TCP, and UDP. Added requirement for ADT Ports using Ethernet to ignore negotiated baud rate in computing acknowledgement timeout. 5 Fifth revision (13 June 2008) Incorporated changes from 4 June 2008 teleconference, minutes in T10/08-256r0. Enhanced model section. Removed LED connections from ADT Ethernet bus description. Added descriptions of LED blinking. Specified a fixed TimeoutACK in seconds for ADT TCP connections. Deleted ADT UDP interconnect

William R. Simpson - One of the best experts on this subject based on the ideXlab platform.

  • Enterprise Considerations for Ports and Protocols
    2016
    Co-Authors: Kevin E. Foltz, William R. Simpson
    Abstract:

    Abstract : The need to control information flow to a restricted set of accepted protocols arises from the vulnerabilities that may come from any protocol. Reducing the acceptable protocols to a small set of well-tested standard protocols will reduce the attack surface and provide high confidence in selected communications. These protocols are restricted to specific Ports or addresses in the receiving web service. HTTPS is familiarly restricted to Port 443. In the standard nomenclature, this traffic may be configured as either Transmission Control Protocol (TCP) or User Datagram Protocol (UDP). The standard Ports are defined by Internet Assigned Numbers Authority (IANA). The IANA is responsible for maintaining the official assignments of Port numbers for specific uses. However, many unofficial uses of both well-known and Registered Port numbers occur in practice. Screening of acceptable Ports and protocols has been done, in the past, by network appliances known as firewalls. Communications on the approved list were permitted, others blocked. However, many appliances now have such functionality and the server or service may have a host-based security system that can apply this functionality. This paper covers enterprise considerations for screening of Ports and protocols.

From Paul - One of the best experts on this subject based on the ideXlab platform.

  • Changed name to Network ADT (iADT).
    2008
    Co-Authors: From Paul, A. Suhler, Quantum Corporation
    Abstract:

    Added Registered Port number. Allowed iADT Ports to use any Port number. Removed iADT-specific baud rate and TimeoutACK. 2 Second revision (11 April 2008) Deleted the ABORT service request and the ABORTED service indication. Added analysis of existing state machines, link services, and frame header fields. Added analysis of physical layer connections. 3 Third revision (30 April 2008) Added discussion of including legacy ADT signals in new Custom Connector section. Added proposed connector signal name and pinout. 4 Fourth revision (29 May 2008) Separated the concept of an “ADT Port ” from an “ADT interconnect Port.” Added link layer protocol services generic to all physical layers, as well as mappings to RS-422, TCP, and UDP. Added requirement for ADT Ports using Ethernet to ignore negotiated baud rate in computing acknowledgement timeout. 5 Fifth revision (13 June 2008) Incorporated changes from 4 June 2008 teleconference, minutes in T10/08-256r0. Enhanced model section. Removed LED connections from ADT Ethernet bus description. Added descriptions of LED blinking. Specified a fixed TimeoutACK in seconds for ADT TCP connections. Deleted ADT UDP interconnect

Kevin E. Foltz - One of the best experts on this subject based on the ideXlab platform.

  • Enterprise Considerations for Ports and Protocols
    2016
    Co-Authors: Kevin E. Foltz, William R. Simpson
    Abstract:

    Abstract : The need to control information flow to a restricted set of accepted protocols arises from the vulnerabilities that may come from any protocol. Reducing the acceptable protocols to a small set of well-tested standard protocols will reduce the attack surface and provide high confidence in selected communications. These protocols are restricted to specific Ports or addresses in the receiving web service. HTTPS is familiarly restricted to Port 443. In the standard nomenclature, this traffic may be configured as either Transmission Control Protocol (TCP) or User Datagram Protocol (UDP). The standard Ports are defined by Internet Assigned Numbers Authority (IANA). The IANA is responsible for maintaining the official assignments of Port numbers for specific uses. However, many unofficial uses of both well-known and Registered Port numbers occur in practice. Screening of acceptable Ports and protocols has been done, in the past, by network appliances known as firewalls. Communications on the approved list were permitted, others blocked. However, many appliances now have such functionality and the server or service may have a host-based security system that can apply this functionality. This paper covers enterprise considerations for screening of Ports and protocols.

A. Suhler - One of the best experts on this subject based on the ideXlab platform.

  • Changed name to Network ADT (iADT).
    2008
    Co-Authors: From Paul, A. Suhler, Quantum Corporation
    Abstract:

    Added Registered Port number. Allowed iADT Ports to use any Port number. Removed iADT-specific baud rate and TimeoutACK. 2 Second revision (11 April 2008) Deleted the ABORT service request and the ABORTED service indication. Added analysis of existing state machines, link services, and frame header fields. Added analysis of physical layer connections. 3 Third revision (30 April 2008) Added discussion of including legacy ADT signals in new Custom Connector section. Added proposed connector signal name and pinout. 4 Fourth revision (29 May 2008) Separated the concept of an “ADT Port ” from an “ADT interconnect Port.” Added link layer protocol services generic to all physical layers, as well as mappings to RS-422, TCP, and UDP. Added requirement for ADT Ports using Ethernet to ignore negotiated baud rate in computing acknowledgement timeout. 5 Fifth revision (13 June 2008) Incorporated changes from 4 June 2008 teleconference, minutes in T10/08-256r0. Enhanced model section. Removed LED connections from ADT Ethernet bus description. Added descriptions of LED blinking. Specified a fixed TimeoutACK in seconds for ADT TCP connections. Deleted ADT UDP interconnect