Subject: [v6ops] FW: New Version Notification for draft-xu-v6ops-dslite-redundancy-00.txt

From: "Yu Fu" <[email-masked]>
Date: Tue, 20 Oct 2015 09:53:43 +0800

Hi All,

As the exhaustion of the public IPv4 address, service providers have deployed DS-Lite in their network widely in nowadays, where a large number of customers are located. These customers within a network which is served by a single CGN function embedded in AFTR element may experience service degradation due to the presence of the single point of failure or loss of state information. Therefore, redundancy capabilities of the AFTR devices are strongly desired in order to deliver highly available services to customers.  Failure detection and repair time should be therefore shortened.
Therefore, we have submitted a new draft to describe a redundancy mechanism for DS-Lite. Comments are very appreciated. 
Thanks.

Cheers
Yu

-----Original Message-----
From: [email-masked] [mailto:[email-masked]] 
Sent: Monday, October 19, 2015 10:37 PM
To: Honglei Xu; Xiaodong Lee; Qiong Sun; Qiong Sun; Yu Fu; XiaoDong Lee; Yu Fu; Honglei Xu
Subject: New Version Notification for draft-xu-v6ops-dslite-redundancy-00.txt

A new version of I-D, draft-xu-v6ops-dslite-redundancy-00.txt
has been successfully submitted by Yu Fu and posted to the IETF repository.

Name:		draft-xu-v6ops-dslite-redundancy
Revision:	00
Title:		A Redundancy Mechanism for Dual-Stack Lite
Document date:	2015-10-19
Group:		Individual Submission
Pages:		10
URL:            https://www.ietf.org/internet-drafts/draft-xu-v6ops-dslite-redundancy-00.txt
Status:         https://datatracker.ietf.org/doc/draft-xu-v6ops-dslite-redundancy/
Htmlized:       https://tools.ietf.org/html/draft-xu-v6ops-dslite-redundancy-00

Abstract:
   Dual-Stack Lite is a solution to offer both IPv4 and IPv6
   connectivity to customers that are addressed only with an IPv6
   prefix.  This document provide a redundancy mechanism for Dual-Stack
   Lite.

Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat