NAT rebinding in Google QUIC

[Rodrigo Alvarez Dominguez]

Hi

Does anyone know how NAT rebinding works in Google Quic?  Does anyone have a capture file of this scenario? I am trying to find what messages are sent after changing the IP address of the user when the connection id remains.

Thanks in advance

Regards,

[Jana Iyengar]

Hi Rodrigo,

As long as packets received after NAT rebinding are received with the same connection ID and are decryptable, a Google QUIC server will respond to the new address. The server does limit its rate until it receives ACKs back from the client for data sent to the new address, but no new messages are sent otherwise.

- jana

--
You received this message because you are subscribed to the Google Groups "QUIC Prototype Protocol Discussion group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to proto-quic+unsubscribe@chromium.org.
To post to this group, send email to proto...@chromium.org.
For more options, visit https://groups.google.com/a/chromium.org/d/optout.

[Rodrigo Alvarez Dominguez]

Hi 

First of all thanks for your quick "Quic" answer

Really appreciate it.

If I understood correctly, after a NAT rebinding it is mandatory to send the connection Id. Is it possible to not send the connection id? If you have any capture of the nat rebinding it would be nice to have it

Thanks in advance 

Rodrigo

El lunes, 5 de febrero de 2018, 23:15:30 (UTC+1), Jana Iyengar escribió:

Hi Rodrigo,

As long as packets received after NAT rebinding are received with the same connection ID and are decryptable, a Google QUIC server will respond to the new address. The server does limit its rate until it receives ACKs back from the client for data sent to the new address, but no new messages are sent otherwise.

- jana

On Mon, Feb 5, 2018 at 2:25 AM, Rodrigo Alvarez Dominguez <rodr...@gmail.com> wrote:

Hi

Does anyone know how NAT rebinding works in Google Quic?  Does anyone have a capture file of this scenario? I am trying to find what messages are sent after changing the IP address of the user when the connection id remains.

Thanks in advance

Regards,

--
You received this message because you are subscribed to the Google Groups "QUIC Prototype Protocol Discussion group" group.

To unsubscribe from this group and stop receiving emails from it, send an email to proto-quic+...@chromium.org.

[Jana Iyengar]

Hi Rodrigo,

Google QUIC servers require that clients always send the connection ID on all packets to the server, which allows the connection to work across a NAT rebinding. So, in the setup we have, it is not possible to have a client not send the connection ID on any packet to the server.

I don't have a packet trace available unfortunately.

- jana

On Mon, Feb 5, 2018 at 2:21 PM, Rodrigo Alvarez Dominguez <rodr...@gmail.com> wrote:

Hi 

First of all thanks for your quick "Quic" answer

Really appreciate it.

If I understood correctly, after a NAT rebinding it is mandatory to send the connection Id. Is it possible to not send the connection id? If you have any capture of the nat rebinding it would be nice to have it

Thanks in advance 

Rodrigo

El lunes, 5 de febrero de 2018, 23:15:30 (UTC+1), Jana Iyengar escribió:

Hi Rodrigo,

As long as packets received after NAT rebinding are received with the same connection ID and are decryptable, a Google QUIC server will respond to the new address. The server does limit its rate until it receives ACKs back from the client for data sent to the new address, but no new messages are sent otherwise.

- jana

On Mon, Feb 5, 2018 at 2:25 AM, Rodrigo Alvarez Dominguez <rodr...@gmail.com> wrote:

Hi

Does anyone know how NAT rebinding works in Google Quic?  Does anyone have a capture file of this scenario? I am trying to find what messages are sent after changing the IP address of the user when the connection id remains.

Thanks in advance

Regards,

--
You received this message because you are subscribed to the Google Groups "QUIC Prototype Protocol Discussion group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to proto-quic+...@chromium.org.
To post to this group, send email to proto...@chromium.org.
For more options, visit https://groups.google.com/a/chromium.org/d/optout.

--
You received this message because you are subscribed to the Google Groups "QUIC Prototype Protocol Discussion group" group.

To unsubscribe from this group and stop receiving emails from it, send an email to proto-quic+unsubscribe@chromium.org.

[Dan Wing]

On Feb 5, 2018, at 2:21 PM, Rodrigo Alvarez Dominguez <rodr...@gmail.com> wrote:
> Hi

> First of all thanks for your quick "Quic" answer
> Really appreciate it.
> If I understood correctly, after a NAT rebinding it is mandatory to send the connection Id. Is it possible to not send the connection id?

Such an optimization implies

(a) the client can detect when a NAT rebinding occurs (which it can't always detect)
or
(b) the client suspects a rebinding occurred [due to lack of acknowledgements] and then starts sending packets with a connection-id.

To avoid both of those, the connection id is always sent. Which, yes, consumes some bandwidth but avoids (a) which can't be solved and avoids the delay inherent in (b).

-d

[Rodrigo Alvarez Dominguez]

Thnaks for your answer

[Rodrigo Alvarez Dominguez]

Thanks fior your answer.