Updates to L2TP v2 & v3 for ECN: draft-ietf-tsvwg-rfc6040update-shim-02
Bob Briscoe <[email protected]> Fri, 16 Jun 2017 15:57:18 +0100
| Newsgroups | gmane.ietf.l2tpext |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format. --===============5802563860518346692== Content-Type: multipart/alternative; boundary="------------DBC2EFF1640885AAA7C8B873" Content-Language: en-GB This is a multi-part message in MIME format. --------------DBC2EFF1640885AAA7C8B873 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Ignacio, Carlos, l2tpext list, I have posted a rev of this draft with the new arrangement for minimally updating L2TP v2 & v3 to ensure legacy implementations are configured safely. The spec to support ECN properly is now within this draft itself as a RECOMMENDED L2TP extension, but it does not update any L2TP specs. Pls review and comment. This is planned to be last-called in tsvwg, deadline Sep 2017. There is talk of also WGLC'ing in opsawg and int-area I think. If you think the L2TP aspects should also be WGLC'd elsewhere in parallel, pls say where. If you think I should give a heads-up presentation in Prague, also pls say where. Cheers Bob -------- Forwarded Message -------- Subject: New Version draft-ietf-tsvwg-rfc6040update-shim-02 Date: Fri, 16 Jun 2017 15:47:58 +0100 From: Bob Briscoe <[email protected]> To: Black, David <[email protected]> CC: tsvwg IETF list <[email protected]> David, as doc shepherd. I have just posted a major revision to draft-ietf-tsvwg-rfc6040update-shim Please also take this as a request to give a 10min presentation in tsvwg. As requested, I included specific text necessary to update certain shim tunnel protocols that didn't mention ECN at all (L2TPv2, L2TPv3, GRE). There are two others to do: * Teredo: I'll do this once I hear from the original author, Christian Huitema * VXLAN-GPE: This is a draft currently going through NVO3 on the standards track. AFAIK the Linux implementation already supports ECN via RFC6040, but the authors will need to add ECN text to the spec, so there is something for other implementations to follow. I have contacted them - they should do this, not me. I have also added more protocols to the list (e.g. CAPWAP, LISP), but these already supported ECN. As you have seen, I have been in conversation with people on the l2tpext list, and on opsawg (for CAPWAP). I haven't found anyone specific to talk to regarding GRE yet, but I have notified int-area and I gave a heads-up at a recent IETF. BTW, your plan was to last call draft-ietf-tsvwg-rfc6040update-shim along with ecn-encap-guidelines, deadline Sep 2017. I should point out that draft-ietf-trill-ecn-support is in WGLC in trill, and it depends normatively on ecn-encap-guidelines opsawg would like to last call draft-ietf-tsvwg-rfc6040update-shim as well (altho I have now realized that no update to CAPWAP is needed, but opsawg is now working on alternative tunnelling protocols to CAPWAP: draft-ietf-opsawg-capwap-alt-tunnel ). I guess int-area might want to last call draft-ietf-tsvwg-rfc6040update-shim too. Bob -------- Forwarded Message -------- Subject: New Version Notification for draft-ietf-tsvwg-rfc6040update-shim-02.txt Date: Fri, 16 Jun 2017 07:14:46 -0700 From: [email protected] To: Bob Briscoe <[email protected]> A new version of I-D, draft-ietf-tsvwg-rfc6040update-shim-02.txt has been successfully submitted by Bob Briscoe and posted to the IETF repository. Name: draft-ietf-tsvwg-rfc6040update-shim Revision: 02 Title: Propagating Explicit Congestion Notification Across IP Tunnel Headers Separated by a Shim Document date: 2017-06-16 Group: tsvwg Pages: 15 URL:https://www.ietf.org/internet-drafts/draft-ietf-tsvwg-rfc6040update-shim-02.txt Status:https://datatracker.ietf.org/doc/draft-ietf-tsvwg-rfc6040update-shim/ Htmlized:https://tools.ietf.org/html/draft-ietf-tsvwg-rfc6040update-shim-02 Htmlized:https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-rfc6040update-shim-02 Diff:https://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-rfc6040update-shim-02 Abstract: RFC 6040 on "Tunnelling of Explicit Congestion Notification" made the rules for propagation of ECN consistent for all forms of IP in IP tunnel. This specification extends the scope of RFC 6040 to include tunnels where two IP headers are separated by at least one shim header that is not sufficient on its own for packet forwarding. It surveys widely deployed IP tunnelling protocols separated by a shim and updates the specifications of those that do not mention ECN propagation (L2TPv2, L2TPv3, GRE and Teredo). The specification also updates RFC 6040 with configuration requirements needed to make any legacy tunnel ingress safe. 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 --------------DBC2EFF1640885AAA7C8B873 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"> Ignacio, Carlos, l2tpext list,<br> <br> I have posted a rev of this draft with the new arrangement for minimally updating L2TP v2 & v3 to ensure legacy implementations are configured safely. The spec to support ECN properly is now within this draft itself as a RECOMMENDED L2TP extension, but it does not update any L2TP specs.<br> <br> Pls review and comment.<br> <br> This is planned to be last-called in tsvwg, deadline Sep 2017.<br> There is talk of also WGLC'ing in opsawg and int-area I think.<br> <br> If you think the L2TP aspects should also be WGLC'd elsewhere in parallel, pls say where.<br> If you think I should give a heads-up presentation in Prague, also pls say where.<br> <br> Cheers<br> <br> <br> <br> Bob<br> <div class="moz-forward-container"><br> <br> -------- Forwarded Message -------- <table class="moz-email-headers-table" cellspacing="0" cellpadding="0" border="0"> <tbody> <tr> <th nowrap="nowrap" valign="BASELINE" align="RIGHT">Subject: </th> <td>New Version draft-ietf-tsvwg-rfc6040update-shim-02</td> </tr> <tr> <th nowrap="nowrap" valign="BASELINE" align="RIGHT">Date: </th> <td>Fri, 16 Jun 2017 15:47:58 +0100</td> </tr> <tr> <th nowrap="nowrap" valign="BASELINE" align="RIGHT">From: </th> <td>Bob Briscoe <a class="moz-txt-link-rfc2396E" href="mailto:[email protected]"><[email protected]></a></td> </tr> <tr> <th nowrap="nowrap" valign="BASELINE" align="RIGHT">To: </th> <td>Black, David <a class="moz-txt-link-rfc2396E" href="mailto:[email protected]"><[email protected]></a></td> </tr> <tr> <th nowrap="nowrap" valign="BASELINE" align="RIGHT">CC: </th> <td>tsvwg IETF list <a class="moz-txt-link-rfc2396E" href="mailto:[email protected]"><[email protected]></a></td> </tr> </tbody> </table> <br> <br> <meta http-equiv="content-type" content="text/html; charset=utf-8"> David, as doc shepherd.<br> <br> I have just posted a major revision to draft-ietf-tsvwg-rfc6040update-shim<br> <br> Please also take this as a request to give a 10min presentation in tsvwg.<br> <br> As requested, I included specific text necessary to update certain shim tunnel protocols that didn't mention ECN at all (L2TPv2, L2TPv3, GRE).<br> There are two others to do: <br> * Teredo: I'll do this once I hear from the original author, Christian Huitema<br> * VXLAN-GPE: This is a draft currently going through NVO3 on the standards track. AFAIK the Linux implementation already supports ECN via RFC6040, but the authors will need to add ECN text to the spec, so there is something for other implementations to follow. I have contacted them - they should do this, not me.<br> <br> I have also added more protocols to the list (e.g. CAPWAP, LISP), but these already supported ECN.<br> <br> As you have seen, I have been in conversation with people on the l2tpext list, and on opsawg (for CAPWAP). I haven't found anyone specific to talk to regarding GRE yet, but I have notified int-area and I gave a heads-up at a recent IETF.<br> <br> <br> BTW, your plan was to last call draft-ietf-tsvwg-rfc6040update-shim along with ecn-encap-guidelines, deadline Sep 2017.<br> I should point out that draft-ietf-trill-ecn-support is in WGLC in trill, and it depends normatively on ecn-encap-guidelines<br> <br> opsawg would like to last call draft-ietf-tsvwg-rfc6040update-shim as well (altho I have now realized that no update to CAPWAP is needed, but opsawg is now working on alternative tunnelling protocols to CAPWAP: draft-ietf-opsawg-capwap-alt-tunnel ). I guess int-area might want to last call draft-ietf-tsvwg-rfc6040update-shim too. <br> <br> <br> <br> Bob<br> <div class="moz-forward-container"><br> <br> -------- Forwarded Message -------- <table class="moz-email-headers-table" cellspacing="0" cellpadding="0" border="0"> <tbody> <tr> <th nowrap="nowrap" valign="BASELINE" align="RIGHT">Subject: </th> <td>New Version Notification for draft-ietf-tsvwg-rfc6040update-shim-02.txt</td> </tr> <tr> <th nowrap="nowrap" valign="BASELINE" align="RIGHT">Date: </th> <td>Fri, 16 Jun 2017 07:14:46 -0700</td> </tr> <tr> <th nowrap="nowrap" valign="BASELINE" align="RIGHT">From: </th> <td><a class="moz-txt-link-abbreviated" href="mailto:[email protected]" moz-do-not-send="true">[email protected]</a></td> </tr> <tr> <th nowrap="nowrap" valign="BASELINE" align="RIGHT">To: </th> <td>Bob Briscoe <a class="moz-txt-link-rfc2396E" href="mailto:[email protected]" moz-do-not-send="true"><[email protected]></a></td> </tr> </tbody> </table> <br> <br> <pre>A new version of I-D, draft-ietf-tsvwg-rfc6040update-shim-02.txt has been successfully submitted by Bob Briscoe and posted to the IETF repository. Name: draft-ietf-tsvwg-rfc6040update-shim Revision: 02 Title: Propagating Explicit Congestion Notification Across IP Tunnel Headers Separated by a Shim Document date: 2017-06-16 Group: tsvwg Pages: 15 URL: <a class="moz-txt-link-freetext" href="https://www.ietf.org/internet-drafts/draft-ietf-tsvwg-rfc6040update-shim-02.txt" moz-do-not-send="true">https://www.ietf.org/internet-drafts/draft-ietf-tsvwg-rfc6040update-shim-02.txt</a> Status: <a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-ietf-tsvwg-rfc6040update-shim/" moz-do-not-send="true">https://datatracker.ietf.org/doc/draft-ietf-tsvwg-rfc6040update-shim/</a> Htmlized: <a class="moz-txt-link-freetext" href="https://tools.ietf.org/html/draft-ietf-tsvwg-rfc6040update-shim-02" moz-do-not-send="true">https://tools.ietf.org/html/draft-ietf-tsvwg-rfc6040update-shim-02</a> Htmlized: <a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-rfc6040update-shim-02" moz-do-not-send="true">https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-rfc6040update-shim-02</a> Diff: <a class="moz-txt-link-freetext" href="https://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-rfc6040update-shim-02" moz-do-not-send="true">https://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-rfc6040update-shim-02</a> Abstract: RFC 6040 on "Tunnelling of Explicit Congestion Notification" made the rules for propagation of ECN consistent for all forms of IP in IP tunnel. This specification extends the scope of RFC 6040 to include tunnels where two IP headers are separated by at least one shim header that is not sufficient on its own for packet forwarding. It surveys widely deployed IP tunnelling protocols separated by a shim and updates the specifications of those that do not mention ECN propagation (L2TPv2, L2TPv3, GRE and Teredo). The specification also updates RFC 6040 with configuration requirements needed to make any legacy tunnel ingress safe. 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> </div> </div> </body> </html> --------------DBC2EFF1640885AAA7C8B873-- --===============5802563860518346692== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ L2tpext mailing list [email protected] https://www.ietf.org/mailman/listinfo/l2tpext --===============5802563860518346692==--