IETF Logo Mail Archive

Re: [i2rs] Question and new use case

ramki Krishnan <ramk@Brocade.com> Wed, 04 June 2014 05:42 UTC

Return-Path: <ramk@Brocade.com>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E0BC1A008A for <i2rs@ietfa.amsl.com>; Tue, 3 Jun 2014 22:42:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.301
X-Spam-Level:
X-Spam-Status: No, score=-1.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_14=0.6, SPF_PASS=-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 Zg4U8TVd6v-H for <i2rs@ietfa.amsl.com>; Tue, 3 Jun 2014 22:42:38 -0700 (PDT)
Received: from mx0a-000f0801.pphosted.com (mx0a-000f0801.pphosted.com [IPv6:2620:100:9001:7a::1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B1A31A0087 for <i2rs@ietf.org>; Tue, 3 Jun 2014 22:42:38 -0700 (PDT)
Received: from pps.filterd (m0048193 [127.0.0.1]) by mx0a-000f0801.pphosted.com (8.14.5/8.14.5) with SMTP id s545PqBl011028; Tue, 3 Jun 2014 22:42:29 -0700
Received: from hq1wp-exchub02.corp.brocade.com ([144.49.131.13]) by mx0a-000f0801.pphosted.com with ESMTP id 1m9hhbg6nu-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 03 Jun 2014 22:42:29 -0700
Received: from HQ1WP-EXHUB02.corp.brocade.com (10.70.38.14) by hq1wp-exchub02.corp.brocade.com (10.70.38.99) with Microsoft SMTP Server (TLS) id 14.3.123.3; Tue, 3 Jun 2014 22:42:28 -0700
Received: from HQ1-EXCH01.corp.brocade.com ([fe80::a540:dc22:25c4:398e]) by HQ1WP-EXHUB02.corp.brocade.com ([fe80::f5db:81ae:2a14:f915%12]) with mapi; Tue, 3 Jun 2014 22:42:26 -0700
From: ramki Krishnan <ramk@Brocade.com>
To: Anton Smith <anton.smith@ericsson.com>, "i2rs@ietf.org" <i2rs@ietf.org>
Date: Tue, 03 Jun 2014 22:42:25 -0700
Thread-Topic: Question and new use case
Thread-Index: Ac9/t7NQWlRd+9iuQrqINSd9SAUbMw==
Message-ID: <C7634EB63EFD984A978DFB46EA5174F2C00500608D@HQ1-EXCH01.corp.brocade.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.12.52, 1.0.14, 0.0.0000 definitions=2014-06-04_01:2014-06-02,2014-06-04,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1406040069
Archived-At: http://mailarchive.ietf.org/arch/msg/i2rs/uk-ltNk0PFzw8g-bvvHt44SlViE
Subject: Re: [i2rs] Question and new use case
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Interface to The Internet Routing System \(IRS\)" <i2rs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2rs>, <mailto:i2rs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/i2rs/>
List-Post: <mailto:i2rs@ietf.org>
List-Help: <mailto:i2rs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2rs>, <mailto:i2rs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Jun 2014 05:42:39 -0000

Hi Anton,

The draft below addresses the use case you are mentioning. Would love to have your comments.

http://datatracker.ietf.org/doc/draft-krishnan-i2rs-large-flow-use-case/?include_text=1

Thanks,
Ramki

-----Original Message-----
From: i2rs [mailto:i2rs-bounces@ietf.org] On Behalf Of Anton Smith
Sent: Tuesday, June 03, 2014 1:51 AM
To: i2rs@ietf.org
Subject: [i2rs] Question and new usecase

Hi all,

I have a question and a potential usecase. I was reading the charter today and it mentioned some fairly specific usecases. I've been thinking of another fairly specific class of usecase that I had hoped I2RS would deliver.

The question is, where do you raise discussion on a new usecase, is it here on the list?

The usecase itself is about flow installation or basically non-destination based routing and forwarding. Imagine a router participating in an IP/MPLS domain, which is running for example multiple L3VPNs, L2VPNs, or even just plain L3 routing.

It would be desirable to be able to dynamically push down new policy based rules to an access interface such that as traffic ingresses the node it can be redirected to either services (like an L3VPN context) or forwarded, based on whatever can be filtered/matched in the incoming packet.

In essence policy based forwarding (aka PBR), but allowing I2RS to push down the policies (match criteria, action, etc.), edit them, remove them, and so forth. This could allow for instance, based off orchestration layer decisions, the dynamic redirection or separation of traffic that would have been previously grouped together, and not restricted to just QoS separation but allowing path separation or service redirection. 

Regards,
Anton

_______________________________________________
i2rs mailing list
i2rs@ietf.org
https://www.ietf.org/mailman/listinfo/i2rs

v2.23.0 | Report a Bug | By Email