RFC 2268
E487733
RFC 2268 is the Internet Engineering Task Force (IETF) document that specifies the RC2 symmetric block cipher algorithm for use in Internet protocols.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 2268 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T5028146 — 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 2268 Context triple: [RC2, standardizedIn, RFC 2268]
-
A.
RFC 1668
RFC 1668 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specifications evolved.
-
B.
RFC 2228
RFC 2228 is an Internet standard that extends the File Transfer Protocol (FTP) with security mechanisms such as authentication, integrity, and confidentiality.
-
C.
RFC 3168
RFC 3168 is an IETF standard that specifies the addition of Explicit Congestion Notification (ECN) to IP and TCP to enable end-to-end congestion signaling without relying solely on packet loss.
-
D.
RFC 2870
RFC 2870 is an Internet Engineering Task Force (IETF) document that specifies operational and technical requirements for the DNS root name server system.
-
E.
RFC 1869
RFC 1869 is an early Internet standard that introduced the Extended Simple Mail Transfer Protocol (ESMTP) framework for adding optional extensions to SMTP.
- 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 2268 Target entity description: RFC 2268 is the Internet Engineering Task Force (IETF) document that specifies the RC2 symmetric block cipher algorithm for use in Internet protocols.
-
A.
RFC 1668
RFC 1668 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specifications evolved.
-
B.
RFC 2228
RFC 2228 is an Internet standard that extends the File Transfer Protocol (FTP) with security mechanisms such as authentication, integrity, and confidentiality.
-
C.
RFC 3168
RFC 3168 is an IETF standard that specifies the addition of Explicit Congestion Notification (ECN) to IP and TCP to enable end-to-end congestion signaling without relying solely on packet loss.
-
D.
RFC 2870
RFC 2870 is an Internet Engineering Task Force (IETF) document that specifies operational and technical requirements for the DNS root name server system.
-
E.
RFC 1869
RFC 1869 is an early Internet standard that introduced the Extended Simple Mail Transfer Protocol (ESMTP) framework for adding optional extensions to SMTP.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standard-track document
ⓘ
Request for Comments ⓘ |
| algorithmName | RC2 NERFINISHED ⓘ |
| area | Security ⓘ |
| author |
R. L. Rivest
NERFINISHED
ⓘ
Ronald L. Rivest NERFINISHED ⓘ |
| blockSize | 64 bits ⓘ |
| category | Informational ⓘ |
| cipherType | symmetric-key block cipher ⓘ |
| contains |
intellectual property rights notice
ⓘ
security considerations section ⓘ test vectors for RC2 ⓘ |
| defines |
RC2 block size
ⓘ
RC2 decryption process ⓘ RC2 effective key length mechanism ⓘ RC2 encryption process ⓘ RC2 key expansion ⓘ RC2 parameterized key size ⓘ |
| format | text ⓘ |
| hasKeyword |
Internet
NERFINISHED
ⓘ
RC2 NERFINISHED ⓘ block cipher ⓘ cryptography ⓘ encryption ⓘ security ⓘ |
| intendedUse |
IP security
NERFINISHED
ⓘ
Internet protocols ⓘ privacy-enhanced mail ⓘ |
| language | English ⓘ |
| mentions |
PKCS
NERFINISHED
ⓘ
export control restrictions ⓘ |
| obsoletes | none ⓘ |
| publicationDate | 1998-03 ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| publishedIn | RFC series NERFINISHED ⓘ |
| relation | describes algorithm originally proprietary to RSA Data Security, Inc. ⓘ |
| seriesNumber | 2268 ⓘ |
| specifies |
RC2 block cipher
NERFINISHED
ⓘ
RC2 encryption algorithm NERFINISHED ⓘ |
| standardizes | RC2 for use in Internet applications ⓘ |
| status | Informational RFC ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| title | A Description of the RC2(r) Encryption Algorithm NERFINISHED ⓘ |
| updatedBy | none ⓘ |
| updates | none ⓘ |
| year | 1998 ⓘ |
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 2268 Description of subject: RFC 2268 is the Internet Engineering Task Force (IETF) document that specifies the RC2 symmetric block cipher algorithm for use in Internet protocols.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.