1 SASP v1 (Server/Application State Protocol) draft-bivens-sasp-00.txt Alan Bivens IBM Research New York, USA IETF 60.

Slides:



Advertisements
Similar presentations
Chapter 16. Windows Internet Name Service(WINS) Network Basic Input/Output System (NetBIOS) N etBIOS over TCP/IP (NetBT) provides commands and support.
Advertisements

Communication Service Identifier Requirements on SIP draft-loreto-3gpp-ics-requirements.txt
L. Alchaal & al. Page Offering a Multicast Delivery Service in a Programmable Secure IP VPN Environment Lina ALCHAAL Netcelo S.A., Echirolles INRIA.
Network Layer IPv6 Slides were original prepared by Dr. Tatsuya Suda.
1 Internet Networking Spring 2004 Tutorial 13 LSNAT - Load Sharing NAT (RFC 2391)
K. Salah 1 Chapter 31 Security in the Internet. K. Salah 2 Figure 31.5 Position of TLS Transport Layer Security (TLS) was designed to provide security.
Hypertext Transfer Protocol Kyle Roth Mark Hoover.
Oct 26, 2004CS573: Network Protocols and Standards1 IP: Routing and Subnetting Network Protocols and Standards Autumn
Chapter 13 Mobile IP. Outline  ADDRESSING  AGENTS  THREE PHASES  AGENT DISCOVERY  REGISTRATION  DATA TRANSFER  INEFFICIENCY IN MOBILE IP.
A Study of Mobile IP Kunal Ganguly Wichita State University CS843 – Distributed Computing.
ICMP: Internet Control Message Protocol used by hosts, routers, gateways to communication network-level information –error reporting: unreachable host,
Internet Networking Spring 2002 Tutorial 13 Web Caching Protocols ICP, CARP.
SIP, Session Initiation Protocol Internet Draft, IETF, RFC 2543.
Subnetting.
TCP/IP Protocol Suite 1 Chapter 11 Upon completion you will be able to: User Datagram Protocol Be able to explain process-to-process communication Know.
SIMPLEStone – A presence server performance benchmarking standard SIMPLEStone – A presence server performance benchmarking standard Presented by Vishal.
1 Spring Semester 2007, Dept. of Computer Science, Technion Internet Networking recitation #12 LSNAT - Load Sharing NAT (RFC 2391)
Introduction to SIP Speaker: Min-Hua Yang Advisor: Ho-Ting Wu Date:2005/3/29.
SNMP & MIME Rizwan Rehman, CCS, DU. Basic tasks that fall under this category are: What is Network Management? Fault Management Dealing with problems.
Technology Integration: RSerPool & Server Load-balancing Curt Kersey, Cisco Systems Aron Silverton, Motorola Labs.
Network Protocols UNIT IV – NETWORK MANAGEMENT FUNDAMENTALS.
Guide to TCP/IP, Third Edition
NECP: the Network Element Control Protocol IETF WREC Working Group November 11, 1999.
Chapter 13 – Network Security
M3UA Patrick Sharp.
Thomas Dreibholz Institute for Experimental Mathematics University of Duisburg-Essen, Germany University of Duisburg-Essen, Institute.
TCP/IP Protocols Dr. Sharon Hall Perkins Applications World Wide Web(HTTP) Presented by.
Mobile IP Most of the slides borrowed from Prof. Sridhar Iyer
TCP/IP Essentials A Lab-Based Approach Shivendra Panwar, Shiwen Mao Jeong-dong Ryoo, and Yihan Li Chapter 5 UDP and Its Applications.
Quick Implementation of a WAP Push Gateway Wen-Hung Su Fu Jen Catholic University Computer Science and Information Engineering Department Moblie Communication.
(Business) Process Centric Exchanges
1 TCP/IP Internetting ä Subnet layer ä Links stations on same subnet ä Often IEEE LAN standards ä PPP for telephone connections ä TCP/IP specifies.
Jun Li DHCP Option for Access Network Information draft-lijun-dhc-clf-nass-option-01.
Web Services Standards. Introduction A web service is a type of component that is available on the web and can be incorporated in applications or used.
Presented By Team Netgeeks SIP Session Initiation Protocol.
Web Client-Server Server Client Hypertext link TCP port 80.
Integrating Digital Libraries by CORBA, XML and Servlet Integrating Digital Libraries by CORBA, XML and Servlet Wing Hang Cheung, Michael R. Lyu and Kam.
DNS SRV and NAPTR Use for SPEERMINT - Tom Creighton, Gaurav Khandpur Comcast SPEERMINT Intermin Meeting Philadelphia Sept
Thomas Dreibholz Institute for Experimental Mathematics University of Duisburg-Essen, Germany University of Duisburg-Essen, Institute.
ARP Address Resolution Protocol RFC 0826 ARP Request – Who has ip address ARP Reply – is mine( a6-50)
Protocol Headers 0x0800 Internet Protocol, Version 4 (IPv4) 0x0806 Address Resolution Protocol (ARP) 0x8100 IEEE 802.1Q-tagged frame 0x86DD Internet Protocol,
Internet Protocols (chapter 18) CSE 3213 Fall 2011.
1 Copyright © The McGraw-Hill Companies, Inc. Permission required for reproduction or display. Dynamic Host Configuration Protocol (DHCP)
CSC 600 Internetworking with TCP/IP Unit 5: IP, IP Routing, and ICMP (ch. 7, ch. 8, ch. 9, ch. 10) Dr. Cheer-Sun Yang Spring 2001.
HTTP evolution - TCP/IP issues Lecture 4 CM David De Roure
1 Requirements for Internet Routers (Gateways) and Hosts Relates to Lab 3. (Supplement) Covers the compliance requirements of Internet routers and hosts.
The Client-Server Model And the Socket API. Client-Server (1) The datagram service does not require cooperation between the peer applications but such.
SOCKS By BITSnBYTES (Bhargavi, Maya, Priya, Rajini and Shruti)
PPSP BAR BOF meeting 74th IETF – San Francisco, CA, USA March, 2009 P2P Streaming Protocol (PPSP) Requirements Ning Zong,Huawei Technologies Yunfei Zhang,China.
Microsoft Windows Server 2003 TCP/IP Protocols and Services Technical Reference Slide: 1 Lesson 18 Windows Internet Name Service (WINS)
IP Protocol CSE TCP/IP Concepts Connectionless Operation Internetworking involves connectionless operation at the level of the Internet Protocol.
Draft-carpenter-v6ops-label-balance-02 Brian Carpenter Sheng Jiang (Speaker) Willy Tarreau March 2012 IPv6 Flow Label for Server Load Balancing - update.
Computer Network Architecture Lecture 7: OSI Model Layers Examples II 1 26/12/2012.
Rserpool Security Trust Argument draft-ietf-rserpool-asap-13.txt Maureen Stillman November 6, 2006
1 © 1999, Cisco Systems, Inc. 1293_07F9_c1 LocalDirector Version3.1.
Chapter 11 User Datagram Protocol
The Transport Layer Implementation Services Functions Protocols
Chapter 9: Transport Layer
Instructor Materials Chapter 9: Transport Layer
WWW and HTTP King Fahd University of Petroleum & Minerals
NDN Messages and NDN Packets
Network Load Balancing Topology
The Reliable Server Pooling Framework
Maureen Stillman March 17, 2003
ECE 544 Protocol Design Project 2016
Chapter 14 User Datagram Protocol (UDP)
Chapter 15. Internet Protocol
Introduction to TCP/IP
Steven Feltner reveller – IRC
HTTP Hypertext Transfer Protocol
Presentation transcript:

