Network Stratum Query (NSQuery) Charter Goals Data Centers offer

advertisement

Network Stratum Query (NSQuery) Charter

Goals

Data Centers offer application services to end-users such as video gaming, cloud computing and others. As the application servers are distributed geographically in many

Data Centers for various reasons, the decision as where to instantiate services needs to be optimized across end-user experience and data center economy.

User experience is impacted by Intra Data Center factors such as server load conditions, and connectivity within Data Center as well as the underlying network behavior (such as congestion, jitter, latency and loss) between end-user and the hosting Data Center and between Data Centers.

The Working Group will design and specify a communication protocol and associated mechanisms that will allow the application to do a whole network query of information at the network-stratum so that synchronized monitoring would be enabled across application and network.

The network stratum is described as non-application resources (as shown in diagram 1) that includes transport to physical layer. The scope is across many boxes in multiple domains (physical, link, network, and transport domains). Application stratum includes multiple applications at the application layer across multiple domains.

Application protocols will use this network protocol mechanism to manage the network.

Why needed:

Currently Network Management only queries network elements at a particular layer.

This charter suggests work that will allow a coordinated query of network stratum resources. The application will talk to a set of N-CSG to Query information.

Avoid NIH (not invented here) : The purpose of this working group is to create the full-network query function leverage appropriate existing technology.

Every effort will be made to utilize existing NM protocols or emerging NM protocols (for focus Part A or Part B). Due to this concern, four documents will be created early in the process (problem statement, architecture document, survey of existing protocols, and requirements document) in order to verify with the Network Management and OPS IETF community that no mechanisms exist.

Application Stratum Needs

Emerging real-time application services (e.g., video gaming, conferencing, on-demand video/HDTV applications, cloud computing, etc.) may make significant demands on network resources such as bandwidth and may have a variety of quality of service requirements such as latency. As more applications begin to be fielded in “cloud computing” environments, the real-time applications are being deployed on network

resources across multiple domains on multiple types of network hardware. This trend to place more applications in “cloud” environments is project to grow.

Due to the lack of cross stratum interaction between the application stratum and the underlying network stratum during service provisioning, many application services make poor use of network resources and capability or not achieve their overall quality of service objectives and/or being denied of service provisioning pre-maturely.

Synchronized full-network network by application monitoring is critical to make the application placement work effectively.

Objectives

The Working Group will focus on the following iems:

-

-

A “problem statement” document that provides the description of the issues in full-network query and key terminology.

An “architecture” document that provides the description of architecture components and their functions. This document also provides how Network

Stratum Query (NSQuery) supports applications requests.

-

A “survey” document that lists all existing works in related to this working group.

-

An “application” of NSQuery for a specific application area data center load balancing and distribution, data center HDTV multi-cast, and streaming video.

- A “requirement” document that specifies requirements for the NSQuery functionalities between Application Stratum and Network Stratum, identifying types of messages and information CSO interface may need to pass for the

NSQuery function.

- A NSQuery “protocol” document that defines request/reply format and semantics to allow identified functionalities on the CSO based on the “requirement” document.

-

A “protocol” document that defines interfaces between network layer controller and internet NM and policy control (PEP/PC)

-

A “protocol” document that defines interfaces between network layer controller and path computation element (PCE) for multi-domain path computation

-

An “implementation” experience document that describes CSO implementation experience or network trial.

Proposed Schedule for IETF Working Group

Problem statement

Architecture statement

[March 2011]

[March 2011]

Survey Document

Application Documents

Requirements Document

AS-NS Protocol

[March 2011]

[July 2011]

[July 2011]

[July 2011]

NS-NM & PCP/PEP Protocol

NS-PCE

Implementation Report

Interested Parties:

[July 2011]

[July 2011]

[November 2011]

Vendors:

- Huawei, Ericsson, Cisco, ETRI, Iridescent

Carriers:

- Telefonica, Verizon, NTT, KDDI, BT, DT, China Mobile

People (Attendees for Bar BOF) – 40 signed attendees

Young Lee

Dave McDysan

Katsushi Kobayashi

Xiangsong Cui

Dirk Hugo

Greg Bernstein

Matthias Kaschub

Aki Myrhinen

Heeyoung Jung

Dan Li

Xie Lei

Hideki Sunahara

Daniele Ceccarelli

Dave Croker

Myung Ki Shin

Dapeng Lin

Tae Yeon Kim

Oscar Gonzales de

Dios

Fatai Zhang

Mirja Kuhlewind

Quintin Zhao

Duan Shihui

Attila Takacs

Sandoche

Balakrichenan

Tomonori Takeda

Malcolm Betts

Jonathan Saddler

Yuji Tochio

Tian Linyi

Alvaro retana

Iguas Bagdonas

Guoying Zhang

Xu Yunbin

Antti Makela

Riccardo Bernadini

Kathy McEwen

Bob Briscoe yajuan Wu

Yosifumi Atarashi

Ray Atarashi ylee@huawei.com dave.mcdysan@varizon.com ikib@AI.AIST.GO.JP

Xiangsong.cui@huawei.com dirk.vou-hugo@telecom.de gregb@grotto-networking.com kaschub@ikr.uni-stuttgart.de anyrhine!@cs.helsinki.fi hyjung@etri.re.kr danli@huawei.com xielei57471@huawei.com suna@wide.ad.jp daniele.ceccarelli@ericsson.com dhc@dcrocker.net mkshin@etri.re.kr lindapeng@chinamobile.com tykim@etri.re.kr ogondio@tid.cs zhangfatai@huawei.com mirja.kuehlewind@ikr.uni-shuttgart.de qzhao@huawei.com duanshihui@mail.ritt.com.cn attila.takacs@ericsson.com sandoche.balakrichenan@afnic.fr takeda.tomonori@lab.ntt.co.jp malcolm.betts@zte.com.cn saddler@homesys.org tochio@jp.fujitsu.com tianlinyi@huawei.com aretana@cisco.com bagdona@cisco.com zhangguoying@mail.ritt.com.cn xuyunbin@catr.ca antti.makela@tlek.fi riccardo.bernardini@unind.it k.mccwen@verizon.net bob.briscoe@bt.com wujajuan@huawei.com

Huawei

Verizon

AIST

Huawei

DT

Grotto

Univ. Stuttgart

ETRI

Huawei

Huawei

Ericsson

ETRI

China Mobil

ETRI

Telefonica

Huawei

Univ. Stuttgart

Huawei

Ericsson

NTT

ZTE

Tellabs

Fujitsu

Huawei

Cisco

Cisco

Iridescent

BT

Huawei

Alaxala

IIJ

Schedule for creation of material for IETF BOF’s consideration:

Preliminary Problem statement

Preliminary Architecture statement

Preliminary Survey Document

Preliminary Application Documents

Preliminary Requirements Document

Preliminary AS-NS Protocol

Preliminary NS-NM & PCP/PEP Protocol

Preliminary NS-PCE

Preliminary Implementation Report

[September 2010 ]

[September 2010 ]

[September 2010 ]

[October 2010]

[October 2010]

[October 2010]

[October 2010]

[October 2010]

[November 2011]

Initial BOF work schedule

Interim Meetings – 3 Meetings (September– October]

Potential collaboration: NG Virtual networks, Internet 2, ITRI.

Download