Internet-Drafts | 9 Nov 2007 20:15
Picon
Favicon

I-D ACTION:draft-ietf-rserpool-policies-07.txt

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Reliable Server Pooling Working Group of the IETF.

	Title		: Reliable Server Pooling Policies
	Author(s)	: M. Tuexen, T. Dreibholz
	Filename	: draft-ietf-rserpool-policies-07.txt
	Pages		: 16
	Date		: 2007-11-9
	
This document describes server pool policies for Reliable Server
   Pooling including considerations for implementing them at ENRP
   servers and pool users.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rserpool-policies-07.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request <at> ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-rserpool-policies-07.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
(Continue reading)

Internet-Drafts | 17 Nov 2007 14:50
Picon
Favicon

I-D Action:draft-ietf-rserpool-common-param-14.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Reliable Server Pooling Working Group of the IETF.

	Title           : Aggregate Server Access Protocol (ASAP) and Endpoint Handlespace Redundancy Protocol (ENRP) Parameters
	Author(s)       : R. Stewart, et al.
	Filename        : draft-ietf-rserpool-common-param-14.txt
	Pages           : 28
	Date            : 2007-11-17

This document details the parameters of the Aggregate Server Access
Protocol (ASAP) and Endpoint Handlespace Redundancy Protocol (ENRP)
protocols defined within the Reliable Server Pooling (RSerPool)
architecture.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rserpool-common-param-14.txt

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request <at> ietf.org with the word unsubscribe in the body of 
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then
	"get draft-ietf-rserpool-common-param-14.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
(Continue reading)

Michael Tuexen | 17 Nov 2007 14:55
Picon

Re: AD comments on draft-ietf-rserpool-enrp-17, draft-ietf-rserpool-asap-17, draft-ietf-rserpool-common-param-13

Hi Magnus,

here are the comments to your comments regarding
draft-ietf-rserpool-common-param-13.txt

My comments are based on a telephone conference between
the authors.

I have removed the other text from the mail...

A new version addressing all your comments has
been submitted and is available at
http://www.ietf.org/internet-drafts/draft-ietf-rserpool-common-param-14.txt

Best regards
Michael

On Oct 16, 2007, at 6:37 PM, Magnus Westerlund wrote:

>
> COMMON:
>
> C1. Page 6: There is a editors note that should be removed.
Done.
>
>
> C2. Section 3.3: Is it a SCTP limitation that there needs to be the  
> same
> port on all the interfaces or this a limitation created in this
> document? Will not this be problematic to get the same port over all
(Continue reading)

Michael Tuexen | 19 Nov 2007 02:49
Picon

Re: AD comments on draft-ietf-rserpool-enrp-17, draft-ietf-rserpool-asap-17, draft-ietf-rserpool-common-param-13

Hi Magnus,

please see my comments regarding the ASAP document in-line. Please
note that my comments are based on a telephone conference between
the authors.

A new version addressing all your comments has been uploaded and
is available at
http://www.ietf.org/internet-drafts/draft-ietf-rserpool-asap-18.txt

I'll remove text from your mail not related to ASAP.

Best regards
Michael

On Oct 16, 2007, at 6:37 PM, Magnus Westerlund wrote:

> Hi,
>
> I will bring up all my comments on the core protocol specs in this
> email. I will do my best to keep it structured.
>
> Generally:
>
> G1. There is some confusion over text and where it is defined. I think
> the document would benefit from trying to be more clear on what is  
> used
> in what communications scopes. It is also important to be clear on  
> when
> one is referring to a process in another scope that result in a
(Continue reading)

Internet-Drafts | 19 Nov 2007 02:50
Picon
Favicon

I-D Action:draft-ietf-rserpool-asap-18.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Reliable Server Pooling Working Group of the IETF.

	Title           : Aggregate Server Access Protocol (ASAP)
	Author(s)       : R. Stewart, et al.
	Filename        : draft-ietf-rserpool-asap-18.txt
	Pages           : 56
	Date            : 2007-11-18

Aggregate Server Access Protocol (ASAP) in conjunction with the
Endpoint Handlespace Redundancy Protocol (ENRP)
[I-D.ietf-rserpool-enrp] provides a high availability data transfer
mechanism over IP networks.  ASAP uses a handle-based addressing
model which isolates a logical communication endpoint from its IP
address(es), thus effectively eliminating the binding between the
communication endpoint and its physical IP address(es) which normally
constitutes a single point of failure.

In addition, ASAP defines each logical communication destination as a
pool, providing full transparent support for server-pooling and load
sharing.  It also allows dynamic system scalability - members of a
server pool can be added or removed at any time without interrupting
the service.

ASAP is designed to take full advantage of the network level
redundancy provided by the Stream Transmission Control Protocol
(SCTP) [RFC4960].  Each transport protocol, other than SCTP, MUST
have an accompanying transport mapping document.  It should be noted
that ASAP messages passed between PE's and ENRP servers MUST use the
SCTP transport protocol.
(Continue reading)

Magnus Westerlund | 20 Nov 2007 16:29
Picon
Favicon

