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

Robert Edmonds <edmonds@mycre.ws> Fri, 15 December 2017 19:32 UTC

Return-Path: <edmonds@mycre.ws>
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 128A3126E3A for <dnsop@ietfa.amsl.com>; Fri, 15 Dec 2017 11:32:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 cLPd6DUL20pM for <dnsop@ietfa.amsl.com>; Fri, 15 Dec 2017 11:32:10 -0800 (PST)
Received: from mycre.ws (mycre.ws [45.33.102.105]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A9770126DCA for <dnsop@ietf.org>; Fri, 15 Dec 2017 11:32:10 -0800 (PST)
Received: by chase.mycre.ws (Postfix, from userid 1000) id 953D712C1CFE; Fri, 15 Dec 2017 14:32:09 -0500 (EST)
Date: Fri, 15 Dec 2017 14:32:09 -0500
From: Robert Edmonds <edmonds@mycre.ws>
To: 左鹏 <zuopeng@cnnic.cn>
Cc: dnsop <dnsop@ietf.org>, bert hubert <bert.hubert@powerdns.com>
Message-ID: <20171215193209.jmt55sltyodjricx@mycre.ws>
References: <2017121315404971736813@cnnic.cn> <20171213081823.GA8970@laperouse.bortzmeyer.org> <20171213084342.GA30523@server.ds9a.nl> <201712131736325755287@cnnic.cn> <20171213095015.GC30523@server.ds9a.nl> <20171214214056.r37cz5rbmpxwjw3q@mycre.ws> <3519c0a3.328f.1605941fa4b.Coremail.zuopeng@cnnic.cn>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <3519c0a3.328f.1605941fa4b.Coremail.zuopeng@cnnic.cn>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/y31yrUxC0ZAszPrVCsuhB-BUjgg>
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: Fri, 15 Dec 2017 19:32:12 -0000

左鹏 wrote:
> The "precise traffice scheduling" i mentioned is not only for performance reason, but also for capacity reason.

CDNs already have the ability to do precise traffic scheduling for both
performance and capacity reasons, using the existing capabilities built
into the DNS.

> yes, more resolvers are good to improve user experience.
> but also maybe we should notice each CDN node has different capacity.(it is the real in practice).
> a "weight-aware" rosolver can schedule clients to diffent nodes according to weight pricisely.
> or shall we do something only for authoritative server like defining the weighted A/AAAAx? 

No, the DNS's existing capabilities provide more than enough power for
CDNs for these use cases.

> btw, any comments on the weightd CNAMEXs for multi-CDN? :)

I don't have any direct experience of the multi-CDN use case. I would
think the intra-CDN case for CDN node selection can be generalized to
the multi-CDN case for CDN provider selection, though you probably have
fewer owner names to work with.

-- 
Robert Edmonds