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

<chopps@chopps.org> Fri, 04 March 2016 22:54 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 558DD1A92E7 for <isis-wg@ietfa.amsl.com>; Fri, 4 Mar 2016 14:54:10 -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 BHtxKTn8-gQI for <isis-wg@ietfa.amsl.com>; Fri, 4 Mar 2016 14:54:09 -0800 (PST)
Received: from smtp.chopps.org (smtp.chopps.org [54.88.81.56]) by ietfa.amsl.com (Postfix) with ESMTP id F38701A92E5 for <isis-wg@ietf.org>; Fri, 4 Mar 2016 14:54:08 -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 BAAB760914; Fri, 4 Mar 2016 22:54:07 +0000 (UTC)
References: <87mvqncny2.fsf@tops.chopps.org> <E881D2D5-D9C1-4702-9A48-9D6A162C48EA@chopps.org> <20160228210405215520.c4a664fd@sniff.de> <87y4a3lf8u.fsf@tops.chopps.org> <F6C28B32DA084644BB6C8D0BD65B669DBCDD55@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: <F6C28B32DA084644BB6C8D0BD65B669DBCDD55@NKGEML515-MBX.china.huawei.com>
Date: Fri, 04 Mar 2016 17:54:06 -0500
Message-ID: <87lh5xg8hd.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/f1cpflrV4pB8g7sWV-I7biEdNd8>
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:54:10 -0000

Youjianjie <youjianjie@huawei.com> writes:

> Hi Chris,
>> I agree if moving forward with this I think we need to look at GENAPP as well..
>>
>> Firs though I'd like to hear more on why intra-domain flowspec (or the
>> equivalent) can't simply be defined using a yang model.
>
> Do you mean disseminating FlowSpec rules by using I2RS? I think it could be an alternative. But They each have their pros and cons. If using routing protocol to disseminate FlowSpec rules, when networks change, FlowSpec rules could be flexible as route entries, i.e. without involvement of management devices.


I mean one would use netconf (or restconf, ...) and flowspec yang model to
configure ones routers with the flowspec data.

Can you explain more what you mean when talking about network changes?
The flowspec entries aren't changing when network changes occur.
If the originator changes them it knows it needs to configure the new
entries on the routers.

Again, this proposal just looks like configuring ones routers using a
routing protocol. If that's what we are doing I'd like it to be more
clearly understood, and then we can decide if this is what we think
routing protocols should be doing. :)

Thanks,
Chris.

>
> Thanks,
> Jianjie
>
>> Thanks,
>> Chris.