Transport Area Working Group (tsvwg)

Changed milestone "Submit "A Non-Queue-Building Per-Hop Behavior (NQB PHB) for Differentiated Services" as a Proposed Standard RFC", set due date to December 2020 from June 2020

Changed milestone "Submit "Identifying Modified Explicit Congestion Notification (ECN) Semantics for Ultra-Low Queuing Delay" as an Experimental RFC", set due date to October 2020 from June 2019

Changed milestone "Submit "DualQ Coupled AQM for Low Latency, Low Loss and Scalable Throughput" as an Experimental RFC", set due date to October 2020 from June 2019

Changed milestone "Submit "Low Latency, Low Loss, Scalable Throughput (L4S) Internet Service: Architecture" as an Informational RFC", set due date to October 2020 from June 2019

Changed milestone "Submit 'Propagating Explicit Congestion Notification Across IP Tunnel Headers Separated by a Shim' as a Proposed Standard RFC", set due date to July 2020 from January 2020

Changed milestone "Submit "A Non-Queue-Building Per-Hop Behavior (NQB PHB) for Differentiated Services" as a Proposed Standard RFC", set state to active from review, accepting new milestone

Changed milestone "Submit "Stream Control Transmission Protocol" aka RFC4960.bis as a Proposed Standard RFC", set due date to September 2020 from December 2019, added draft-ietf-tsvwg-rfc4960-bis to milestone

Changed milestone "Submit “The Impact of Transport Header Confidentiality on Network Operation and Evolution of the Internet” as an Informational RFC", set due date to April 2020 from September 2019, added draft-ietf-tsvwg-transport-encrypt to milestone

Changed milestone "Submit 'Packetization Layer Path MTU Discovery for Datagram Transports' as a Proposed Standard RFC", set due date to April 2020 from August 2019, added draft-ietf-tsvwg-datagram-plpmtud to milestone

Changed milestone "Submit 'SCTP NAT Support' to IESG for consideration as a PS RFC", set due date to February 2020 from July 2019, added draft-ietf-tsvwg-natsupp to milestone

Changed milestone "Submit 'Propagating Explicit Congestion Notification Across IP Tunnel Headers Separated by a Shim' as a Proposed Standard RFC", set due date to January 2020 from February 2019, added draft-ietf-tsvwg-rfc6040update-shim to milestone

Changed milestone "Submit 'Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP' as a BCP RFC", set due date to January 2020 from February 2019, added draft-ietf-tsvwg-ecn-encap-guidelines to milestone

Following completion of a set of drafts on Explicit Congestion Notifictaion, Working Group Last Calls (WGLC) are expected for work on L4S. 

Work continues on development of SCTP, including replacing RFC 4960.

The working group remains the home for work on UDP.

It is also responsible for maintaining DiffServ, PLPMTUD, and other mechanisms that apply across transport protocols.

Changed milestone "Submit “The Impact of Transport Header Confidentiality on Network Operation and Evolution of the Internet” as an Informational RFC", set state to active from review, accepting new milestone

Added milestone "Submit “The Impact of Transport Header Confidentiality on Network Operation and Evolution of the Internet” as an Informational RFC" for review, due September 2019

Changed milestone "Submit "Identifying Modified Explicit Congestion Notification (ECN) Semantics for Ultra-Low Queuing Delay" as an Experimental RFC", set due date to June 2019 from September 2018

Changed milestone "Submit "DualQ Coupled AQM for Low Latency, Low Loss and Scalable Throughput" as an Experimental RFC", set due date to June 2019 from September 2018

Changed milestone "Submit "Low Latency, Low Loss, Scalable Throughput (L4S) Internet Service: Architecture" as an Informational RFC", set due date to June 2019 from September 2018

Changed milestone "Submit 'Propagating Explicit Congestion Notification Across IP Tunnel Headers Separated by a Shim' as a Proposed Standard RFC", set due date to February 2019 from June 2018

Changed milestone "Submit 'Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP' as a BCP RFC", set due date to February 2019 from June 2018

