To: trill IETF list <trill@ietf.org>, "Donald E. Eastlake" <d3e3e3@gmail.com>
References: <149602685471.13342.7416119508424818522.idtracker@ietfa.amsl.com>
From: Bob Briscoe <ietf@bobbriscoe.net>
Message-ID: <7392c971-7ab7-1586-6421-95b0a4fb3450@bobbriscoe.net>
Date: Tue, 30 May 2017 10:12:56 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <149602685471.13342.7416119508424818522.idtracker@ietfa.amsl.com>
Content-Type: multipart/alternative;
 boundary="------------FDD11D1480DF7689734DC42D"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/P-m9ZDxAHWcCBL3OicCrtsgJupk>
Subject: [trill] New Version: draft-ietf-trill-ecn-support-03
Precedence: list

This is a multi-part message in MIME format.
--------------FDD11D1480DF7689734DC42D
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Trillers,

Donald & I have just posted a minor rev of draft-ietf-trill-ecn-support 
to address the following points:

* Until now Low Latency Low Loss Scalable throughput (L4S) was 
referenced as an individual contribution. L4S is now adopted (tsvwg 
milestone), so trill support for the L4S variant of ECN is now more 
significant. However, the advice on L4S marking only explains how 
trill/ECN handling (already specified in this doc) can work correctly 
with the L4S variant of ECN as well. So the L4S text is still not 
normative and still consigned to an appendix.

* Used the new key word boilerplate including RFC 8174.

* Acknowledged Loa Andersson's review.

* Some minor corrections.

As usual, you can get the full diff from the links below.

Cheers


Bob



On 29/05/17 04:00, internet-drafts@ietf.org wrote:
> A new version of I-D, draft-ietf-trill-ecn-support-03.txt
> has been successfully submitted by Donald E. Eastlake and posted to the
> IETF repository.
>
> Name:		draft-ietf-trill-ecn-support
> Revision:	03
> Title:		TRILL: ECN (Explicit Congestion Notification) Support
> Document date:	2017-05-28
> Group:		trill
> Pages:		19
> URL:            https://www.ietf.org/internet-drafts/draft-ietf-trill-ecn-support-03.txt
> Status:         https://datatracker.ietf.org/doc/draft-ietf-trill-ecn-support/
> Htmlized:       https://tools.ietf.org/html/draft-ietf-trill-ecn-support-03
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-trill-ecn-support-03
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-trill-ecn-support-03
>
> Abstract:
>     Explicit congestion notification (ECN) allows a forwarding element to
>     notify downstream devices, including the destination, of the onset of
>     congestion without having to drop packets. This can improve network
>     efficiency through better flow control without packet drops. This
>     document extends ECN to TRILL switches, including integration with IP
>     ECN, and provides for ECN marking in the TRILL Header Extension Flags
>     Word (see RFC 7179).
>
>
>                                                                                    
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>

-- 
________________________________________________________________
Bob Briscoe                               http://bobbriscoe.net/


--------------FDD11D1480DF7689734DC42D
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Trillers,<br>
    <br>
    Donald &amp; I have just posted a minor rev of
    draft-ietf-trill-ecn-support to address the following points:<br>
    <br>
    * Until now Low Latency Low Loss Scalable throughput (L4S) was
    referenced as an individual contribution. L4S is now adopted (tsvwg
    milestone), so trill support for the L4S variant of ECN is now more
    significant. However, the advice on L4S marking only explains how
    trill/ECN handling (already specified in this doc) can work
    correctly with the L4S variant of ECN as well. So the L4S text is
    still not normative and still consigned to an appendix.<br>
    <br>
    * Used the new key word boilerplate including RFC 8174.<br>
    <br>
    <span class="insert">* Acknowledged Loa Andersson's review.</span><br>
    <br>
    * Some minor corrections.<br>
    <br>
    As usual, you can get the full diff from the links below.<br>
    <br>
    Cheers<br>
    <br>
    <br>
    Bob<br>
    <br>
    <br>
    <br>
    <div class="moz-cite-prefix">On 29/05/17 04:00,
      <a class="moz-txt-link-abbreviated" href="mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a> wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:149602685471.13342.7416119508424818522.idtracker@ietfa.amsl.com">
      <pre wrap="">
A new version of I-D, draft-ietf-trill-ecn-support-03.txt
has been successfully submitted by Donald E. Eastlake and posted to the
IETF repository.

Name:		draft-ietf-trill-ecn-support
Revision:	03
Title:		TRILL: ECN (Explicit Congestion Notification) Support
Document date:	2017-05-28
Group:		trill
Pages:		19
URL:            <a class="moz-txt-link-freetext" href="https://www.ietf.org/internet-drafts/draft-ietf-trill-ecn-support-03.txt">https://www.ietf.org/internet-drafts/draft-ietf-trill-ecn-support-03.txt</a>
Status:         <a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-ietf-trill-ecn-support/">https://datatracker.ietf.org/doc/draft-ietf-trill-ecn-support/</a>
Htmlized:       <a class="moz-txt-link-freetext" href="https://tools.ietf.org/html/draft-ietf-trill-ecn-support-03">https://tools.ietf.org/html/draft-ietf-trill-ecn-support-03</a>
Htmlized:       <a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/html/draft-ietf-trill-ecn-support-03">https://datatracker.ietf.org/doc/html/draft-ietf-trill-ecn-support-03</a>
Diff:           <a class="moz-txt-link-freetext" href="https://www.ietf.org/rfcdiff?url2=draft-ietf-trill-ecn-support-03">https://www.ietf.org/rfcdiff?url2=draft-ietf-trill-ecn-support-03</a>

Abstract:
   Explicit congestion notification (ECN) allows a forwarding element to
   notify downstream devices, including the destination, of the onset of
   congestion without having to drop packets. This can improve network
   efficiency through better flow control without packet drops. This
   document extends ECN to TRILL switches, including integration with IP
   ECN, and provides for ECN marking in the TRILL Header Extension Flags
   Word (see RFC 7179).


                                                                                  


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

</pre>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
________________________________________________________________
Bob Briscoe                               <a class="moz-txt-link-freetext" href="http://bobbriscoe.net/">http://bobbriscoe.net/</a></pre>
  </body>
</html>

--------------FDD11D1480DF7689734DC42D--