RFC 4395
E863224
RFC 4395 was an IETF document that originally defined the procedures and guidelines for registering new URI schemes before being superseded by RFC 7320.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 4395 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T10447640 — 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 4395 Context triple: [RFC 7320, obsoletes, RFC 4395]
-
A.
RFC 3995
RFC 3995 is an IETF specification that defines the Event Notifications extension for the Internet Printing Protocol (IPP), enabling printers and print services to send asynchronous status and alert messages to clients.
-
B.
RFC 4954
RFC 4954 is an Internet standard that specifies the SMTP Authentication (SMTP AUTH) extension, enabling secure client authentication when sending email.
-
C.
RFC 3947
RFC 3947 is an IETF standard that specifies how to detect and negotiate IPsec NAT Traversal (NAT-T) using IKE.
-
D.
RFC 3948
RFC 3948 is an IETF standard that specifies how to encapsulate IPsec ESP packets over UDP to enable IPsec traversal through NAT devices.
-
E.
RFC 3490
RFC 3490 is an Internet standard that defines Internationalized Domain Names in Applications (IDNA), enabling the use of non-ASCII characters in domain names.
- 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 4395 Target entity description: RFC 4395 was an IETF document that originally defined the procedures and guidelines for registering new URI schemes before being superseded by RFC 7320.
-
A.
RFC 3995
RFC 3995 is an IETF specification that defines the Event Notifications extension for the Internet Printing Protocol (IPP), enabling printers and print services to send asynchronous status and alert messages to clients.
-
B.
RFC 4954
RFC 4954 is an Internet standard that specifies the SMTP Authentication (SMTP AUTH) extension, enabling secure client authentication when sending email.
-
C.
RFC 3947
RFC 3947 is an IETF standard that specifies how to detect and negotiate IPsec NAT Traversal (NAT-T) using IKE.
-
D.
RFC 3948
RFC 3948 is an IETF standard that specifies how to encapsulate IPsec ESP packets over UDP to enable IPsec traversal through NAT devices.
-
E.
RFC 3490
RFC 3490 is an Internet standard that defines Internationalized Domain Names in Applications (IDNA), enabling the use of non-ASCII characters in domain names.
- F. None of above. chosen
Statements (44)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
Standards-track document ⓘ |
| area | Applications Area ⓘ |
| BCPNumber | BCP 35 ⓘ |
| category | Best Current Practice ⓘ |
| concerns |
maintenance of URI scheme registry
ⓘ
registration of new URI schemes ⓘ |
| defines |
guidelines for registering new URI schemes
ⓘ
procedures for registering new URI schemes ⓘ requirements for historical URI schemes ⓘ requirements for permanent URI schemes ⓘ requirements for provisional URI schemes ⓘ |
| documentClass | Internet Standards-related document ⓘ |
| focusesOn |
IANA registration policy for URI schemes
ⓘ
URI scheme design guidelines ⓘ security considerations for URI schemes ⓘ |
| governs |
expert review process for URI schemes
ⓘ
process for historical URI scheme registration ⓘ process for permanent URI scheme registration ⓘ process for provisional URI scheme registration ⓘ |
| hasNumber | 4395 ⓘ |
| hasSuccessor |
RFC 7320
ⓘ
RFC 7595 ⓘ |
| intendedAudience |
IANA experts
ⓘ
linked to:
IANA
URI scheme authors ⓘ protocol designers ⓘ |
| language | English ⓘ |
| obsoletedBy |
RFC 7320
ⓘ
RFC 7595 ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
RFC Editor ⓘ |
| registry | IANA URI Schemes registry ⓘ |
| relatedTo |
URI scheme registry
ⓘ
Uniform Resource Identifier ⓘ |
| series |
Request for Comments
ⓘ
linked to:
RFCs
|
| specifies | IANA considerations for URI scheme registration ⓘ |
| standardizes | URI scheme registration template ⓘ |
| status | Obsoleted ⓘ |
| title | Guidelines and Registration Procedures for New URI Schemes ⓘ |
| topic |
Internet application protocols
ⓘ
URI syntax and semantics ⓘ
linked to:
RFC 3986
Web architecture ⓘ |
| type | Best Current Practice RFC ⓘ |
| updates | URI scheme registration process ⓘ |
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 4395 Description of subject: RFC 4395 was an IETF document that originally defined the procedures and guidelines for registering new URI schemes before being superseded by RFC 7320.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.