RFC 3977
E827892
RFC 3977 is the Internet standard that defines the Network News Transfer Protocol (NNTP), updating and replacing the earlier specification in RFC 977.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 3977 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T9865337 — 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 3977 Context triple: [RFC 977, supersededBy, RFC 3977]
-
A.
RFC 3947
RFC 3947 is an IETF standard that specifies how to detect and negotiate IPsec NAT Traversal (NAT-T) using IKE.
-
B.
RFC 3727
RFC 3727 is an Internet Engineering Task Force (IETF) document that defined earlier specifications for LDAP-related schema or matching rules, later superseded by RFC 4517.
-
C.
RFC 5907
RFC 5907 is an Internet Engineering Task Force (IETF) document that defines management information base (MIB) modules for monitoring and managing the Network Time Protocol (NTP) as specified in RFC 5905.
-
D.
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.
-
E.
RFC 3980
RFC 3980 is an Internet Engineering Task Force (IETF) document that previously specified aspects of the iSCSI (Internet Small Computer Systems Interface) protocol before being superseded by RFC 7143.
- 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 3977 Target entity description: RFC 3977 is the Internet standard that defines the Network News Transfer Protocol (NNTP), updating and replacing the earlier specification in RFC 977.
-
A.
RFC 3947
RFC 3947 is an IETF standard that specifies how to detect and negotiate IPsec NAT Traversal (NAT-T) using IKE.
-
B.
RFC 3727
RFC 3727 is an Internet Engineering Task Force (IETF) document that defined earlier specifications for LDAP-related schema or matching rules, later superseded by RFC 4517.
-
C.
RFC 5907
RFC 5907 is an Internet Engineering Task Force (IETF) document that defines management information base (MIB) modules for monitoring and managing the Network Time Protocol (NTP) as specified in RFC 5905.
-
D.
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.
-
E.
RFC 3980
RFC 3980 is an Internet Engineering Task Force (IETF) document that previously specified aspects of the iSCSI (Internet Small Computer Systems Interface) protocol before being superseded by RFC 7143.
- F. None of above. chosen
Statements (46)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ |
| abbrev | NNTP NERFINISHED ⓘ |
| area | Applications Area ⓘ |
| category | Standards Track ⓘ |
| defines |
article retrieval mechanisms for NNTP
ⓘ
authentication framework for NNTP ⓘ capability negotiation for NNTP ⓘ client-server protocol for reading and posting Usenet articles ⓘ commands for NNTP ⓘ error codes for NNTP ⓘ group selection mechanisms for NNTP ⓘ message formats for NNTP ⓘ responses for NNTP ⓘ streaming extensions for NNTP ⓘ |
| definesConformanceRequirementsFor | NNTP implementations ⓘ |
| definesProtocol | Network News Transfer Protocol NERFINISHED ⓘ |
| documentType | Standards-track protocol specification ⓘ |
| intendedAudience |
implementers of NNTP clients
ⓘ
implementers of NNTP servers ⓘ |
| language | English ⓘ |
| obsoletes | RFC 977 ⓘ |
| obsoletesSpecification | Network News Transfer Protocol as defined in RFC 977 ⓘ |
| partOf | NNTP standards family ⓘ |
| portNumber | 119 ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| publishedInSeries | Request for Comments NERFINISHED ⓘ |
| relatedTo |
Internet messaging
ⓘ
Usenet NERFINISHED ⓘ email-like protocols ⓘ |
| replaces | original NNTP specification ⓘ |
| rfcNumber | 3977 ⓘ |
| securePortNumber | 563 ⓘ |
| specifies |
article numbering and message identifiers in NNTP
ⓘ
capability discovery via CAPABILITIES command ⓘ error handling rules for NNTP ⓘ group status and article range reporting in NNTP ⓘ minimum feature set for compliant NNTP clients ⓘ minimum feature set for compliant NNTP servers ⓘ use of UTF-8 in certain NNTP contexts ⓘ |
| standardizes | NNTP over TCP NERFINISHED ⓘ |
| status | Proposed Standard ⓘ |
| title | Network News Transfer Protocol (NNTP) NERFINISHED ⓘ |
| updatesSpecificationOf | Network News Transfer Protocol NERFINISHED ⓘ |
| usesTransportProtocol | TCP 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 3977 Description of subject: RFC 3977 is the Internet standard that defines the Network News Transfer Protocol (NNTP), updating and replacing the earlier specification in RFC 977.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.