RFC 3205
E863221
RFC 3205 is an informational Internet standard that provides guidelines and considerations for designing and deploying application protocols that use HTTP as a substrate.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 3205 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T10447592 — 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 3205 Context triple: [Building Protocols with HTTP, updates, RFC 3205]
-
A.
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.
-
B.
RFC 3652
RFC 3652 is an IETF standards-track document that specifies the technical architecture and protocols of the Handle System for assigning, managing, and resolving persistent digital identifiers.
-
C.
RFC 2572
RFC 2572 is an earlier IETF specification that defined the Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) before being superseded by RFC 3412.
-
D.
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.
-
E.
RFC 3655
RFC 3655 is an Internet Engineering Task Force (IETF) document that was an earlier specification later superseded by the DNS Security (DNSSEC)–related standard defined in RFC 4033.
- 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 3205 Target entity description: RFC 3205 is an informational Internet standard that provides guidelines and considerations for designing and deploying application protocols that use HTTP as a substrate.
-
A.
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.
-
B.
RFC 3652
RFC 3652 is an IETF standards-track document that specifies the technical architecture and protocols of the Handle System for assigning, managing, and resolving persistent digital identifiers.
-
C.
RFC 2572
RFC 2572 is an earlier IETF specification that defined the Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) before being superseded by RFC 3412.
-
D.
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.
-
E.
RFC 3655
RFC 3655 is an Internet Engineering Task Force (IETF) document that was an earlier specification later superseded by the DNS Security (DNSSEC)–related standard defined in RFC 4033.
- F. None of above. chosen
Statements (45)
| Predicate | Object |
|---|---|
| instanceOf |
Informational RFC
ⓘ
Internet standard document ⓘ Request for Comments ⓘ |
| addresses |
appropriate and inappropriate uses of HTTP as a substrate
ⓘ
design trade-offs for HTTP-based application protocols ⓘ |
| area | Applications Area ⓘ |
| author | Keith Moore NERFINISHED ⓘ |
| category | Informational ⓘ |
| definesGuidelinesFor |
deployment of application protocols using HTTP as a substrate
ⓘ
design of application protocols using HTTP as a substrate ⓘ |
| discusses |
considerations for tunneling protocols over HTTP
ⓘ
impact on HTTP infrastructure such as proxies and caches ⓘ interoperability issues of HTTP-based application protocols ⓘ port usage and assignment when using HTTP as a substrate ⓘ security considerations when using HTTP as a substrate ⓘ |
| documentType | Best current practice-style guidance ⓘ |
| editor | Keith Moore NERFINISHED ⓘ |
| focusesOn | use of HTTP as a substrate for other application protocols ⓘ |
| hasLanguage | English ⓘ |
| intendedAudience |
IETF working groups
NERFINISHED
ⓘ
application protocol designers ⓘ |
| obsoletedBy | none ⓘ |
| obsoletes | none ⓘ |
| pageCount | 19 ⓘ |
| protocol | Hypertext Transfer Protocol NERFINISHED ⓘ |
| protocolAbbreviation | HTTP NERFINISHED ⓘ |
| publicationDate | 2001-02 ⓘ |
| publicationMonth | February ⓘ |
| publicationYear | 2001 ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| RFCNumber | 3205 ⓘ |
| series | RFC Series NERFINISHED ⓘ |
| standardsBody | Internet Engineering Task Force NERFINISHED ⓘ |
| status | Informational ⓘ |
| stream | IETF Stream NERFINISHED ⓘ |
| subject |
HTTP tunneling
ⓘ
Internet architecture NERFINISHED ⓘ application protocol design ⓘ security considerations for HTTP-based protocols ⓘ |
| title | On the use of HTTP as a Substrate NERFINISHED ⓘ |
| updatedBy | none ⓘ |
| updates | none ⓘ |
| url | https://www.rfc-editor.org/rfc/rfc3205 ⓘ |
| workingGroup | Applications Area Directorate 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 3205 Description of subject: RFC 3205 is an informational Internet standard that provides guidelines and considerations for designing and deploying application protocols that use HTTP as a substrate.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.