RFC 7320
E246334
RFC 7320 is an Internet Engineering Task Force (IETF) document that provided guidelines and best practices for the use and management of URI registries in Internet protocols.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 7320 canonical | 4 |
How this entity was disambiguated
This entity first appeared as the object of triple T2222907 — 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 7320 Context triple: [RFC 9205, obsoletes, RFC 7320]
-
A.
RFC 7720
RFC 7720 is an IETF standards document that specifies the technical and operational requirements for the DNS Root Server System.
-
B.
RFC 8332
RFC 8332 is an Internet Engineering Task Force (IETF) standard that updates and replaces earlier SSH protocol specifications to enhance security and functionality.
-
C.
RFC 7539
RFC 7539 is an IETF standard that specifies the ChaCha20 stream cipher and the Poly1305 message authentication code for use in secure Internet protocols.
-
D.
RFC 7950
RFC 7950 is the IETF specification that standardizes the YANG 1.1 data modeling language used for modeling configuration and state data in network management protocols.
-
E.
RFC 7143
RFC 7143 is the Internet Engineering Task Force (IETF) standard that defines the updated core specification for the iSCSI (Internet Small Computer Systems Interface) protocol used for block-level storage over IP networks.
- 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 7320 Target entity description: RFC 7320 is an Internet Engineering Task Force (IETF) document that provided guidelines and best practices for the use and management of URI registries in Internet protocols.
-
A.
RFC 7720
RFC 7720 is an IETF standards document that specifies the technical and operational requirements for the DNS Root Server System.
-
B.
RFC 8332
RFC 8332 is an Internet Engineering Task Force (IETF) standard that updates and replaces earlier SSH protocol specifications to enhance security and functionality.
-
C.
RFC 7539
RFC 7539 is an IETF standard that specifies the ChaCha20 stream cipher and the Poly1305 message authentication code for use in secure Internet protocols.
-
D.
RFC 7950
RFC 7950 is the IETF specification that standardizes the YANG 1.1 data modeling language used for modeling configuration and state data in network management protocols.
-
E.
RFC 7143
RFC 7143 is the Internet Engineering Task Force (IETF) standard that defines the updated core specification for the iSCSI (Internet Small Computer Systems Interface) protocol used for block-level storage over IP networks.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standards document
ⓘ
Request for Comments ⓘ |
| aimsTo |
improve long-term stability of URI registries
ⓘ
promote interoperability of URI usage ⓘ reduce ambiguity in URI ownership ⓘ |
| area | Applications ⓘ |
| BCPNumber | BCP 190 ⓘ |
| category | Best Current Practice ⓘ |
| definesGuidelinesFor |
URI design in Internet protocols
ⓘ
linked to:
RFC 3986
management of URI registries ⓘ use of URI registries in Internet protocols ⓘ |
| focusesOn |
URI ownership
ⓘ
change control for URI schemes and parameters ⓘ security considerations for URI registries ⓘ stability of registered URIs ⓘ |
| governs |
design of new URI schemes in IETF protocols
ⓘ
use of existing URI schemes in IETF protocols ⓘ |
| hasSection |
IANA Considerations
ⓘ
Security Considerations ⓘ |
| hasURI | https://www.rfc-editor.org/rfc/rfc7320 ⓘ |
| intendedAudience |
IETF working groups
ⓘ
protocol designers ⓘ registry operators ⓘ |
| isPartOfSeries | RFC series ⓘ |
| language | English ⓘ |
| obsoletes | RFC 4395 ⓘ |
| publishedAs | RFC 7320 ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| publishedDate | 2014-07 ⓘ |
| registryPolicy |
discourages protocol-specific ownership of generic URIs
ⓘ
emphasizes clear change control policies ⓘ recommends stable, long-term ownership of URIs ⓘ |
| relatedTo |
IANA registries
ⓘ
URI parameter registration ⓘ URI scheme registration ⓘ |
| standardizationLevel | Best Current Practice (BCP) ⓘ |
| status | Best Current Practice ⓘ |
| stream |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| subject |
IANA policy
ⓘ
Internet protocol design ⓘ Internet registries ⓘ
linked to:
Regional Internet Registries
Uniform Resource Identifiers ⓘ
linked to:
RFC 3986
|
| title | URI Design and Ownership ⓘ |
| updates | RFC 3986 ⓘ |
| workingGroup | Applications Area ⓘ |
| year | 2014 ⓘ |
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 7320 Description of subject: RFC 7320 is an Internet Engineering Task Force (IETF) document that provided guidelines and best practices for the use and management of URI registries in Internet protocols.
Referenced by (4)
Full triples — surface form annotated when it differs from this entity's canonical label.