Re: [OSPF] New Version Notification for draft-liang-ospf-flowspec-extensions-01.txt

"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> Thu, 09 October 2014 05:15 UTC

Return-Path: <ginsberg@cisco.com>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C36071A90C6; Wed, 8 Oct 2014 22:15:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.287
X-Spam-Level:
X-Spam-Status: No, score=-15.287 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 Zo2OLbrm3kDr; Wed, 8 Oct 2014 22:15:17 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 605831A90C1; Wed, 8 Oct 2014 22:15:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7916; q=dns/txt; s=iport; t=1412831718; x=1414041318; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=BR2/zSX7EtVbZHRe5I+YACwELAilFiYa7xBmVU+xYTM=; b=XnZP53FCc3oPU3JBWCHVyrzVEPPK7lDlIKyJFfn9ru9a2ds46G5H+a7k 2RIfvdsUvzaiO0DWGlhgMRo4dmwQlJ/Aq32HVhABk3jpM0fyORJ9qo84Q fiWyTxM2TqsTv0oonznj8gpYdavPg80cLTSHwYRTfPng/C5covT7n0nyT Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkYFALQYNlStJA2L/2dsb2JhbABfgmsjU00GBQSDAshaCodNAhltFgF7hAMBAQEEAQEBIBE4AggBAgwEAgEGAhEEAQEBAgIGHQMCAgIlCxQBCAgCBAENBQgBiDUBBwWUMJxNlEIBF4EsjmcWGwcGgnE2gR4BBJF3hD6IPjyDCY0bg3+BchgWgUNsAYFHgQIBAQE
X-IronPort-AV: E=Sophos;i="5.04,682,1406592000"; d="scan'208";a="361591473"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by rcdn-iport-1.cisco.com with ESMTP; 09 Oct 2014 05:15:16 +0000
Received: from xhc-rcd-x06.cisco.com (xhc-rcd-x06.cisco.com [173.37.183.80]) by alln-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id s995FFdu020241 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 9 Oct 2014 05:15:15 GMT
Received: from xmb-aln-x02.cisco.com ([fe80::8c1c:7b85:56de:ffd1]) by xhc-rcd-x06.cisco.com ([173.37.183.80]) with mapi id 14.03.0195.001; Thu, 9 Oct 2014 00:15:15 -0500
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "Acee Lindem (acee)" <acee@cisco.com>, "Peter Psenak (ppsenak)" <ppsenak@cisco.com>
Thread-Topic: [OSPF] New Version Notification for draft-liang-ospf-flowspec-extensions-01.txt
Thread-Index: AQHP2sRacNlB1LfkPUCKV4l1MfxdD5wX3ddwgA2jYQCAAOUi0IAAXj8AgAAFpQCAAH33wA==
Date: Thu, 9 Oct 2014 05:15:14 +0000
Message-ID: <F3ADE4747C9E124B89F0ED2180CC814F48532CFF@xmb-aln-x02.cisco.com>
References: <F6C28B32DA084644BB6C8D0BD65B669D11A0A9@nkgeml509-mbs.china.huawei.com> <63CB93BC589C1B4BAFDB41A0A19B7ACDF930C2@USIDCWVEMBX08.corp.global.level3.com> <54356344.3040806@cisco.com> <AD14FE00-F121-4551-9E84-4680562A5AFF@cisco.com>
In-Reply-To: <AD14FE00-F121-4551-9E84-4680562A5AFF@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.21.68.25]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ospf/Sfr5JXc-RigXQ92LLbtsk7Dz49s
Cc: "ospf@ietf.org" <ospf@ietf.org>, "isis-wg@ietf.org" <isis-wg@ietf.org>
Subject: Re: [OSPF] New Version Notification for draft-liang-ospf-flowspec-extensions-01.txt
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ospf/>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Oct 2014 05:15:20 -0000

Adding the IS-IS WG since there is an equivalent draft for IS-IS submitted by the same authors.

"IF" this were something the respective WGs decide the protocol should support, then running a separate instance of the protocol so that the flowspec  advertisements can be isolated from the primary function of the IGP (routing) would be the right way to implement it - and this is precisely what GENINFO/MI (RFC 6823/6822) were defined to address. OSPF Transport instance would be the analogous mechanism for OSPF.

But the first question is whether this is something the IGPs should support at all. As Acee has indicated this was proposed previously in OSPF and there was little interest. In the case of IS-IS there is even less reason to consider it since IS-IS is NOT deployed as a PE-CE protocol.

   Les


