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

Alia Atlas <akatlas@gmail.com> Mon, 19 June 2017 16:11 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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80B8612943C for <isis-wg@ietfa.amsl.com>; Mon, 19 Jun 2017 09:11:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 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, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gwOl0SGAxM8T for <isis-wg@ietfa.amsl.com>; Mon, 19 Jun 2017 09:11:53 -0700 (PDT)
Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (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 4E5E0128C81 for <isis-wg@ietf.org>; Mon, 19 Jun 2017 09:11:53 -0700 (PDT)
Received: by mail-wm0-x233.google.com with SMTP id x70so80834945wme.0 for <isis-wg@ietf.org>; Mon, 19 Jun 2017 09:11:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=fH8kdaFjTqvuv5jY6/wADO/D9kX96NbC8dMFu6FgKTs=; b=JiHSVilooMpCBnA56cA86yPdFNYI71abg8PAIFgmIMYoXeVsHdRMfPm4MgMREIdfuJ S5ujDd3+eZ3hPsCpAeKr8v/rSTdxL1MdbFKfdPjyjetkRpUtznhyTX8aqiNogxb/6TXA rxRGM4Vs6rF8gFvph/12zsCOt+10B492wY6mvbvtBlxZSNJ5/Kl23UEkELyoT45TzuCQ R1xck3WJIDURcNiv7OMpHQAUS7wKGBkYxsDBUz3U43nfVRpwcX9T57m4ghbBmlijuWX7 koa+rHn0qbGNCSMjKEO0UkzU9H+7EcqyTfGcyYxrmG9C7IG+ec0r5awUmc5u/f26oovO cC1w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=fH8kdaFjTqvuv5jY6/wADO/D9kX96NbC8dMFu6FgKTs=; b=Y4wHJ8bF3fpflgBRKRPgttPESq/OxOy3kde2RT2Z1U6kH9crhmdWrMk63/to+85Vgm OFFGW74/3NjSh0LIBn0vDY4IKdB/DSgLw5XJdVoLAUi/xYyowitm9TBek1ZK03RRGuHw XM5/mo/Cy1lNTOj6TZGCmPKNljWH8IvVilYFzhtr7E7A5CqXX6LgZTPQiQooVFl1KEqm j5c0WQ7l4gY260GmkJsdjgwYiKG1qP8B472EHUJK4RpZy9FJPhXd2F9O1CzFtLMC/P/b Xu/9UfolyWTBOxWvrGtk4kN9eg7k/ut/2Sa7k7bR53+dhbPCLIjAJUCPSYhLupFGZd48 ukng==
X-Gm-Message-State: AKS2vOx+4tvQIxgASFrSyVUpgCgyuIF9WOkb3FWKdRPdOM0kCb51bUuP +iSP+kDpnycjka35C6wTRmxtbUMuOg==
X-Received: by 10.28.154.11 with SMTP id c11mr16480023wme.109.1497888711654; Mon, 19 Jun 2017 09:11:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.130.179 with HTTP; Mon, 19 Jun 2017 09:11:51 -0700 (PDT)
In-Reply-To: <17aae40f06c141a3a416c2eefab30a3a@XCH-ALN-001.cisco.com>
References: <CAG4d1rdVmdAarEa=twh0YWoYhLf7v5m_-Qr0QKQ9BHqUV9Ym4w@mail.gmail.com> <CAG4d1rePsu==fGmUMAbrV2BfJE+j87-AtM5bqmtmu_5TMo18_w@mail.gmail.com> <17aae40f06c141a3a416c2eefab30a3a@XCH-ALN-001.cisco.com>
From: Alia Atlas <akatlas@gmail.com>
Date: Mon, 19 Jun 2017 12:11:51 -0400
Message-ID: <CAG4d1rdfTGO6KMgcFYMw9sX_00Es6W4=2mUQ-Eb2zFCOG_QGig@mail.gmail.com>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
Cc: "isis-wg@ietf.org" <isis-wg@ietf.org>
Content-Type: multipart/alternative; boundary="001a114b41309259b00552526439"
Archived-At: <https://mailarchive.ietf.org/arch/msg/isis-wg/PVz_X0V1bd5rbQ7FLZzR_O4IIrQ>
Subject: Re: [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: Mon, 19 Jun 2017 16:11:56 -0000

Ack - ok, cleaning that up and sending liaison.

On Tue, Jun 13, 2017 at 7:29 PM, Les Ginsberg (ginsberg) <ginsberg@cisco.com
> wrote:

> Alia –
>
>
>
> Regarding
>
>
>
> “The ISIS Working Group will discuss whether there is additional work to
> do now that IEEE Std 802.1AC-2016 is available.”
>
>
>
> Did we not discuss this on the list and determined there is no work??
>
>
>
>    Les
>
>
>
>
>
> *From:* Isis-wg [mailto:isis-wg-bounces@ietf.org] *On Behalf Of *Alia
> Atlas
> *Sent:* Tuesday, June 13, 2017 2:26 PM
> *To:* isis-wg@ietf.org
> *Subject:* Re: [Isis-wg] Proposed Liaison response on Ethernet Jumbo
> Frames
>
>
>
> I would like to send this liaison on June 15.  Please send any additional
> comments.
>
>
>
> Thanks,
>
> Alia
>
>
>
> On Fri, Jun 2, 2017 at 12:15 PM, Alia Atlas <akatlas@gmail.com> wrote:
>
> Hi,
>
>
>
> 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.
>
>
>
> =========
>
> Colleagues,
>
>
>
> 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.
>
>
>
> Regards,
>
> Alia
>
>
>
>
>
>
>