IETF Logo Mail Archive

Re: [Isis-wg] 答复: Call for WG Adoption for draft-you-isis-flowspec-extensions-04

<chopps@chopps.org> Fri, 04 March 2016 22:58 UTC

Return-Path: <chopps@chopps.org>
X-Original-To: isis-wg@ietfa.amsl.com
Delivered-To: isis-wg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CC371A930A for <isis-wg@ietfa.amsl.com>; Fri, 4 Mar 2016 14:58:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.601
X-Spam-Level:
X-Spam-Status: No, score=-1.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.001] autolearn=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 eZOwV6DUXrX8 for <isis-wg@ietfa.amsl.com>; Fri, 4 Mar 2016 14:58:22 -0800 (PST)
Received: from smtp.chopps.org (smtp.chopps.org [54.88.81.56]) by ietfa.amsl.com (Postfix) with ESMTP id 902731A92F4 for <isis-wg@ietf.org>; Fri, 4 Mar 2016 14:58:18 -0800 (PST)
Received: from tops.chopps.org (24-247-68-31.dhcp.trcy.mi.charter.com [24.247.68.31]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by smtp.chopps.org (Postfix) with ESMTPSA id DBC0460914; Fri, 4 Mar 2016 22:58:17 +0000 (UTC)
References: <87mvqncny2.fsf@tops.chopps.org> <E881D2D5-D9C1-4702-9A48-9D6A162C48EA@chopps.org> <20160228210405215520.c4a664fd@sniff.de> <87y4a3lf8u.fsf@tops.chopps.org> <CAG4d1rd+q1+cBrvg2zD611PjZFS0xnGNetGT8PNGB4nyQtSXcg@mail.gmail.com> <F6C28B32DA084644BB6C8D0BD65B669DBCDDC3@NKGEML515-MBX.china.huawei.com>
User-agent: mu4e 0.9.17; emacs 24.5.1
From: chopps@chopps.org
To: Youjianjie <youjianjie@huawei.com>
In-reply-to: <F6C28B32DA084644BB6C8D0BD65B669DBCDDC3@NKGEML515-MBX.china.huawei.com>
Date: Fri, 04 Mar 2016 17:58:16 -0500
Message-ID: <87k2lhg8af.fsf@tops.chopps.org>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Archived-At: <http://mailarchive.ietf.org/arch/msg/isis-wg/IeT6tgn4kUDpvYaSKS98wYJomrI>
Cc: Marc Binderberger <marc@sniff.de>, "isis-wg@ietf.org" <isis-wg@ietf.org>
Subject: Re: [Isis-wg] 答复: Call for WG Adoption for draft-you-isis-flowspec-extensions-04
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/isis-wg/>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Mar 2016 22:58:23 -0000

Youjianjie <youjianjie@huawei.com> writes:

> Hi Alia, Chris,
>
> A Yang model based FlowSpec: https://tools.ietf.org/html/draft-wu-idr-flowspec-yang-cfg-02
> Is this the draft that you may refer to? I think we still need to adapt it to IS-IS protocol if using Yang model?
> The Yang model based FlowSpec does have some application scenarios, such as inject FlowSpec rules into specified routers by management system. In this document, we think FlowSpec is more like a n-tuple route. So we extend IS-IS.

But why should we think of flowspec as an N-tuple route?

Thanks,
Chris.

>
> Thanks,
> Jianjie

v2.23.0 | Report a Bug | By Email