RFC 7785 on Recommendations for Prefix Binding in the Context of Softwire Dual-Stack Lite

rfc-editor@rfc-editor.org Wed, 17 February 2016 03:17 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 7F50E1A8AD0 for <ietf-announce@ietfa.amsl.com>; Tue, 16 Feb 2016 19:17:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.908
X-Spam-Level:
X-Spam-Status: No, score=-101.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.006, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, 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 OHKkU1bGXL6U for <ietf-announce@ietfa.amsl.com>; Tue, 16 Feb 2016 19:17:36 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 07D7B1A8ACA for <ietf-announce@ietf.org>; Tue, 16 Feb 2016 19:17:36 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 8BFBB180478; Tue, 16 Feb 2016 19:17:24 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7785 on Recommendations for Prefix Binding in the Context of Softwire Dual-Stack Lite
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160217031724.8BFBB180478@rfc-editor.org>
Date: Tue, 16 Feb 2016 19:17:24 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/0-qw2Kh2l70v6PlylF1G9KUGfI4>
Cc: 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: <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: Wed, 17 Feb 2016 03:17:37 -0000

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

        
        RFC 7785

        Title:      Recommendations for Prefix Binding in 
                    the Context of Softwire Dual-Stack Lite 
        Author:     S. Vinapamula, 
                    M. Boucadair
        Status:     Informational
        Stream:     Independent
        Date:       February 2016
        Mailbox:    sureshk@juniper.net, 
                    mohamed.boucadair@orange.com
        Pages:      9
        Characters: 20529
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-vinapamula-softwire-dslite-prefix-binding-12.txt

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

        DOI:        http://dx.doi.org/10.17487/RFC7785

This document discusses issues induced by the change of the Dual-
Stack Lite (DS-Lite) Basic Bridging BroadBand (B4) IPv6 address and
sketches a set of recommendations to solve those issues.


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