[savi] RFC 8074 on Source Address Validation Improvement (SAVI) for Mixed Address Assignment Methods Scenario
rfc-editor@rfc-editor.org Sat, 18 February 2017 05:31 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: savi@ietfa.amsl.com
Delivered-To: savi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18FFE129540; Fri, 17 Feb 2017 21:31:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dgzc3zOYQpn7; Fri, 17 Feb 2017 21:31:35 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C0098120726; Fri, 17 Feb 2017 21:31:35 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id B89F8B80285; Fri, 17 Feb 2017 21:31:35 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170218053135.B89F8B80285@rfc-editor.org>
Date: Fri, 17 Feb 2017 21:31:35 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/savi/ug1uWaf6s2s4u8yw7hzhts2UQMk>
Cc: drafts-update-ref@iana.org, savi@ietf.org, rfc-editor@rfc-editor.org
Subject: [savi] RFC 8074 on Source Address Validation Improvement (SAVI) for Mixed Address Assignment Methods Scenario
X-BeenThere: savi@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Mailing list for the SAVI working group at IETF <savi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/savi>, <mailto:savi-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/savi/>
List-Post: <mailto:savi@ietf.org>
List-Help: <mailto:savi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/savi>, <mailto:savi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Feb 2017 05:31:37 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8074
Title: Source Address Validation Improvement (SAVI)
for Mixed Address Assignment Methods Scenario
Author: J. Bi,
G. Yao,
J. Halpern,
E. Levy-Abegnoli, Ed.
Status: Standards Track
Stream: IETF
Date: February 2017
Mailbox: junbi@tsinghua.edu.cn,
yaoguang.china@gmail.com,
joel.halpern@ericsson.com,
elevyabe@cisco.com
Pages: 12
Characters: 23910
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-savi-mix-15.txt
URL: https://www.rfc-editor.org/info/rfc8074
DOI: 10.17487/RFC8074
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.
This document is a product of the Source Address Validation Improvements Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC