[i2rs] FW: New Version Notification for draft-krishnan-i2rs-large-flow-use-case-01.txt

ramki Krishnan <ramk@Brocade.com> Tue, 21 January 2014 05:43 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 26BAC1A0296 for <i2rs@ietfa.amsl.com>; Mon, 20 Jan 2014 21:43:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.267
X-Spam-Level:
X-Spam-Status: No, score=-2.267 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-0.7, 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 D8WfpK4_ZeXf for <i2rs@ietfa.amsl.com>; Mon, 20 Jan 2014 21:43:27 -0800 (PST)
Received: from mx0a-000f0801.pphosted.com (mx0a-000f0801.pphosted.com [67.231.144.122]) by ietfa.amsl.com (Postfix) with ESMTP id 846FB1A0290 for <i2rs@ietf.org>; Mon, 20 Jan 2014 21:43:27 -0800 (PST)
Received: from pps.filterd (m0048193 [127.0.0.1]) by mx0a-000f0801.pphosted.com (8.14.5/8.14.5) with SMTP id s0L5hRHJ015964; Mon, 20 Jan 2014 21:43:27 -0800
Received: from hq1wp-exchub01.corp.brocade.com ([144.49.131.13]) by mx0a-000f0801.pphosted.com with ESMTP id 1hgbdh0pv7-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 20 Jan 2014 21:43:27 -0800
Received: from HQ1WP-EXHUB02.corp.brocade.com (10.70.38.14) by HQ1WP-EXCHUB01.corp.brocade.com (10.70.36.99) with Microsoft SMTP Server (TLS) id 14.3.123.3; Mon, 20 Jan 2014 21:43:26 -0800
Received: from HQ1-EXCH01.corp.brocade.com ([fe80::ed42:173e:fe7d:d0a6]) by HQ1WP-EXHUB02.corp.brocade.com ([fe80::e1f4:a4c8:696b:3780%10]) with mapi; Mon, 20 Jan 2014 21:43:25 -0800
From: ramki Krishnan <ramk@Brocade.com>
To: "i2rs@ietf.org" <i2rs@ietf.org>
Date: Mon, 20 Jan 2014 21:43:24 -0800
Thread-Topic: New Version Notification for draft-krishnan-i2rs-large-flow-use-case-01.txt
Thread-Index: Ac8WSH9b9r8VY28MStSA+ftrHMjeWAAIpZPA
Message-ID: <C7634EB63EFD984A978DFB46EA5174F2C0013133D3@HQ1-EXCH01.corp.brocade.com>
References: <20140121013118.3737.29737.idtracker@ietfa.amsl.com>
In-Reply-To: <20140121013118.3737.29737.idtracker@ietfa.amsl.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="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.11.87, 1.0.14, 0.0.0000 definitions=2014-01-20_03:2014-01-21, 2014-01-20, 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-1305240000 definitions=main-1401200253
Cc: "draft-krishnan-i2rs-large-flow-use-case@tools.ietf.org" <draft-krishnan-i2rs-large-flow-use-case@tools.ietf.org>
Subject: [i2rs] FW: New Version Notification for draft-krishnan-i2rs-large-flow-use-case-01.txt
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: Tue, 21 Jan 2014 05:43:29 -0000

Dear All,

Besides load balancing, we have added an additional use of case for DDoS attack mitigation in the latest draft. Looking forward to your comments.

Thanks,
Ramki on behalf of the co-authors

-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Monday, January 20, 2014 5:31 PM
To: ramki Krishnan; Dave Mcdysan; Sriganesh Kini; Diego R. Lopez; Sriganesh Kini; Diego Lopez; Anoop Ghanwani; ramki Krishnan; Anoop Ghanwani; Dave McDysan
Subject: New Version Notification for draft-krishnan-i2rs-large-flow-use-case-01.txt


A new version of I-D, draft-krishnan-i2rs-large-flow-use-case-01.txt
has been successfully submitted by ram (ramki) krishnan and posted to the IETF repository.

Name:		draft-krishnan-i2rs-large-flow-use-case
Revision:	01
Title:		Large Flow Use Cases for I2RS PBR and QoS
Document date:	2014-01-20
Group:		Individual Submission
Pages:		12
URL:            http://www.ietf.org/internet-drafts/draft-krishnan-i2rs-large-flow-use-case-01.txt
Status:         https://datatracker.ietf.org/doc/draft-krishnan-i2rs-large-flow-use-case/
Htmlized:       http://tools.ietf.org/html/draft-krishnan-i2rs-large-flow-use-case-01
Diff:           http://www.ietf.org/rfcdiff?url2=draft-krishnan-i2rs-large-flow-use-case-01

Abstract:
   This draft discusses two use cases to help identify the requirements
   for policy-based routing in I2RS.  Both of the use cases involve
   identification of certain flows and then using I2RS to program
   special handling for those flows.

   The first use case deals with improving bandwidth efficiency.
   Demands on networking bandwidth are growing exponentially due to
   applications such as large file transfers and those with rich media.
   Link Aggregation Group (LAG) and Equal Cost Multipath (ECMP) are
   extensively deployed in networks to scale the bandwidth. However,
   the flow-based load balancing techniques used today make inefficient
   use of the bandwidth in the presence of long-lived large flows. We
   discuss how I2RS can be used for achieving better load balancing.

   The second use case is for recognizing and mitigating Layer 3-4
   based DDoS attacks. Behavioral security threats such as Distributed
   Denial of Service (DDoS) attacks are an ongoing problem in today's
   networks. DDoS attacks can be Layer 3-4 based or Layer 7 based. We
   discuss how such attacks can be recognized and how I2RS can be used
   for mitigating their effects.



                                                                                  


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