1 / 6

Secure Communication Protocol Update for Multicast and Unicast Traffic

Update on ESP and AH protocols focusing on multicast considerations, anti-replay requirements, SA identification, and protocol fields. Discusses the use of tunnel vs. transport modes and SAD flags for unicast and multicast communications.

butch
Download Presentation

Secure Communication Protocol Update for Multicast and Unicast Traffic

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. Update on ESP v2 & AH v2 and a Word on 2401bis Steve Kent BBN Technologies

  2. ESP & AH Changes • Revised SA identification text to better accommodate multicast (MSEC WG) • Clarified anti-replay requirements for multicast & multi-sender SAs (MSEC WG) • Move discussion of when to use tunnel vs. transport modes to 2401 bis • Should we remove mandatory algorithm references from AH + ESP?

  3. SA Identification • Unicast: SPI is sufficient, receiver may use protocol (AH/ESP) too, but a purely local decision • Multicast: SHOULD support demuxing based on SPI & destination address and optionally, source address too • SAD flags to cover unicast and multicast: • SPI only • SPI + destination address • SPI + source + destination addresses • But, what about protocol field in multicast case?

  4. Anti-Replay • Transmitter always increments sequence number • Receiver may choose to ignore, locally • Receiver SHOULD tell transmitter to ignore sequence counter wrap-around via IKE negotiation, if the receiver is not going to perform anti-replay check (implies an SAD flag) • Multi-sender SA anti-replay not supported at this time

  5. 2401bis • Reconcile with IKEv2 selector capabilities • Relax specs on when to use tunnel vs.transport mode • Add forwarding/routing lookup prior to SPD lookup, for more sophisticated VPN support • Remove mandatory algorithm references?

  6. Ready for Last Call?

More Related