Source Address Validation Improvement (SAVI) for Mixed Address Assignment Methods Scenario
RFC 8074
| Document | Type |
RFC - Proposed Standard
(February 2017; No errata)
Was draft-ietf-savi-mix (savi WG)
|
|
|---|---|---|---|
| Authors | Jun Bi , Guang Yao , Joel Halpern , Eric Levy-Abegnoli | ||
| Last updated | 2017-02-17 | ||
| Stream | IETF | ||
| Formats | plain text html pdf htmlized bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Jean-Michel Combes | ||
| Shepherd write-up | Show (last changed 2016-06-12) | ||
| IESG | IESG state | RFC 8074 (Proposed Standard) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Suresh Krishnan | ||
| Send notices to | (None) | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | No IANA Actions | ||
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
Abstract
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 Notice
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 Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3
3. Problem Scope . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Architecture . . . . . . . . . . . . . . . . . . . . . . . . 4
5. Recommendations for Assignment Separation . . . . . . . . . . 6
6. Resolving Binding Collisions . . . . . . . . . . . . . . . . 6
6.1. Same Address on Different Binding Anchors . . . . . . . . 6
6.1.1. Basic Preference . . . . . . . . . . . . . . . . . . 7
6.1.2. Exceptions . . . . . . . . . . . . . . . . . . . . . 7
6.1.3. Multiple SAVI Device Scenario . . . . . . . . . . . . 8
6.2. Same Address on the Same Binding Anchor . . . . . . . . . 9
7. Security Considerations . . . . . . . . . . . . . . . . . . . 9
8. Privacy Considerations . . . . . . . . . . . . . . . . . . . 9
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
10.1. Normative References . . . . . . . . . . . . . . . . . . 10
10.2. Informative References . . . . . . . . . . . . . . . . . 11
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
Bi, et al. Standards Track [Page 2]
RFC 8074 SAVI-MIX February 2017
1. Introduction
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).
While multiple IP assignment techniques can be used in the same layer
Show full document text