[FE] January interim meeting reminder, call for presentations
All,
In case anyone didn't see Bob's earlier announcement, we have officially become a task force!!
Just as a reminder, the Frame Expansion Task Force will be holding its January interim meeting in Sacramento, California on Wednesday, January 12, 2005. We are co-locating with the Congestion Management Task Force. We are piggy-backing on the 802.1 interim courtesy of Paul Congdon and HP.
Please see the meeting announcement at the following URL:
http://ieee802.org/3/frame_study/0501_interim.html
I anticipate that CMTF will meet on Tuesday, January 11th. The FETF will meet on Wednesday. Both task forces will hold a combined joint meeting with 802.1 on Wednesday afternoon.
If you plan to present during the FETF meeting, please send me an e-mail by Friday, January 7th. The e-mail should include name of presenter, title and expected duration. I apologize for the short notice.
At our last meeting in November, our discussion raised a number of questions and potential issues with expanding the frame size. These include:
Are there impacts to 802.3ad Link Aggregation? For load-balancing purposes, flow defined as DA, SA, CoS. If the CoS field is moved (i.e., another field is placed before the VLAN Tag field, say a Security Tag) would anything break in 802.3ad?
Should an 802.1QTag always be first?
Should a management attribute be included to convey maximum frame size support? If so, how would this be accomplished? Would this be a Clause 30 "auto-magical" port attribute? Would this be a Clause 22/45 PHY attribute?
Should we send a liaison to ITU-T regarding our work? Since they're referencing the EFM copper standard, should we warn them about frame size expansion?
Should 802.3 reserve space for 802.3 and allocate remainder to MAC client?
I welcome any and all presentations on the above topics, or on any other related topic to expanding the frame size.
Hope to see you in Sacramento.
Kevin Daines
Chair, Frame Expansion Task Force