Re: [Idr] WG Adoption call for draft-hao-idr-flowspec-evpn (1/19/2015 to 2/2/2015
"Smith, Donald" <Donald.Smith@CenturyLink.com> Tue, 20 January 2015 15:23 UTC
Return-Path: <Donald.Smith@CenturyLink.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9704D1B2DC7 for <idr@ietfa.amsl.com>; Tue, 20 Jan 2015 07:23:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.55
X-Spam-Level:
X-Spam-Status: No, score=0.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_CHARSET_FARAWAY=2.45] autolearn=ham
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 8dLhJAm3jzJG for <idr@ietfa.amsl.com>; Tue, 20 Jan 2015 07:23:45 -0800 (PST)
Received: from suomp64i.qwest.com (suomp64i.qwest.com [155.70.16.237]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 32F4A1B2DC4 for <idr@ietf.org>; Tue, 20 Jan 2015 07:23:45 -0800 (PST)
Received: from lxdenvmpc030.qintra.com (lxdenvmpc030.qintra.com [10.1.51.30]) by suomp64i.qwest.com (8.14.4/8.14.4) with ESMTP id t0KFNSQt019290 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 Jan 2015 09:23:28 -0600 (CST)
Received: from lxdenvmpc030.qintra.com (unknown [127.0.0.1]) by IMSA (Postfix) with ESMTP id E9ED41E0064; Tue, 20 Jan 2015 08:23:22 -0700 (MST)
Received: from lxdnp31k.corp.intranet (unknown [151.119.91.93]) by lxdenvmpc030.qintra.com (Postfix) with ESMTP id CE9441E0061; Tue, 20 Jan 2015 08:23:22 -0700 (MST)
Received: from lxdnp31k.corp.intranet (localhost [127.0.0.1]) by lxdnp31k.corp.intranet (8.14.8/8.14.8) with ESMTP id t0KFNMQl020298; Tue, 20 Jan 2015 08:23:22 -0700
Received: from vddcwhubex502.ctl.intranet (vddcwhubex502.ctl.intranet [151.119.128.29]) by lxdnp31k.corp.intranet (8.14.8/8.14.8) with ESMTP id t0KFNM4I020294 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 20 Jan 2015 08:23:22 -0700
Received: from PDDCWMBXEX503.ctl.intranet ([fe80::9033:ef22:df02:32a9]) by vddcwhubex502.ctl.intranet ([2002:9777:801d::9777:801d]) with mapi id 14.03.0195.001; Tue, 20 Jan 2015 08:23:22 -0700
From: "Smith, Donald" <Donald.Smith@CenturyLink.com>
To: Zhuangshunwan <zhuangshunwan@huawei.com>, 'Susan Hares' <shares@ndzh.com>, 'idr wg' <idr@ietf.org>
Thread-Topic: [Idr] WG Adoption call for draft-hao-idr-flowspec-evpn (1/19/2015 to 2/2/2015
Thread-Index: AdA0BQzsQKwqq1HRQreIR6xvWbabDgAe9n2gABBQaxM=
Date: Tue, 20 Jan 2015 15:23:21 +0000
Message-ID: <68EFACB32CF4464298EA2779B058889D24C85828@PDDCWMBXEX503.ctl.intranet>
References: <04fa01d03405$483d92a0$d8b8b7e0$@ndzh.com>, <000d01d03481$afed1480$0fc73d80$@com>
In-Reply-To: <000d01d03481$afed1480$0fc73d80$@com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [151.119.128.7]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/idr/lrvRng05guxaKgKkFcIU2_-8RlE>
Cc: "draft-hao-idr-flowspec-evpn.all@tools.ietf.org" <draft-hao-idr-flowspec-evpn.all@tools.ietf.org>, "'John G. Scudder'" <jgs@bgp.nu>
Subject: Re: [Idr] WG Adoption call for draft-hao-idr-flowspec-evpn (1/19/2015 to 2/2/2015
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jan 2015 15:23:50 -0000
So far all the "support" responses re from Huawei ( single vendor support) engineers. When will the intended status be decided? Intended RFC status:Unknown The draft itself at first review appears to be pretty good. I didn't see any large technical issues with it (yet:) I am considering how an ISP would use this or if they would. "Please comment on the usefulness of the draft in deployments and on the technical pros/cons of the draft." so I look forward to use cases or other descriptions of how/when people would use this. I think the security considerations should probably match what other flow-spec drafts have said. Currently it is very weak and probably inaccurate. I will withhold support for now. But also don't object to adoption by this wg! (coffee != sleep) & (!coffee == sleep) Donald.Smith@centurylink.com From: Idr [idr-bounces@ietf.org] on behalf of Zhuangshunwan [zhuangshunwan@huawei.com] Sent: Tuesday, January 20, 2015 12:21 AM To: 'Susan Hares'; 'idr wg' Cc: 'John G. Scudder' Subject: Re: [Idr] WG Adoption call for draft-hao-idr-flowspec-evpn (1/19/2015 to 2/2/2015 Support as co-author and not aware any IPR regarding this document. Thanks, Shunwan 发件人: Idr [mailto:idr-bounces@ietf.org] 代表 Susan Hares 发送时间: 2015年1月20日 0:31 收件人: idr wg 抄送: 'John G. Scudder' 主题: [Idr] WG Adoption call for draft-hao-idr-flowspec-evpn (1/19/2015 to 2/2/2015 This is to begin a 2 week adoption call for draft-hao-idr-flowspec-evpn. Please comment on the usefulness of the draft in deployments and on the technical pros/cons of the draft. In your comments please include: “support” or “no support” indicate. Authors should indicate if any IPR exists for this draft. The draft can be found at: http://datatracker.ietf.org/doc/draft-hao-idr-flowspec-evpn Sue Hares This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.
- [Idr] WG Adoption call for draft-hao-idr-flowspec… Susan Hares
- [Idr] FW: WG Adoption call for draft-hao-idr-flow… stephane.litkowski
- Re: [Idr] FW: WG Adoption call for draft-hao-idr-… UTTARO, JAMES
- Re: [Idr] WG Adoption call for draft-hao-idr-flow… Lucy yong
- Re: [Idr] WG Adoption call for draft-hao-idr-flow… Mach Chen
- Re: [Idr] WG Adoption call for draft-hao-idr-flow… Dongjie (Jimmy)
- Re: [Idr] WG Adoption call for draft-hao-idr-flow… Xuxiaohu
- Re: [Idr] WG Adoption call for draft-hao-idr-flow… Zhuangshunwan
- Re: [Idr] WG Adoption call for draft-hao-idr-flow… Smith, Donald
- Re: [Idr] WG Adoption call for draft-hao-idr-flow… Susan Hares
- Re: [Idr] WG Adoption call for draft-hao-idr-flow… Haoweiguo
- Re: [Idr] WG Adoption call for draft-hao-idr-flow… Liangqiandeng
- Re: [Idr] WG Adoption call for draft-hao-idr-flow… Smith, Donald
- Re: [Idr] WG Adoption call for draft-hao-idr-flow… Haoweiguo
- Re: [Idr] WG Adoption call for draft-hao-idr-flow… Haoweiguo
- Re: [Idr] WG Adoption call for draft-hao-idr-flow… Jeffrey Haas
- Re: [Idr] WG Adoption call for draft-hao-idr-flow… Haoweiguo