Re: [DNSOP] Ask for advice of 3 new RRs for precise traffic scheduling

Stephane Bortzmeyer <bortzmeyer@nic.fr> Wed, 13 December 2017 08:18 UTC

Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55EEF124B17 for <dnsop@ietfa.amsl.com>; Wed, 13 Dec 2017 00:18:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 pABYep8ri5Vg for <dnsop@ietfa.amsl.com>; Wed, 13 Dec 2017 00:18:36 -0800 (PST)
Received: from mail.bortzmeyer.org (aetius.bortzmeyer.org [IPv6:2001:4b98:dc0:41:216:3eff:fece:1902]) (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 44BB31241FC for <dnsop@ietf.org>; Wed, 13 Dec 2017 00:18:36 -0800 (PST)
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id 955EB31CBA; Wed, 13 Dec 2017 09:18:33 +0100 (CET)
Received: by godin (Postfix, from userid 1000) id B10DAEC0B81; Wed, 13 Dec 2017 09:18:23 +0100 (CET)
Date: Wed, 13 Dec 2017 09:18:23 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: "zuopeng@cnnic.cn" <zuopeng@cnnic.cn>
Cc: dnsop <dnsop@ietf.org>
Message-ID: <20171213081823.GA8970@laperouse.bortzmeyer.org>
References: <2017121315404971736813@cnnic.cn>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <2017121315404971736813@cnnic.cn>
X-Transport: UUCP rules
X-Operating-System: Ubuntu 16.04 (xenial)
X-Charlie: Je suis Charlie
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/cemTBkDFwbvMvGk-LwGasXBYbjw>
Subject: Re: [DNSOP] Ask for advice of 3 new RRs for precise traffic scheduling
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Dec 2017 08:18:38 -0000

On Wed, Dec 13, 2017 at 03:40:50PM +0800,
 zuopeng@cnnic.cn <zuopeng@cnnic.cn> wrote 
 a message of 1343 lines which said:

>  For example, a CDN provider can’t schedule 70% of traffic to node A
>  and 30% of traffic to node B [...] adding a “weight” attribute

First, the obvious question: why reinventing RFC 2782?