Wireshark-bugs: [Wireshark-bugs] [Bug 10500] wrong decode at ethernet OAM Y.1731 Synthetic Loss

Date: Thu, 25 Sep 2014 11:38:40 +0000

Comment # 6 on bug 10500 from
go to:
http://www.itu.int/ITU-T/recommendations/rec.aspx?rec=11136
you can get for free the original standard ITU-T Y.1731.

Go in the pdf to chapter 8.4 the protocol is described.
We used singele-ended ETH-SLM.
Chapter 8.4.1.1 (SLM transmission) says:
Source MEP ID: MEP´s  own identity in the MEG

Go in the pdf to chapter 9.22 the PDUs are described.
Source MEP ID: Source MEP ID is a 2-octet field where the last 13 least
significant bits are used to identify the MEP transmitting the SLM frame.
MEP ID is unique within the MEG.

chapter 9.23.1:
Responder MEP ID: Responder MEP ID is a 2-octet field where the last 13 least
significant bits are used to identify the MEP transmitting the SLR frame.
MEP ID is unique within the MEG.

So please decode to: 0x0064 so everybody knows this is hex
or decode to: 100 so everybody think this is decimal (I think the better way).

Why you decode (see my attatched error description) in the second picture
(frame 4;  ETH-CCM (Ethernet Continuity Check Message) (the first picture was
the “About Wireshark”) the local MEP ID (Maintenance Association End Point
Identifire) in plan 2 (Packet Details view) to 100 in decimal and not to hex
0x0064?


You are receiving this mail because:
  • You are watching all bug changes.