draft-ietf-rserpool-tcpmapping-00.txt   draft-ietf-rserpool-tcpmapping-01.txt 
Network Working Group P. Conrad Network Working Group P. Conrad
Internet-Draft Temple University Internet-Draft University of Delaware
Expires: December 22, 2003 P. Lei Expires: June 18, 2004 P. Lei
Cisco Systems, Inc. Cisco Systems, Inc.
June 23, 2003 December 19, 2003
TCP Mapping for Reliable Server Pooling Failover Mode TCP Mapping for Reliable Server Pooling Enhanced Mode
draft-ietf-rserpool-tcpmapping-00.txt draft-ietf-rserpool-tcpmapping-01.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts. groups may also distribute working documents as Internet-Drafts.
skipping to change at page 1, line 32 skipping to change at page 1, line 32
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at http:// The list of current Internet-Drafts can be accessed at http://
www.ietf.org/ietf/1id-abstracts.txt. www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on December 22, 2003. This Internet-Draft will expire on June 18, 2004.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
Abstract Abstract
This memo defines the shim protocol that maps the requirements of the This memo defines the shim protocol that maps the requirements of the
ASAP protocol [5] to the capabilities of the TCP protocol [7]. In ASAP protocol [5] to the capabilities of the TCP protocol [7]. In
particular, this shim protocol adds the following capabiltiies that particular, this shim protocol adds the following capabilties that
are required by ASAP, but not provided by TCP: (1) message are required by ASAP, but not provided by TCP: (1) message
orientation, (2) heartbeat messages, (3) multiple streams, and (4) orientation, (2) heartbeat messages, (3) multiple streams, and (4)
undelivered message retrieval (if provided). undelivered message retrieval (if provided).
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1 Brief overview of RSerPool . . . . . . . . . . . . . . . . . . 3 1.1 Brief overview of RSerPool . . . . . . . . . . . . . . . . . . 3
1.2 Role of the TCP Mapping Protocol . . . . . . . . . . . . . . . 3 1.2 Role of the TCP Mapping Protocol . . . . . . . . . . . . . . . 3
1.3 Consistency of Service . . . . . . . . . . . . . . . . . . . . 5 1.3 Consistency of Service . . . . . . . . . . . . . . . . . . . . 5
2. Conventions Used In This Document . . . . . . . . . . . . . . 6 2. Conventions Used In This Document . . . . . . . . . . . . . . 6
3. Packet Format . . . . . . . . . . . . . . . . . . . . . . . . 6 3. Packet Format . . . . . . . . . . . . . . . . . . . . . . . . 6
3.1 Basic Chunk Format . . . . . . . . . . . . . . . . . . . . . . 6 3.1 Basic Chunk Format . . . . . . . . . . . . . . . . . . . . . . 6
3.2 DATA Chunk . . . . . . . . . . . . . . . . . . . . . . . . . . 8 3.2 DATA Chunk . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.3 INIT Chunk . . . . . . . . . . . . . . . . . . . . . . . . . . 10 3.3 INIT Chunk . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.4 ACK Chunk . . . . . . . . . . . . . . . . . . . . . . . . . . 13 3.4 ACK Chunk . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.5 HEARTBEAT Chunk . . . . . . . . . . . . . . . . . . . . . . . 13 3.5 HEARTBEAT Chunk . . . . . . . . . . . . . . . . . . . . . . . 14
3.6 HEARTBEAT ACK Chunk . . . . . . . . . . . . . . . . . . . . . 14 3.6 HEARTBEAT ACK Chunk . . . . . . . . . . . . . . . . . . . . . 15
4. Protocol Operations . . . . . . . . . . . . . . . . . . . . . 15 4. Protocol Operations . . . . . . . . . . . . . . . . . . . . . 16
5. Security Considerations . . . . . . . . . . . . . . . . . . . 15 5. Security Considerations . . . . . . . . . . . . . . . . . . . 17
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 16 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 17
References . . . . . . . . . . . . . . . . . . . . . . . . . . 16 References . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 16 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 18
Intellectual Property and Copyright Statements . . . . . . . . 18 Intellectual Property and Copyright Statements . . . . . . . . 19
1. Introduction 1. Introduction
This memo defines the shim protocol that maps the requirements of the This memo defines the shim protocol that maps the requirements of the
ASAP protocol [5] to the capabilities of the TCP protocol [7]. See ASAP protocol [5] to the capabilities of the TCP protocol [7]. See
[6] for details of these mapping requirements. [6] for details of these mapping requirements.
1.1 Brief overview of RSerPool 1.1 Brief overview of RSerPool
The RSerPool framework is designed to provide high availability for The RSerPool framework is designed to provide high availability for
skipping to change at page 15, line 43 skipping to change at page 17, line 7
[TBD: In this section describe the basic operation of the protocol. [TBD: In this section describe the basic operation of the protocol.
Most of this is already pretty much spelled out in the descriptions Most of this is already pretty much spelled out in the descriptions
of the packets, but a few details need to be ironed out, mainly how of the packets, but a few details need to be ironed out, mainly how
and under what conditions the TCP mapping layer decides that a and under what conditions the TCP mapping layer decides that a
failure occured. Perhaps the upper layer needs to be able to specify failure occured. Perhaps the upper layer needs to be able to specify
a timeout value for data, and a heartbeat interval? Are there any a timeout value for data, and a heartbeat interval? Are there any
other details that need to specified in this section?] other details that need to specified in this section?]
5. Security Considerations 5. Security Considerations
[Open Issue TBD: Security issues are not discussed in this memo at There are no known additional security considerations over what is
this time, but will be added in a later version of this draft.] already present for TCP.
6. IANA Considerations 6. IANA Considerations
[Open Issue TBD: Will there be an enumeration of the various [Open Issue TBD: Will there be an enumeration of the various
transport layer mappings that must be registered with IANA?] transport layer mappings that must be registered with IANA?]
7. Acknowledgements 7. Acknowledgements
References References
[1] Xie, Q. and M. Tuexen, "Architecture for Reliable Server [1] Tuexen, M. and Q. Xie, "Architecture for Reliable Server
Pooling", draft-ietf-rserpool-arch-05 (work in progress), March Pooling", draft-ietf-rserpool-arch-07 (work in progress),
2003. October 2003.
[2] Bradner, S., "Key words for use in RFCs to Indicate Requirement [2] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997. Levels", BCP 14, RFC 2119, March 1997.
[3] Loughney, J., "Comparison of Protocols for Reliable Server [3] Loughney, J., "Comparison of Protocols for Reliable Server
Pooling", draft-ietf-rserpool-comp-05 (work in progress), Pooling", draft-ietf-rserpool-comp-07 (work in progress),
November 2002. October 2003.
[4] Stillman, M., Xie, Q. and R. Stewart, "Enpoint Name Resolution [4] Xie, Q., Stewart, R. and M. Stillman, "Enpoint Name Resolution
Protocol (ENRP)", draft-ietf-rserpool-enrp-06 (work in Protocol (ENRP)", draft-ietf-rserpool-enrp-07 (work in
progress), May 2003. progress), October 2003.
[5] Stillman, M., Xie, Q., Tuexen, M. and R. Stewart, "Aggregate [5] Stewart, R., Xie, Q., Stillman, M. and M. Tuexen, "Aggregate
Server Access Protocol (ASAP)", draft-ietf-rserpool-asap-07 Server Access Protocol (ASAP)", draft-ietf-rserpool-asap-08
(work in progress), May 2003. (work in progress), October 2003.
[6] Conrad, P. and P. Lei, "Services Provided By Reliable Server [6] Conrad, P. and P. Lei, "Services Provided By Reliable Server
Pooling", draft-conrad-rserpool-service-02 (work in progress), Pooling", draft-ietf-rserpool-service-00 (work in progress),
October 2002. December 2003.
[7] Postel, J., "Transmission Control Protocol", STD 7, RFC 793, [7] Postel, J., "Transmission Control Protocol", STD 7, RFC 793,
September 1981. September 1981.
[8] Stewart, R., Xie, Q., Morneault, K., Sharp, C., Schwarzbauer, [8] Stewart, R., Xie, Q., Morneault, K., Sharp, C., Schwarzbauer,
H., Taylor, T., Rytina, I., Kalla, M., Zhang, L. and V. Paxson, H., Taylor, T., Rytina, I., Kalla, M., Zhang, L. and V. Paxson,
"Stream Control Transmission Protocol", RFC 2960, October 2000. "Stream Control Transmission Protocol", RFC 2960, October 2000.
Authors' Addresses Authors' Addresses
Phillip T. Conrad Phillip T. Conrad
Temple University University of Delaware
CIS Department Dept. of Computer and Information Sciences
Room 303, Computer Building (038-24) 103 Smith Hall
1805 N. Broad St. Newark, DE 19716
Philadelphia, PA 19122
US US
Phone: +1 215 204 7910 Phone: +1 302 831 8622
EMail: conrad@acm.org EMail: conrad@acm.org
URI: http://www.cis.temple.edu/~conrad URI: http://udel.edu/~pconrad
Peter Lei Peter Lei
Cisco Systems, Inc. Cisco Systems, Inc.
8735 W Higgins Rd, Suite 300 8735 W Higgins Rd, Suite 300
Chicago, IL 60631 Chicago, IL 60631
US US
Phone: +1 847 870 7201 Phone: +1 847 870 7201
EMail: peterlei@cisco.com EMail: peterlei@cisco.com
Intellectual Property Statement Intellectual Property Statement
skipping to change at page 19, line 7 skipping to change at page 20, line 7
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assignees. revoked by the Internet Society or its successors or assignees.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/