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

Brian E Carpenter <brian.e.carpenter@gmail.com> Sat, 30 March 2019 21:13 UTC

Return-Path: <brian.e.carpenter@gmail.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 B25C11202AE for <ipv6@ietfa.amsl.com>; Sat, 30 Mar 2019 14:13:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 L206pYclGCyD for <ipv6@ietfa.amsl.com>; Sat, 30 Mar 2019 14:13:37 -0700 (PDT)
Received: from mail-pl1-x62b.google.com (mail-pl1-x62b.google.com [IPv6:2607:f8b0:4864:20::62b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2FFD01202F4 for <ipv6@ietf.org>; Sat, 30 Mar 2019 14:13:37 -0700 (PDT)
Received: by mail-pl1-x62b.google.com with SMTP id y6so2626466plt.1 for <ipv6@ietf.org>; Sat, 30 Mar 2019 14:13:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:cc:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=GvdCFVc1JyHR7Bw8pO7AQh02n0EnbKEWqzpGnH9/4e4=; b=Ju6qpnvDUjoS+bphK35Vt5yjPpH8qNvHFFdw7ROM7+7y3sNLgTK63dP5WN6v91B+aW pAbkNkdMzZcoQeFIGlRjNgxslKhvKrn/wn7HplhRHMG7NY00czL4NK5fPNvBpcX/gAUs Ehqc9O36m2yO6Y+TVcQiNu/RjyFoJJNVvlwM4kz5IOejK6WS6vTuF7xF61JIBa68O/qx 7I+OmPzekiY0jgvw8Zu8MvmH5XzLpSmXdFkRz6lh26jW30ac/8zpocwK8dSelKQNWPD1 CGL+bvfSmNWZdYXBtxofsaNfrpene7TusQmW66WJuY4+aB8HVul9g+eVKj6e5tXkC29H /j6w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:cc:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=GvdCFVc1JyHR7Bw8pO7AQh02n0EnbKEWqzpGnH9/4e4=; b=bt53xYS3MXFS4mpDELyzDIMZDI653tf7/mZW91q9Bo0yEE8hHWB1gqqanQJy7EeDin ZcSBiEChpOgu/7deJCU6YL0uAyYwmB9TLgcUlN4Yqa9Y3sQVDcoiZDgtQXN3pDeAWT8V qG/uNwxZLVPynRCogkyZ6g7WE9qsYTyl+9p4CtbvM0auJ6Uh+qbJ/7SxAQmFWArXiZhY pMAejEtI7v2Q6l5LNtuzuDhgNE2MJ+O4HVHgq+8TQgMsqAVbGRyYnnhgXROBk94Tw+Um OcD7Ad9d+CF871MuUDvget9VgCo2ciPbdQ9SL/ACNdaPIbkNSkr68W5kko+/BHWZ3i/s mMNQ==
X-Gm-Message-State: APjAAAUcykxO1Liz4GbgOhv+9Mk8O4Piy49REvtf6y5/RHbJpt/eMPgf Z+JBUo0Yr1D7wegYYotsR41isouj
X-Google-Smtp-Source: APXvYqyWPJu7H1yIIOzTFZ6yFKDqom0vwelqKyRx5kCzOVbkveq7/4/AwVfpdEvInh0JCeJpjP/LcQ==
X-Received: by 2002:a17:902:a81:: with SMTP id 1mr56432809plp.308.1553980416400; Sat, 30 Mar 2019 14:13:36 -0700 (PDT)
Received: from [192.168.178.30] ([118.148.72.95]) by smtp.gmail.com with ESMTPSA id h65sm17489334pfd.108.2019.03.30.14.13.34 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 30 Mar 2019 14:13:35 -0700 (PDT)
Subject: Re: Regarding draft-li-6man-service-aware-ipv6-network-00
To: Lizhenbin <lizhenbin@huawei.com>
References: <5A5B4DE12C0DAC44AF501CD9A2B01A8D8F56D629@dggemm512-mbx.china.huawei.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
Message-ID: <54735b79-0faa-6e12-35f6-cd76de4fcca6@gmail.com>
Date: Sun, 31 Mar 2019 10:13:34 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <5A5B4DE12C0DAC44AF501CD9A2B01A8D8F56D629@dggemm512-mbx.china.huawei.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/WxSIq-TLaUVqrSZLme0HhoKsG8I>
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: Sat, 30 Mar 2019 21:13:40 -0000

Hi Zhenbin,

Thanks for your draft. I have a few general questions:

1. As you may know, it's been impossible to deploy new IPv4 options for operational reasons, and also very difficult to deploy new IPv6 extension headers or options. So my first question about your proposal is: what is the intended scope? Do you expect such options to be deployed locally or over the open Internet? (For some background on this question, see https://tools.ietf.org/html/draft-carpenter-limited-domains)

2. How does this proposal relate to the existing standard for network service headers (https://tools.ietf.org/html/rfc8300)?

3. How does ths proposal relate to the existing standard for segment routing (https://tools.ietf.org/html/rfc8402) and the segment routing header (https://tools.ietf.org/html/draft-ietf-6man-segment-routing-header)?

4. How does this proposal relate to FAST tickets (https://tools.ietf.org/html/draft-herbert-fast-03)?

Regards
   Brian Carpenter

On 19-Mar-19 06:12, Lizhenbin wrote:
> 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
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>