RFC 822
E187107
RFC 822 is an early Internet standard that defines the format of text-based email messages, including headers and addressing conventions.
All labels observed (2)
| Label | Occurrences |
|---|---|
| RFC 822 canonical | 3 |
| Internet message header fields | 1 |
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments document ⓘ email message format specification ⓘ |
| appliesTo | text-based email messages ⓘ |
| area | Applications ⓘ |
| author | David H. Crocker ⓘ |
| basedOn | RFC 733 ⓘ |
| category | Standards Track ⓘ |
| context |
ARPANET
ⓘ
surface form:
ARPA Internet
|
| defines |
addressing conventions for email
ⓘ
format of ARPA Internet text messages ⓘ rules for message bodies as text ⓘ syntax of email message headers ⓘ |
| documentNumber | 822 ⓘ |
| hasSection |
Address Specification
ⓘ
Message Header Fields ⓘ Semantics ⓘ Syntax ⓘ |
| historicStatus | Historic ⓘ |
| influenced |
RFC 2822
ⓘ
RFC 5322 ⓘ |
| intendedAudience |
Internet protocol designers
ⓘ
email system implementers ⓘ |
| language | English ⓘ |
| obsoletedBy |
RFC 2822
ⓘ
RFC 5322 ⓘ |
| protocolFamily | Internet mail ⓘ |
| publicationDate | 1982-08 ⓘ |
| publishedBy |
Internet Activities Board
ⓘ
Internet Engineering Task Force ⓘ |
| publisher | RFC Editor ⓘ |
| relatedTo |
SMTP
ⓘ
SMTP ⓘ
surface form:
Simple Mail Transfer Protocol
|
| replaces | RFC 733 ⓘ |
| scope | message format, not transport ⓘ |
| series |
RFCs
ⓘ
surface form:
Request for Comments
|
| specifies |
address specification syntax
ⓘ
date and time format in email headers ⓘ header field structure ⓘ message identification fields ⓘ optional informational header fields ⓘ trace fields such as Received ⓘ |
| standardizes |
Standard for the Format of ARPA Internet Text Messages
ⓘ
surface form:
ARPA Internet text message format
|
| status | Obsoleted ⓘ |
| title | Standard for the Format of ARPA Internet Text Messages ⓘ |
| updates | RFC 733 ⓘ |
| usesCharacterSet | US-ASCII ⓘ |
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 822 Description of subject: RFC 822 is an early Internet standard that defines the format of text-based email messages, including headers and addressing conventions.
Referenced by (4)
Full triples — surface form annotated when it differs from this entity's canonical label.