Re: AD comments on draft-ietf-rserpool-enrp-17, draft-ietf-rserpool-asap-17, draft-ietf-rserpool-common-param-13

Thanks,

I have removed everything that seems clear to me.

Michael Tuexen skrev:
> Hi Magnus,
> 
> here are the comments to your comments regarding
> draft-ietf-rserpool-common-param-13.txt
> 
> My comments are based on a telephone conference between
> the authors.
> 
> I have removed the other text from the mail...
> 
>>
>>
>> C2. Section 3.3: Is it a SCTP limitation that there needs to be the same
>> port on all the interfaces or this a limitation created in this
>> document? Will not this be problematic to get the same port over all
>> interfaces?
> I would not call it a limitation of SCTP, but an SCTP endpoint has
> one or more IP-addresses (it can be a mixture of IPv4 and IPv6
> addresses) and one single port number. This feature is not related
> to RSerPool and the message format is correct.

Okay, that it is correct is the only thing I needed to know.

>>
>>
(Continue reading)

Magnus Westerlund | 20 Nov 2007 16:58
Picon
Favicon

Re: AD comments on draft-ietf-rserpool-enrp-17, draft-ietf-rserpool-asap-17, draft-ietf-rserpool-common-param-13

I have reviewed the changes. Some comments and unfortunately I think
some few additional fixes are needed.

Michael Tuexen skrev:
> Hi Magnus,
> 
> please see my comments regarding the ASAP document in-line. Please
> note that my comments are based on a telephone conference between
> the authors.
> 
> A new version addressing all your comments has been uploaded and
> is available at
> http://www.ietf.org/internet-drafts/draft-ietf-rserpool-asap-18.txt
> 
> I'll remove text from your mail not related to ASAP.
> 
> Best regards
> Michael
> 
> On Oct 16, 2007, at 6:37 PM, Magnus Westerlund wrote:
> 
>> Hi,
>>
>> I will bring up all my comments on the core protocol specs in this
>> email. I will do my best to keep it structured.
>>
>> Generally:
>>
>> G1. There is some confusion over text and where it is defined. I think
>> the document would benefit from trying to be more clear on what is used
(Continue reading)

Michael Tuexen | 20 Nov 2007 18:11
Picon

Re: AD comments on draft-ietf-rserpool-enrp-17, draft-ietf-rserpool-asap-17, draft-ietf-rserpool-common-param-13

Hi Magnus,

is changing the DCCP parameter to

  0                   1                   2                   3
  0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|        Type = 0x3             |      Length = variable        |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|         DCCP port             |          (reserved)           |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                      DCCP service code                        |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
:                     IPv4 or IPv6 Address                      :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

what you want?

Best regards
Michael

On Nov 20, 2007, at 4:29 PM, Magnus Westerlund wrote:

> Thanks,
>
> I have removed everything that seems clear to me.
>
> Michael Tuexen skrev:
>> Hi Magnus,
>>
(Continue reading)

Michael Tuexen | 20 Nov 2007 18:36
Picon

Re: AD comments on draft-ietf-rserpool-enrp-17, draft-ietf-rserpool-asap-17, draft-ietf-rserpool-common-param-13

Hi Magnus,

see my comments in-line.

Best regards
Michael

On Nov 20, 2007, at 4:58 PM, Magnus Westerlund wrote:

> I have reviewed the changes. Some comments and unfortunately I think
> some few additional fixes are needed.
No problem, since they improve the document they are welcome!
>
>
>
> Michael Tuexen skrev:
>> Hi Magnus,
>>
>> please see my comments regarding the ASAP document in-line. Please
>> note that my comments are based on a telephone conference between
>> the authors.
>>
>> A new version addressing all your comments has been uploaded and
>> is available at
>> http://www.ietf.org/internet-drafts/draft-ietf-rserpool-asap-18.txt
>>
>> I'll remove text from your mail not related to ASAP.
>>
>> Best regards
>> Michael
(Continue reading)

Internet-Drafts | 20 Nov 2007 20:15
Picon
Favicon

I-D ACTION:draft-ietf-rserpool-enrp-18.txt

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Reliable Server Pooling Working Group of the IETF.

	Title		: Endpoint Handlespace Redundancy Protocol (ENRP)
	Author(s)	: Q. Xie, R. Stewart, M. Stillman, M. Tuexen, A. Silverton
	Filename	: draft-ietf-rserpool-enrp-18.txt
	Pages		: 41
	Date		: 2007-11-20
	
The Endpoint Handlespace Redundancy Protocol (ENRP) is designed to
   work in conjunction with the Aggregate Server Access Protocol (ASAP)
   to accomplish the functionality of the Reliable Server Pooling
   (RSerPool) requirements and architecture.  Within the operational
   scope of RSerPool, ENRP defines the procedures and message formats of
   a distributed, fault-tolerant registry service for storing,
   bookkeeping, retrieving, and distributing pool operation and
   membership information.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rserpool-enrp-18.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request <at> ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
(Continue reading)


Gmane