RFC 2203
E724130
RFC 2203 is an Internet standard that specifies the RPCSEC_GSS security protocol extension for providing authentication, integrity, and confidentiality in Remote Procedure Call (RPC) systems using GSS-API.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 2203 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T8285214 — 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 2203 Context triple: [RPCSEC_GSS, standardizedIn, RFC 2203]
-
A.
RFC 2572
RFC 2572 is an earlier IETF specification that defined the Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) before being superseded by RFC 3412.
-
B.
RFC 3207
RFC 3207 is the Internet standard that specifies the STARTTLS extension for upgrading plain text email connections to use TLS encryption in SMTP.
-
C.
RFC 3652
RFC 3652 is an IETF standards-track document that specifies the technical architecture and protocols of the Handle System for assigning, managing, and resolving persistent digital identifiers.
-
D.
RFC 2026
RFC 2026 is an Internet Engineering Task Force (IETF) document that defines the standardization process and procedures for developing and approving Internet Standards.
-
E.
RFC 2279
RFC 2279 is an older Internet standard that originally defined UTF-8 as a transformation format for Unicode, later superseded by RFC 3629.
- 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 2203 Target entity description: RFC 2203 is an Internet standard that specifies the RPCSEC_GSS security protocol extension for providing authentication, integrity, and confidentiality in Remote Procedure Call (RPC) systems using GSS-API.
-
A.
RFC 2572
RFC 2572 is an earlier IETF specification that defined the Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) before being superseded by RFC 3412.
-
B.
RFC 3207
RFC 3207 is the Internet standard that specifies the STARTTLS extension for upgrading plain text email connections to use TLS encryption in SMTP.
-
C.
RFC 3652
RFC 3652 is an IETF standards-track document that specifies the technical architecture and protocols of the Handle System for assigning, managing, and resolving persistent digital identifiers.
-
D.
RFC 2026
RFC 2026 is an Internet Engineering Task Force (IETF) document that defines the standardization process and procedures for developing and approving Internet Standards.
-
E.
RFC 2279
RFC 2279 is an older Internet standard that originally defined UTF-8 as a transformation format for Unicode, later superseded by RFC 3629.
- F. None of above. chosen
Statements (42)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ |
| appliesTo |
ONC RPC
NERFINISHED
ⓘ
Remote Procedure Call (RPC) systems ⓘ |
| area | Transport Area NERFINISHED ⓘ |
| category | Standards Track ⓘ |
| defines |
mechanism-independent security for RPC
ⓘ
per-RPC-call security services ⓘ security context establishment for RPC ⓘ |
| definesField |
RPCSEC_GSS credential format
ⓘ
RPCSEC_GSS sequence numbers ⓘ RPCSEC_GSS verifier format ⓘ |
| definesOperation |
context creation procedure
ⓘ
context destruction procedure ⓘ per-message protection operations ⓘ |
| definesProtocol | RPCSEC_GSS NERFINISHED ⓘ |
| intendedUse | secure remote procedure calls over untrusted networks ⓘ |
| language | English ⓘ |
| networkLayer | application layer ⓘ |
| obsoletedBy | RFC 5403 NERFINISHED ⓘ |
| provides |
authentication for RPC
ⓘ
confidentiality for RPC ⓘ integrity protection for RPC ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedTo |
NFS version 3
ⓘ
NFS version 4 ⓘ |
| RFCNumber | 2203 ⓘ |
| scope | Internet-wide RPC security ⓘ |
| securityProperty |
prevents message tampering at RPC layer
ⓘ
prevents replay attacks at RPC layer ⓘ supports privacy via encryption ⓘ |
| specifies | RPCSEC_GSS security protocol extension NERFINISHED ⓘ |
| standardizes | use of GSS-API with RPC ⓘ |
| status | Proposed Standard ⓘ |
| targetAudience |
RPC implementers
ⓘ
protocol designers ⓘ security architects ⓘ |
| title | RPCSEC_GSS Protocol Specification NERFINISHED ⓘ |
| updatesSpecificationOf | Remote Procedure Call NERFINISHED ⓘ |
| usesFramework |
GSS-API
NERFINISHED
ⓘ
Generic Security Service Application Program Interface 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 2203 Description of subject: RFC 2203 is an Internet standard that specifies the RPCSEC_GSS security protocol extension for providing authentication, integrity, and confidentiality in Remote Procedure Call (RPC) systems using GSS-API.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.