RFC 2358
E823481
RFC 2358 is an Internet Engineering Task Force (IETF) standards-track document that updates and replaces earlier specifications related to the Point-to-Point Protocol (PPP) and its associated network control protocols.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 2358 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T9818127 — 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 2358 Context triple: [RFC 1655, obsoletedBy, RFC 2358]
-
A.
RFC 1908
RFC 1908 is an older Internet standards document related to network management that was later superseded by RFC 3410.
-
B.
RFC 2870
RFC 2870 is an Internet Engineering Task Force (IETF) document that specifies operational and technical requirements for the DNS root name server system.
-
C.
RFC 858
RFC 858 is an early Internet standard that defines the Telnet protocol’s status option, specifying how a Telnet client and server can exchange information about their current status.
-
D.
RFC 2865
RFC 2865 is the IETF standard that specifies the Remote Authentication Dial-In User Service (RADIUS) protocol for centralized authentication, authorization, and accounting in network access.
-
E.
RFC 5838
RFC 5838 is an IETF specification that updates and extends OSPFv3 to support multiple address families, including IPv4 and IPv6, within a single protocol instance.
- 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 2358 Target entity description: RFC 2358 is an Internet Engineering Task Force (IETF) standards-track document that updates and replaces earlier specifications related to the Point-to-Point Protocol (PPP) and its associated network control protocols.
-
A.
RFC 1908
RFC 1908 is an older Internet standards document related to network management that was later superseded by RFC 3410.
-
B.
RFC 2870
RFC 2870 is an Internet Engineering Task Force (IETF) document that specifies operational and technical requirements for the DNS root name server system.
-
C.
RFC 858
RFC 858 is an early Internet standard that defines the Telnet protocol’s status option, specifying how a Telnet client and server can exchange information about their current status.
-
D.
RFC 2865
RFC 2865 is the IETF standard that specifies the Remote Authentication Dial-In User Service (RADIUS) protocol for centralized authentication, authorization, and accounting in network access.
-
E.
RFC 5838
RFC 5838 is an IETF specification that updates and extends OSPFv3 to support multiple address families, including IPv4 and IPv6, within a single protocol instance.
- F. None of above. chosen
Statements (41)
| Predicate | Object |
|---|---|
| instanceOf | RFC ⓘ |
| appliesTo |
LAN bridging over wide-area links
ⓘ
bridged Ethernet over PPP ⓘ |
| area | Internet Area NERFINISHED ⓘ |
| category | Standards Track ⓘ |
| defines |
LCP extensions for bridging
ⓘ
NCP behavior for bridging ⓘ PPP options for bridging ⓘ configuration procedures for PPP bridging ⓘ encapsulation of bridged Ethernet frames over PPP ⓘ |
| definesAbbreviation | BCP NERFINISHED ⓘ |
| definesProtocol | PPP Bridging Control Protocol NERFINISHED ⓘ |
| definesUseCase |
support of remote LAN bridging over PPP
ⓘ
transport of bridged LAN traffic over point-to-point links ⓘ |
| documentType | Standards-track specification ⓘ |
| hasSection |
Configuration Options
ⓘ
IANA Considerations ⓘ Introduction ⓘ Packet Format ⓘ Protocol Overview ⓘ Security Considerations ⓘ |
| intendedFor | Internet community ⓘ |
| isPartOf | PPP-related RFCs ⓘ |
| language | English ⓘ |
| number | 2358 ⓘ |
| obsoletes | RFC 1638 NERFINISHED ⓘ |
| publicationMonth | June ⓘ |
| publicationYear | 1998 ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedToProtocol | PPP Network Control Protocols NERFINISHED ⓘ |
| series | Request for Comments NERFINISHED ⓘ |
| specifies |
control protocol for enabling and disabling PPP bridging
ⓘ
frame format for bridged packets over PPP ⓘ negotiation of bridging capabilities between PPP peers ⓘ |
| standardsBody | Internet Engineering Task Force NERFINISHED ⓘ |
| status | Proposed Standard ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| title | PPP Bridging Control Protocol (BCP) NERFINISHED ⓘ |
| updatesProtocol |
PPP
NERFINISHED
ⓘ
Point-to-Point Protocol 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 2358 Description of subject: RFC 2358 is an Internet Engineering Task Force (IETF) standards-track document that updates and replaces earlier specifications related to the Point-to-Point Protocol (PPP) and its associated network control protocols.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.