1 SASP v1 (Server/Application State Protocol) draft-bivens-sasp-00.txt Alan Bivens IBM Research New York, USA IETF 60

2 SASP objectives Provide a mechanism for workload managers to give distribution recommendations to load balancers. Must be lightweight –little implementation complexity –little processing overhead –little additional user configuration Must be free of corporate ownership issues Must be extendible Control must remain at the load balancer SASP will not handle the transport or actual distribution of work, only give recommendations

3 Example System Architecture Group Workload Manager Individual Workload Manager Member Requests Load Balancer Request Origins Individual Workload Manager Member Individual Workload Manager Member Requests SASP Protocol Characteristics Binary Streams SSL

4 SASP Messages Registration Messages DeRegistration Messages Get Weight and Send Weight Messages Set Member State Messages Set LB State Messages

5 Example Flow A: (lb registration, get weights, and resource set state) 1.LB registers A, B, and C in GRP1. GWM replies with no error. 2.LB sends Get Weights message for GRP1 and receives the following: 3.LB sends Set LB State Message: 4.A sends SetMember State Message: 5.Resource C sends a Set Member State message to quiesce itself with the following flags: Load Balancer Member C Member A Member C Group Workload Manager time Register A, B, C in group GRP1 Register Reply Get Weights for GRP1 Get Weights Reply Get Weights for GRP1 Get Weights Reply 4 Set State for ResourceA Set State Reply Set Quiesce State ResC Set State Reply Get Weights for GRP1 Get Weights Reply Set Quiesce State ResC GroupMemberOpaque State General Flags Weight GRP1 Resource A0x Resource B0x Resource C0x MemberOpaque StateFlags Resource A0x MemberOpaque StateFlags Resource C0x0A Set State for LB Set State Reply MemberLB HealthFlags Load Balancer0x7F

