Michael Welzl , Distributed and Parallel Systems Group

Slides:



Advertisements
Similar presentations
Prentice HallHigh Performance TCP/IP Networking, Hassan-Jain Chapter 2 TCP/IP Fundamentals.
Advertisements

BZUPAGES.COM 1 User Datagram Protocol - UDP RFC 768, Protocol 17 Provides unreliable, connectionless on top of IP Minimal overhead, high performance –No.
Transport Layer – TCP (Part1) Dr. Sanjay P. Ahuja, Ph.D. Fidelity National Financial Distinguished Professor of CIS School of Computing, UNF.
EE228A Project, Fall 2000 Yunfei Deng, Kenneth Cheung, Daniil Khidekel Professor Jean Walrand 12/5/2000 Modular TCP.
1 Internet Networking Spring 2003 Tutorial 11 Explicit Congestion Notification (RFC 3168) Limited Transmit (RFC 3042)
1 Spring Semester 2007, Dept. of Computer Science, Technion Internet Networking recitation #8 Explicit Congestion Notification (RFC 3168) Limited Transmit.
Gursharan Singh Tatla Transport Layer 16-May
What Can IP Do? Deliver datagrams to hosts – The IP address in a datagram header identify a host IP treats a computer as an endpoint of communication Best.
CS640: Introduction to Computer Networks Aditya Akella Lecture 22 - Wireless Networking.
MulTFRC: TFRC with weighted fairness draft-welzl-multfrc-00 Michael Welzl, Dragana Damjanovic 75th IETF Meeting Stockholm, Sweden 29 July 2009.
Introduction to Networks CS587x Lecture 1 Department of Computer Science Iowa State University.
TCP : Transmission Control Protocol Computer Network System Sirak Kaewjamnong.
Adding Explicit Congestion Notification (ECN) Capability to TCP's SYN/ACK Packets A. Kuzmanovic, A. Mondal, S. Floyd, and K.K. Ramakrishnan draft-ietf-tcpm-ecnsyn-03.txt.
TCP1 Transmission Control Protocol (TCP). TCP2 Outline Transmission Control Protocol.
MulTFRC: TFRC with weighted fairness draft-welzl-multfrc-01 Michael Welzl, Dragana Damjanovic 76th IETF Meeting Hiroshima, Japan 10 November2009.
Teacher:Quincy Wu Presented by: Ying-Neng Hseih
Transport Layer: Sliding Window Reliability
1 Transport Layer: Basics Outline Intro to transport UDP Congestion control basics.
IP1 The Underlying Technologies. What is inside the Internet? Or What are the key underlying technologies that make it work so successfully? –Packet Switching.
Uni Innsbruck Informatik th IETF, PMTUD WG: Path MTU Discovery Using Options draft-welzl-pmtud-options-01.txt Michael Welzl
11 CS716 Advanced Computer Networks By Dr. Amir Qayyum.
U Innsbruck Informatik - 1 Specification of a Network Adaptation Layer for the Grid GGF7 presentation Michael Welzl University.
3. END-TO-END PROTOCOLS (PART 1) Rocky K. C. Chang Department of Computing The Hong Kong Polytechnic University 22 March
Establishing Host Identity Protocol Opportunistic Mode with TCP Option
Chapter 9: Transport Layer
Master’s Project Presentation
Introduction to TCP/IP networking
Instructor Materials Chapter 9: Transport Layer
NDNLP Implementation of Best-Effort Link-Layer Reliability
Carles Gomez Universitat Politècnica de Catalunya (UPC)/Fundació i2cat
Internet Networking recitation #9
PANA Issues and Resolutions
draft-khademi-tsvwg-ecn-response-00
draft-ietf-simple-message-sessions-00 Ben Campbell
5. End-to-end protocols (part 1)
Transmission Control Protocol (TCP)
Discussion: Messaging
TCP-in-UDP draft-welzl-irtf-iccrg-tcp-in-udp-00.txt
PART 5 Transport Layer Computer Networks.
Extending Option Space Discussion Overview and its requirements
Magda El Zarki Professor, ICS UC, Irvine
Reliable Transport CS 3700 Project 3.
draft-bagnulo-tcpm-generalized-ecn-00 M. Bagnulo & B. Briscoe IETF97
Introduction of Transport Protocols
TCP Extended Option Space in the Payload of a Supplementary Segment
CSCI-1680 Transport Layer I
CSCI-1680 Transport Layer I
TCP - Part I Relates to Lab 5. First module on TCP which covers packet format, data transfer, and connection management.
TCB Control Block Sharing: 2140bis
Transport Options for UDP
I like the protocol. What I have to say makes me sad.
Falling Back! … and: a Functional Decomposition of Post-Sockets
Quick-Start for TCP and IP
Michael Welzl University of Oslo
Reliable Transport CS 3700 Project 3.
Internet Networking recitation #10
A Minimal Set of Transport Services for TAPS Systems draft-ietf-taps-minset-00 Michael Welzl, Stein-Gjessing IETF
TRANSMISSION CONTROL PROTOCOL
Carles Gomez Universitat Politècnica de Catalunya Jon Crowcroft
CSCI-1680 Transport Layer I
TCB Control Block Sharing: 2140bis
The Transmission Control Protocol (TCP)
Transport Protocols: TCP Segments, Flow control and Connection Setup
Introduction to Computer Networks
Transport Layer Outline Intro to transport UDP
Transport Protocols: TCP Segments, Flow control and Connection Setup
DCCP: Issues From the Mailing List
Transport Layer 9/22/2019.
ECN in QUIC - Questions Surfaced
Parameters & Defaults:
Presentation transcript:

