Call it prop296

This commit is contained in:
Nick Mathewson 2018-07-17 08:46:18 -04:00
parent b3abfdffee
commit c0b2dc9f17
2 changed files with 4 additions and 2 deletions

View File

@ -216,6 +216,7 @@ Proposals by number:
293 Other ways for relays to know when to publish [OPEN]
294 TLS 1.3 Migration [DRAFT]
295 Using ADL-GCM for relay cryptography (solving the crypto-tagging attack) [OPEN]
296 Have Directory Authorities expose raw bandwidth list files [OPEN]
Proposals by status:
@ -246,6 +247,7 @@ Proposals by status:
289 Authenticating sendme cells to mitigate bandwidth attacks
293 Other ways for relays to know when to publish [for 0.3.5]
295 Using ADL-GCM for relay cryptography (solving the crypto-tagging attack)
296 Have Directory Authorities expose raw bandwidth list files
ACCEPTED:
188 Bridge Guards and other anti-enumeration defenses
249 Allow CREATE cells with >505 bytes of handshake data

View File

@ -1,4 +1,4 @@
Filename: xxx-expose-bandwidth-files.txt
Filename: 296-expose-bandwidth-files.txt
Title: Have Directory Authorities expose raw bandwidth list files
Author: Tom Ritter
Created: 11-December-2017
@ -82,4 +82,4 @@ Exposing the document presents no compatibility concerns.
Applications that parse the document should follow the bandwidth list file
specification in bandwidth-file-spec.txt.
If a new bandwidth list format version is added, the applications MAY need
to upgrade to that version.
to upgrade to that version.