-1TD 76 (PLEN)
Question(s):
5/13
Study Group: 13
Meeting, date:
Working Party:
Geneva, 25 April – 6 May 2005
4
Source:
ITU-T Study Group 13
Title:
Liaison Statement on EtherType codes for Ethernet OAM
LIAISON STATEMENT
To:
IEEE 802.1
Approval:
WP 4/13
For:
Action
Deadline:
August 2005
Contact:
Gilles JONCOUR
France Telecom
France
Contact:
Tel: + 33 2 96 05 24 69
Email:
gilles.joncour@francetelecom.com
Tel:
Fax:
Email:
Please don’t change the structure of this table, just insert the necessary information.
Q.5/13 has discussed the coding of the Ethernet Maintenance Entity (ME) levels in the Ethernet
OAM frames. At the moment Y.17ethoam (consent foreseen for February 2006) and IEEE 802.1ag
specify that the ME level is carried in the ME level field and a copy of it is carried in the MAC DA
field of a multicast Ethernet OAM frame by virtue of a reserved multicast MAC address. Unicast
Ethernet OAM frames do not carry such copy.
The copy of the ME level in the MAC DA field allows existing bridges to support Ethernet OAM
after a software upgrade. The ports on those upgraded bridges detect the presence of an Ethernet
OAM frame by looking for one of the OAM specific multicast MAC addresses. Ports with a
maintenance entity group endpoint function are furthermore required to block and discard Ethernet
OAM frames (both multicast and unicast OAM frames) that have a ME level with a numerical value
that is equal or higher than the ME level of the maintenance entity group endpoint function. Ports
on upgraded bridges are able to identify the ME level of multicast Ethernet OAM frames by
inspecting the MAC DA field. Those ports are not able to identify the ME level of the unicast
Ethernet OAM frames, while this ME level is only available in the non accessible ME level field in
the OAM PDU.
Q.5/13 considered the proposal to carry the ME level in the TYPE field and deploy eight
consecutive Ethertype values, one for each ME level. Ports on upgraded bridges would then be able
to identify the ME level for both multicast and unicast Ethernet OAM frames and block and discard
frames that do not comply with the ME level condition. Q.5/13 considers this proposal a better
alternative while it allows filtering of all Ethernet OAM frames by ports on upgraded bridges.
Q.5/13 therefore requests IEEE 802.1 to adapt 802.1ag and specify that the ME level is encoded in
the ETH OAM Ethertype values carried in the TYPE field. Furthermore Q.5/13 proposes that IEEE
802.1 requests the registration authority to allocate a set of eight consecutive Ethertype values for
Ethernet OAM.
___________________
-2TD 76 (PLEN)
Question(s):
5/13
Study Group: 13
Meeting, date:
Working Party:
Geneva, 25 April – 6 May 2005
4
Source:
ITU-T Study Group 13
Title:
Liaison Statement on the latest version of Draft Rec. Y.17ethoam
LIAISON STATEMENT
To:
IEEE 802.1, MEF, IETF/PWE3 & L2VPN
Approval:
WP 4/13
For:
Information/comment
Deadline:
August 2005
Contact:
Gilles JONCOUR
France Telecom
France
Contact:
Tel: + 33 2 96 05 24 69
Email:
gilles.joncour@francetelecom.com
Tel:
Fax:
Email:
Please don’t change the structure of this table, just insert the necessary information.
ITU-T Q.5/13 wishes to inform you about the latest version of draft Recommendation Y.17ethoam
titled “OAM Functions and Mechanisms for Ethernet based Networks”.
We understand that you are currently addressing related OAM work. We intend to continue keeping
an alignment between Q.5/13 work and your work in the area of OAM Functions and Mechanisms
for Ethernet based Networks, and our continuing communication in the past has facilitated this
objective. For example, it is our desire to use CFM protocols being defined in draft IEEE 802.1ag
which are common with some of our OAM functions and mechanisms for Fault Management in
Ethernet based Networks.
The latest draft of Y.17ethoam is attached for your review. We would also appreciate receiving an
update on your on-going OAM work.
We look forward to your inputs before our next meeting in Geneva, 29 August - 9 September 2005.
Note that we intend to have Y.17ethoam approved by SG 13 in February 2006.
Attachment: (TD 75 (PLEN)) May 05 - Draft Recommendation Y.17ethoam
___________________
-3TD 76 (PLEN)
Question(s):
4/13
Study Group: 13
Meeting, date:
Working Party:
Geneva, 25 April – 6 May 2005
4
Source:
ITU-T Study Group 13
Title:
QoS control Architecture for Ethernet-Based IP Access Networks
LIAISON STATEMENT
To:
IEEE 802.1, MEF, SG 12
Approval:
WP 4/13
For:
Comment
Deadline:
19 August 2005
Contact:
Hui-Lan Lu
Lucent Technologies
USA
Tel: +1 732 949 0321
Fax: +1 732 949 1196
Email: huilanlu@lucent.com
Q.4/13 (on Requirements and framework for QoS for Next Generation Networks) is developing a
QoS control architecture for Ethernet-based IP access networks. Because of your Ethernet-related
work, we would like to invite you to review the latest version of the draft. You comments, if any,
will help align our approach with yours as appropriate. Our next meeting is scheduled for 29 August
– 9 September 2005. Thank you.
Attachment: the latest version of TR-123.qos (TD 74 (PLEN)).
___________________