6 Example Flow A (continued) : (lb registration, get weights, and resource set state) 6.LB sends the Get Weights message for GRP1 and receives the following: 7.Resource C sends a Set State message to un-quiesce itself with the following flags: 8.LB sends the Get Weights message for GRP1 and receives the following: Load Balancer Member C Member A Member C Group Workload Manager time Register A, B, C in group GRP1 Register Reply Get Weights for GRP1 Get Weights Reply Get Weights for GRP1 Get Weights Reply 4 Set State for ResourceA Set State Reply Set Quiesce State ResC Set State Reply Get Weights for GRP1 Get Weights Reply Set Quiesce State ResC GroupMemberOpaque State General Flags Weight GRP1 Resource A0x Resource B0x Resource C0x0A11110 MemberOpaque StateFlags Resource C0x0A0000 GroupMemberOpaque State General Flags Weight GRP1 Resource A0x Resource B0x Resource C0x0A Set State for LB Set State Reply

7 Only Overlap between SASP and RSERPOOL Providing “A means for allowing flexible load assignment and balancing policies” –SASP provides a manner of doing this between two entities, but not by way of a policy.

8 Differences between SASP and RSERPOOL Terminology and topology: –PU -> client, outside of SASP scope –PE -> group member –ENRP Server -> some blend of load balancer and GWM Traditional load balancing does not have such an entity –PU Proxy -> outside of SASP scope, not needed for traditional load balancing

9 Differences cont. Flow of protocols: –ASAP/ENRP: PE registers with the ENRP Server PU contacts ENRP server for PE handle resolution, and then contacts PE using designated transport protocol –SASP/Traditional load balancing: Load balancer admin registers all group members. Load balancer is transparent, client contacts load balancer using expected transport protocol and receives reply from initial message

10 Current State of SASP Multiple vendors have begun to announce support of this protocol 2 implementations of SASP GWM components coming out in products this year. 2 interoperating implementations of SASP Router component by two different vendors this year. Current version of SASP available as individual ID “

11 What next Should this be an informational RFC? Would this working group like to adopt it as a standards track document? Should we have a full BOF at the next IETF?

12 Thank You

13 Extra Slides Basic Protocol Components Group Protocol Components Message Types

14 Basic Protocol Components Member State Instance Group Data Protocol Port IP Address Label length Label Member Data Opaque Member State Field Weight Contact Flag Quiesce Flag Registration Flag Confident Flag SASP Header Member Data Weight Entry Version Message Length Message ID 5 Basic Components are used throughout the protocol Member Data Opaque State Quiesce Flag LB UID Length LB UID Group Name Length Group Name

15 Group Protocol Components Group of Weight Data Group of Member State Data Group Data Member Data Count Array of Member Data Components Group Data Weight Entry Count Array of Weight Entry Components Group of Member Data 3 Group Components are used throughout the protocol Group Data Resource State Instance Count Array of Resource State Instances

16 Registration Messages Registration Deregistration Group Workload Manager Load Balancer SASP LB || Member ---> GWM (Request)(Response) SASP Header “Group of Member Data” Count Array of “Group of Member Data” Components SASP Header Return Code LB || Member ---> GWM (Request)(Response) SASP Header “Group of Member Data” Count Array of “Group of Member Data” Components Reason SASP Header Return Code Individual Workload Manager Resource

17 Weight Exchange Messages Get Weights Send Weights Group Workload Manager Load Balancer SASP LB ---> GWM (Request)(Response) SASP Header Group Data Count Array of Group Data Components SASP Header Group Weight Data Count Array of Group Weight Data Components Return Code Interval GWM ---> LB (Push)No Response SASP Header “Group of Weight Data” Count Array of “Group of Weight Data” Components Fields in Weight Entry Weight Entry fields Opaque Member State Contact Flag Quiesce Flag Registration Flag Confident Flag Weight

18 Set Member State Messages Set Member State Group Workload Manager Load Balancer SASP Individual Workload Manager Resource LB || Member ---> GWM (Request) (Response) SASP Header LB or Member Flag “Group of Member State” Count Array of “Group of Member State” Components SASP Header Return Code Fields in Member State Instance Member State Instance fields Opaque State Quiesce Flag SASP

19 Set Load Balancer State Messages Group Workload Manager Load Balancer SASP LB ---> GWM (Request)(Response) SASP Header LB Identifier Length LB Identifier Push Flag Trust Flag No Change / No Send Flag LB Health SASP Header Return Code Set Load Balancer State