Changed milestone "Submit 'Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP' as a BCP RFC", set due date to June 2018 from October 2018

Changed milestone "Submit 'Propagating Explicit Congestion Notification Across IP Tunnel Headers Separated by a Shim' as a Proposed Standard RFC", set due date to June 2018 from January 2018

Changed milestone "Submit 'Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP' as a BCP RFC", set due date to October 2018 from January 2018

Changed milestone "Submit 'Propagating Explicit Congestion Notification Across IP Tunnel Headers Separated by a Shim' as a Proposed Standard RFC", set due date to January 2018 from October 2017

Changed milestone "Submit 'Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP' as a BCP RFC", set due date to January 2018 from October 2017

Changed milestone "Submit "Identifying Modified Explicit Congestion Notification (ECN) Semantics for Ultra-Low Queuing Delay" as an Experimental RFC", set state to active from review, accepting new milestone

Changed milestone "Submit "DualQ Coupled AQM for Low Latency, Low Loss and Scalable Throughput" as an Experimental RFC", set state to active from review, accepting new milestone

Changed milestone "Submit "Low Latency, Low Loss, Scalable Throughput (L4S) Internet Service: Architecture" as an Informational RFC", set state to active from review, accepting new milestone

Changed milestone "Submit "Sliding Window Random Linear Code (RLC) Forward Erasure Correction (FEC) Scheme for FECFRAME" as a Proposed Standard RFC", set state to active from review, accepting new milestone

Changed milestone "Submit "Forward Error Correction (FEC) Framework Extension to Sliding Window Codes" as a Proposed Standard RFC", set state to active from review, accepting new milestone

Added milestone "Submit "Sliding Window Random Linear Code (RLC) Forward Erasure Correction (FEC) Scheme for FECFRAME" as a Proposed Standard RFC" for review, due June 2018

Changed milestone "Submit 'Propagating Explicit Congestion Notification Across IP Tunnel Headers Separated by a Shim' as a Proposed Standard RFC", set due date to October 2017 from September 2017

Changed milestone "Submit 'Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP' as a BCP RFC", set due date to October 2017 from September 2017

Changed milestone "Submit 'Guidelines for DiffServ to IEEE 802.11 Mapping' as an Informational RFC ", set description to "Submit 'Guidelines for DiffServ to IEEE 802.11 Mapping' as an Informational RFC"

Changed milestone "Submit 'Propagating Explicit Congestion Notification Across IP Tunnel Headers Separated by a Shim' as a Proposed Standard RFC", set due date to September 2017 from June 2017

Changed milestone "Submit 'Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP' as a BCP RFC", set due date to September 2017 from April 2017

Four TSVWG drafts have been published as RFCs:  Circuit Breakers, UDP Guidelines GRE in UDP and Diffserv Interconnection. There are two TSVWG drafts at the RFC Editor in MISSREF state (waiting for referenced RFCs to arrive):WebRTC Diffserv usage and DTLS encapsulation of SCTP.

Working Group Last Calls (WGLC) have been completed for three drafts: Tunnel Congestion Feedback (follow-up with the authors), 802.11 (WiFi) Diffserv (reviews received, a revised ID is needed) and SCTP stream scheduling/interleaving (a revised ID is needed). 

The ECN experimentation enablement draft and the Diffserv LE (Lower Effort) PHB drafts were recently adopted, but are close to done. 

The following drafts require feedback and work by the working group:
* RFC 4960 Errata
* SCTP NAT Support
* ECN Encaps Guidelines (recently discussed in external liaisons).
* RFC 6040 Update

The L4S drafts are likely to be an active area of WG activity in 2017.

The AQM (Active Queue Management and Packet Scheduling) WG is nearing the end of its life - future AQM-related work is likely to be done in TSVWG.

Three TSVWG drafts have been published as RFCs:  Circuit Breakers, UDP Guidelines and GRE in UDP.  The Diffserv Interconnection draft is expected to be published as an RFC soon.  There are two TSVWG drafts at the RFC Editor in MISSREF state (waiting for referenced RFCs to arrive):WebRTC Diffserv usage and DTLS encapsulation of SCTP.

