Source Address Validation Improvement (SAVI) for Mixed Address Assignment Methods Scenario (RFC8074)
Original Publication Date: 2017-Feb-01
Included in the Prior Art Database: 2017-Feb-19
Internet Society Requests For Comment (RFCs)
J. Bi: AUTHOR [+5]
There are currently several Source Address Validation Improvement (SAVI) documents ([RFC6620], [RFC7513], and [RFC7219]) that describe the different methods by which a switch can discover and record bindings between a node's IP address and a binding anchor and use that binding to perform source address validation. Each of these documents specifies how to learn on-link addresses, based on the technique used for their assignment: StateLess Address Autoconfiguration (SLAAC), the Dynamic Host Control Protocol (DHCP), and Secure Neighbor Discovery (SEND), respectively. Each of these documents describes separately how one particular SAVI method deals with address collisions (same address but different binding anchor).
Internet Engineering Task Force (IETF) J. Bi Request for Comments: 8074 Tsinghua University Category: Standards Track G. Yao ISSN: 2070-1721 Tsinghua University/Baidu J. Halpern Ericsson E. Levy-Abegnoli, Ed. Cisco February 2017
Source Address Validation Improvement (SAVI) for Mixed Address Assignment Methods Scenario
In networks that use multiple techniques for address assignment, the spoofing of addresses assigned by each technique can be prevented using the appropriate Source Address Validation Improvement (SAVI) methods. This document reviews how multiple SAVI methods can coexist in a single SAVI device and how collisions are resolved when the same binding entry is discovered by two or more methods.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841.
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc8074.
Bi, et al. Standards Track [Page 1]
RFC 8074 SAVI-MIX February 2017
Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code C...