RFC 4555
E522217
RFC 4555 is an Internet Engineering Task Force (IETF) specification that defines the MOBIKE (IKEv2 Mobility and Multihoming) protocol extensions for the IKEv2 key management protocol.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 4555 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T5479148 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 4555 Context triple: [IKEv2, MOBIKEDefinedInRFC, RFC 4555]
-
A.
RFC 5155
RFC 5155 is an Internet standards document that specifies the NSEC3 extension to DNSSEC, enhancing DNS security by providing authenticated denial of existence while mitigating zone enumeration.
-
B.
RFC 4175
RFC 4175 is an IETF standard that specifies the packetization of uncompressed video over RTP for professional media over IP networks.
-
C.
RFC 4516
RFC 4516 is an Internet standard that specifies the LDAP (Lightweight Directory Access Protocol) Uniform Resource Locator (URL) format used to locate and access directory entries over a network.
-
D.
RFC 6145
RFC 6145 is an IETF standard that specifies the stateless translation mechanism between IPv4 and IPv6 packet headers used in NAT64 environments.
-
E.
RFC 4954
RFC 4954 is an Internet standard that specifies the SMTP Authentication (SMTP AUTH) extension, enabling secure client authentication when sending email.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 4555 Target entity description: RFC 4555 is an Internet Engineering Task Force (IETF) specification that defines the MOBIKE (IKEv2 Mobility and Multihoming) protocol extensions for the IKEv2 key management protocol.
-
A.
RFC 5155
RFC 5155 is an Internet standards document that specifies the NSEC3 extension to DNSSEC, enhancing DNS security by providing authenticated denial of existence while mitigating zone enumeration.
-
B.
RFC 4175
RFC 4175 is an IETF standard that specifies the packetization of uncompressed video over RTP for professional media over IP networks.
-
C.
RFC 4516
RFC 4516 is an Internet standard that specifies the LDAP (Lightweight Directory Access Protocol) Uniform Resource Locator (URL) format used to locate and access directory entries over a network.
-
D.
RFC 6145
RFC 6145 is an IETF standard that specifies the stateless translation mechanism between IPv4 and IPv6 packet headers used in NAT64 environments.
-
E.
RFC 4954
RFC 4954 is an Internet standard that specifies the SMTP Authentication (SMTP AUTH) extension, enabling secure client authentication when sending email.
- F. None of above. chosen
Statements (40)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standard-track document
ⓘ
Request for Comments ⓘ |
| abbreviation | RFC 4555 ⓘ |
| appliesTo |
VPN scenarios with roaming clients
ⓘ
mobile IPsec gateways ⓘ multihomed hosts ⓘ |
| area |
Internet
NERFINISHED
ⓘ
Security ⓘ |
| category | Standards Track ⓘ |
| defines |
IKEv2 Mobility and Multihoming extensions
NERFINISHED
ⓘ
MOBIKE NERFINISHED ⓘ MOBIKE protocol behavior for NAT traversal scenarios ⓘ new IKEv2 exchange mechanisms for MOBIKE ⓘ new IKEv2 payloads for mobility and multihoming ⓘ procedures for updating IKEv2 endpoints’ IP addresses ⓘ |
| documentType | Standards-track RFC ⓘ |
| enables |
changing IP addresses for IKEv2 peers without re-establishing security associations
ⓘ
support for multiple IP addresses per endpoint in IKEv2 ⓘ |
| extends | IKEv2 NERFINISHED ⓘ |
| focusesOn |
mobility support for IKEv2
ⓘ
multihoming support for IKEv2 ⓘ |
| hasProtocolName | MOBIKE NERFINISHED ⓘ |
| intendedUse | Internet-wide deployment ⓘ |
| language | English ⓘ |
| protocolScope |
IKEv2
NERFINISHED
ⓘ
IPsec NERFINISHED ⓘ |
| protocolType | key management protocol extension ⓘ |
| publicationMonth | June ⓘ |
| publicationYear | 2006 ⓘ |
| publisher | RFC Editor NERFINISHED ⓘ |
| relation | part of the IPsec and IKEv2 standards family ⓘ |
| securityDomain | IPsec key management ⓘ |
| series | Request for Comments ⓘ |
| shortTitle | MOBIKE NERFINISHED ⓘ |
| standardsBody | Internet Engineering Task Force NERFINISHED ⓘ |
| status | Proposed Standard ⓘ |
| targetEnvironment |
IPv4 networks
ⓘ
IPv6 networks ⓘ |
| title | IKEv2 Mobility and Multihoming (MOBIKE) NERFINISHED ⓘ |
| updatesProtocol | Internet Key Exchange Protocol Version 2 NERFINISHED ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: RFC 4555 Description of subject: RFC 4555 is an Internet Engineering Task Force (IETF) specification that defines the MOBIKE (IKEv2 Mobility and Multihoming) protocol extensions for the IKEv2 key management protocol.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.