Services Provided by RSerPool Authors: Peter Lei Phillip Conrad Presenter: Michael Tüxen

2 Motivation Two concerns raised at IETF 53 –Need clearer picture of how applications interact with RSerPool –Need way to support PU-PE interactions on protocols other than SCTP Drafts: –draft-ietf-rserpool-service –draft-ietf-rserpool-tcpmapping

3 Current iteration of services Two ways an application can interact with RSerPool Basic Mode ASAP interaction to do server selection PU-PE application layer protocol done separately (not mediated by RSerPool) Enhanced Mode Multiplexed control/data channel managed by RSerPool over either SCTP or TCP+shim layer (tcpmapping) notes: –a given application must choose one, and all PEs in a given pool must make the same choice –the choice is implicit for a given application, and therefore no on the wire signaling is necessary

4 Current iteration of services Two ways an application can interact with RSerPool Basic Mode Enhanced Mode Services common to both types of application interaction (1)Initialization (2)PE Registration Services (3)PE Selection (high availability and load balancing) PE selection services (Basic Mode) 1)pool handle-> ip address/protocol/port translation (but enhanced with PE selection to make sure the choice is a good one 2)transport.failure report Enhanced failover services: (available only with multiplexed data/control channel managed by RSerPool) data send/receive primitives With automatic PE selection With optional best-effort redirection if PE fails or is unreachable business card state cookie failure indication callback

5 RSerPool Framework Any Transport Protocol RSerPool API ASAP Layer Upper Layer Protocol / Application Mapping Layer RSerPool API ASAP Layer Upper Layer Protocol / Application TCP or SCTP SCTPTCP Multiplexed ASAPand Data messages Basic Mode Enhanced Mode Data