1 / 5

Services Provided by RSerPool < draft-ietf-rserpool-service-00.txt >

This document discusses the interactions and protocols involved in RSerPool services, including basic and enhanced modes, initialization, PE registration, PE selection, and failover services. It also explores the upper layer protocols and the RSerPool API. The text language is English.

laurawilson
Download Presentation

Services Provided by RSerPool < draft-ietf-rserpool-service-00.txt >

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Services Provided by RSerPool<draft-ietf-rserpool-service-00.txt > Authors: Peter Lei <peterlei@cisco.com> Phillip Conrad <conrad@acm.org> Presenter: Michael Tüxen <tuexen@fh-muenster.de>

  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 RSerPoolover 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 • Initialization • PE Registration Services • PE Selection (high availability and load balancing) • PE selection services (Basic Mode) • pool handle-> ip address/protocol/port translation (but enhanced with PE selection to make sure the choice is a good one • 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 Basic Mode Enhanced Mode Upper Layer Protocol / Application Upper Layer Protocol / Application RSerPool API RSerPool API Data ASAP Layer ASAP Layer Multiplexed ASAPand Data messages Mapping Layer Any Transport Protocol TCP or SCTP SCTP TCP

More Related