Skip to content

Issues: ietf-wg-ppm/draft-ietf-ppm-dap

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Author
Filter by author
Label
Filter by label
Use alt + click/return to exclude labels
or + click/return for logical OR
Projects
Filter by project
Milestones
Filter by milestone
Assignee
Filter by who’s assigned
Sort

Issues list

Discuss lifecycle of various objects and how they relate to each other editorial The issue raised is purely editorial (i.e., doesn't impact implementations).
#560 opened May 9, 2024 by tgeoghegan
Add a ladder diagram illustrating what bits need to be stored editorial The issue raised is purely editorial (i.e., doesn't impact implementations).
#553 opened Apr 22, 2024 by cjpatton
Security considerations: privacy impact of per-task HpkeConfigs editorial The issue raised is purely editorial (i.e., doesn't impact implementations).
#505 opened Oct 17, 2023 by divergentdave
Document extensions to and/or deviations from RFC 8446 presentation language editorial The issue raised is purely editorial (i.e., doesn't impact implementations).
#472 opened Jun 14, 2023 by tgeoghegan
Replay attack requirements could be tighter editorial The issue raised is purely editorial (i.e., doesn't impact implementations).
#442 opened Apr 27, 2023 by martinthomson
Pre-Aggregation into buckets editorial The issue raised is purely editorial (i.e., doesn't impact implementations).
#385 opened Nov 29, 2022 by simon-friedberger
DP: Bound contribution from a single client editorial The issue raised is purely editorial (i.e., doesn't impact implementations).
#210 opened Mar 25, 2022 by martinthomson
Diagrams editorial The issue raised is purely editorial (i.e., doesn't impact implementations).
#158 opened Oct 8, 2021 by coopdanger
TODO: Fix the bounds for length-prefixed parameters in protocol messages editorial The issue raised is purely editorial (i.e., doesn't impact implementations).
#110 opened Aug 13, 2021 by ekr
ProTip! Add no:assignee to see everything that’s not assigned.