Working Group Last Calls (WGLC) have been completed, on three drafts: Tunnel Congestion Feedback (follow-up with the authors), 802.11 (WiFi) Diffserv (reviews received, a revised ID is needed) and SCTP stream scheduling/interleaving (a revised ID is needed). 

The ECN experimentation enablement draft and the Diffserv LE (Lower Effort) PHB drafts were recently adopted, but are close to done. 

The following drafts required feedback and work by the working group:
* RFC 4960 Errata
* SCTP NAT Support
* ECN Encaps Guidelines (recently discussed in external liaisons).
* RFC 6040 Update

[information on other drafts will be added here in next revision of this status]

The AQM (Active Queue Management and Packet Scheduling) WG is nearing the end of its life - future AQM-related work is likely to be done in TSVWG.

Three TSVWG drafts have been published as RFCs:  Circuit Breakers, UDP Guidelines and GRE in UDP.  The Diffserv Interconnection draft is expected to be published as an RFC soon.  There are two TSVWG drafts at the RFC Editor in MISSREF state (waiting for referenced RFCs to arrive):WebRTC Diffserv usage and DTLS encapsulation of SCTP.

Working Group Last Calls (WGLC) have been completed, on three drafts: Tunnel Congestion Feedback, 802.11 (WiFi) Diffserv and SCTP stream scheduling/interleaving.  All three drafts are in various stages of follow-up with the authors and WG chairs before the RFC publication requests are submitted.

The ECN experimentation enablement draft and the Diffserv LE (Lower Effort) PHB drafts are close to done. 

[information on other drafts will be added here in next revision of this status]

The AQM (Active Queue Management and Packet Scheduling) WG is nearing the end of its life - future AQM-related work is likely to be done in TSVWG.

Changed milestone "Submit 'Propagating Explicit Congestion Notification Across IP Tunnel Headers Separated by a Shim' as a Proposed Standard RFC", set state to active from review, accepting new milestone

Changed milestone "Submit 'Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP' as a BCP RFC", set due date to April 2017 from December 2016

There are four TSVWG drafts at the RFC Editor in MISSREF state (waiting for referenced RFCs to arrive): Circuit Breakers, GRE in UDP, WebRTC Diffserv usage and DTLS encapsulation of SCTP.  There are two drafts at the IESG: 1) The UDP Guidelines draft has been approved by the IESG, but needs another revision to make the final changes before that approval can be announced and the draft sent to the RFC Editor.  2) The Diffserv Interconnection draft has completed IETF Last Call and is on the December 1 IESG Telechat agenda.

The Tunnel Congestion Feedback draft WGLC will conclude just before the Seoul meeting week.  Both the 802.11 (WiFi) Diffserv draft and the SCTP stream scheduling and interleaving draft expected to go to WGLC in the near future. 

ECN (Explicit Congestion Notification) is a theme of proposed new TSVWG work - a draft will be discussed in Seoul that makes the necessary standards track changes to ECN that will enable the experiments to proceed.  TCP-specific experimental modifications of ECN will be done in the TCPM WG.  L4S (successful BOF in Berlin), including its use of ECN to distinguish low latency service traffic, will also be experimental and is expected to be handled by TSVWG.  A new  draft has been adopted to specify ECN propagation across IP-in-IP tunnels that include a shim header (this is an extension of RFC 6040).

The AQM (Active Queue Management and Packet Scheduling) WG is nearing the end of its life - future AQM-related work is likely to be done in TSVWG.

TSVWG continues to pick up transport work that does not have a home in another working group, e.g., revision of the Diffserv LE (Lower Effort, i.e.,  less-than-best effort) specification and errata for the base SCTP spec (RFC 4960).

Changed milestone "Submit 'Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP' as a BCP RFC", set due date to December 2016 from September 2016

