RFC 3490
E453730
RFC 3490 is an Internet standard that defines Internationalized Domain Names in Applications (IDNA), enabling the use of non-ASCII characters in domain names.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 3490 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T4575434 — 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 3490 Context triple: [UTF-7, deprecatedIn, RFC 3490]
-
A.
RFC 3710
RFC 3710 is an IETF document that defines the purpose, structure, and procedures of the Internet Engineering Steering Group (IESG) within the Internet standards process.
-
B.
RFC 3650
RFC 3650 is an IETF document that specifies the architectural framework and core concepts of the Handle System, a global identifier and resolution system for digital resources.
-
C.
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.
-
D.
RFC 4380
RFC 4380 is an IETF standard that specifies the Teredo protocol for providing IPv6 connectivity to nodes located behind IPv4 network address translators (NATs).
-
E.
RFC 4954
RFC 4954 is an Internet standard that specifies the SMTP Authentication (SMTP AUTH) extension, enabling secure client authentication when sending email.
- 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 3490 Target entity description: RFC 3490 is an Internet standard that defines Internationalized Domain Names in Applications (IDNA), enabling the use of non-ASCII characters in domain names.
-
A.
RFC 3710
RFC 3710 is an IETF document that defines the purpose, structure, and procedures of the Internet Engineering Steering Group (IESG) within the Internet standards process.
-
B.
RFC 3650
RFC 3650 is an IETF document that specifies the architectural framework and core concepts of the Handle System, a global identifier and resolution system for digital resources.
-
C.
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.
-
D.
RFC 4380
RFC 4380 is an IETF standard that specifies the Teredo protocol for providing IPv6 connectivity to nodes located behind IPv4 network address translators (NATs).
-
E.
RFC 4954
RFC 4954 is an Internet standard that specifies the SMTP Authentication (SMTP AUTH) extension, enabling secure client authentication when sending email.
- F. None of above. chosen
Statements (39)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ |
| aimsTo | allow users to use native-language characters in domain names ⓘ |
| appliesTo | application protocols using domain names ⓘ |
| area | Applications ⓘ |
| category | Standards Track ⓘ |
| defines | Internationalized Domain Names in Applications NERFINISHED ⓘ |
| definesConcept |
IDN processing rules
ⓘ
Nameprep NERFINISHED ⓘ |
| definesMappingTo | ASCII-Compatible Encoding NERFINISHED ⓘ |
| documentType | Standards Track RFC ⓘ |
| enables | use of non-ASCII characters in domain names ⓘ |
| focusesOn | internationalization of domain names ⓘ |
| intendedAudience |
application protocol designers
ⓘ
software implementers of domain name handling ⓘ |
| language | English ⓘ |
| obsoletedBy |
RFC 5890
NERFINISHED
ⓘ
RFC 5891 NERFINISHED ⓘ RFC 5892 NERFINISHED ⓘ RFC 5893 NERFINISHED ⓘ RFC 5894 NERFINISHED ⓘ |
| partOf | original IDNA protocol ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedTo |
RFC 3491
NERFINISHED
ⓘ
RFC 3492 ⓘ |
| relatesTo |
DNS
NERFINISHED
ⓘ
Domain Name System NERFINISHED ⓘ |
| RFCNumber | 3490 ⓘ |
| securityConsiderations | phishing risks due to visually confusable characters in IDNs ⓘ |
| shortName | IDNA NERFINISHED ⓘ |
| specifies |
conversion between Unicode and ASCII-Compatible Encoding for domain names
ⓘ
processing of internationalized domain names in applications ⓘ |
| standardizes | IDN handling at the application layer ⓘ |
| status | Obsoleted ⓘ |
| title | Internationalizing Domain Names in Applications (IDNA) NERFINISHED ⓘ |
| updates | domain name handling in application protocols ⓘ |
| uses | Punycode NERFINISHED ⓘ |
| usesCharacterSet | Unicode 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 3490 Description of subject: RFC 3490 is an Internet standard that defines Internationalized Domain Names in Applications (IDNA), enabling the use of non-ASCII characters in domain names.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.