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

Re: [802.3_YANG] 802.3cf YANG Task Force Ad Hoc

Rob,

 

Sounds good. Can you send a basic presentation ahead of time so we can structure the discussion?

 

Cheers

Peter

 

 

_________________________________________________

Peter Jones 

802.3cf YANG Task Force Ad Hoc Chair  

http://www.ieee802.org/3/cf/index.html          

_________________________________________________

 

From: Robert Wilton -X (rwilton - ENSOFT LIMITED at Cisco)
Sent: Friday, January 27, 2017 6:37 AM
To: Peter Jones (petejone) <petejone@xxxxxxxxx>; STDS-802-3-YANG@xxxxxxxxxxxxxxxxx
Subject: Re: [802.3_YANG] 802.3cf YANG Task Force Ad Hoc

 

Hi Peter, all,

There are two things that I would like to discuss at Monday's Ad Hoc please:

(1) I would like to discuss the interface statistics a bit further:
  - the interim suggested keeping a higher granularity of frame drop/error counters, but the detailed counter registers do not appear to be defined in clause 30.

So, at the moment, I have defined the following 3 error counters:
          +--ro in-error-fcs-pkts? // 64 <= pkt <= 1518, bad FCS or alignment
          +--ro in-error-runt-pkts? // pkt < 64, good or bad FCS
          +--ro in-error-giant-pkts? // pkt > MRU, good or bad FCS.

The problems that I'm trying to work around in Clause 30 is that there don't appear to be separate registers for:
in-pkts-errors-runt         counter64, // pkt < 64, good frame
in-pkts-errors-fragment     counter64, // pkt < 64, bad frame
in-pkts-errors-giant        counter64, // pkt > MRU, good frame
in-pkts-errors-jabber       counter64, // pkt > MRU, bad frame

There are separate registers in clause 30 for bad FCS vs bad alignment. However, from "30.3.1.1.7 aAlignmentErrors": "This counter will not increment for group encoding schemes encoding greater than 4 bits per group.".  Does this imply that this counter will be 0 for all speeds at 1GB/s or faster?

(2) The IETF/IEEE liaison meeting is on Monday, a couple of hours after the Task Force Ad Hoc.  I will email them to give them a heads up that I want to speak about RMON MIB vs Ethernet 802.3 YANG.  But it would be good to confirm what I say for that meeting.

Thanks,
Rob

On 27/01/2017 01:24, Peter Jones (petejone) wrote:

Folks,

 

We have a call coming up Monday January 30, 2017 7:00 AM-8:00 AM (UTC-08:00) Pacific Time (US & Canada).

 

This will be our first call for the year.

 

Please let me know by end of Day Saturday if you would like to present.

 

Webex details below.

 

Regards

Peter

 

 

_________________________________________________

Peter Jones 

802.3cf YANG Task Force Ad Hoc Chair  

http://www.ieee802.org/3/cf/index.html          

_________________________________________________

 

 

 

 

Join WebEx meeting<https://cisco.webex.com/ciscosales/j.php?MTID=m438de3d0258d7c3656810fe1fdebd85b>

Meeting number: 202 679 154

Meeting password: dot3yang (36839264 from phones)

 

Join by phone

+1-408-525-6800 Call-in toll number (US/Canada)

+1-866-432-9903 Call-in toll-free number (US/Canada)

Access code: 202 679 154

Global call-in numbers<https://cisco.webex.com/ciscosales/globalcallin.php?serviceType=MC&ED=368373162&tollFree=1>  |  Toll-free calling restrictions<https://www.webex.com/pdf/tollfree_restrictions.pdf>

 

 

Can't join the meeting? Contact support.<https://cisco.webex.com/ciscosales/mc>

 

IMPORTANT NOTICE: Please note that this WebEx service allows audio and other information sent during the session to be recorded, which may be discoverable in a legal matter. By joining this session, you automatically consent to such recordings. If you do not consent to being recorded, discuss your concerns with the host or do not join the session..