
From nobody Thu Oct  1 06:01:53 2015
Return-Path: <cuiyong@tsinghua.edu.cn>
X-Original-To: storagesync@ietfa.amsl.com
Delivered-To: storagesync@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE5C61B2C95 for <storagesync@ietfa.amsl.com>; Thu,  1 Oct 2015 06:01:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level: 
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 3Orc1ODbNCzS for <storagesync@ietfa.amsl.com>; Thu,  1 Oct 2015 06:01:50 -0700 (PDT)
Received: from tsinghua.edu.cn (smtp07.tsinghua.edu.cn [166.111.204.36]) by ietfa.amsl.com (Postfix) with ESMTP id 9FE841B2C8C for <storagesync@ietf.org>; Thu,  1 Oct 2015 06:01:49 -0700 (PDT)
Received: from [192.168.0.123] (unknown [123.118.20.177]) by app4 (Coremail) with SMTP id DcxvpgCniSK0Lg1WsX8FAQ--.32501S3; Thu, 01 Oct 2015 21:01:41 +0800 (CST)
From: Yong Cui <cuiyong@tsinghua.edu.cn>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Thu, 1 Oct 2015 21:01:40 +0800
Message-Id: <850CEC66-9592-4BF4-8B92-8297CE3050B4@tsinghua.edu.cn>
To: storagesync@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
X-CM-TRANSID: DcxvpgCniSK0Lg1WsX8FAQ--.32501S3
X-Coremail-Antispam: 1UD129KBjvdXoW7Gr47uF1xXF1xWw1rZFW5Wrg_yoWDKFb_AF y8W3s0g3yv9F4UJw47CFs7ArZ8Xayvga40yw18XFW5tas2vws5ArnrGr9I93WxXF4fGrs8 WrsI9ryftwn09jkaLaAFLSUrUUUUUb8apTn2vfkv8UJUUUU8Yxn0WfASr-VFAUDa7-sFnT 9fnUUIcSsGvfJTRUUUb08FF20E14v26r1j6r4UM7CY07I20VC2zVCF04k26cxKx2IYs7xG 6rWj6s0DM7CIcVAFz4kK6r1j6r18M28lY4IEw2IIxxk0rwA2z4x0Y4vE2Ix0cI8IcVAFwI 0_Xr0_Ar1l84ACjcxK6xIIjxv20xvEc7CjxVAFwI0_Gr0_Cr1l84ACjcxK6I8E87Iv67AK xVW0oVCq3wA2z4x0Y4vEx4A2jsIEc7CjxVAFwI0_GcCE3s1le2I262IYc4CY6c8Ij28IcV AaY2xG8wAqx4xG64xvF2IEw4CE5I8CrVC2j2WlYx0E2Ix0cI8IcVAFwI0_Jr0_Jr4lYx0E x4A2jsIE14v26r1j6r4UMcvjeVCFs4IE7xkEbVWUJVW8JwACjcxG0xvY0x0EwIxGrwACjI 8F5VA0II8E6IAqYI8I648v4I1l42xK82IYc2Ij64vIr41lx2IqxVAqx4xG67AKxVWUJVWU GwC20s026x8GjcxK67AKxVWUGVWUWwC2zVAF1VAY17CE14v26r1Y6r17MIIYrxkI7VAKI4 8JMIIF0xvE2Ix0cI8IcVAFwI0_Jr0_JF4lIxAIcVC0I7IYx2IY6xkF7I0E14v26r1j6r4U MIIF0xvE42xK8VAvwI8IcIk0rVWrJr0_WFyUJwCI42IY6I8E87Iv67AKxVWUJVW8JwCI42 IY6I8E87Iv6xkF7I0E14v26r1j6r4UYxBIdaVFxhVjvjDU0xZFpf9x0UUjRWDUUUUU=
X-CM-SenderInfo: 5fxl50tqj632xlqjx3vdohv3gofq/
Archived-At: <http://mailarchive.ietf.org/arch/msg/storagesync/fvTDcCLUFqAbJs-1OYNf-lPjEvY>
Cc: =?utf-8?Q?Cui_=E5=B4=94=E5=8B=87?= <cuiyong@tsinghua.edu.cn>
Subject: [Storagesync] New version of "Internet Storage Sync: Problem Statement"
X-BeenThere: storagesync@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mechanisms to synchronize client file systems with Internet-based data storage services <storagesync.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/storagesync>, <mailto:storagesync-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/storagesync/>
List-Post: <mailto:storagesync@ietf.org>
List-Help: <mailto:storagesync-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/storagesync>, <mailto:storagesync-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Oct 2015 13:01:52 -0000

Dear all,

We've updated the draft, Internet Storage Sync: Problem Statement.

https://datatracker.ietf.org/doc/draft-cui-iss-problem/


Abstract:
   Internet storage services have become more and more popular.  They
   attract a huge number of users and produce a significant share of
   Internet traffic.  Most existing Internet storage services make use
   of proprietary sync protocols with different capabilities to achieve
   the data sync.  However, a single Internet storage service using its
   proprietary sync protocols has intrinsic limitations on service
   usability and network performance.  This document outlines the
   related problems caused by using proprietary sync protocols and
   missing key capabilities.  It also shows a demand for designing a
   standard sync protocol to achieve better usability and sync
   performance.

Compared to the earlier versions, this version emphasizes the very 
different protocol capabilities that different commercial services 
support, and also the understanding of sync protocol.

You are welcome to comment!

Thanks,

Yong

