[Isis-wg] Proposed Liaison response on Ethernet Jumbo Frames

Alia Atlas <akatlas@gmail.com> Fri, 02 June 2017 16:15 UTC

Return-Path: <akatlas@gmail.com>
X-Original-To: isis-wg@ietfa.amsl.com
Delivered-To: isis-wg@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id F0444126DEE for <isis-wg@ietfa.amsl.com>; Fri, 2 Jun 2017 09:15:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id j26lYK1ql74V for <isis-wg@ietfa.amsl.com>; Fri, 2 Jun 2017 09:15:52 -0700 (PDT)
Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 921BB126C25 for <isis-wg@ietf.org>; Fri, 2 Jun 2017 09:15:52 -0700 (PDT)
Received: by mail-wm0-x230.google.com with SMTP id d127so30706532wmf.0 for <isis-wg@ietf.org>; Fri, 02 Jun 2017 09:15:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=harLD7pXAfXEY04HTmLunneX1STbefZprJfSiSCqlqo=; b=V19cE6AGkEsoIFxGFU+1GazH5NVEWSjWHf/8AA383e7mNGHJHXQsPE1DVVQqs+DWQR jOW1YsVR/2Xwzu637oaQRkTnkurozJOyqVW1ursRrawKRtW5nGwFVSILgkzcTmn/ouCk ylD6NoDhMbEShQ9tv8JQ6kFOOUDD+xwMnFpNvNje3bhQjWW4bQNKM6jP2I2cRc+DeNN0 vmzi/wUFXgekZAul/PPI4idC5m6pUlIWRmIcJIh/0qHkavaObBLW8no/SiZ2nZWZGYS2 Imlmsb1j18iT85h5SSahXVoxuU/wTBaT2sYTG25rgMkZEKfSWNtlHW4YPrDqm6XHpzS0 w4sA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=harLD7pXAfXEY04HTmLunneX1STbefZprJfSiSCqlqo=; b=TVFvnbXz+pL8ozHTSahIMKqqDxgr5/V3dv8SzW9P8BV/ecGiBXS1OeNXw1ZQ3MGTXb 0w9u/kBGCMeSm03/quYbuXqmeGDDJE2fEO7WsANfG/SAG6UbWNYsHEZbyKpEHmKTvZ8i KfOd38AT2MbPyx5gSAw5f996cv2xp+uEhNqfKW4DS5CEhqGLG5KvnRcyObb2fLhvUFEA xvjf+C+MgH+tIECHwgJxnD1XqzLBGdflxxIrlN1g8d88xkJmr92HKnlp6PUsNAnuRYcz iIr5BdRDSyOA8HKxciBWCRvG6ApzTLsqhpxjE0D/zhQ/bXE81vHglPZoEreVnR31Y4e8 bJAw==
X-Gm-Message-State: AODbwcCVN8yE15J0FO8wpeVAzccy4x3d6wrpULF/PmRVBmS6shKjKxoA 6pxyLw5pf3Jb2UJlMZsSjkpeTqL66y1xIxA=
X-Received: by with SMTP id i135mr37659wmg.123.1496420150842; Fri, 02 Jun 2017 09:15:50 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Fri, 2 Jun 2017 09:15:50 -0700 (PDT)
From: Alia Atlas <akatlas@gmail.com>
Date: Fri, 2 Jun 2017 12:15:50 -0400
Message-ID: <CAG4d1rdVmdAarEa=twh0YWoYhLf7v5m_-Qr0QKQ9BHqUV9Ym4w@mail.gmail.com>
To: "isis-wg@ietf.org" <isis-wg@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c13055a869b910550fc77d4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/isis-wg/P_Y7UEUxLtk0Vl8qMeW-ulstNps>
Subject: [Isis-wg] Proposed Liaison response on Ethernet Jumbo Frames
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/isis-wg/>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Jun 2017 16:15:55 -0000


At the end of the ISIS WG meeting at IETF 98, I called attention to the
recent liaison from IEEE -  https://datatracker.ietf.org/liaison/1509/
<https://datatracker.ietf.org/liaison/1509/>.  There was significant
concern expressed about the decision to use a new EtherType instead of
EtherType 88-70, which is widely deployed.

Here is a proposed liaison response, which should also update you on
progress that has been made in this area. I would prefer to get this
liaison, with any improvements, agreed to by June 15.


Thank you very much for your liaison on March 25.  We are happy to learn
that IEEE now has a standard, IEEE Std 802.1AC-2016, for encoding LLC
frames and that its use appears to be exactly as described in
draft-ietf-isis-ext-eth-01.  There are a large number of pre-standard
implementations and deployments of this functionality.

With informal discussion, we were able to determine the current owner of
EtherType 88-70 and have what we believe is the necessary statement so that
this EtherType is now available for this functionality.  I would like to
thank both Yaakov Stein, CTO RAD, for making this happen and David Aviv,
CTO Radware.  As these types of challenges come up and have large impact,
we would prefer to learn of them earlier so that we can try and assist
sooner in the process.

We are quite concerned about the allocation of a new EtherType given the
extremely large deployment of this pre-standard common feature.  We would
encourage the IEEE 802.1 Working Group to strongly consider updating IEEE
Std 802.1AC to use the deployed EtherType 88-70 that is now available for
this purpose.

The ISIS Working Group will discuss whether there is additional work to do
now that IEEE Std 802.1AC-2016 is available.

Warmest regards,
Alia Atlas, IETF Routing Area Director
Chris Hopps, ISIS Working Group Chair
Hannes Gredler, ISIS Working Group Chair


Please also discuss whether there is additional ISIS work to be done.  I'm
specifically thinking about sending hello packets at the MTU.