Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Source address validation #52

Closed
martinthomson opened this issue Nov 30, 2016 · 3 comments
Closed

Source address validation #52

martinthomson opened this issue Nov 30, 2016 · 3 comments
Assignees
@martinthomson
Labels
-transport design An issue that affects the design of the protocol; resolution requires consensus. has-consensus An issue that the Chairs have determined has consensus, by canvassing the mailing list.

Comments

@martinthomson
Copy link
Member

We need to write down how this happens:

  1. on the same connection
  2. on a subsequent connection
@martinthomson martinthomson added design An issue that affects the design of the protocol; resolution requires consensus. -transport labels Nov 30, 2016
@MikeBishop
Copy link
Contributor

#120 addresses this.

@martinthomson martinthomson added the needs-discussion An issue that needs more discussion before we can resolve it. label Jan 20, 2017
@mnot
Copy link
Member

mnot commented Jan 26, 2017

Discussed in Tokyo. Need to work on the abstraction and the interface to TLS. Need to expand upon how to generate the token and what to do when you don't have a token.

@mnot mnot added editor-ready and removed needs-discussion An issue that needs more discussion before we can resolve it. labels Jan 26, 2017
@mnot mnot mentioned this issue Jan 26, 2017
Closed
@martinthomson martinthomson self-assigned this Feb 8, 2017
@martinthomson martinthomson mentioned this issue Feb 9, 2017
Merged
@martinthomson
Copy link
Member Author

I think that we're now far enough along to call this one done. We might iterate on what we have, but that can be done with new issues.

@mnot mnot removed the editor-ready label Mar 15, 2017
@mnot mnot added the has-consensus An issue that the Chairs have determined has consensus, by canvassing the mailing list. label Apr 19, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@martinthomson martinthomson

Labels
-transport design An issue that affects the design of the protocol; resolution requires consensus. has-consensus An issue that the Chairs have determined has consensus, by canvassing the mailing list.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@martinthomson @mnot @MikeBishop