50 likes | 83 Views
This draft discusses Non-Renegrable SACKs in SCTP, addressing reneging issues and enhancing data delivery reliability, with a proposal to negotiate NR-SACK capability at INIT time for improved buffer management.
E N D
NR-SACKs for SCTP(Non-RenegableSACKs) draft-natarajan-tsvwg-sctp-nrsack-00 Preethi Natarajan Paul Amer Ertugrul Yilmaz (slides) Randall Stewart Janardhan Iyengar
Reneging and SCTP • SCTP SACK chunk carries cum ack, gap acks • Receiver may reneg ongap-acked data • due to buffer overbooking • sender does not discard gap-acked data • Receiver cannot reneg on delivered / cum-acked data • sender can discard cum-acked data
Eg: Using SCTP multistreaming 5 6 7 8 9 sent from application delivered to application objects in send buffer receive buffer cum-ack 1 retransmission loss stream 1 cum-ack 1 ; Gap-ack 2-2 cum-ack 1 ; Gap-ack 2-3 cum-ack 1 ; Gap-ack 2-4 cum-ack 1 ; Gap-ack 2-5 cum-ack 1 ; Gap-ack 2-6 cum-ack 1 ; Gap-ack 2-7 cum-ack 8 cum-ack 9 stream 2 stream 3 SCTP association Web client Web server
Now with NR-SACKs 5 6 7 8 9 sent from application delivered to application objects in send buffer receive buffer cum-ack 1 retransmission loss stream 1 cum-ack 1;gap-ack 2-4 nr-gap-ack 4-4 cum-ack 1 ; Gap-ack 2-2 cum-ack 1 ; Gap-ack 2-3 cum-ack 8 cum-ack 9 cum-ack 1;gap-ack 2-5 nr-gap-ack 4-5 cum-ack 1;gap-ack 2-7 nr-gap-ack 4-7 cum-ack 1;gap-ack 2-6 nr-gap-ack 4-6 stream 2 stream 3 SCTP association Web client Web server
draft-natarajan-tsvwg-sctp-nrsack-00 • Proposal: • Negotiate NR-SACK capability at INIT time • Replace SACKs with NR-SACKs • Sender can use NR-SACK info to free buffer • (see draft for more on structure and use cases) • Is this draft ready to be a wg item?