tfpauly/draft-pauly-adaptive-dns-privacy

Issues

• Address David's review

  #206 opened 3 years ago
  0

• Describe "experimental" details

  #197 opened 3 years ago
  0

• Polish registry contents

  #193 opened 3 years ago
  0

• Clarify Tor "cost" in ODoH

  #192 opened 3 years ago
  0

• Revisit normative requirements language in ODoH

  #190 opened 3 years ago
  0

• Clarify collusion limitations in security considerations

  #189 opened 3 years ago
  0

• Fix idnits issues for ODoH

  #188 opened 3 years ago
  1

• Add "outside the IETF" to the abstract

  #187 opened 3 years ago
  0

• Discuss handling of 3xx responses

  #186 opened 3 years ago
  0

• Remove normative references to add-resolver-discovery and adaptive-dns-privacy

  #179 opened 3 years ago
  0

• [ODoH] how is path specified in SVCB RR?

  #177 opened 3 years ago
  2

• Describe allowances for proxy authentication

  #175 opened 3 years ago
  0

• Provide guidance about which status codes should be forwarded

  #174 opened 3 years ago
  1

• minor: provide ipv6hint in examples

  #172 opened 4 years ago
  2

• Clarification on Opportunistic with respect to dns://resolver.arpa

  #163 opened 4 years ago
  2

• Bump ODoH version

  #162 opened 4 years ago
  1

• Clarification of expectations in certain NAT environments

  #161 opened 4 years ago
  7

• DEER: Clarification of SUDN

  #160 opened 4 years ago
  3

• [ODoH] Client bootstrapping concerns. How should client obtain T's SVCB/HTTPS records?

  #159 opened 3 years ago
  13

• Require proxies to passthrough HTTP error codes from target

  #157 opened 4 years ago
  0

• Recommend limits

  #156 opened 4 years ago
  4

• DEER caching text

  #155 opened 4 years ago
  1

• Check for bad dns request in the protocol

  #154 opened 4 years ago
  3

• ODoH: Failure status codes

  #151 opened 4 years ago
  3

• Promote proxy URI template

  #150 opened 4 years ago
  2

• [ODoH] Add EDNS(0) client subnet guidance

  #149 opened 3 years ago
  2

• Update HPKE to draft-06

  #148 opened 4 years ago
  4

• Clarification...

  #146 opened 4 years ago
  1

• Clarify use of address hints

  #145 opened 4 years ago
  1

• DEER: Describe opportunistic interaction with probing port 853

  #144 opened 4 years ago
  1

• DEER: Reference threat model

  #143 opened 4 years ago
  4

• DEER: Mention cases where name is provisioned

  #140 opened 4 years ago
  0

• DEER: Work on abstract

  #139 opened 4 years ago
  0

• [Privacy] Add details about proxy connection management to minimize tracking

  #137 opened 3 years ago
  0

• [Privacy] Malicious oDoH target can learn the client's IP address through an active attack

  #136 opened 3 years ago
  3

• Key rotation considerations

  #135 opened 4 years ago
  4

• Pin Oblivious DoH to HPKE-06

  #132 opened 4 years ago
  2

• Whitelist -> Allowlist

  #131 opened 3 years ago
  2

• Default HPKE ciphersuite?

  #128 opened 4 years ago
  0

• Add alt-svc parameter for ODoH key distribution

  #124 opened 4 years ago
  3

• Add explicit key to indicate zone cuts

  #121 opened 4 years ago
  0

• HTTP server push clarification

  #120 opened 4 years ago
  2

• Editorial

  #119 opened 4 years ago
  2

• Add tracking/cross-referencing

  #118 opened 4 years ago
  0

• Detail out possible leakages of clients' public information in ODOH

  #113 opened 3 years ago
  0

• Explore mechanisms to audit proxies or rank the proxies by their reliability/privacy guarantees

  #112 opened 4 years ago
  1

• [Privacy] Explicitly indicate the users' trust model when using ODOH

  #111 opened 4 years ago
  0

• [Privacy] Detail the ideal expected way of usage for Oblivious DOH

  #110 opened 4 years ago
  1

• [Privacy] Spell out the possible loss of privacy guarantees

  #109 opened 4 years ago
  1

• Detail out potential for flooding attacks or DoS from Proxies --> Targets

  #108 opened 3 years ago
  0