Skip to content

Clarification on Negotiating Connection IDs #331

@backkem

Description

@backkem

I wanted to clarify how the Connection IDs are to be established.

The OSP spec says:

The connection IDs used both by agents should be zero length.

The Quic spec says:

7.2. [Negotiating Connection IDs]
When an Initial packet is sent by a client that has not previously received an Initial or Retry packet from the server, the client populates the Destination Connection ID field with an unpredictable value. This Destination Connection ID MUST be at least 8 bytes in length. Until a packet is received from the server, the client MUST use the same Destination Connection ID value on all packets in this connection.

Am I correct in understanding this means the initial connection should use a random connection ID (>= 8 bytes) and afterwards a zero-length connection ID should be negotiated?

I ran into this while trying to connect between the Chromium and Go implementation. For reference: quic-go/quic-go#4465

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions