IETF Logo Mail Archive

Re: [i2rs] Question and new use case

Anton Smith <anton.smith@ericsson.com> Wed, 04 June 2014 06:16 UTC

Return-Path: <anton.smith@ericsson.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 DFD381A009C for <i2rs@ietfa.amsl.com>; Tue, 3 Jun 2014 23:16:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.601
X-Spam-Level:
X-Spam-Status: No, score=-3.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] 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 GNRrBoe8xRv8 for <i2rs@ietfa.amsl.com>; Tue, 3 Jun 2014 23:16:24 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB0F91A0099 for <i2rs@ietf.org>; Tue, 3 Jun 2014 23:16:23 -0700 (PDT)
X-AuditID: c1b4fb2d-f79776d000001085-e4-538eb9b0eb29
Received: from ESESSHC006.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 7D.0D.04229.0B9BE835; Wed, 4 Jun 2014 08:16:16 +0200 (CEST)
Received: from ESESSMB305.ericsson.se ([169.254.5.52]) by ESESSHC006.ericsson.se ([153.88.183.36]) with mapi id 14.03.0174.001; Wed, 4 Jun 2014 08:16:15 +0200
From: Anton Smith <anton.smith@ericsson.com>
To: ramki Krishnan <ramk@Brocade.com>
Thread-Topic: Question and new use case
Thread-Index: Ac9/t7NQWlRd+9iuQrqINSd9SAUbMwABMpGz
Date: Wed, 04 Jun 2014 06:16:15 +0000
Message-ID: <D2A2F4BE-4042-4CA3-9BC9-68E6DAAB3A16@ericsson.com>
References: <C7634EB63EFD984A978DFB46EA5174F2C00500608D@HQ1-EXCH01.corp.brocade.com>
In-Reply-To: <C7634EB63EFD984A978DFB46EA5174F2C00500608D@HQ1-EXCH01.corp.brocade.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrPLMWRmVeSWpSXmKPExsUyM+Jvje6GnX3BBqvmiVqsm/GBxWLbzJ/M DkwePccus3ksWfKTKYApissmJTUnsyy1SN8ugSvj5pp9rAWfBCqevH7H0sD4kLeLkYNDQsBE YusD8S5GTiBTTOLCvfVsILaQwFFGiX3L47sYuYDsRYwSHw73sIPUswnoSDzpKwCpERFQlXi0 7yJYPbOAssTEl/vBbGEBNYn3lyawQtSoS9y9c4EdwjaS6Ph6igXEZhFQkfh87glYDa+AvcTf zn5miL0hEh1XFoDN4RQIlThw6CITiM0IdNv3U2uYIHaJS9x6Mp8J4mYBiSV7zjND2KISLx// Y4Wo0ZFYsPsT1G3aEssWvmaG2CUocXLmE5YJjKKzkIyahaRlFpKWWUhaFjCyrGIULU4tLs5N NzLWSy3KTC4uzs/Ty0st2cQIjJGDW37r7mBc/drxEKMAB6MSD68Cb1+wEGtiWXFl7iFGaQ4W JXHeSxrVwUIC6YklqdmpqQWpRfFFpTmpxYcYmTg4pRoY3Y4InQtQjzHMbTnwutGDW0ma68kb VhnpkK3qRxZ3Zj9rNK9YIG9gfmSPUKDd9Ve2rx6qXVtsv+DS9ykq5ys/yBYvuT/75TXOr2tk dkldv+WZ/vRLqZ6RRM73K++6RE4LKqddePzK6hR/ysYpZqYPX0YvzpilkDNtqbjmpuwTnbev RN64KfjhuBJLcUaioRZzUXEiADECNAlyAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/i2rs/il94qgmcdzU_9DF0-2ayJb9bx6g
Cc: "i2rs@ietf.org" <i2rs@ietf.org>
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 06:16:26 -0000

Thanks Ramki,

Will take a look.

Rest regards
Anton

Sent from my iPhone

> On 4 jun 2014, at 07:42, "ramki Krishnan" <ramk@Brocade.com> wrote:
> 
> 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