search

quicwg / multipath

In-progress version of draft-ietf-quic-multipath
Other
48 stars 17 forks source link

We need to review the path initiation paragraph. #398

Closed huitema closed 5 days ago

huitema commented 5 days ago

In particular, this part is wrong:

If validation succeeds, the client can continue to use the path.
If validation fails, the client MUST NOT use the path and can
remove any status associated to the path initation attempt.
However, as the used Path ID is anyway consumed,
and the endpoint MUST abandon the path by sending a PATH_ABANDON frame
and retire all corresponding connection IDs by sending MP_RETIRE_CONNECTION_ID frames
on another path to inform the peer that the Path ID cannot be used anymore.

Path abandon is sufficient to retire the connection ID, and the second sentence is awkward.

huitema commented 5 days ago

There is the same issue with Example section "## Path Closure"

huitema commented 5 days ago

My bad. I was working from a copy that was not up to date.