1 / 18

LMAP Framework: Guidelines for Measurement and Network Assessment

The LMAP Framework draft provides a comprehensive architecture for network measurement and assessment protocols. It merges three individual documents into a cohesive model that simplifies constraints and introduces a protocol model. The draft discusses key components, including bootstrapping, control, and reporting of measurement activities, while ensuring alignment with existing information models. It addresses privacy considerations and offers guidance on starting and stopping tests. This draft is intended for submission to the IESG as an Informational RFC in December 2013.

habib
Télécharger la présentation

LMAP Framework: Guidelines for Measurement and Network Assessment

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. LMAP Frameworkdraft-ietf-lmap-framework-01 Philip Eardley Al Morton, Marcelo Bagnulo, Trevor Burbridge, Paul Aitken, AamerAkhter 6th November 2013 Vancouver, IETF-88

  2. Framework • Milestone • Dec 2013 Submit the LMAP Framework I-D to the IESG for consideration as Informational RFC • Reviews needed!!

  3. Framework • Merger of 3 individual i-ds • Terminology from eardley-lmap-terminology • Simplifying constraints from eardley-lmap-framework • Detailed discussion of LMAP components from akhter-lmap-framework • Several aspects updated, • Introduced protocol model • "an architectural model for how the protocol operates ... a short description of the system in overview form, ... • Trying to keep this aligned with burbridge-lmap-information-model-01 • Better discussion about bootstrapping, starting & stopping tests, etc • New section on privacy considerations • Many aspects unchanged, • For instance, Constraints: • Measurement system is under the direction of a single organisation • Each MA may only have a single Controller at any point in time • Introduced a protocol model • Bootstrapping; control; report; • Better discussion about bootstrapping, starting & stopping tests…

  4. Bootstrapping Notation: (optional) +--------------+ | Measurement | | Agent | +--------------+ (Initial Controller details: address or FQDN, -> security credentials) +-----------------+ | Initial | | Controller | +-----------------+ <- (register) Controller details: address or FQDN, -> security credentials +-----------------+ | | | Controller | +-----------------+ <- register MA-ID, (Group-ID, report?) ->

  5. Bootstrapping Notation: (optional) +--------------+ | Measurement | | Agent | +--------------+ (Initial Controller details: address or FQDN, -> security credentials) +-----------------+ | Initial | | Controller | +-----------------+ <- (register) Controller details: address or FQDN, -> security credentials +-----------------+ | | | Controller | +-----------------+ <- register MA-ID, (Group-ID, report?) -> May be a device/access specific mechanism Typically there are NAT interactions (not shown)

  6. Notation: [potentially repeated] (optional) Control protocol +-----------------+ +-------------+ | | | Measurement | | Controller |===================================| Agent | +-----------------+ +-------------+ Instruction: [(Measurement Task (parameters)), -> (Measurement Schedule), (Report Channel(s))] <- ACK (Capability request) -> <- List of Measurement Methods ACK -> Suppress -> <- Failure report: (reason) ACK ->

  7. Notation: [potentially repeated] (optional) Control protocol +-----------------+ +-------------+ | | | Measurement | | Controller |===================================| Agent | +-----------------+ +-------------+ Instruction: [(Measurement Task (parameters)), -> (Measurement Schedule), (Report Channel(s))] <- ACK (Capability request) -> <- List of Measurement Methods ACK -> Suppress -> <- Failure report: (reason) ACK -> Nothing about progress of M. Task

  8. Notation: [potentially repeated] (optional) Control protocol +-----------------+ +-------------+ | | | Measurement | | Controller |===================================| Agent | +-----------------+ +-------------+ Instruction: [(Measurement Task (parameters)), -> (Measurement Schedule), (Report Channel(s))] <- ACK (Capability request) -> <- List of Measurement Methods ACK -> Suppress -> <- Failure report: (reason) ACK -> No negotiation Can report to >1 Collector Generalised to ‘Channel’ in latest Info Model i-d

  9. Notation: [potentially repeated] (optional) Control protocol +-----------------+ +-------------+ | | | Measurement | | Controller |===================================| Agent | +-----------------+ +-------------+ Instruction: [(Measurement Task (parameters)), -> (Measurement Schedule), (Report Channel(s))] <- ACK (Capability request) -> <- List of Measurement Methods ACK -> Suppress -> <- Failure report: (reason) ACK -> Open question: Details of suppress (amber state? Time limit?) Controller asks MA to stop doing M. Tasks Not ACK’d

  10. Notation: [potentially repeated] (optional) Control protocol +-----------------+ +-------------+ | | | Measurement | | Controller |===================================| Agent | +-----------------+ +-------------+ Instruction: [(Measurement Task (parameters)), -> (Measurement Schedule), (Report Channel(s))] <- ACK (Capability request) -> <- List of Measurement Methods ACK -> Suppress -> <- Failure report: (reason) ACK -> MA cannot action Instruction M. Task could not be executed Called ‘logging’ in Info model i-d

  11. Report protocol Notation: [potentially repeated] +-----------------+ +-------------+ | | | Measurement | | Controller |===================================| Agent | +-----------------+ +-------------+ <- Report: [MA-ID &/or Group-ID, Measurement Results, Measurement Task] ACK ->

  12. Report protocol Notation: [potentially repeated] +-----------------+ +-------------+ | | | Measurement | | Controller |===================================| Agent | +-----------------+ +-------------+ <- Report: [MA-ID &/or Group-ID, Measurement Results, Measurement Task] ACK -> Open question: How /if label M. Results impacted (potentially?) by cross-traffic

  13. New privacy section • Responds to Charter requirements • Mostly follows outline of RFC 6973 & benefits greatly from its timely publication • "Privacy Considerations for Internet Protocols" • Please review the section! • Open question: should it be removed to a separate draft • Open question: how useful is a Group-ID?

  14. New privacy section 8. Privacy Considerations for LMAP . . . . . . . . . . . . . . . 24 8.1. Categories of Entities with Information of Interest . . . 25 8.2. Examples of Sensitive Information . . . . . . . . . . . . 25 8.3. Key Distinction Between Active and Passive Measurement Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . 26 8.4. Communications Model (for Privacy) . . . . . . . . . . . 26 8.4.1. Controller <-> Measurement Agent . . . . . . . . . . 27 8.4.2. Collector <-> Measurement Agent . . . . . . . . . . . 28 8.4.3. Active Measurement Peer <-> Measurement Agent . . . . 28 8.4.4. Passive Measurement Peer <-> Measurement Agent . . . 29 8.4.5. Result Storage and Reporting . . . . . . . . . . . . 30 8.5. Threats . . . . . . . . . . . . . . . . . . . . . . . . . 30 8.5.1. Surveillance . . . . . . . . . . . . . . . . . . . . 30 8.5.2. Stored Data Compromise . . . . . . . . . . . . . . . 31 8.5.3. Correlation and Identification . . . . . . . . . . . 31 8.5.4. Secondary Use and Disclosure . . . . . . . . . . . . 31 8.6. Mitigations . . . . . . . . . . . . . . . . . . . . . . . 32 8.6.1. Data Minimization . . . . . . . . . . . . . . . . . . 32 8.6.2. Anonymity . . . . . . . . . . . . . . . . . . . . . . 33 8.6.3. Pseudonymity . . . . . . . . . . . . . . . . . . . . 34 8.6.4. Other Mitigations . . . . . . . . . . . . . . . . . . 34 8.7. The potential role of a Group-ID for privacy . . . . . . 34

  15. Beyond scope of lmap • coordination process between MAs. • interactions between the Collector and Controller. • coordination between different measurement systems • Including 2 independent MAsin a home • user-initiated measurements

  16. Next steps • Please review! • (default) we’ll create a separate i-d for privacy section • (default) we’ll ask for WGLC on next rev

  17. Spare slides

  18. Overall measurement system ^ | IPPM +---------------+ Test +-------------+ Scope +------->| Measurement |<---------->| Measurement | v | | Agent | Traffic | Peer | ^ | +---------------+ +-------------+ | | ^ | | | Instruction | | Report | | | +-----------------+ | | | | | | | v LMAP | +------------+ +------------+ Scope | | Controller | | Collector | | | +------------+ +------------+ v | ^ ^ | ^ | | | | | | | +----------+ | | | | | v | +-----------+ +---------+ +--------+ +----------+ | |Initializer| |Parameter|--->|Analysis|<---|Repository| Out +-----------+ |DataBase | | tools | +----------+ of +---------+ +--------+ Scope | v Figure 1: Schematic of main elements of an LMAP-based measurement system (showing the elements in and out of the scope of the LMAP WG)

More Related