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

"Les Ginsberg (ginsberg)" <> Tue, 13 June 2017 23:29 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B7C5712EB6B for <>; Tue, 13 Jun 2017 16:29:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Status: No, score=-14.521 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 3IqF2pR9OXGr for <>; Tue, 13 Jun 2017 16:29:23 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 0ED6912EB6F for <>; Tue, 13 Jun 2017 16:29:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=17056; q=dns/txt; s=iport; t=1497396562; x=1498606162; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=bUdBEco43rsK1bh7SdFtHbEWG2PPjI+Q2+yFE6WCXxg=; b=Uf1K6yrhUYf+QI+V4aJrglD6SD8Qez4S1GMzwCTw0Yiy0fR2/9RXiC5c qwecueeDAWQpGXG6G1+4hc4j2o/P/Cd2MR5kfDmtnfjyngZaXvr1nytqn nfsL6PQUdJ7fjumpFdNhkqnTV8/mbOzTUHReqoMMVCroL9HilGG+JyH+5 g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.39,339,1493683200"; d="scan'208,217";a="255593536"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-SHA; 13 Jun 2017 23:29:21 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id v5DNTLH3007000 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 13 Jun 2017 23:29:21 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 13 Jun 2017 18:29:21 -0500
Received: from ([]) by ([]) with mapi id 15.00.1210.000; Tue, 13 Jun 2017 18:29:21 -0500
From: "Les Ginsberg (ginsberg)" <>
To: Alia Atlas <>, "" <>
Thread-Topic: [Isis-wg] Proposed Liaison response on Ethernet Jumbo Frames
Thread-Index: AQHS27uRpY0xAGqXbEeZp8hqSyW9E6Ijs6SA///OWiA=
Date: Tue, 13 Jun 2017 23:29:21 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_17aae40f06c141a3a416c2eefab30a3aXCHALN001ciscocom_"
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [Isis-wg] Proposed Liaison response on Ethernet Jumbo Frames
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF IS-IS working group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 13 Jun 2017 23:29:27 -0000

Alia –


“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??


From: Isis-wg [] On Behalf Of Alia Atlas
Sent: Tuesday, June 13, 2017 2:26 PM
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.


On Fri, Jun 2, 2017 at 12:15 PM, Alia Atlas <<>> wrote:

At the end of the ISIS WG meeting at IETF 98, I called attention to the recent liaison from IEEE -<>9/>.  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.