TSVWG has two RFCs published since IETF-95 (Buenos Aires) - SCTP-PF: Quick Failover (RFC 7829) and NAT Behavioral Reqts. Updates (RFC 7857), and two more drafts in the RFC Editor Queue - DTLS encap of SCTP (for WebRTC) and Circuit Breakers (approved after IETF-95).

There are three TSVWG drafts at the IESG: 1) The Diffserv usage by WebRTC draft is IESG-approved, but awaiting a clarification on how to deal with black-holes caused by non-zero DSCPs; for WebRTC, ICE will use STUN to check for connectivity, and details of the text are expected to be worked out during Berlin meeting week.  2) The UDP Guidelines draft is post-IETF-Last-Call, but awaiting resolution of RTO text wrt TCPM WG's RTO draft.  The TCPM WG agreed on an approach in principle at the Berlin meeting, with text details to be worked out offline, a revised draft should be ready for IESG  evaluation in August.  3) The GRE in UDP draft will be in IETF Last Call by end of Berlin meeting week.

TSVWG has completed work on the Diffserv Interconnection draft, and RFC publication will be requested soon.  Most other current TSVWG drafts are close to done - the WG chairs are planning approximately a WG Last Call per month between now and the end of 2016, including WGLC for the recently adopted draft on Diffserv mapping to 802.11 (WiFi). New work is planned to update the SCTP base spec.

ECN (Explicit Congestion Notification) is a theme of proposed new TSVWG work - drafts have been proposed to TSVWG on ECN codepoint usage/semantics, and propagation of ECN at endpoints of IP-in-IP tunnels that use shim headers; in addition, recent discussion of the RTP circuit breaker (AVTCORE draft) indicates that work would be needed to specify how ECN congestion indications could be used with RTP.

TSVWG has two RFCs published since IETF-95 (Buenos Aires) - SCTP-PF: Quick Failover (RFC 7829) and NAT Behavioral Reqts. Updates (RFC 7857), and two more drafts in the RFC Editor Queue - DTLS encap of SCTP (for WebRTC) and Circuit Breakers (approved after IETF-95).

There are three TSVWG drafts at the IESG: 1) The Diffserv usage by WebRTC draft is IESG-approved, but awaiting a clarification on how to deal with black-holes caused by non-zero DSCPs; for WebRTC, ICE will use STUN to check for connectivity, and details of the text are expected to be worked out during Berlin meeting week.  2) The UDP Guidelines draft is post-IETF-Last-Call, but awaiting resolution of RTO text wrt TCPM WG's RTO draft.  The TCPM WG agreed on an approach in principle at the Berlin meeting, with text details to be worked out offline, a revised draft should be ready for IESG  evaluation in August.  3) The GRE in UDP draft will be in IETF Last Call by end of Berlin meeting week.

TSVWG has completed work on the Diffserv Interconnection draft, and RFC publication will be requested soon.  Most other current TSVWG drafts are close to done - the WG chairs are planning approximately a WG Last Call per month between now and the end of 2016, including WGLC for the recently adopted draft on Diffserv mapping to 802.11 (WiFi). New work is planned to update the SCTP base spec.

ECN (Explicit Congestion Notification) is a theme of proposed new TSVWG work - drafts proposed to WG on ECN codepoint usage/semantics, and propagation of ECN at endpoints of IP-in-IP tunnels that use shim headers, and recent discussion of the RTP circuit breaker (AVTCORE draft) indicates that work would be needed to specify how ECN congestion indications could be used with RTP.

TSVWG has two RFCs published since IETF-95 (Buenos Aires) - SCTP-PF: Quick Failover (RFC 7829) and NAT Behavioral Reqts. Updates (RFC 7857), and two more drafts in the RFC Editor Queue - DTLS encap of SCTP (for WebRTC) and Circuit Breakers (approved after IETF-95).

