RFC 2028
E876214
RFC 2028 is an Internet Engineering Task Force (IETF) document that defines the procedures and organizational structure for the Internet Standards Process and the roles of key IETF bodies.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 2028 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T10623790 — 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 2028 Context triple: [RFC 2026, updates, RFC 2028]
-
A.
RFC 2830
RFC 2830 is an Internet standard that originally specified how to use Transport Layer Security (TLS) to secure LDAP (Lightweight Directory Access Protocol) connections.
-
B.
RFC 2228
RFC 2228 is an Internet standard that extends the File Transfer Protocol (FTP) with security mechanisms such as authentication, integrity, and confidentiality.
-
C.
RFC 2358
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.
-
D.
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.
-
E.
RFC 2845
RFC 2845 is the Internet standard that specifies the Transaction SIGnature (TSIG) mechanism for securing DNS transactions using shared secret keys and message authentication codes.
- 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 2028 Target entity description: RFC 2028 is an Internet Engineering Task Force (IETF) document that defines the procedures and organizational structure for the Internet Standards Process and the roles of key IETF bodies.
-
A.
RFC 2830
RFC 2830 is an Internet standard that originally specified how to use Transport Layer Security (TLS) to secure LDAP (Lightweight Directory Access Protocol) connections.
-
B.
RFC 2228
RFC 2228 is an Internet standard that extends the File Transfer Protocol (FTP) with security mechanisms such as authentication, integrity, and confidentiality.
-
C.
RFC 2358
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.
-
D.
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.
-
E.
RFC 2845
RFC 2845 is the Internet standard that specifies the Transaction SIGnature (TSIG) mechanism for securing DNS transactions using shared secret keys and message authentication codes.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standards process document
ⓘ
Request for Comments ⓘ |
| area | General ⓘ |
| author | Scott O. Bradner NERFINISHED ⓘ |
| bcpNumber | 11 ⓘ |
| category | Best Current Practice ⓘ |
| defines |
IETF decision-making structure
ⓘ
IETF standards-related organizations ⓘ Internet Standards Process NERFINISHED ⓘ Internet standards track procedures ⓘ appeal and review procedures in the IETF standards process ⓘ organizational structure for the IETF standards process ⓘ procedures for Internet Standards ⓘ relationships among IETF, IAB, and IESG ⓘ requirements for advancing documents on the standards track ⓘ roles of IAB ⓘ roles of IESG ⓘ roles of IETF Area Directors ⓘ roles of IETF Chair ⓘ roles of IETF Secretariat ⓘ roles of IETF Working Groups ⓘ roles of external organizations in the IETF standards process ⓘ |
| editor | Scott O. Bradner NERFINISHED ⓘ |
| format | text ⓘ |
| hasURI | https://www.rfc-editor.org/rfc/rfc2028 ⓘ |
| isPartOf | BCP 11 ⓘ |
| language | English ⓘ |
| number | 2028 ⓘ |
| obsoletedBy |
RFC 3932
NERFINISHED
ⓘ
RFC 4714 NERFINISHED ⓘ RFC 4844 NERFINISHED ⓘ RFC 4845 NERFINISHED ⓘ RFC 5620 NERFINISHED ⓘ RFC 6635 NERFINISHED ⓘ RFC 8728 NERFINISHED ⓘ RFC 9280 NERFINISHED ⓘ |
| organization | Harvard University NERFINISHED ⓘ |
| published | 1996-10 ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| series | RFC NERFINISHED ⓘ |
| status | Obsoleted ⓘ |
| stdStatus | Best Current Practice ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| title | The Organizations Involved in the IETF Standards Process NERFINISHED ⓘ |
| updates | RFC 1602 ⓘ |
| year | 1996 ⓘ |
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 2028 Description of subject: RFC 2028 is an Internet Engineering Task Force (IETF) document that defines the procedures and organizational structure for the Internet Standards Process and the roles of key IETF bodies.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.