Skip to main content

An Overview of Reliable Server Pooling Protocols
RFC 5351

Revision differences

Document history

Date Rev. By Action
2015-10-14
06 (System) Notify list changed from rserpool-chairs@ietf.org, draft-ietf-rserpool-overview@ietf.org to (None)
2008-09-30
06 Amy Vezza State Changes to RFC Published from RFC Ed Queue by Amy Vezza
2008-09-30
06 Amy Vezza [Note]: 'RFC 5351' added by Amy Vezza
2008-09-30
06 (System) RFC published
2008-06-24
06 Amy Vezza State Changes to RFC Ed Queue from Approved-announcement sent by Amy Vezza
2008-06-23
06 (System) IANA Action state changed to No IC from In Progress
2008-06-23
06 (System) IANA Action state changed to In Progress
2008-06-23
06 Amy Vezza IESG state changed to Approved-announcement sent
2008-06-23
06 Amy Vezza IESG has approved the document
2008-06-23
06 Amy Vezza Closed "Approve" ballot
2008-06-19
06 Cindy Morgan State Changes to Approved-announcement to be sent from IESG Evaluation - Defer by Cindy Morgan
2008-06-19
06 Ross Callon [Ballot Position Update] New position, No Objection, has been recorded by Ross Callon
2008-06-19
06 David Ward [Ballot Position Update] New position, No Objection, has been recorded by David Ward
2008-06-19
06 Cullen Jennings [Ballot Position Update] New position, No Objection, has been recorded by Cullen Jennings
2008-06-19
06 Ron Bonica [Ballot Position Update] New position, No Objection, has been recorded by Ron Bonica
2008-06-19
06 Mark Townsley [Ballot Position Update] New position, No Objection, has been recorded by Mark Townsley
2008-06-19
06 Tim Polk [Ballot Position Update] New position, No Objection, has been recorded by Tim Polk
2008-06-18
06 Russ Housley [Ballot Position Update] New position, No Objection, has been recorded by Russ Housley
2008-06-06
06 (System) Removed from agenda for telechat - 2008-06-05
2008-06-04
06 Pasi Eronen [Ballot Position Update] New position, No Objection, has been recorded by Pasi Eronen
2008-06-04
06 Cullen Jennings State Changes to IESG Evaluation - Defer from IESG Evaluation by Cullen Jennings
2008-06-04
06 Jari Arkko [Ballot Position Update] New position, No Objection, has been recorded by Jari Arkko
2008-06-04
06 Jari Arkko
[Ballot comment]
Section 4.2 says:

  Since the application data (e.g. data channel) is managed by the
  RSerPool framework, unsent data (data not yet …
[Ballot comment]
Section 4.2 says:

  Since the application data (e.g. data channel) is managed by the
  RSerPool framework, unsent data (data not yet submitted by
  RSerPool to the underlying transport protocol) is automatically
  redirected to the newly selected pool element upon failover.  If
  the underlying transport layer supports retrieval of unsent data
  (as in SCTP), retrieved unsent data can also be automatically re-
  sent to the newly selected pool element.

This model seems simplistic. Depending on what your application
semantics are, you may want one of the following:
- resending data that has not been *received* by the server yet
- resending data that has not been committed to stable storage by the
  server yet
- resending information requests that have not been answered yet
- resending state-affecting requests that came after latest state
  cookie was received

Perhaps this is something that you can deal with using the callbacks
that the document talks about later. However, its not entirely clear
to me that the specified default behaviour of sending unsent data
is very useful.

This is a just a comment. You may or may not want to deal with this.
I'm fine with the documents going forward as-is, given that they
are experimental.
2008-05-30
06 Magnus Westerlund [Ballot Position Update] New position, Yes, has been recorded for Magnus Westerlund
2008-05-30
06 Magnus Westerlund Ballot has been issued by Magnus Westerlund
2008-05-30
06 Magnus Westerlund Created "Approve" ballot
2008-05-30
06 Magnus Westerlund Placed on agenda for telechat - 2008-06-05 by Magnus Westerlund
2008-05-30
06 Magnus Westerlund State Changes to IESG Evaluation from Waiting for AD Go-Ahead by Magnus Westerlund
2008-05-05
06 (System) New version available: draft-ietf-rserpool-overview-06.txt
2008-04-14
06 (System) State has been changed to Waiting for AD Go-Ahead from In Last Call by system
2008-04-12
06 Samuel Weiler Request for Last Call review by SECDIR Completed. Reviewer: Charles Clancy.
2008-04-10
06 Amanda Baber IANA Last Call comments:

As described in the IANA Considerations section, we understand
this document to have NO IANA Actions.
2008-04-03
06 Samuel Weiler Request for Last Call review by SECDIR is assigned to Charles Clancy
2008-04-03
06 Samuel Weiler Request for Last Call review by SECDIR is assigned to Charles Clancy
2008-03-31
06 Amy Vezza Last call sent
2008-03-31
06 Amy Vezza State Changes to In Last Call from Last Call Requested by Amy Vezza
2008-03-31
06 Magnus Westerlund State Changes to Last Call Requested from AD Evaluation::AD Followup by Magnus Westerlund
2008-03-31
06 Magnus Westerlund Last Call was requested by Magnus Westerlund
2008-03-31
06 (System) Ballot writeup text was added
2008-03-31
06 (System) Last call text was added
2008-03-31
06 (System) Ballot approval text was added
2008-02-22
05 (System) New version available: draft-ietf-rserpool-overview-05.txt
2008-02-07
04 (System) New version available: draft-ietf-rserpool-overview-04.txt
2008-01-22
06 (System) Sub state has been changed to AD Follow up from New Id Needed
2008-01-22
03 (System) New version available: draft-ietf-rserpool-overview-03.txt
2007-10-16
06 Magnus Westerlund State Changes to AD Evaluation::Revised ID Needed from AD Evaluation by Magnus Westerlund
2007-10-09
06 Magnus Westerlund State Changes to AD Evaluation from Publication Requested by Magnus Westerlund
2007-10-04
06 Magnus Westerlund
RFC 4858 Writeup for Rserpool Overview

(1.a)  Who is the Document Shepherd for this document?  Has the
          Document Shepherd personally …
RFC 4858 Writeup for Rserpool Overview

(1.a)  Who is the Document Shepherd for this document?  Has the
          Document Shepherd personally reviewed this version of the
          document and, in particular, does he or she believe this
          version is ready for forwarding to the IESG for publication?

No Document Shepherd has been appointed for this document, the
Working Group Chairs are taking responsibility for reviewing and
Forwarding the document.

  (1.b)  Has the document had adequate review both from key WG members
          and from key non-WG members?  Does the Document Shepherd have
          any concerns about the depth or breadth of the reviews that
          have been performed?

The document has been reviewed by key WG members.

We have had a number of outside reviews, most especially detailed review of the document by Scott Bradner.

  (1.c)  Does the Document Shepherd have concerns that the document
          needs more review from a particular or broader perspective,
          e.g., security, operational complexity, someone familiar with
          AAA, internationalization, or XML?

No concerns that we know of.

  (1.d)  Does the Document Shepherd have any specific concerns or
          issues with this document that the Responsible Area Director
          and/or the IESG should be aware of?  For example, perhaps he
          or she is uncomfortable with certain parts of the document, or
          has concerns whether there really is a need for it.  In any
          event, if the WG has discussed those issues and has indicated
          that it still wishes to advance the document, detail those
          concerns here.  Has an IPR disclosure related to this document
          been filed?  If so, please include a reference to the
          disclosure and summarize the WG discussion and conclusion on
          this issue.

There are no IPR filings on the document.

  (1.e)  How solid is the WG consensus behind this document?  Does it
          represent the strong concurrence of a few individuals, with
          others being silent, or does the WG as a whole understand and
          agree with it?

There is strong WG consensus on the document.

  (1.f)  Has anyone threatened an appeal or otherwise indicated extreme
          discontent?  If so, please summarize the areas of conflict in
          separate email messages to the Responsible Area Director.  (It
          should be in a separate email because this questionnaire is
          entered into the ID Tracker.)

No one has threatened an appeal or otherwise objected.

  (1.g)  Has the Document Shepherd personally verified that the
          document satisfies all ID nits?  (See
          http://www.ietf.org/ID-Checklist.html and
          http://tools.ietf.org/tools/idnits/.)  Boilerplate checks are
          not enough; this check needs to be thorough.  Has the document
          met all formal review criteria it needs to, such as the MIB
          Doctor, media type, and URI type reviews?  If the document
          does not already indicate its intended status at the top of
          the first page, please indicate the intended status here.

Nit checker has been run on the document successfully.  This draft is informational only.

  (1.h)  Has the document split its references into normative and
          informative?  Are there normative references to documents that
          are not ready for advancement or are otherwise in an unclear
          state?  If such normative references exist, what is the
          strategy for their completion?  Are there normative references
          that are downward references, as described in [RFC3967]?  If
          so, list these downward references to support the Area
          Director in the Last Call procedure for them [RFC3967].

Yes, references are split as required. 

  (1.i)  Has the Document Shepherd verified that the document's IANA
          Considerations section exists and is consistent with the body
          of the document?  If the document specifies protocol
          extensions, are reservations requested in appropriate IANA
          registries?  Are the IANA registries clearly identified?  If
          the document creates a new registry, does it define the
          proposed initial contents of the registry and an allocation
          procedure for future registrations?  Does it suggest a
          reasonable name for the new registry?  See [RFC2434].  If the
          document describes an Expert Review process, has the Document
          Shepherd conferred with the Responsible Area Director so that
          the IESG can appoint the needed Expert during IESG Evaluation?

There are no IANA considerations required for this draft. 

  (1.j)  Has the Document Shepherd verified that sections of the
          document that are written in a formal language, such as XML
          code, BNF rules, MIB definitions, etc., validate correctly in
          an automated checker?

There are no sections written in a formal language.

  (1.k)  The IESG approval announcement includes a Document
          Announcement Write-Up.  Please provide such a Document
          Announcement Write-Up.  Recent examples can be found in the
          "Action" announcements for approved documents.  The approval
          announcement contains the following sections:

Technical Summary

This draft provides a high level overview of the Rserpool protocols.

Working Group Summary

The Working Group process was constrained by the relatively small number of people actively involved (although those involved were committed to doing implementations of the protocols).  Otherwise there was little controversy within the group.

Document Quality

There are multiple implementations of both ENRP and ASAP protocols, thanks to participants.  However, there are no vendors that have indicated plans for implementation.  Based on this and the limited number of participants, Experimental track seems appropriate.  We received detailed comments and review from Scott Bradner and his help was greatly appreciated.

Personnel

Document Shepherding is being provided by the Working Group chairs, Maureen Stillman and Lyndon Ong.  Responsible Area Director is Magnus Westerland.
2007-10-04
06 Magnus Westerlund Draft Added by Magnus Westerlund in state Publication Requested
2007-10-04
06 Magnus Westerlund [Note]: 'Doc Shepherd: Maureen Stillman' added by Magnus Westerlund
2007-07-06
02 (System) New version available: draft-ietf-rserpool-overview-02.txt
2007-04-30
01 (System) New version available: draft-ietf-rserpool-overview-01.txt
2006-10-17
00 (System) New version available: draft-ietf-rserpool-overview-00.txt