1 / 6

Mtrace Version 2: Traceroute Facility for IP Multicast

96 th IETF , Jul . 2016, Berlin, German. Mtrace Version 2: Traceroute Facility for IP Multicast. draft-ietf-mboned-mtrace-v2-13 Hitoshi Asaeda, NICT Kerry Meyer, Cisco WeeSan Lee (Ed.). Change from -12. Add a new section: 9.2. Filtering of Clients Comment raised by John Kristoff

sueharvey
Download Presentation

Mtrace Version 2: Traceroute Facility for IP Multicast

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. 96thIETF, Jul. 2016, Berlin, German Mtrace Version 2:Traceroute Facility for IP Multicast draft-ietf-mboned-mtrace-v2-13 Hitoshi Asaeda, NICT Kerry Meyer, Cisco WeeSan Lee (Ed.)

  2. Change from -12 • Add a new section: 9.2. Filtering of Clients • Comment raised by John Kristoff • There is only a brief mention of the potential for amplification of responses and no detailed analysis to the extent, including no mention of the susceptibility to it from spoofed requests. • Perhaps it would be sufficient if the LHR had to ensure a client issuing an Mtrace2 Query can receive a response.

  3. New: 9.2. Filtering of Clients • A router SHOULD support a mechanism to filter out queries from clients beyond a specified administrative boundary. Such a boundary could, for example, be specified via a list of allowed/disallowed client addresses or subnets. If a query is received from beyond the specified administrative boundary, the Query MUST NOT be processed. The router MAY, however, perform rate limited logging of such events.

  4. Old: 4.1.1. Query Packet Verification • Mtrace2 supports a non-local client to the LHR/RP. It is up to the implementation to filter out such queries.

  5. New: 4.1.1. Query Packet Verification • Mtrace2 supports a non-local client to the LHR/RP. A router SHOULD, however, support a mechanism to filter out queries from clients beyond a specified administrative boundary. The potential approaches are described in Section 9.2.

  6. Next Step • Ready for WGLC? • (We’ll revise the draft with small changes and submit it within a few days unless no other changes required)

More Related