Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

[802SEC] FW: List of potential areas for IETF/IEEE802 coordination

The following is a list of areas that have been identified where there may be a need for coordination between IETF and IEEE 802. That may mean that there is an overlap, an opportunity to reference or leverage work, a concern on whether the work is being used appropriately or a possibility to get a better standard by cooperation. This list was compiled without filtering - any areas suggested were added. Pruning, grouping and prioritizing  is yet be done.


A next step toward the pruning, grouping and prioritizing process would be to provide a brief explanation of why each item is on the list. Some first cuts at examples have been provided as examples.


- IETF work proposed and underway in that addresses the operation and control of MAC bridged networks and IEEE 802.1 including

                IETF TRILL Fine-grained labeling and IEEE 802.1 tags

                IETF BFD and IEEE 802.1AX


- IETF NVO and IEEE 802.1 DCB

                IEEE 802.1Qbg VDP might be used as the basis for the communication that NVO may need between an end system and an external box (e.g. bridge or router) doing the NVO encapsulation. Coordination will help determine if VDP is a suitable candidate and possibly to make any amendment needed in VDP for NVO usage.


- IETF awareness of IEEE 802.1Q-2011

                Many IETF drafts reflect a knowledge of IEEE 802.1Q-2005 and ignore the evolution to IEEE 802.1Q-2011. There are two aspects of this. First, it leads to statements in IETF drafts about the capabilities of IEEE 802.1 bridging that are incorrect, often as part of the justification for new work.  Many NVO drafts are an example of this.  E.g. frequent references to the 12-bit VLAN ID not scaling without mention that the I-tag carries a 24-bit I-SID (backbone Service Instance Identifier) for networks needing a bigger scale. Secondly, it can lead to incompatibility between bridging using more recent capabilities of IEEE 802.1Q-2011 and protocols written based on IEEE 802.1Q-2005.


- Effect of virtualization on IEEE 802 architecture


- IETF EMU and IEEE 802.1X, 802.11 and 802.16 security based on EAP


- IETF ADSL MIB and IEEE 802.3


- IETF 6LOWPAN and IEEE 802.15


- IETF PAWS WG and IEEE 802.1, 802.11, 802.15, 802.16, 802.22


-  IETF IPPM and IEEE 802.16 Metrology Study Group


-  IETF Mobile IP and IEEE 802.16 HetNet Study Group


- IETF HOKEY and IEEE 802.21

                The HOKEY charter includes:  Assistance to the 802.21a group in specifying the integration of EAP pre-authentication with IEEE 802.21a. The Hokey Working Group shall perform tasks that are complementary to and do not duplicate work being done in IEEE 802.21a.


- IETF mif and IEEE 802.21


- IETF IPFIX Information Elements for Data Link monitoring


- IETF RADIUS attributes for IEEE 802 networks


- 802.1Q SRP (and Gen2 updates) and RSVP/SIP


- 802.1AS/1588 and NTP


- 802.1AS/1588, 802.1Q time aware shaper(s) and RTP



---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.