1
Information Elements for Data Link Layer Traffic Measurement - - PowerPoint PPT Presentation
Information Elements for Data Link Layer Traffic Measurement - - PowerPoint PPT Presentation
Information Elements for Data Link Layer Traffic Measurement draft-kashima-ipfix-data-link-layer-monitoring-07 draft-ietf-ipfix-data-link-layer-monitoring-00 Shingo Kashima, Paul Aitken 84th IETF Meeting, Vancouver, 2012 1 Introduction
2
Introduction
- This is the WG version of draft-kashima-ipfix-data-link-layer-
monitoring-07.
- This document lists a series of new Information Elements for
data link layer monitoring.
- The draft has been slowly evolving over the last 3 years.
3
Changes in -00
- Change of authors
- the NTT team are unable to take the work forward at this time.
- Changed export IDs 347 through 354 to “TBD”
- the authors had thought these IDs were reserved, but they’ve been allocated
for other purposes.
- Minor edits:
- removed unused references
- typos corrected
4
Plan
- Resolve open issue (see next slide)
- Produce -01 for WGLC.
5
Open Issue
- New Information Elements related to packet section (ie,
sectionOffset and sectionObservedOctets) can be applied not
- nly to dataLinkFrameSection but also all kinds of packet section:
ipHeaderPacketSection, ipPayloadPacketSection mplsLabelStackSection, mplsPayloadPacketSection.
- Three proposals:
1: modify the existing packet section Information Elements Descriptions 2: deprecate existing packet section Information Elements and create new ones 3: sectionOffset and sectionObservedOctets don’t apply to existing packet section Information Elements
- Looking for WG feedback.
6
Open Issue: proposal 1
- modify the existing packet section Information Elements
- Descriptions. eg for ipHeaderPacketSection:
This Information Element, which may have a variable length, carries a series of
- ctets starting sectionOffset octets from the start of the IP header of a sampled
- packet. With sufficient length, this element also reports octets from the IP
payload, subject to [RFC2804]. See the Security Considerations section. The size of the exported section may be constrained due to limitations in the IPFIX
- protocol. The data for this field MUST NOT be padded unless
sectionObservedOctets is also reported.