There are three TSVWG drafts at the IESG: 1) The Diffserv usage by WebRTC draft is IESG-approved, but awaiting a clarification on how to deal with black-holes caused by non-zero DSCPs; for WebRTC, ICE will use STUN to check for this, and details are expected to be worked out during Berlin meeting week.  2) The UDP Guidelines draft is post-IETF-Last-Call, but awaiting resolution of RTO text wrt TCPM WG's RTO draft.  The TCPM WG agreed on approach in principle in Berlin meeting, with text details to be worked out offline, revised draft should be ready for IESG  evaluation by end of August.  3) The GRE in UDP draft will be in IETF Last Call by end of Berlin meeting week.

TSVWG has completed work on the Diffserv Interconnection draft, and RFC publication will be requested soon.  Most other current TSVWG drafts are close to done - the WG chairs are planning approximately a WG Last Call per month between now and the end of 2016, including WGLC for the recently adopted draft on Diffserv mapping to 802.11 (WiFi).

ECN (Explicit Congestion Notification) is a theme of proposed new TSVWG work - drafts proposed to WG on ECN codepoint usage/semantics, and propagation of ECN at endpoints of IP-in-IP tunnels that use shim headers, and recent discussion of the RTP circuit breaker (AVTCORE draft) indicates that there is work to be done on how ECN congestion indications should be used.

Changed milestone "Submit 'Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP' as a BCP RFC", set due date to September 2016 from August 2015

Changed milestone "Submit 'SCTP NAT Support' to IESG for consideration as a PS RFC", set due date to December 2015 from November 2014, added draft-ietf-tsvwg-natsupp to milestone

Changed milestone "Submit 'Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP' as a BCP RFC", set state to active from review, accepting new milestone

Changed milestone "Submit 'Quick Failover Algorithm in SCTP' to the IESG for consideration as a Proposed Standard RFC", set due date to May 2015 from December 2014

Changed milestone "Submit 'DTLS Encapsulation of SCTP Packets for RTCWEB ' to IESG for consideration as a Proposed Standard RFC", set due date to December 2014 from October 2014, resolved as "Done", added draft-ietf-tsvwg-sctp-dtls-encaps to milestone

Changed milestone "Submit 'SCTP New Data Chunk' as a PS RFC", set description to "Submit 'SCTP New Data Chunk' as a Proposed Standard RFC", set due date to February 2015 from July 2014

Changed milestone "Submit 'Quick Failover Algorithm in SCTP' to the IESG for consideration as an Experimental RFC", set description to "Submit 'Quick Failover Algorithm in SCTP' to the IESG for consideration as a Proposed Standard RFC", set due date to December 2014 from May 2014

Changed milestone "Submit 'Encoding and Transport of (Pre-) Congestion Information from the Domain Egress to the Ingress' to the IESG for consideration as an Experimental RFC", resolved as "Done"

Changed milestone "Submit 'DTLS Encapsulation of SCTP Packets for RTCWEB ' to IESG for consideration as a Proposed Standard RFC", set due date to October 2014 from January 2014

Changed milestone "Submit 'Intserv Multiple TSpec' to IESG for consideration as a Proposed Standard RFC", set description to "Submit 'RSVP Multiple Instance' to IESG as a PS RFC", set due date to April 2015 from May 2012

Changed milestone "Submit 'SCTP NAT Support' to IESG for consideration as a Proposed Standard", set description to "Submit 'SCTP NAT Support' to IESG for consideration as a PS RFC", set due date to November 2014 from May 2013

Changed milestone "Submit 'Quick Failover Algorithm in SCTP' to the IESG for consideration as an Experimental RFC", set due date to May 2014 from July 2013

Changed milestone "Submit 'RSVP Application-ID Profiles for Voice and Video Streams' to IESG for consideration as a Proposed Standard RFC", set due date to January 2014 from July 2013

Changed milestone "Submit 'Encoding and Transport of (Pre-) Congestion Information from the Domain Egress to the Ingress' to the IESG for consideration as an Experimental RFC", set due date to January 2014 from May 2013

Changed milestone "Updates to RFC 793 to resolve conflict between diffserv and TCP interpretation of IP Precedence submitted for publication as Proposed Standard", resolved as "Done"