BCP 38
E35280
BCP 38 is an Internet Engineering Task Force (IETF) Best Current Practice that recommends network ingress filtering to prevent IP address spoofing and reduce the impact of denial-of-service attacks.
All labels observed (1)
| Label | Occurrences |
|---|---|
| BCP 38 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T271052 — 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: BCP 38 Context triple: [Best Current Practice, hasExample, BCP 38]
-
A.
RFC 5321
RFC 5321 is the Internet standard that specifies the Simple Mail Transfer Protocol (SMTP) used for email transmission across IP networks.
-
B.
RFC 8200
RFC 8200 is the Internet Engineering Task Force (IETF) standard that specifies the core protocol architecture and operation of Internet Protocol version 6 (IPv6).
-
C.
RFC 791
RFC 791 is the foundational Internet standard that specifies the design, structure, and operation of the Internet Protocol version 4 (IPv4).
-
D.
RFC 792
RFC 792 is the Internet standard document that specifies the Internet Control Message Protocol (ICMP), which is used for network diagnostics and error reporting in IP networks.
-
E.
RFC 9114
RFC 9114 is the Internet standard that specifies HTTP/3, the version of the Hypertext Transfer Protocol that runs over the QUIC transport protocol.
- 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: BCP 38 Target entity description: BCP 38 is an Internet Engineering Task Force (IETF) Best Current Practice that recommends network ingress filtering to prevent IP address spoofing and reduce the impact of denial-of-service attacks.
-
A.
RFC 5321
RFC 5321 is the Internet standard that specifies the Simple Mail Transfer Protocol (SMTP) used for email transmission across IP networks.
-
B.
RFC 8200
RFC 8200 is the Internet Engineering Task Force (IETF) standard that specifies the core protocol architecture and operation of Internet Protocol version 6 (IPv6).
-
C.
RFC 791
RFC 791 is the foundational Internet standard that specifies the design, structure, and operation of the Internet Protocol version 4 (IPv4).
-
D.
RFC 792
RFC 792 is the Internet standard document that specifies the Internet Control Message Protocol (ICMP), which is used for network diagnostics and error reporting in IP networks.
-
E.
RFC 9114
RFC 9114 is the Internet standard that specifies HTTP/3, the version of the Hypertext Transfer Protocol that runs over the QUIC transport protocol.
- F. None of above. chosen
Statements (39)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Best Current Practice
ⓘ
network security recommendation ⓘ |
| abbreviationFor |
Best Current Practice
ⓘ
surface form:
Best Current Practice 38
|
| addressesProblem |
IP source address spoofing
ⓘ
distributed denial-of-service attacks ⓘ reflection and amplification attacks ⓘ |
| aimsTo |
increase accountability of traffic sources
ⓘ
reduce abuse of spoofed addresses in attacks ⓘ |
| appliesTo |
Internet service providers
ⓘ
edge networks ⓘ network operators ⓘ |
| associatedWith |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| category | Internet standardization document ⓘ |
| documentSeries | Best Current Practice (BCP) ⓘ |
| encourages | deployment of ingress filters at network boundaries ⓘ |
| focusesOn | ingress filtering of IP packets ⓘ |
| governedBy | IETF standards process ⓘ |
| hasAudience |
ISPs
ⓘ
network engineers ⓘ security engineers ⓘ |
| hasFullName |
Best Current Practice
ⓘ
surface form:
Best Current Practice 38
|
| intendedEffect |
improve overall Internet security posture
ⓘ
limit propagation of spoofed traffic across the Internet ⓘ |
| primaryGoal |
prevent IP address spoofing
ⓘ
reduce impact of denial-of-service attacks ⓘ |
| publishedBy | Internet Engineering Task Force ⓘ |
| recommends | network ingress filtering ⓘ |
| relatedConcept |
DDoS protection
ⓘ
Internet infrastructure security ⓘ anti-spoofing filters ⓘ source address validation ⓘ |
| requires |
dropping traffic with invalid source prefixes
ⓘ
filtering packets with spoofed source addresses ⓘ |
| securityDomain |
DDoS mitigation
ⓘ
Internet routing security ⓘ source address validation ⓘ |
| status | active Best Current Practice ⓘ |
| targetLayer | network layer ⓘ |
| usesProtocol | IP ⓘ |
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: BCP 38 Description of subject: BCP 38 is an Internet Engineering Task Force (IETF) Best Current Practice that recommends network ingress filtering to prevent IP address spoofing and reduce the impact of denial-of-service attacks.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.