1 / 3

RDDP: TCP Alignment David L. Black (RDDP WG Chair)

RDDP: TCP Alignment David L. Black (RDDP WG Chair). RDDP WG rough consensus (mailing list): The RDDP protocols must allow implementations over unmodified TCP/IP stacks. Implication: receivers MUST cope with sender loss of alignment (or meddling middlebox) Observations:

najila
Download Presentation

RDDP: TCP Alignment David L. Black (RDDP WG Chair)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. RDDP: TCP AlignmentDavid L. Black (RDDP WG Chair) • RDDP WG rough consensus (mailing list): • The RDDP protocols must allow implementations over unmodified TCP/IP stacks. • Implication: receivers MUST cope with sender loss of alignment (or meddling middlebox) • Observations: • Those in favor of sender alignment appear to be opposed to telling the receiver that the sender is aligning (beyond normal TCP behavior) • There does not appear to be a functional requirement for this sort of notification

  2. RFC 2119 Section 6:Use of MUST and SHOULD • Imperatives of the type defined in this memo must be used with care and sparingly. In particular, they MUST only be used where it is actually required for interoperation or to limit behavior which has potential for causing harm (e.g., limiting retransmissions) For example, they must not be used to try to impose a particular method on implementors where the method is not required for interoperability. • Observation: Alignment is not required for interoperation. • Question: Potential for causing harm? • NB: receivers can’t rely on alignment

  3. TCP Alignment Summary & Proposal • Alignment is • Not required for interoperability • Not something an RDDP receiver can rely on • A potentially useful optimization • Proposal: Treat as optimization only • No “MUST” or “SHOULD” • Describe circumstances under which sender use of alignment improves performance • Discussion?

More Related