https://github.com/dns-violations/dns-violations
List of DNS violations by implementations, software and/or systems
https://github.com/dns-violations/dns-violations
compliance dns dns-protocol dns-rfcs dns-violation dve violations
Last synced: 5 months ago
JSON representation
List of DNS violations by implementations, software and/or systems
- Host: GitHub
- URL: https://github.com/dns-violations/dns-violations
- Owner: dns-violations
- License: mit
- Created: 2017-01-25T15:26:39.000Z (over 8 years ago)
- Default Branch: master
- Last Pushed: 2023-03-30T12:54:49.000Z (about 2 years ago)
- Last Synced: 2024-08-08T23:20:55.028Z (9 months ago)
- Topics: compliance, dns, dns-protocol, dns-rfcs, dns-violation, dve, violations
- Homepage:
- Size: 101 KB
- Stars: 240
- Watchers: 64
- Forks: 28
- Open Issues: 7
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# DNS Violations
List of DNS violations by implementations, software and/or systems
## About
This _List_ consists of DNS Violation Entries (_DVE_'s) that describes known
violations to the DNS protocol by implementations, software and/or systems.
## Purpose
The purpose of the _List_ is to better understand how wrongfully the DNS
protocol is used out in the wild in order to try and make it better.
There is also a great gain for implementers to verify that they can handle
wrong DNS correctly.
## Community based
The _List_ is driven by the community for the community, anyone can send in
a violation and a team of community members will review and accept or reject
the violation, this team in called _Maintainers_. Anyone can request to join
the _Maintainers_ team and \.
## Violation
An implementation, software and/or system is considered to be in violation
to the DNS protocol when it does not strongly conform to the current DNS
RFCs. Violations can also include updated or obsolete DNS RFCs.
## Submission
Anyone can submit a DNS violation and request a _DVE_, this is done as a
pull request or an issue. If submitted as a markdown file, add it under
the year directory and with the full `DVE-YEAR-NUMBER.md` filename.
### Format
The format is Markdown with the following suggested headers, which are not
strict but should at least have short and long description. Metadata may be
included at the end of headers, together under `Metadata` header or at the
end of the file.
```
# DVE--:
## Description
## Evidence
## Proposed fix
## Workaround
## DNS Operator/Vendor Response
## Files
(): ``
application/dns+dnstap: `DVE-YEAR-NUMBER/example.dnstap`
application/dns+dnstap (segfault): `DVE-YEAR-NUMBER/example_that_segfaults.dnstap`
## Metadata
Submitter:
Submit-Date:
Report-Date:
Fixed-Date:
Tags:
:
```
### Files
You may attach files to the _DVE_ by using the `Files` section and add the
files in a directory related to the _DVE_ as (from repository root)
`YEAR/DVE-YEAR-NUMBER/`.
## DVE Allocation
_DVE_ are allocated sequentially starting from the number 1 using the format
`DVE--`. The number is allocated on a first-come-first-served
bases via pull requests or by the _Maintainers_ for an issue. The
_Maintainers_ may reserve a number for an issue by updated the title of the
issue with the full _DVE_ and also add a comment addressed to
`@DNS-OARC/dve-maintainers` that it has been reserved. Collisions are
rejected/asked to be updated.
## Repository Directory Layout
- In the root of the repository there should only be documentation
- The _DVE_ is placed under a year directory
- The _DVE_ is in markdown format and the filename is `DVE-YEAR-NUMBER.md`
- Optional files attached to the _DVE_ may be put under a directory with the full _DVE_ name under the year directory, example `YEAR/DVE-YEAR-NUMBER/file`