Regarding draft-li-6man-service-aware-ipv6-network-00

Lizhenbin <lizhenbin@huawei.com> Mon, 18 March 2019 17:12 UTC

Return-Path: <lizhenbin@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 875A31279E6 for <ipv6@ietfa.amsl.com>; Mon, 18 Mar 2019 10:12:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 Qrp5vuOTGVfl for <ipv6@ietfa.amsl.com>; Mon, 18 Mar 2019 10:12:24 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2CF5C1200D8 for <ipv6@ietf.org>; Mon, 18 Mar 2019 10:12:24 -0700 (PDT)
Received: from lhreml707-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id DFD42FCD3FBF079FFE6C for <ipv6@ietf.org>; Mon, 18 Mar 2019 17:12:21 +0000 (GMT)
Received: from DGGEMM423-HUB.china.huawei.com (10.1.198.40) by lhreml707-cah.china.huawei.com (10.201.108.48) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 18 Mar 2019 17:12:21 +0000
Received: from DGGEMM512-MBX.china.huawei.com ([169.254.3.122]) by dggemm423-hub.china.huawei.com ([10.1.198.40]) with mapi id 14.03.0415.000; Tue, 19 Mar 2019 01:12:16 +0800
From: Lizhenbin <lizhenbin@huawei.com>
To: "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Regarding draft-li-6man-service-aware-ipv6-network-00
Thread-Topic: Regarding draft-li-6man-service-aware-ipv6-network-00
Thread-Index: AQHU3a28Xjkfy85WEEGIYxAm7HmFuw==
Date: Mon, 18 Mar 2019 17:12:15 +0000
Message-ID: <5A5B4DE12C0DAC44AF501CD9A2B01A8D8F56D629@dggemm512-mbx.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.45.104.117]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/-Cp3kDSoTKG1AX2e_McpXxL3nyk>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Mar 2019 17:12:26 -0000

Hi Folks,
Currently applications are developed very fast which are carried over the network and have
varying needs for network bandwidth, latency, jitter, and packet loss, etc. However, since 
the current network is lack of enough information of service requirements of such applications 
it is difficult to guarantee the SLA or it may take long time to provide such guarantee.  In order
to solve these these challenges, the draft proposes the solution to take use of IPv6 extensions 
header to convey the service requirement information along with the packet to the network and
accordingly the flow-driven method is adopted to facilitate the service deployment and network 
resource adjustment to guarantee SLA for applications. It defines the Service-aware IPv6 ID to 
identify the possible service/application/user and Service-Para Option is defined to convey the 
related service parameters.

Comments and suggestions are welcome!


Best Regards,
Zhenbin (Robin)






________________________________________
发件人: internet-drafts@ietf.org [internet-drafts@ietf.org]
发送时间: 2019年3月12日 0:46
收件人: Pengshuping (Peng Shuping); Lizhenbin
主题: New Version Notification for draft-li-6man-service-aware-ipv6-network-00.txt

A new version of I-D, draft-li-6man-service-aware-ipv6-network-00.txt
has been successfully submitted by Zhenbin Li and posted to the
IETF repository.

Name:           draft-li-6man-service-aware-ipv6-network
Revision:       00
Title:          Service-aware IPv6 Network
Document date:  2019-03-11
Group:          Individual Submission
Pages:          12
URL:            https://www.ietf.org/internet-drafts/draft-li-6man-service-aware-ipv6-network-00.txt
Status:         https://datatracker.ietf.org/doc/draft-li-6man-service-aware-ipv6-network/
Htmlized:       https://tools.ietf.org/html/draft-li-6man-service-aware-ipv6-network-00
Htmlized:       https://datatracker.ietf.org/doc/html/draft-li-6man-service-aware-ipv6-network


Abstract:
   A multitude of applications are carried over the network, which have
   varying needs for network bandwidth, latency, jitter, and packet
   loss, etc.  Some applications such as online gaming and live video
   streaming have very demanding network requirements thereof require
   special treatments in the network.  However, since the current
   network is lack of enough information of service requirements of such
   applications it is difficult to guarantee the SLA or it may take long
   time to provide such guarantee.  This document proposes the solution
   to make use of IPv6 extensions header to convey the service
   requirement information along with the packet to the network to
   facilitate the service deployment and network resource adjustment to
   guarantee SLA for applications.  Then it defines the service-aware
   options which can be used in the different IPv6 extension headers for
   the purpose.





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