IETF Logo Mail Archive

Re: [Dime] New I-D: draft-bertz-dime-perflowmbr-00

Dave Dolson <ddolson@sandvine.com> Wed, 06 July 2016 16:48 UTC

Return-Path: <ddolson@sandvine.com>
X-Original-To: dime@ietfa.amsl.com
Delivered-To: dime@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EFCB12D13D for <dime@ietfa.amsl.com>; Wed, 6 Jul 2016 09:48:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.345
X-Spam-Level:
X-Spam-Status: No, score=-3.345 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426] autolearn=ham autolearn_force=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 o3vFxiGnI_6c for <dime@ietfa.amsl.com>; Wed, 6 Jul 2016 09:48:16 -0700 (PDT)
Received: from mail1.sandvine.com (mail1.sandvine.com [64.7.137.165]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8CC8B126B6D for <dime@ietf.org>; Wed, 6 Jul 2016 09:48:12 -0700 (PDT)
Received: from BLR-EXCHP-2.sandvine.com (192.168.196.172) by WTL-EXCHP-3.sandvine.com (192.168.196.177) with Microsoft SMTP Server (TLS) id 14.3.195.1; Wed, 6 Jul 2016 12:48:11 -0400
Received: from WTL-EXCHP-2.sandvine.com ([fe80::68ac:f071:19ff:3455]) by blr-exchp-2.sandvine.com ([fe80::6c6d:7108:c63c:9055%14]) with mapi id 14.03.0294.000; Wed, 6 Jul 2016 12:48:10 -0400
From: Dave Dolson <ddolson@sandvine.com>
To: "Bertz, Lyle T [CTO]" <Lyle.T.Bertz@sprint.com>, "dime@ietf.org" <dime@ietf.org>
Thread-Topic: New I-D: draft-bertz-dime-perflowmbr-00
Thread-Index: AdHXoI27HhmJQL9SSVCCcgs9eQDIkwABGo+QAAAmleAAABKD8A==
Date: Wed, 06 Jul 2016 16:48:10 +0000
Message-ID: <E8355113905631478EFF04F5AA706E9830FE6F64@wtl-exchp-2.sandvine.com>
References: <bda537d9971b46858976bb40b11ef23c@PLSWE13M07.ad.sprint.com> <E8355113905631478EFF04F5AA706E9830FE6E7F@wtl-exchp-2.sandvine.com> <d5a2213039d44096b87253727dbb8d6a@PLSWE13M07.ad.sprint.com>
In-Reply-To: <d5a2213039d44096b87253727dbb8d6a@PLSWE13M07.ad.sprint.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.200.63]
x-c2processedorg: b2f06e69-072f-40ee-90c5-80a34e700794
Content-Type: multipart/alternative; boundary="_000_E8355113905631478EFF04F5AA706E9830FE6F64wtlexchp2sandvi_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dime/6slv5apQP2MZ8aVlhrFR3vs6oog>
Subject: Re: [Dime] New I-D: draft-bertz-dime-perflowmbr-00
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dime>, <mailto:dime-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dime/>
List-Post: <mailto:dime@ietf.org>
List-Help: <mailto:dime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jul 2016 16:48:18 -0000

OK, I see in Security Considerations.

For your use-case, is it acceptable that a client could open two 5-tuple connections to achieve double the rate?




From: Bertz, Lyle T [CTO] [mailto:Lyle.T.Bertz@sprint.com]
Sent: Wednesday, July 06, 2016 12:44 PM
To: Dave Dolson; dime@ietf.org
Subject: RE: New I-D: draft-bertz-dime-perflowmbr-00

Hmm.

Should say IP flow (5-tuple) but that may be in the wrong location.


From: Dave Dolson [mailto:ddolson@sandvine.com]
Sent: Wednesday, July 06, 2016 11:43 AM
To: Bertz, Lyle T [CTO] <Lyle.T.Bertz@sprint.com<mailto:Lyle.T.Bertz@sprint.com>>; dime@ietf.org<mailto:dime@ietf.org>
Subject: RE: New I-D: draft-bertz-dime-perflowmbr-00

Lyle,
This document doesn't define a "flow". What did you have in mind as a definition?

It sounds like you are thinking of a TCP or UDP connection? So if the intent were to limit video rates, each TCP or UDP connection would be granted the specified rate?

-Dave


From: DiME [mailto:dime-bounces@ietf.org] On Behalf Of Bertz, Lyle T [CTO]
Sent: Wednesday, July 06, 2016 12:31 PM
To: dime@ietf.org<mailto:dime@ietf.org>
Subject: [Dime] New I-D: draft-bertz-dime-perflowmbr-00

All,

I have added a new I-D for consideration.  It permits setting *per flow* maximum bit rates.  This can serve in some applications, e.g. video throttling, to limit features such as resolutions as opposed to requiring deeper inspection.

https://datatracker.ietf.org/doc/draft-bertz-dime-perflowmbr/

Thank you.

Lyle

________________________________
Learn more on how to switch to Sprint and save 50% on most Verizon, AT&T or T-Mobile rates. See sprint.com/50off<http://sprint.com/50off> for details.
________________________________

This e-mail may contain Sprint proprietary information intended for the sole use of the recipient(s). Any use by others is prohibited. If you are not the intended recipient, please contact the sender and delete all copies of the message.

v2.23.0 | Report a Bug | By Email