RFC 3232
E741736
RFC 3232 is an IETF document that provides the current list of assigned Internet protocol numbers and related parameters, updating and replacing earlier registries.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 3232 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T8530335 — 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.
Target entity: RFC 3232 Context triple: [RFC 870, obsoletedBy, RFC 3232]
-
A.
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.
-
B.
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.
-
C.
RFC 3410
RFC 3410 is an informational RFC that provides an overview, framework, and goals for the Simple Network Management Protocol version 3 (SNMPv3) and its related specifications.
-
D.
RFC 1452
RFC 1452 is an early Internet standards document that was later superseded by RFC 1901 as part of the evolution of network protocols.
-
E.
RFC 3530
RFC 3530 is the IETF specification that defines version 4 of the Network File System (NFSv4) protocol for file sharing over networks.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Target entity: RFC 3232 Target entity description: RFC 3232 is an IETF document that provides the current list of assigned Internet protocol numbers and related parameters, updating and replacing earlier registries.
-
A.
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.
-
B.
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.
-
C.
RFC 3410
RFC 3410 is an informational RFC that provides an overview, framework, and goals for the Simple Network Management Protocol version 3 (SNMPv3) and its related specifications.
-
D.
RFC 1452
RFC 1452 is an early Internet standards document that was later superseded by RFC 1901 as part of the evolution of network protocols.
-
E.
RFC 3530
RFC 3530 is the IETF specification that defines version 4 of the Network File System (NFSv4) protocol for file sharing over networks.
- F. None of above. chosen
Statements (36)
| Predicate | Object |
|---|---|
| instanceOf |
IETF document
ⓘ
Request for Comments ⓘ |
| area | General ⓘ |
| BCPNumber | BCP 26 NERFINISHED ⓘ |
| category | Best Current Practice ⓘ |
| concerns |
Internet protocol numbers
NERFINISHED
ⓘ
port numbers ⓘ protocol parameter values ⓘ |
| defines |
procedure for maintaining IANA protocol parameter registries
ⓘ
relationship between RFCs and IANA registries for protocol parameters ⓘ |
| delegatesTo | IANA for maintaining up-to-date protocol parameter registries ⓘ |
| documentType | Standards-related specification ⓘ |
| focusesOn | current list of assigned Internet protocol numbers and related parameters ⓘ |
| goal | ensure that protocol parameter assignments are maintained online rather than in a single static RFC ⓘ |
| intendedAudience |
IANA staff
ⓘ
Internet protocol designers ⓘ network implementers ⓘ |
| language | English ⓘ |
| obsoletes | RFC 1700 NERFINISHED ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| publisher | RFC Editor NERFINISHED ⓘ |
| registryAuthority |
IANA
NERFINISHED
ⓘ
Internet Assigned Numbers Authority NERFINISHED ⓘ |
| relationshipWith | IANA protocol parameter registries NERFINISHED ⓘ |
| replaces | static Assigned Numbers document model ⓘ |
| series | RFC series NERFINISHED ⓘ |
| standardizationBody | IETF NERFINISHED ⓘ |
| status | Best Current Practice ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| subject |
IANA registries
ⓘ
Internet protocol parameter assignment NERFINISHED ⓘ assigned numbers ⓘ |
| title | Assigned Numbers NERFINISHED ⓘ |
| updates | RFC 1700 NERFINISHED ⓘ |
| workingGroup | IETF General Area 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.
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.
Subject: RFC 3232 Description of subject: RFC 3232 is an IETF document that provides the current list of assigned Internet protocol numbers and related parameters, updating and replacing earlier registries.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.