Internet Protocol
Enable an AI agent to recognise Internet Protocol specifications and deployments, assess packet-delivery constraints, and determine compatible and authorised network actions.
Research draft, second pass
A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.
recalled by Codex without web access - no source was read
Researched by: Codex
Purpose and description
Enable an AI agent to recognise Internet Protocol specifications and deployments, assess packet-delivery constraints, and determine compatible and authorised network actions.
Internet Protocol (IP) is a network-layer protocol that specifies addressing and best-effort delivery of datagrams across interconnected networks without guaranteeing delivery, ordering, or freedom from duplication.
It can be Classify an IP packet or configuration by version and applicable specification profile.; Validate address, prefix and scope compatibility within a stated routing context.; Inspect datagram structure and identify malformed or unsupported header combinations.; Assess likely forwarding and packet-size constraints using routes, MTU evidence and diagnostics.; Plan authorised connectivity tests and distinguish observed failures from untested hypotheses.; Evaluate whether a proposed configuration or transition mechanism preserves required IP connectivity..
Distinguishing features
IP provides network-layer datagram addressing and forwarding across interconnected networks; Ethernet provides link-layer delivery.
IP delivery does not itself guarantee arrival, ordering or freedom from duplication; transport protocols may supply additional guarantees.
An IP address identifies an addressable network attachment within an addressing context, not necessarily a unique physical device or person.
IPv4 and IPv6 are versions within this entry, with distinct packet formats and addressing rules; they are not directly interchangeable on the wire.
IP forwarding uses routing information but does not itself specify how routing protocols discover and distribute routes.
Scope
+ Identification of IPv4 or IPv6 and the applicable specification profile
+ IP address semantics, prefixes, scope and interface assignment
+ Datagram headers, payload identification and extension mechanisms
+ Forwarding, delivery constraints, packet lifetime and fragmentation
+ IP interoperability, diagnostic evidence and security boundaries
- The Internet as a global infrastructure and institutional ecosystem
- Transport-layer reliability, congestion control and application sessions
- Routing-protocol algorithms and their independent operational state
- Physical media and link-layer framing or medium access
- DNS naming and application-level resource identification
- The discipline of computer networking and its practitioners or literature
Characteristics
- Protocol version
- IPv4 | IPv6 Determines address width, header interpretation and forwarding rules.
- Applicable specification profile
- Base specification and relevant updates, extensions and implementation requirements Makes conformance claims traceable to an explicit technical baseline.
- Address width
- 32 bits for IPv4; 128 bits for IPv6 Constrains address representation and prefix interpretation.
- Address role and scope
- Version-specific unicast, multicast, anycast or broadcast role where applicable; scope and special-purpose status Determines valid destinations and where an address may be used.
- Interface address assignment
- Address and prefix associated with an interface, routing context and observation time Prevents an address from being mistaken for a persistent device identity.
- Path MTU
- Octets; measured or inferred for a specified path and time Constrains packet size and exposes delivery problems caused by fragmentation or missing feedback.
- Packet lifetime control
- IPv4 Time to Live or IPv6 Hop Limit field value Limits continued forwarding and supports interpretation of expiry diagnostics.
- Observed reachability
- Confirmed for a specified test | failed for a specified test | unknown Separates observed delivery from assumptions based on address assignment or route presence.
Also called
Where this came from
wikidata · CC0 1.0
Drafted structure
Bundle to layer to finding to question, as the second pass will find it: 6 bundles · 11 layers · 19 findings · 29 questions.
Protocol identity and conformance Establishes which IP version and technical requirements govern the subject being assessed.
An agent cannot interpret packets or judge compatibility using an undifferentiated notion of IP.
Version and model boundary
Separates the IP family, its versions and concrete implementations.
IP family and version
Record whether the subject is the protocol family, an IPv4 or IPv6 specification, or a deployment supporting one or both versions.
- Does this record describe IP generally, a particular version, or a concrete implementation? definition
- Which responsibilities belong to IP here, and which belong to transport, link or routing protocols? boundary
Specification profile
Connects claimed behaviour to the technical documents and implementation evidence that support it.
Applicable IP requirements
Record the base specification, relevant updates and extensions, and evidence for implementation support.
- Which specification documents and updates define the behaviour being assessed? provenance
- What documentation or observed behaviour supports the claimed implementation conformance? provenance
Addressing and network context Captures how IP addresses and prefixes acquire meaning within a deployment.
Address syntax alone cannot establish identity, permitted use or reachability.
Address semantics
Interprets address representation, destination role and scope according to the IP version.
Address role, prefix and scope
Record the address, prefix length, version-specific role, scope and any relevant special-purpose designation.
- What IP version, prefix length and destination role apply to this address? definition
- Within which network scope or zone is this address meaningful and usable? boundary
Assignment and routing context
Relates addresses to interfaces and the forwarding environment in which they operate.
Contextual address assignment
Record interface association, assignment evidence, observation time and routing context, allowing multiple addresses and reused address spaces.
- Which interface and routing context use this address, and when was that association verified? provenance
- Could address reuse, translation or anycast make this address refer to different endpoints from different observation points? boundary
Datagram structure and processing Describes the packet information an IP implementation must interpret and the version-specific processing it requires.
Packet validity and interoperability depend on concrete header semantics rather than protocol labels.
Headers and payload dispatch
Covers base headers, length interpretation and identification of the following protocol.
Version-specific datagram interpretation
Record header fields and packet-length evidence using the selected version, including IPv4 Protocol or IPv6 Next Header interpretation.
- Are the version, header structure and length fields consistent with the available packet bytes? measurement
- Which protocol or next header does the datagram identify, and can the observer interpret it? definition
Options, extensions and fragments
Covers additional header processing and reconstruction of fragmented datagrams.
Additional processing requirements
Record IPv4 options or IPv6 extension headers, fragmentation state and evidence of receiver or intermediate-device support.
- Which options, extension headers or fragmentation fields are present, and what processing do they require? definition
- Is sufficient fragment evidence available for reassembly, or must the payload remain uninterpreted? action
Forwarding and delivery constraints Captures the conditions under which an IP datagram can progress toward its destination.
An assigned address and a valid packet do not establish successful end-to-end delivery.
Next hop and packet lifetime
Relates destination lookup, next-hop selection and lifetime limits to forwarding outcomes.
Forwarding decision evidence
Record the routing context, selected route, next hop, egress interface and remaining TTL or Hop Limit without absorbing routing-protocol design into IP.
- Which route, next hop and egress interface apply to this destination in the selected routing context? measurement
- Would the TTL or Hop Limit permit another forwarding step, and what evidence indicates expiry? measurement
Packet size and delivery evidence
Connects MTU constraints, fragmentation rules and diagnostic observations to delivery assessment.
MTU and version-specific fragmentation
Record packet size, relevant MTU evidence and fragmentation permissions; distinguish IPv4 fragmentation behaviour from IPv6, where routers do not fragment packets.
- Does the packet fit the known path MTU, and how reliable and recent is that MTU evidence? measurement
- Given the IP version and packet flags or headers, should an oversized packet be fragmented by an eligible node or discarded with applicable diagnostic feedback? action
Interoperability and operational boundaries Assesses communication across version boundaries and the limits of operational and security conclusions.
Agents must distinguish protocol compatibility from observed connectivity and from permission to change or probe a network.
Version coexistence and transition
Records how endpoints and intervening networks accommodate IPv4 and IPv6.
Cross-version connectivity mechanism
Identify native connectivity, dual-stack operation, tunnelling or translation and the address, header and packet-size consequences of the selected mechanism.
- Which IP versions are available at each endpoint and across the intervening network? measurement
- What coexistence or transition mechanism is configured, and what constraints does it impose on the proposed communication? boundary
Diagnostics, trust and authorised actions
Separates observable IP behaviour from identity guarantees, security controls and operational permissions.
Bounded connectivity and trust claims
Record test conditions, filtering and diagnostic evidence; do not treat a source address as authenticated identity or a failed probe as proof that all IP delivery is unavailable.
- What do the available packet captures, counters and diagnostic responses actually establish about connectivity or filtering? measurement
- Which probes or configuration changes are authorised, and what additional controls are required if authenticity or confidentiality is needed? action
Evidence and external alignment What the world already says about this thing, gathered so the model can be checked against it.
A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.
Reported evidence
Findings from the breadth pass, kept separate from the structural claims.
Check these first
Recalled without web access and unsourced; every item is a lead to verify.
- This describes the networking protocol, not a discipline or field of knowledge; the batch classification should be checked.
- Standards and identifiers are recalled without consulting sources; RFC updates and errata should be checked during research.
- IPv4 and IPv6 differ in fragmentation, header structure, and supporting mechanisms; detailed findings should distinguish the versions.
- Which of these check these first hold for the sense of Internet Protocol this model covers, and on what evidence? provenance
Kinds and varieties
Recalled without web access and unsourced; every item is a lead to verify.
- IPv4
- IPv6
- Which of these kinds and varieties hold for the sense of Internet Protocol this model covers, and on what evidence? provenance
Identifiers and schemes
Recalled without web access and unsourced; every item is a lead to verify.
- IP version field - 4 or 6 - A four-bit field identifies IPv4 or IPv6 in the packet header.
- IPv4 address notation - Four decimal octets separated by periods - Represents a 32-bit address; each octet ranges from 0 to 255.
- IPv6 address notation - Eight colon-separated hexadecimal groups, with permitted zero compression - Represents a 128-bit address.
- CIDR prefix notation - address/prefix-length - Prefix lengths range from 0 to 32 for IPv4 and 0 to 128 for IPv6.
- Which of these identifiers and schemes hold for the sense of Internet Protocol this model covers, and on what evidence? provenance
Standards and regulation
Recalled without web access and unsourced; every item is a lead to verify.
- RFC 791, Internet Protocol: IPv4 specification published in the RFC series.
- RFC 8200, Internet Protocol, Version 6 (IPv6) Specification: IETF.
- RFC 4291, IP Version 6 Addressing Architecture: IETF.
- RFC 4632, Classless Inter-domain Routing (CIDR): The Internet Address Assignment and Aggregation Plan: IETF.
- RFC 1122, Requirements for Internet Hosts - Communication Layers: IETF.
- Which of these standards and regulation hold for the sense of Internet Protocol this model covers, and on what evidence? provenance
Real-world use
Recalled without web access and unsourced; every item is a lead to verify.
- Carrying transport-layer traffic across the public Internet.
- Connecting hosts and subnets within enterprise and private networks.
- Providing addressing and packet forwarding across heterogeneous link technologies.
- Carrying encapsulated traffic through tunnels and virtual private networks.
- Which of these real-world use hold for the sense of Internet Protocol this model covers, and on what evidence? provenance
Typical measurements
Recalled without web access and unsourced; every item is a lead to verify.
- Address width - 32 for IPv4; 128 for IPv6 - bit
- Base header length - 20-60 for IPv4; 40 for IPv6 before extension headers - byte
- IPv6 Hop Limit - 0-255 representable; decremented at each forwarding node - hop
- Which of these typical measurements hold for the sense of Internet Protocol this model covers, and on what evidence? provenance
Failure modes and hazards
Recalled without web access and unsourced; every item is a lead to verify.
- Congestion and link failures can cause packet loss; IP itself does not retransmit lost packets.
- Routing loops or incorrect routes can cause packet expiry, misdelivery, or unreachable destinations.
- Packets exceeding a path's supported size can be dropped; failed path MTU discovery can produce connectivity black holes.
- Source-address spoofing is possible where appropriate filtering or authentication is absent.
- IP alone does not provide confidentiality or cryptographic authentication.
- Which of these failure modes and hazards hold for the sense of Internet Protocol this model covers, and on what evidence? provenance
Regional variation
Recalled without web access and unsourced; every item is a lead to verify.
- Address allocation and registration are administered through regional Internet registries under globally coordinated arrangements.
- IPv6 deployment and reliance on IPv4 address sharing vary among countries, operators, and networks.
- Which of these regional variation hold for the sense of Internet Protocol this model covers, and on what evidence? provenance
Neighbouring kinds and how to tell them apart
Recalled without web access and unsourced; every item is a lead to verify.
- Internet protocol suite - The suite includes IP and numerous associated protocols; IP is its network-layer datagram protocol.
- Transmission Control Protocol - TCP provides reliable, ordered byte streams between endpoints using IP for packet delivery.
- User Datagram Protocol - UDP adds transport-layer ports and datagram delivery between applications over IP.
- Ethernet - Ethernet supplies link-layer framing and delivery on a local link; IP supports delivery across interconnected networks.
- Border Gateway Protocol - BGP exchanges routing information used to select paths; IP defines the datagrams forwarded along those paths.
- Which of these neighbouring kinds and how to tell them apart hold for the sense of Internet Protocol this model covers, and on what evidence? provenance
What the second pass must settle
- Does the registry intend the full IPv4 and IPv6 family, and should its classification be corrected from an apparent field-of-knowledge grouping to a protocol specification?
- Which existing Vercy world models already own IP or overlapping network-layer concepts, requiring linkage instead of a duplicate publication?
- Which base specifications, updates and extensions should define the researched conformance baseline for each IP version?
- How should ownership of ICMP, neighbour discovery, address configuration, translation and IPsec be divided between this model and neighbouring models?
- What deployment evidence and observation freshness are sufficient to support claims about reachability, path MTU and extension-header compatibility?