Re: [tsvwg] I-D Action: draft-ietf-tsvwg-ecn-l4s-id-18.txt

[Bob Briscoe <[e-mail]>]

tsvwg,

The latest rev of the l4s architecture draft announced below was updated 
as follows:

The anti-replay problem: Focusing on VPN configuration solutions, rather 
than changes to VPN implementations, which are out of scope for L4S. 
These are in 3 places:

  * §6.2 "VPN Behaviour to Avoid Limitations of Anti-Replay"
  * §9 "Security Considerations"
  * Appendix B.  "Compromises in the Choice of L4S Identifier"

Also:

  * Changes to the terminology section, to remain consistent with
    l4s-arch (new rev also just posted)
  * Putting the citation of RFC4774 in context.
  * Misc other changes we noticed during editing.

Non-changes:

  * After consulting with the int-area
    <https://mailarchive.ietf.org/arch/msg/int-area/y5UmhfSAka7xi_iBvX50bZ0jxzQ/>
    and PALS
    <https://mailarchive.ietf.org/arch/msg/pals/iWxEpj0MB-Du_U8KjelIocbg6Yk/>
    lists (follow the links for the relevant long threads), it was
    decided there is no need to mention that tunnels that support
    resequencing like L2TP should have it disabled for data channels
    carrying L4S traffic (because there's no evidence that any would
    enable sequencing for IP data - sequencing is generally for the
    tunnel control channel or for stateful header compression that
    nowadays hinders rather than helps performance).


Please check the changes and let the list know if there are new problems.

Cheers



Bob



On 01/07/2021 13:23, [e-mail] wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Transport Area Working Group WG of the IETF.
>
>          Title           : Explicit Congestion Notification (ECN) Protocol for Very Low Queuing Delay (L4S)
>          Authors         : Koen De Schepper
>                            Bob Briscoe
> 	Filename        : draft-ietf-tsvwg-ecn-l4s-id-18.txt
> 	Pages           : 57
> 	Date            : 2021-07-01
>
> Abstract:
>     This specification defines the protocol to be used for a new network
>     service called low latency, low loss and scalable throughput (L4S).
>     L4S uses an Explicit Congestion Notification (ECN) scheme at the IP
>     layer that is similar to the original (or 'Classic') ECN approach,
>     except as specified within.  L4S uses 'scalable' congestion control,
>     which induces much more frequent control signals from the network and
>     it responds to them with much more fine-grained adjustments, so that
>     very low (typically sub-millisecond on average) and consistently low
>     queuing delay becomes possible for L4S traffic without compromising
>     link utilization.  Thus even capacity-seeking (TCP-like) traffic can
>     have high bandwidth and very low delay at the same time, even during
>     periods of high traffic load.
>
>     The L4S identifier defined in this document distinguishes L4S from
>     'Classic' (e.g. TCP-Reno-friendly) traffic.  It gives an incremental
>     migration path so that suitably modified network bottlenecks can
>     distinguish and isolate existing traffic that still follows the
>     Classic behaviour, to prevent it degrading the low queuing delay and
>     low loss of L4S traffic.  This specification defines the rules that
>     L4S transports and network elements need to follow with the intention
>     that L4S flows neither harm each other's performance nor that of
>     Classic traffic.  Examples of new active queue management (AQM)
>     marking algorithms and examples of new transports (whether TCP-like
>     or real-time) are specified separately.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-tsvwg-ecn-l4s-id/
>
> There is also an htmlized version available at:
> https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-ecn-l4s-id-18
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-ecn-l4s-id-18
>
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
>

-- 
________________________________________________________________
Bob Briscoe                               http://bobbriscoe.net/