Re: [dcp] sequence numbers on resend

>   1] the above - using the same ISN would let you use the same
>   connection and not have orphaned timers.

The connection is uniquely identified by the port numbers [and Service
Name]. A retransmitted Request will have the same port numbers, so there's
only one connection, and no orphaned timers.

>   3] least surprise - in TCP a retransmit is a RE-transmit, the same
>   TCP level data is simply sent again. this way you only have to worry
>   about dups not which one is "right". 

Well, in DCCP, every packet increments the sequence number, including pure
acks (and retransmitted pure acks). Therefore I think incrementing the
Request sequence number would surprise the least.

>   2] (rvcd_ackn == local_isn) has to match on each side to complete
>   the handshake.. extending that to (rcvd_ackn is_in
>   list_of_local_isns) is an implementation hassle - requiring state
>   maintenance for each resend.

I agree with this concern, although I don't think the hassle would be that
serious. It's not a new kind of state, after all; it's just like the state
DCCP endpoints maintain for established connections.

Again, it doesn't seem like a big deal either way. I prefer incrementing
the sequence number for internal consistency, and because it provides more
information to the endpoints.

With incremented sequence numbers, the endpoints need to handle old (=
delayed) and duplicated Requests and Responses. With identical sequence
numbers, the endpoints need to handle duplicated Requests and Responses.
The logic will be basically the same. Doesn't seem that much easier.

Eddie

_______________________________________________
dcp mailing list
dcp@ietf.org
https://www1.ietf.org/mailman/listinfo/dcp