> -----Original Message-----
> From: OSPF [mailto:ospf-bounces@ietf.org] On Behalf Of Acee Lindem
> (acee)
> Sent: Wednesday, October 08, 2014 9:36 AM
> To: Peter Psenak (ppsenak)
> Cc: ospf@ietf.org
> Subject: Re: [OSPF] New Version Notification for draft-liang-ospf-flowspec-
> extensions-01.txt
> 
> Hi Peter, et al,
> I’ve also seen many OSPF PE-CE deployments as well. One question is
> whether the CE is under the administrative control of the provider or the
> customer?
> Note that this was proposed at least once before -
> http://www.ietf.org/archive/id/draft-shrivastava-ospf-flow-spec-01.txt bit
> it didn’t gain momentum.
> 
> With respect to Hannes’ comment, Les Ginsberg said he sees this as a
> candidate for the ISIS Generic Information instance (RFC 6823). We could do
> the same and push it to the OSPF transport instance which has also lost
> momentum as a draft.
> 
> We’ve heard from one provider (Eric) who doesn’t think this is useful - any
> other input?
> 
> One thing I hope is that no sees this a generic flow-spec distribution
> mechanism for SDN. The reason being that you really need per peer
> granularity of advertisement and policy, e.g. BGP.
> 
> Thanks,
> Acee
> 
> On Oct 8, 2014, at 12:16 PM, Peter Psenak <ppsenak@cisco.com> wrote:
> 
> > Hi Eric,
> >
> > there are definitely deployments using OSPF as PE-CE. It's typically used
> for enterprise customers, that use OSPF as their IGP and use L3 VPN service
> to interconnect their sites.
> >
> > thanks,
> > Peter
> >
> > On 10/8/14 17:45 , Osborne, Eric wrote:
> >> I'm not sure this has much value.  The vast majority of dynamic PE-CE is
> done with BGP; the little bit that isn't BGP is, in my experience, RIP.  I don't
> think I've seen many (any?) OSPF PE-CE deployments.
> >>
> >>
> >>
> >>
> >> eric
> >>
> >> -----Original Message-----
> >> From: OSPF [mailto:ospf-bounces@ietf.org] On Behalf Of Youjianjie
> >> Sent: Tuesday, October 07, 2014 10:11 PM
> >> To: ospf@ietf.org
> >> Subject: [OSPF] 转发: New Version Notification for draft-liang-ospf-
> flowspec-extensions-01.txt
> >>
> >> Hi all,
> >>
> >> This document discusses the use cases that OSPF is used to distribute
> FlowSpec routes. This document also defines a new OSPF FlowSpec Opaque
> Link State Advertisement (LSA) encoding format.
> >> Your comments are appreciated.
> >>
> >> Best Regards,
> >> Jianjie
> >>
> >> -----邮件原件-----
> >> 发件人: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> >> 发送时间: 2014年9月28日 10:32
> >> 收件人: Youjianjie; Youjianjie; liuweihang; liuweihang
> >> 主题: New Version Notification for draft-liang-ospf-flowspec-
> extensions-01.txt
> >>
> >>
> >> A new version of I-D, draft-liang-ospf-flowspec-extensions-01.txt
> >> has been successfully submitted by Jianjie You and posted to the IETF
> repository.
> >>
> >> Name:		draft-liang-ospf-flowspec-extensions
> >> Revision:	01
> >> Title:		OSPF Extensions for Flow Specification
> >> Document date:	2014-09-27
> >> Group:		Individual Submission
> >> Pages:		11
> >> URL:            http://www.ietf.org/internet-drafts/draft-liang-ospf-
> flowspec-extensions-01.txt
> >> Status:         https://datatracker.ietf.org/doc/draft-liang-ospf-flowspec-
> extensions/
> >> Htmlized:       http://tools.ietf.org/html/draft-liang-ospf-flowspec-
> extensions-01
> >> Diff:           http://www.ietf.org/rfcdiff?url2=draft-liang-ospf-flowspec-
> extensions-01
> >>
> >> Abstract:
> >>    This document discusses the use cases why OSPF (Open Shortest Path
> >>    First) distributing flow specification (FlowSpec) routes is
> >>    necessary.  This document also defines a new OSPF FlowSpec Opaque
> >>    Link State Advertisement (LSA) encoding format that can be used to
> >>    distribute FlowSpec routes.
> >>
> >>    For the network only deploying IGP (Interior Gateway Protocol) (e.g.
> >>    OSPF), it is expected to extend IGP to distribute FlowSpec routes.
> >>    One advantage is to mitigate the impacts of Denial-of-Service (DoS)
> >>    attacks.
> >>
> >>
> >>
> >>
> >>
> >> Please note that it may take a couple of minutes from the time of
> submission until the htmlized version and diff are available at tools.ietf.org.
> >>
> >> The IETF Secretariat
> >>
> >> _______________________________________________
> >> OSPF mailing list
> >> OSPF@ietf.org
> >> https://www.ietf.org/mailman/listinfo/ospf
> >> _______________________________________________
> >> OSPF mailing list
> >> OSPF@ietf.org
> >> https://www.ietf.org/mailman/listinfo/ospf
> >>
> >
> > _______________________________________________
> > OSPF mailing list
> > OSPF@ietf.org
> > https://www.ietf.org/mailman/listinfo/ospf
> 
> _______________________________________________
> OSPF mailing list
> OSPF@ietf.org
> https://www.ietf.org/mailman/listinfo/ospf