7017
Summary
- // if you see it open
- GRASP relies on an external security and transport substrate. RFC 8990 requires cryptographic member authentication and message integrity, and the substrate must restrict communication to mutually trusted group members. Port assignment does not establish the protection used by a specific deployment.
- // common applications
- Autonomic networking Expected in an autonomic networking deployment between participating nodes or service agents; the supplied evidence does not establish observed traffic or deployment frequency.
About port 7017/tcp.
IANA assigns TCP port 7017 to grasp, the GeneRic Autonomic Signaling Protocol (GRASP), and references RFC 8990. The assignment identifies the registered service; it does not show that a particular host runs GRASP or that the port is reachable from the public internet. The intended access policy for a deployment therefore remains unknown from the supplied evidence.
RFC 8990 describes GRASP as a protocol for autonomic nodes and Autonomic Service Agents to discover peers, synchronize state, and negotiate parameter settings. It is a framework for exchanging objectives whose details depend on the application scenario. GRASP uses CBOR for message representation.
GRASP does not define its own transport security. RFC 8990 requires each adopting solution to specify a security and transport substrate that limits message exchange to authenticated, mutually trusted group members and provides message integrity. The standard describes the Autonomic Control Plane as the substrate in the ANI. A port number alone cannot establish which substrate, if any, protects a given deployment.
- Protocol
- IANA assigns
7017/tcpto GRASP, the GeneRic Autonomic Signaling Protocol. [Confirmed] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv - Exposure
- Whether a specific service should be reachable from the public internet is Unknown; the assignment and RFC do not establish deployment audience or reachability. [Unknown] — https://www.rfc-editor.org/rfc/rfc8990.txt
- Security
- RFC 8990 requires an external security and transport substrate for authenticated, integrity-protected communication among trusted group members. [Confirmed] — https://www.rfc-editor.org/rfc/rfc8990.txt
- IANA service
grasp— GeneRic Autonomic Signaling Protocol [Confirmed] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv
Protocol function
Peer discovery, state synchronization, and parameter negotiation for autonomic nodes and service agents
- RFC reference
- RFC 8990 [Confirmed] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv
- Deployment or public reachability
- Unknown [Unknown] — https://www.rfc-editor.org/rfc/rfc8990.txt
About port 7017/udp.
IANA registers UDP port 7017 as grasp, the GeneRic Autonomic Signaling Protocol, and cites RFC 8990. The registration identifies the protocol assignment; it does not show that a particular host runs GRASP or establish whether the port belongs on the public internet. The intended access policy for a specific deployment is therefore Unknown from the available evidence.
RFC 8990 describes GRASP as signaling for autonomic nodes and Autonomic Service Agents to discover peers, synchronize state, and negotiate parameter settings. The RFC says GRASP depends on an external security and transport substrate that restricts messages to mutually trusted group members and provides cryptographic authentication and message integrity. The substrate and its configuration are part of the solution using GRASP.
This evidence supports identifying the registered protocol and its security model, but does not establish observed deployments, traffic prevalence, vendor implementations, or malicious use. A port match alone cannot identify the software or determine whether a service is appropriately exposed.
- Registered service
grasp(GeneRic Autonomic Signaling Protocol), assigned to UDP 7017 by IANA [Confirmed] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv- Protocol purpose
- Enables autonomic nodes and service agents to discover peers, synchronize state, and negotiate parameters [Confirmed] — https://www.rfc-editor.org/rfc/rfc8990.txt
- Exposure
- Unknown; the evidence describes use within a mutually trusted domain but does not establish public-internet deployment policy [Unknown] — https://www.rfc-editor.org/rfc/rfc8990.txt
- Security
- GRASP relies on an external substrate for group restriction, cryptographic member authentication, and message integrity [Confirmed] — https://www.rfc-editor.org/rfc/rfc8990.txt
- IANA service name
grasp[Confirmed] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv
Primary use
Signaling for autonomic peer discovery, state synchronization, and parameter negotiation
Exposure
Unknown from supplied evidence
- RFC reference
- RFC 8990 [Confirmed] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv
Service assignments.
| Name | Protocol | Description | Open frequency |
|---|---|---|---|
| grasp | TCP | GeneRic Autonomic Signaling Protocol | 0.00% |
Service assignments from the IANA Service Name and Transport Protocol Port Number Registry, with open-frequency data from nmap-services.