60th IETF, TCPM WG: TCP Corruption Notification Options draft-welzl-tcp-corruption-00.txt Michael Welzl http://www.welzl.at , michael.welzl@uibk.ac.at Distributed and Parallel Systems Group Institute of Computer Science University of Innsbruck, Austria

Motivation TCP problems with noisy links are well known lots of research efforts lots of possibilities if a sender knows about noise but: no “noise notification“ Explicit (ICMP style) signaling was unsuccessful up to now Scaling issues, layering problems, etc. Partial and separate checksums have gained some IETF acceptance Partial checksums (give erroneous data to apps): UDP Lite - RFC 3828 (Proposed Standard) DCCP Separate checksums (distinguish congestion / corruption): DCCP (“Data Checksum Option“)

Proposal Introduce separate checksums to TCP Not a new idea! e.g., TCP HACK by Balan et al, Infocom 2001 Introduce separate checksums to TCP Note: partial checksums useless here (reliably transmit erroneous data?) How it works: additional (CRC-32c) checksum in TCP option covers relevant header parts (pseudo header) only look at it if TCP checksum fails if it succeeds, we know that packet #XY experienced corruption! (otherwise, we don‘t even know if the port numbers are correct) Notify sender now, it‘s an option in the ACK that says “the ACKed packet is corrupt“ alternatives: flag in the reserved field of the TCP header SACK-like option format (is this overkill?)

Link layer considerations Currently, only few link layers hand over corrupt data and typically must be configured to do so; why do it? similarly, why support corrupt data in transport endpoints? chicken-egg type of problem ... someone has to make a start! with UDP Lite (and DCCP), the IETF did (will do) Clearly, link layers should not always hand over corrupt data how to signal from transport to link? current strategy (UDP Lite and DCCP): link layer notices transport feature IMO problematic, but lack of better alternative Link layers MAY notice this feature and hand over corrupt data Transport endpoints MUST stay robust no matter what link layers do Note: various reasons for corruption (e.g. broken equipment)

Using this feedback (potential benefits) Feedback usage Status Discussions Less severe congestion control reaction will not be specified in this draft AWJT Earlier retransmission will be removed Don‘t retransmit if ACK is erroneous specified Updating RTT estimate DWJT Earlier congestion control reaction to ECE=1 ND Earlier reaction to control flags (SYN, FIN..) Discussion code: ND ... Not Discussed AWJT ... Agreed With Joe Touch :) DWJT ... Discussed With Joe Touch

Summary Research demand + attractive (potential) benefits + some agreement on partial / separate checksums = about time to add this to TCP Still lots of open issues How to use this feedback: more discussions required When to include these options? Feedback format Really no better inter-layer communication possible? Request Volunteers for implementations and simulations