Re: [alto] Ato extension for representing SDN policies

郭华明 <guohuaming@caict.ac> Thu, 09 April 2015 14:49 UTC

Return-Path: <guohuaming@caict.ac>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BBA11A8A3D for <alto@ietfa.amsl.com>; Thu, 9 Apr 2015 07:49:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.689
X-Spam-Level: *
X-Spam-Status: No, score=1.689 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, J_CHICKENPOX_31=0.6, MIME_8BIT_HEADER=0.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 x-XAmXq-88Js for <alto@ietfa.amsl.com>; Thu, 9 Apr 2015 07:49:49 -0700 (PDT)
Received: from caict.ac (mail.caict.ac [219.239.97.64]) by ietfa.amsl.com (Postfix) with ESMTP id 800F61A8A62 for <alto@ietf.org>; Thu, 9 Apr 2015 07:49:45 -0700 (PDT)
Received: by ajax-webmail-app1 (Coremail) ; Thu, 9 Apr 2015 22:49:27 +0800 (GMT+08:00)
X-CM-HeaderCharset: UTF-8
X-Originating-IP: [32.212.54.127]
Date: Thu, 09 Apr 2015 22:49:27 +0800
From: 郭华明 <guohuaming@caict.ac>
To: ChenGuohai <chenguohai67@outlook.com>
X-Priority: 3
X-Mailer: Coremail Webmail Server Version XT3.0.5b dev build 20150108(58896.7041) Copyright (c) 2002-2015 www.mailtech.cn catr
In-Reply-To: <BLU174-W106FDCED76BBC75A71EFA6C0FC0@phx.gbl>
References: <4500cb32.5842.14c6c5ac349.Coremail.guohuaming@caict.ac> <BLU174-W106FDCED76BBC75A71EFA6C0FC0@phx.gbl>
X-SendMailWithSms: false
Content-Type: multipart/alternative; boundary="----=_Part_130417_1522999221.1428590967076"
MIME-Version: 1.0
Message-ID: <6fe2ae11.8ee1.14c9ea83924.Coremail.guohuaming@caict.ac>
X-CM-TRANSID: FhADCgBn3yJ4kSZV+usIAA--.8553W
X-CM-SenderInfo: xjxrx3xdpl0w46fdxunwodu/1tbiAQEMBVGrSYJFhAAPs2
X-Coremail-Antispam: 1Ur529EdanIXcx71UUUUU7IcSsGvfJ3iIAIbVAYjsxI4VW7Jw CS07vEb4IE77IF4wCS07vE1I0E4x80FVAKz4kxMIAIbVAFxVCaYxvI4VCIwcAKzIAtYxBI daVFxhVjvjDU=
Archived-At: <http://mailarchive.ietf.org/arch/msg/alto/td7ZctiGLVAAKrQnNhSa-VetcPU>
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] Ato extension for representing SDN policies
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto/>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 14:49:52 -0000

Hi Guohai,


I think your example is good, it's my opinion that more meaningful policies are helpful for traffic optimization.

-----原始邮件-----
发件人:ChenGuohai <chenguohai67@outlook.com>
发送时间:2015-04-08 21:18:44 (星期三)
收件人: "郭华明" <guohuaming@caict.ac>, "Richard Yang Y." <yry@cs.yale.edu>
抄送: "alto@ietf.org" <alto@ietf.org>
主题: RE: [alto] Ato extension for representing SDN policies


Hi Huaming,All


Getting policy rules does benefit to traffic optimization. In addition to that it can reduce ALTO request and response. 


For example, a policy is that band between a pair of src(A)and dst is 20M between 11:00 to 14:00 and is 10M for other time. And band between other src(B,C,D ....) and this dst is 15M. The ALTO client can use this policy in selecting more optimal peers without sending ATLO cost map request to ALTO server now and then. 


ALTO client select src(A) as the peer between 11:00 to 14:00 and one of src(B,C,D....) at other time.


Make sense?




BR
Guohai

Date: Tue, 31 Mar 2015 04:23:49 +0800
From: guohuaming@caict.ac
To: yry@cs.yale.edu
CC: alto@ietf.org
Subject: [alto] Ato extension for representing SDN policies

Hi Richard, All


In SDN, each pair of source and destination network could have multiple policy rules. These rules maybe include source/destination address, protocols, ports, QoS, actions and so on. These information is
also important attributes of the path.     

I am thinking that if some policy information could be provided for applications in Alto, this is also helpful for traffic optimization.


I think there are two methods to do that in Alto.


1, Use a multiple cost types in Cost Maps (similar ideas in  draft-randriamasy-alto-multi-cost-10), add a new Cost Mode: policy, the Cost Metric use multiple fields, like <Protocol, Port, QoS>,  to represent a policy.


2, Add a new map service, like Policy Maps Service. In Policy Maps, applications can get the policy rule information.




Thanks.   

--

----------------
Best!




Huaming Guo


China Academy of Information and Communications Technology (CAICT)

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

--

----------------
Best!




Huaming Guo


China Academy of Information and Communications Technology (CAICT)