IETF Logo Mail Archive

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

Lanlan Pan <abbypan@gmail.com> Wed, 13 December 2017 10:25 UTC

Return-Path: <abbypan@gmail.com>
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 B61E3126BF0 for <dnsop@ietfa.amsl.com>; Wed, 13 Dec 2017 02:25:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 WPPZIf0qaFbF for <dnsop@ietfa.amsl.com>; Wed, 13 Dec 2017 02:25:32 -0800 (PST)
Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (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 4F9A7126B7F for <dnsop@ietf.org>; Wed, 13 Dec 2017 02:25:32 -0800 (PST)
Received: by mail-wm0-x229.google.com with SMTP id t8so3926521wmc.3 for <dnsop@ietf.org>; Wed, 13 Dec 2017 02:25:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=k/1f0Rsg3pqV+ZN0oIGi0f48IgQqfgXv7XoX/RbihH0=; b=rZHVYdt4SsMuuK1dH2wgwKnNGQ/YcnVJthURXouX3qVLs6ACmzRRs4wL0EsVbVbbMa lkERXWr69bCmL1Aeelc/0O+NpglOflMzADrL6l0ocAPaVO7+4j249Wwp9W7yqHzEL2Zv 76b8McyVcEZYkoFBWLG7H3Dv9yOufpCB4V+cMk1maM/cup9/f1KyOEARgO43lHdOf3Cn H37PZR+gjztwTR7uyJj0hKjqVJziMZfMckaX6p7MM0TTmu5/VnDLRhg3CWbMM7QuuwZr vJIugSXns9qgHjrI2E5ivhFneHxAr8H+y3+NlbSIjfvZ85cNRSzxpGr31de8M9HaKZWa 4Bqg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=k/1f0Rsg3pqV+ZN0oIGi0f48IgQqfgXv7XoX/RbihH0=; b=rV/6P+lCNFXzNPYkme8othNZZK88GIZeRixLML8EEs+Zj7GR/DzBqmdkl2YeOJoM4k dAR2MvHbYN9cfbOLXCxhhHrY3H2FjIC+T2m2gvsll38j2i7Ta3wYLrCqljzdRLZJysQW Or63jT7KHnKYNEIniA0TVb5cX0O/7IcF6NfS1CNgdRhxsULGKEpAG7OkFfyeqqBaxocm BbcitNqoUedTQQNXPXqQZM5oK4tNVCaqu1NjbERpnuox4Qj9jE4EYBHCULmahF5iJfHj WZAR9fJ4jB5qisAbx7+5NjFVjzCmQXnLKQxlTQKK00wTHLevhFCX1ehlY2RrXGG+hIR3 P22w==
X-Gm-Message-State: AKGB3mIlKF4wxgepkBRwvWtikvlaQs7eJV+Gepg4o3e/MN9G7UGy0gRn YMi0+NOsNL4mYHxMH/Z2PWPf5rJ0fWPT69NiUWs=
X-Google-Smtp-Source: ACJfBou18k1pyq/XKE4sA13VKZOWtNqJYch7eFqYZZJI8tb6cvIUSPWCd6/3cI+0/u6F1LTqkLrGexZchkYfaPNtH3c=
X-Received: by 10.80.169.115 with SMTP id m48mr7017809edc.118.1513160730839; Wed, 13 Dec 2017 02:25:30 -0800 (PST)
MIME-Version: 1.0
References: <2017121315404971736813@cnnic.cn> <20171213081823.GA8970@laperouse.bortzmeyer.org> <20171213084342.GA30523@server.ds9a.nl> <201712131731058457451@cnnic.cn> <20171213095533.tpd52wo6xy7v6qct@sources.org>
In-Reply-To: <20171213095533.tpd52wo6xy7v6qct@sources.org>
From: Lanlan Pan <abbypan@gmail.com>
Date: Wed, 13 Dec 2017 10:25:20 +0000
Message-ID: <CANLjSvXOjaQ2wm9F9y51FSuaWtmnV6E=156uvWbLyeh9LcP1OQ@mail.gmail.com>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Cc: "zuopeng@cnnic.cn" <zuopeng@cnnic.cn>, dnsop <dnsop@ietf.org>, bert hubert <bert.hubert@powerdns.com>
Content-Type: multipart/alternative; boundary="94eb2c0de3b2d98e250560362fed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/CS-F0QAP6c7xFPl6Vfktp1F06h8>
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 10:25:34 -0000

Stephane Bortzmeyer <bortzmeyer@nic.fr>于2017年12月13日周三 下午5:58写道：

> On Wed, Dec 13, 2017 at 05:31:06PM +0800,
>  zuopeng@cnnic.cn <zuopeng@cnnic.cn> wrote
>  a message of 130 lines which said:
>
> > (2) RFC2782 requires browser's support;
>
> Client support. This is even worse, there are much more HTTP clients
> than browsers.
>
> >     Using this method, a browser has no idea about weighted AX/AAAAXs.
> >     It requires no change of browsers.
>
> But it requires change in all resolvers. One may wonder which will be
> the fastest path.
>
something like ANAME ?
ANAME can let resolvers choose IP for clients.

>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>
-- 
致礼  Best Regards

潘蓝兰  Pan Lanlan

v2.35.0 | Report a Bug | By Email | System Status