RFC 7445 on Analysis of Failure Cases in IPv6 Roaming Scenarios

rfc-editor@rfc-editor.org Wed, 11 March 2015 00:50 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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B10151A9140; Tue, 10 Mar 2015 17:50:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level:
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
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 bk4VhHmyByxu; Tue, 10 Mar 2015 17:50:25 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id F32301A9118; Tue, 10 Mar 2015 17:50:19 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id CD51F180463; Tue, 10 Mar 2015 17:49:33 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7445 on Analysis of Failure Cases in IPv6 Roaming Scenarios
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150311004933.CD51F180463@rfc-editor.org>
Date: Tue, 10 Mar 2015 17:49:33 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/0puWF8Y5atfg_YV7jHEY6Qu0UR0>
Cc: v6ops@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 11 Mar 2015 00:50:26 -0000

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

        
        RFC 7445

        Title:      Analysis of Failure Cases in 
                    IPv6 Roaming Scenarios 
        Author:     G. Chen, H. Deng,
                    D. Michaud, J. Korhonen,
                    M. Boucadair
        Status:     Informational
        Stream:     IETF
        Date:       March 2015
        Mailbox:    phdgang@gmail.com, 
                    denghui@chinamobile.com, 
                    dave.michaud@rci.rogers.com,
                    jouni.nospam@gmail.com, 
                    mohamed.boucadair@orange.com
        Pages:      19
        Characters: 44466
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-v6ops-ipv6-roaming-analysis-07.txt

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

This document identifies a set of failure cases that may be
encountered by IPv6-enabled mobile customers in roaming scenarios.
The analysis reveals that the failure causes include improper
configurations, incomplete functionality support in equipment, and
inconsistent IPv6 deployment strategies between the home and the
visited networks.

This document is a product of the IPv6 Operations Working Group of the IETF.


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/rfc.html

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