Editing EtherType (section)

== Jumbo frames ==
The size of the payload of non-standard [[jumbo frame]]s, typically ~9000 Bytes long, collides with the range used by EtherType, and cannot be used for indicating the length of such a frame. The proposition to resolve this conflict was to substitute the special EtherType value 0x8870 when a length would otherwise be used.<ref>{{cite IETF |draft=draft-ietf-isis-ext-eth-01 |title=Extended Ethernet Frame Size Support |date=November 2001}}</ref> However, the proposition (its use case was bigger packets for [[IS-IS]]) was not accepted and it is defunct. The chair of IEEE 802.3 at the time, Geoff Thompson, responded to the draft outlining IEEE 802.3's official position and the reasons behind the position. The draft authors also responded to the chair's letter, but no subsequent answer from the IEEE 802.3 has been recorded.<ref name="jumbo">{{cite news |url=https://datatracker.ietf.org/doc/draft-kaplan-isis-ext-eth/ |title=Extended Ethernet Frame Size Support |author=Kaplan |newspaper=Ietf Datatracker |publisher=[[Internet Engineering Task Force]] |date=2000-05-26|display-authors=etal}}</ref>

While defunct, this draft was implemented and is used in Cisco routers in their IS-IS implementation (for IIH Hello packets padding).<ref>{{cite mailing list |url=http://permalink.gmane.org/gmane.comp.security.scapy.general/5154 |title=Fwd: Re: ISIS in SCAPY and Jumbo frames |first=Marcel |last=Patzlaff |mailing-list=scapy-ml |date=2015-04-08 |access-date=2017-05-09 |archive-url=https://web.archive.org/web/20180331104715/http://permalink.gmane.org/gmane.comp.security.scapy.general/5154 |archive-date=2018-03-31 |url-status=dead }}</ref>