RFC 8043 on Source-Address-Dependent Routing and Source Address Selection for IPv6 Hosts: Overview of the Problem Space

rfc-editor@rfc-editor.org Fri, 06 January 2017 21:04 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1D09129EF5 for <ietf-announce@ietfa.amsl.com>; Fri, 6 Jan 2017 13:04:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.302
X-Spam-Level:
X-Spam-Status: No, score=-7.302 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-3.1, 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 Mk2K28z8HiWq for <ietf-announce@ietfa.amsl.com>; Fri, 6 Jan 2017 13:04:14 -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 30EA0129EF7 for <ietf-announce@ietf.org>; Fri, 6 Jan 2017 13:04:00 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 063A4B80112; Fri, 6 Jan 2017 13:04:00 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8043 on Source-Address-Dependent Routing and Source Address Selection for IPv6 Hosts: Overview of the Problem Space
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170106210400.063A4B80112@rfc-editor.org>
Date: Fri, 6 Jan 2017 13:04:00 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/e6ZFndDA86P9WZAaq-NLLTLVz_0>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Jan 2017 21:04:16 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8043

        Title:      Source-Address-Dependent Routing and Source Address 
                    Selection for IPv6 Hosts: Overview of 
                    the Problem Space 
        Author:     B. Sarikaya, M. Boucadair
        Status:     Informational
        Stream:     Independent
        Date:       January 2017
        Mailbox:    sarikaya@ieee.org, 
                    mohamed.boucadair@orange.com
        Pages:      16
        Characters: 35213
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-sarikaya-6man-sadr-overview-12.txt

        URL:        https://www.rfc-editor.org/info/rfc8043

        DOI:        10.17487/RFC8043

This document presents the source-address-dependent routing (SADR)
problem space from the host's perspective.  Both multihomed hosts and
hosts with multiple interfaces are considered.  Several network
architectures are presented to illustrate why source address
selection and next-hop resolution are needed in view of
source-address-dependent routing.

The document is scoped on identifying a set of scenarios for
source-address-dependent routing from the host's perspective and
analyzing a set of solutions to mitigate encountered issues.  The
document does not make any solution recommendations.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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