Folks,
The IS-IS WG has a draft out on how IP over GigE jumbograms
should work. This is online at:
http://www.ietf.org/internet-drafts/draft-ietf-isis-ext-eth-00.txt
As this does have implications for IPv6 over GigE jumbograms,
folks over here in IPv6-land might want to look over that document
and participate in the discussions over on the IS-IS mailing list.
Because all IS-IS WG documents are published as Informational
RFCs (because ISO is the standards-body for IS-IS), many folks treat
Informational RFCs from the IS-IS WG as carrying equal weight
as a standards-track document. While it might not precisely *be*
a standards-tack document, this tends to be the reality of output
from that particular WG.
For reference, one issue is how big an Ethernet Jumbogram
is. The IEEE position is that there is only one Ethernet MTU size.
Widely available GigE products support a frame size of ~9K bytes.
The IS-IS WG, with its folks on POS interfaces that have been designed
for FDDI MTU (4470 bytes) for historical reasons, might end up
picking 4470 as their spec for Ethernet Jumbogram MTU. There is
also the matter of how the IP packet is encapsulated into Ethernet/
802.3 for the case of an Ethernet jumbogram and several opinions
there also.
If none of this matters to folks, fine. If it does matter,
the discussion is occurring over on the IS-IS list and the time
to review and comment is now...
Cheers,
Ran
[EMAIL PROTECTED]
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
