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

Yuval Lifshitz <ylifshitz@sandvine.com> Wed, 06 July 2016 17:30 UTC

Return-Path: <ylifshitz@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 DE86712D0EB for <dime@ietfa.amsl.com>; Wed, 6 Jul 2016 10:30:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.346
X-Spam-Level:
X-Spam-Status: No, score=-3.346 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 zJUI4jnjr7CX for <dime@ietfa.amsl.com>; Wed, 6 Jul 2016 10:30:19 -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 EB77F12D129 for <dime@ietf.org>; Wed, 6 Jul 2016 10:30:18 -0700 (PDT)
Received: from WTL-EXCHP-2.sandvine.com ([fe80::68ac:f071:19ff:3455]) by WTL-EXCHP-3.sandvine.com ([::1]) with mapi id 14.03.0195.001; Wed, 6 Jul 2016 13:30:17 -0400
From: Yuval Lifshitz <ylifshitz@sandvine.com>
To: "Bertz, Lyle T [CTO]" <Lyle.T.Bertz@sprint.com>, Dave Dolson <ddolson@sandvine.com>, "dime@ietf.org" <dime@ietf.org>
Thread-Topic: New I-D: draft-bertz-dime-perflowmbr-00
Thread-Index: AdHXoI27HhmJQL9SSVCCcgs9eQDIkwABGo+QAAAmleAAABKD8AAAFziQAAE97GA=
Date: Wed, 6 Jul 2016 17:30:17 +0000
Message-ID: <C43C255C7106314F8D13D03FA20CFE4930C8AE19@wtl-exchp-2.sandvine.com>
References: <bda537d9971b46858976bb40b11ef23c@PLSWE13M07.ad.sprint.com> <E8355113905631478EFF04F5AA706E9830FE6E7F@wtl-exchp-2.sandvine.com> <d5a2213039d44096b87253727dbb8d6a@PLSWE13M07.ad.sprint.com> <E8355113905631478EFF04F5AA706E9830FE6F64@wtl-exchp-2.sandvine.com> <5976352e235d43598a2f2d86c919a65c@PLSWE13M07.ad.sprint.com>
In-Reply-To: <5976352e235d43598a2f2d86c919a65c@PLSWE13M07.ad.sprint.com>
Accept-Language: en-CA, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.143.1]
x-c2processedorg: b2f06e69-072f-40ee-90c5-80a34e700794
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dime/C1ZbajDAxGZX0tES4cUHVQYgQnM>
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 17:30:21 -0000

* maybe good to mention how these rates work with the overall rates defined for all flows of the filter
* types in section 4 should be Unsigned32 

From: DiME [mailto:dime-bounces@ietf.org] On Behalf Of Bertz, Lyle T [CTO]
Sent: Wednesday, July 06, 2016 7:55 PM
To: Dave Dolson; dime@ietf.org
Subject: Re: [Dime] New I-D: draft-bertz-dime-perflowmbr-00

Yes, if you are using the IPFilterRule or RFC 5777 Filter-Rule as it is tied to the Protocol field.  I also intended for this not to conflict with multi-path based protocols.  

If you are applying these attributes to another kind of Rule, e.g. 3GPP ADC Rule, then sticking to the L3 is still fine.  However, if you want to use it for the Application level flow this document would need to be changed and we'd need to incorporate it in the draft.  Is that something I should look at for this document.  More work would be needed to clarify interaction with multipath and other protocols though.


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

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>om>; 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
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 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.