Consider the Archived-At header in DKIM-ID generation
- Dominant language
- Python
- Stars
- 45
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
The `Archived-At` header was introduced by [RFC 5064](https://datatracker.ietf.org/doc/html/rfc5064) for mailing list managers to give a link to an archived message. It was not included in [RFC 6376 § 5.4.1](https://datatracker.ietf.org/doc/html/rfc6376#section-5.4.1) as a recommended header to sign, even though it did recommend signing `List-Archive`. Since `Archived-At` is a refinement of `List-Archive` with a very similar purpose it may be worthwhile including it in the DKIM-ID generation algorithm. Its omission from RFC 6376, whose recommendations are not anyway intended to be exhaustive, was possibly an oversight.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading RFC 5064 and RFC 6376 §5.4.1, then locate the DKIM-ID generation entry point in the repository. Determine the expected treatment of the Archived-At header and identify the tests or documentation that would define completion; the issue currently names no files, tests, or acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100