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.

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

Add support for NAT rebinding #2

Closed
jlaine opened this issue May 18, 2019 · 0 comments
Closed

Add support for NAT rebinding #2

jlaine opened this issue May 18, 2019 · 0 comments
Labels
enhancement New feature or request

Comments

@jlaine
Copy link
Contributor

jlaine commented May 18, 2019

Currently aioquic has no explicit support for rebinding, i.e. dealing with changes in the peer's (IP address, port) tuple.

The specs mention that we should perform path validation if we detect a network path change:

https://tools.ietf.org/html/draft-ietf-quic-transport-20#section-9

Open questions:

  • How should this interact with asyncio's transport / protocol scheme? Currently the client example creates a "connected" UDP socket which means we never pass the "addr" argument to sendto(). Likewise in the server example we store the peer's initial address

  • What does this mean if QUIC is layered on top of ICE? Who makes the decisions as to which network path to use: ICE or QUIC?

  • What is the behaviour while the new network path is being validated? Do we continue using the previous network path until path validation completes?

@jlaine jlaine added the enhancement New feature or request label May 18, 2019
@jlaine jlaine closed this as completed May 22, 2019
hansroh added a commit to hansroh/aioquic that referenced this issue Nov 7, 2019
hansroh added a commit to hansroh/aioquic that referenced this issue Nov 8, 2019
hansroh added a commit to hansroh/aioquic that referenced this issue Nov 8, 2019
hansroh added a commit to hansroh/aioquic that referenced this issue Nov 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant