From mailman-bounces@ietf.org  Fri Oct  1 10:00:59 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01125
	for <rserpool-archive@lists.ietf.org>; Fri, 1 Oct 2004 10:00:59 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CDKAv-00066C-8E
	for rserpool-archive@lists.ietf.org; Fri, 01 Oct 2004 05:58:05 -0400
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@ietf.org
To: rserpool-archive@ietf.org
X-No-Archive: yes
Message-ID: <mailman.26169.1096622541.3166.mailman@lists.ietf.org>
Date: Fri, 01 Oct 2004 05:22:21 -0400
Precedence: bulk
X-BeenThere: mailman@lists.ietf.org
X-Mailman-Version: 2.1.5
List-Id: Mailman site list <mailman.lists.ietf.org>
X-List-Administrivia: yes
Sender: mailman-bounces@ietf.org
Errors-To: mailman-bounces@ietf.org
Content-Transfer-Encoding: 7bit

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, mailman-request@ietf.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

**********************************************************************

NOTE WELL:

Any submission to the IETF intended by the Contributor for publication
as all or part of an IETF Internet-Draft or RFC and any statement made
within the context of an IETF activity is considered an "IETF
Contribution". Such statements include oral statements in IETF
sessions, as well as written and electronic communications made at any
time or place, which are addressed to:

o the IETF plenary session, o any IETF working group or portion
thereof, o the IESG, or any member thereof on behalf of the IESG, o
the IAB or any member thereof on behalf of the IAB, o any IETF mailing
list, including the IETF list itself, any working group
  or design team list, or any other list functioning under IETF
auspices,
o the RFC Editor or the Internet-Drafts function

All IETF Contributions are subject to the rules of RFC 3667 and RFC
3668.

Statements made outside of an IETF session, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not IETF Contributions in the context
of this notice.

Please consult RFC 3667 for details.

*******************************************************************************


If you have questions, problems, comments, etc, send them to
mailman-owner@ietf.org.  Thanks!

Passwords for rserpool-archive@lists.ietf.org:

List                                     Password // URL
----                                     --------  
rserpool@ietf.org                        RVOD      
https://www1.ietf.org/mailman/options/rserpool/rserpool-archive%40lists.ietf.org


From rserpool-bounces@ietf.org  Mon Oct 11 17:33:57 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01082
	for <rserpool-archive@lists.ietf.org>; Mon, 11 Oct 2004 17:33:57 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CH7Zy-0004GZ-Op; Mon, 11 Oct 2004 17:19:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CH74O-0002pW-8B
	for rserpool@megatron.ietf.org; Mon, 11 Oct 2004 16:47:00 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23253
	for <rserpool@ietf.org>; Mon, 11 Oct 2004 16:46:57 -0400 (EDT)
Received: from motgate4.mot.com ([144.189.100.102])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CH7Ev-0003DU-CW
	for rserpool@ietf.org; Mon, 11 Oct 2004 16:57:54 -0400
Received: from az33exr02.mot.com (az33exr02.mot.com [10.64.251.232])
	by motgate4.mot.com (8.12.11/Motgate4) with ESMTP id i9BKm9tQ017822
	for <rserpool@ietf.org>; Mon, 11 Oct 2004 13:48:09 -0700 (MST)
Received: from il02exm11.corp.mot.com (il02exm11.corp.mot.com [10.0.111.22])
	by az33exr02.mot.com (Motorola/az33exr02) with ESMTP id i9BKiWNM007004
	for <rserpool@ietf.org>; Mon, 11 Oct 2004 15:44:33 -0500
Received: by il02exm11 with Internet Mail Service (5.5.2657.72)
	id <TD9Z3V93>; Mon, 11 Oct 2004 15:46:52 -0500
Message-ID: <6F8DFFA2C996D711945800065BFC9E4A10C1FBBA@il02exm11>
From: Johnson Walter-CWJ002 <Walter.Johnson@motorola.com>
To: "'rserpool@ietf.org'" <rserpool@ietf.org>
Date: Mon, 11 Oct 2004 15:46:51 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
Subject: [Rserpool] PEER_ERROR message
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Sender: rserpool-bounces@ietf.org
Errors-To: rserpool-bounces@ietf.org

Any reference to the PEER_ERROR message should be removed from the ASAP protocol document since I believe it is not an ASAP message. It is an ENRP message. In fact, both documents define PEER_ERROR but completely differently. I think it simply got added into the ASAP document sometime accidentally and has remained there ever since. 

The locations within the ASAP protocol document where it should be removed are the TOC, the message list in section 3, and section 3.11 should be deleted. Within the ENRP document, I couldn't find the use of the PEER_ERROR message easily since it is mislabeled ENRP_ERROR in section 4.12. 

Can this be fixed?

Thanks
Walter

_______________________________________________
rserpool mailing list
rserpool@ietf.org
https://www1.ietf.org/mailman/listinfo/rserpool


From rserpool-bounces@ietf.org  Tue Oct 12 05:09:45 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01782
	for <rserpool-archive@lists.ietf.org>; Tue, 12 Oct 2004 05:09:45 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CHIbG-0007id-MK; Tue, 12 Oct 2004 05:05:43 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CHIWf-0006ce-Vn
	for rserpool@megatron.ietf.org; Tue, 12 Oct 2004 05:00:58 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01288
	for <rserpool@ietf.org>; Tue, 12 Oct 2004 05:00:55 -0400 (EDT)
Received: from ms.iem.uni-duisburg-essen.de ([132.252.150.1]
	helo=pilz.exp-math.uni-essen.de)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHIhM-0000Of-W9
	for rserpool@ietf.org; Tue, 12 Oct 2004 05:12:01 -0400
Received: from kappes.exp-math.uni-essen.de (kappes.exp-math.uni-essen.de
	[132.252.150.151])
	by pilz.exp-math.uni-essen.de (8.12.10/8.12.8) with ESMTP id
	i9C90iOp065804; Tue, 12 Oct 2004 11:00:44 +0200
From: Thomas Dreibholz <dreibh@exp-math.uni-essen.de>
Organization: University of Essen, Institute for Experimental Mathematics
To: rserpool@ietf.org
Subject: Re: [Rserpool] PEER_ERROR message
Date: Tue, 12 Oct 2004 11:00:39 +0200
User-Agent: KMail/1.6.1
References: <6F8DFFA2C996D711945800065BFC9E4A10C1FBBA@il02exm11>
In-Reply-To: <6F8DFFA2C996D711945800065BFC9E4A10C1FBBA@il02exm11>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: Text/Plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable
Message-Id: <200410121100.43398.dreibh@exp-math.uni-essen.de>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Content-Transfer-Encoding: quoted-printable
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Sender: rserpool-bounces@ietf.org
Errors-To: rserpool-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 11 October 2004 22:46, Johnson Walter-CWJ002 wrote:
> Any reference to the PEER_ERROR message should be removed from the ASAP
> protocol document since I believe it is not an ASAP message.

It is useful to have this message type in ASAP, because e.g. a component (N=
S,=20
PE or PU) could receive a bad message via ASAP. Then, it can report the=20
sender that it does not understand/accept this message via a PEER_ERROR. Th=
is=20
is useful for debugging.

To make ASAP and ENRP PEER_ERROR more consistent, their definitions and=20
especially the message type number (currently: 0x0e or ASAP, 0x0b for ENRP)=
=20
could be unified. For example, the message number could be 0xff for both.


Best regards
=2D --=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
 Dipl.-Inform. Thomas Dreibholz

 University of Essen,                            Room ES210
 Inst. for Experimental Mathematics              Ellernstra=DFe 29
 Computer Networking Technology Group            D-45326 Essen/Germany
=2D -----------------------------------------------------------------------
 E-Mail:     dreibh@exp-math.uni-essen.de
 Homepage:   http://www.exp-math.uni-essen.de/~dreibh
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBa50632BbsHYPLWURAg5hAJwPJxLFPfWhNx0afzjntqKl/rmgagCdGO+G
EDx/otU5qMtWX79xZKnCSxU=3D
=3DK88g
=2D----END PGP SIGNATURE-----

_______________________________________________
rserpool mailing list
rserpool@ietf.org
https://www1.ietf.org/mailman/listinfo/rserpool


From rserpool-bounces@ietf.org  Tue Oct 12 10:44:45 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25753
	for <rserpool-archive@lists.ietf.org>; Tue, 12 Oct 2004 10:44:45 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CHNj9-0002Sj-6Z; Tue, 12 Oct 2004 10:34:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CHNWd-0006jW-3N
	for rserpool@megatron.ietf.org; Tue, 12 Oct 2004 10:21:15 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22583
	for <rserpool@ietf.org>; Tue, 12 Oct 2004 10:21:12 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHNdb-00060h-Be
	for rserpool@ietf.org; Tue, 12 Oct 2004 10:28:28 -0400
Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133])
	by motgate8.mot.com (Motorola/Motgate8) with ESMTP id i9CEITh2005581
	for <rserpool@ietf.org>; Tue, 12 Oct 2004 07:18:29 -0700 (MST)
Received: from il02exm11.corp.mot.com (il02exm11.corp.mot.com [10.0.111.22])
	by il06exr03.mot.com (Motorola/il06exr03) with ESMTP id i9CEHALw017121
	for <rserpool@ietf.org>; Tue, 12 Oct 2004 09:17:10 -0500
Received: by il02exm11 with Internet Mail Service (5.5.2657.72)
	id <TD9ZPM2V>; Tue, 12 Oct 2004 09:17:10 -0500
Message-ID: <6F8DFFA2C996D711945800065BFC9E4A10D06123@il02exm11>
From: Johnson Walter-CWJ002 <Walter.Johnson@motorola.com>
To: "'Thomas Dreibholz'" <dreibh@exp-math.uni-essen.de>,
        "'rserpool@ietf.org'" <rserpool@ietf.org>
Subject: RE: [Rserpool] PEER_ERROR message
Date: Tue, 12 Oct 2004 09:17:10 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Sender: rserpool-bounces@ietf.org
Errors-To: rserpool-bounces@ietf.org

Comments inline.

Thomas Dreibholz <mailto:dreibh@exp-math.uni-essen.de> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Monday 11 October 2004 22:46, Johnson Walter-CWJ002 wrote:
>> Any reference to the PEER_ERROR message should be removed from the
>> ASAP protocol document since I believe it is not an ASAP message.
> 
> It is useful to have this message type in ASAP, because e.g. a
> component (NS, PE or PU) could receive a bad message via ASAP. Then,
> it can report the sender that it does not understand/accept this
> message via a PEER_ERROR. This is useful for debugging.
> 

I understand this could be case but there has not been a procedure for its use defined within the ASAP document unlike there has been for ENRP (section 4.12). This fact combined with the fact the message is prefaced with PEER_* which is typical of all ENRP messages indicated to me this message may have been misplaced. If the group agrees to keep this message then I would lobby for a new section explaining its use within the ASAP document. 

> To make ASAP and ENRP PEER_ERROR more consistent, their definitions
> and especially the message type number (currently: 0x0e or ASAP, 0x0b
> for ENRP) could be unified. For example, the message number could be
> 0xff for both. 
> 

One could lobby for aligning the PEER_ERROR messages or one could lobby for two unique message PEER_ERROR for ENRP and ASAP_ERROR for ASAP since the protocols are unique and they signal two unique cases. In addition, if different parameters are required then I would think the messages should be unique. 

What is everyone's opinion? 

_______________________________________________
rserpool mailing list
rserpool@ietf.org
https://www1.ietf.org/mailman/listinfo/rserpool


From rserpool-bounces@ietf.org  Tue Oct 12 10:49:12 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26436
	for <rserpool-archive@lists.ietf.org>; Tue, 12 Oct 2004 10:49:12 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CHNjd-0002ug-Ng; Tue, 12 Oct 2004 10:34:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CHNdU-0000GO-O8
	for rserpool@megatron.ietf.org; Tue, 12 Oct 2004 10:28:20 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23835
	for <rserpool@ietf.org>; Tue, 12 Oct 2004 10:28:19 -0400 (EDT)
Received: from dpc674425142.direcpc.com ([67.44.25.142]
	helo=stewart.chicago.il.us)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHNoD-0006R4-9O
	for rserpool@ietf.org; Tue, 12 Oct 2004 10:39:28 -0400
Received: from stewart.chicago.il.us (localhost [127.0.0.1])
	by stewart.chicago.il.us (8.12.9p2/8.12.8) with ESMTP id i9CERPKG017773;
	Tue, 12 Oct 2004 10:27:47 -0400 (EDT)
	(envelope-from randall@stewart.chicago.il.us)
Message-ID: <416BE972.10207@stewart.chicago.il.us>
Date: Tue, 12 Oct 2004 10:25:54 -0400
From: Randall Stewart <randall@stewart.chicago.il.us>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040429
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Thomas Dreibholz <dreibh@exp-math.uni-essen.de>
Subject: Re: [Rserpool] PEER_ERROR message
References: <6F8DFFA2C996D711945800065BFC9E4A10C1FBBA@il02exm11>
	<200410121100.43398.dreibh@exp-math.uni-essen.de>
In-Reply-To: <200410121100.43398.dreibh@exp-math.uni-essen.de>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by stewart.chicago.il.us
	id i9CERPKG017773
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Content-Transfer-Encoding: quoted-printable
Cc: rserpool@ietf.org
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Sender: rserpool-bounces@ietf.org
Errors-To: rserpool-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

Thomas.. I have taken this
suggestion.

Next revision we will make PEER_ERROR the same
error number (0xe)

and then change all reference to ENRP_ERROR
to PEER_ERROR

R


Thomas Dreibholz wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> On Monday 11 October 2004 22:46, Johnson Walter-CWJ002 wrote:
>=20
>>Any reference to the PEER_ERROR message should be removed from the ASAP
>>protocol document since I believe it is not an ASAP message.
>=20
>=20
> It is useful to have this message type in ASAP, because e.g. a componen=
t (NS,=20
> PE or PU) could receive a bad message via ASAP. Then, it can report the=
=20
> sender that it does not understand/accept this message via a PEER_ERROR=
. This=20
> is useful for debugging.
>=20
> To make ASAP and ENRP PEER_ERROR more consistent, their definitions and=
=20
> especially the message type number (currently: 0x0e or ASAP, 0x0b for E=
NRP)=20
> could be unified. For example, the message number could be 0xff for bot=
h.
>=20
>=20
> Best regards
> - --=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>  Dipl.-Inform. Thomas Dreibholz
>=20
>  University of Essen,                            Room ES210
>  Inst. for Experimental Mathematics              Ellernstra=DFe 29
>  Computer Networking Technology Group            D-45326 Essen/Germany
> - ---------------------------------------------------------------------=
--
>  E-Mail:     dreibh@exp-math.uni-essen.de
>  Homepage:   http://www.exp-math.uni-essen.de/~dreibh
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (GNU/Linux)
>=20
> iD8DBQFBa50632BbsHYPLWURAg5hAJwPJxLFPfWhNx0afzjntqKl/rmgagCdGO+G
> EDx/otU5qMtWX79xZKnCSxU=3D
> =3DK88g
> -----END PGP SIGNATURE-----
>=20
> _______________________________________________
> rserpool mailing list
> rserpool@ietf.org
> https://www1.ietf.org/mailman/listinfo/rserpool
>=20
>=20
>=20


_______________________________________________
rserpool mailing list
rserpool@ietf.org
https://www1.ietf.org/mailman/listinfo/rserpool


From rserpool-bounces@ietf.org  Tue Oct 12 13:46:33 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13291
	for <rserpool-archive@lists.ietf.org>; Tue, 12 Oct 2004 13:46:33 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CHQgG-0002EH-T4; Tue, 12 Oct 2004 13:43:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CHQQy-0006cd-W4
	for rserpool@megatron.ietf.org; Tue, 12 Oct 2004 13:27:37 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11386
	for <rserpool@ietf.org>; Tue, 12 Oct 2004 13:27:34 -0400 (EDT)
Received: from mail-n.franken.de
	([193.175.24.27] helo=ilsa.franken.de ident=postfix)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHQbj-0002nc-Ni
	for rserpool@ietf.org; Tue, 12 Oct 2004 13:38:46 -0400
Received: from [192.168.1.224] (pD9FF1AFE.dip.t-dialin.net [217.255.26.254])
	by ilsa.franken.de (Postfix) with ESMTP
	id 228C3245F8; Tue, 12 Oct 2004 19:27:28 +0200 (CEST)
	(KNF account authenticated via SMTP-AUTH)
In-Reply-To: <416BE972.10207@stewart.chicago.il.us>
References: <6F8DFFA2C996D711945800065BFC9E4A10C1FBBA@il02exm11>
	<200410121100.43398.dreibh@exp-math.uni-essen.de>
	<416BE972.10207@stewart.chicago.il.us>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
Message-Id: <F9644AB0-1C73-11D9-8955-000D932C78D8@lurchi.franken.de>
Content-Transfer-Encoding: quoted-printable
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Subject: Re: [Rserpool] PEER_ERROR message
Date: Tue, 12 Oct 2004 19:27:21 +0200
To: Randall Stewart <randall@stewart.chicago.il.us>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
Content-Transfer-Encoding: quoted-printable
Cc: Thomas Dreibholz <dreibh@exp-math.uni-essen.de>, rserpool@ietf.org
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Sender: rserpool-bounces@ietf.org
Errors-To: rserpool-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

Dear all,

just a general thought.

we decided to align the parameters between APAP and ENRP, that is why
we have the common parameter ID. As far as I think, we also decided not
to align the messages between ASAP and ENRP. This might become more
complex in the future.

So I'm not sure what it helps in aligning the type number, the error =20
causes
will be different and the code will also be different...

Best regards
Michael

On Oct 12, 2004, at 16:25 Uhr, Randall Stewart wrote:

> Thomas.. I have taken this
> suggestion.
>
> Next revision we will make PEER_ERROR the same
> error number (0xe)
>
> and then change all reference to ENRP_ERROR
> to PEER_ERROR
>
> R
>
>
> Thomas Dreibholz wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>> On Monday 11 October 2004 22:46, Johnson Walter-CWJ002 wrote:
>>> Any reference to the PEER_ERROR message should be removed from the =20=

>>> ASAP
>>> protocol document since I believe it is not an ASAP message.
>> It is useful to have this message type in ASAP, because e.g. a =20
>> component (NS, PE or PU) could receive a bad message via ASAP. Then, =20=

>> it can report the sender that it does not understand/accept this =20
>> message via a PEER_ERROR. This is useful for debugging.
>> To make ASAP and ENRP PEER_ERROR more consistent, their definitions =20=

>> and especially the message type number (currently: 0x0e or ASAP, 0x0b =
=20
>> for ENRP) could be unified. For example, the message number could be =20=

>> 0xff for both.
>> Best regards
>> - -- =20
>> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=20
>> =3D
>>  Dipl.-Inform. Thomas Dreibholz
>>  University of Essen,                            Room ES210
>>  Inst. for Experimental Mathematics              Ellernstra=DFe 29
>>  Computer Networking Technology Group            D-45326 =
Essen/Germany
>> - =20
>> =
----------------------------------------------------------------------=20=

>> -
>>  E-Mail:     dreibh@exp-math.uni-essen.de
>>  Homepage:   http://www.exp-math.uni-essen.de/~dreibh
>> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=20
>> =3D
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.2.4 (GNU/Linux)
>> iD8DBQFBa50632BbsHYPLWURAg5hAJwPJxLFPfWhNx0afzjntqKl/rmgagCdGO+G
>> EDx/otU5qMtWX79xZKnCSxU=3D
>> =3DK88g
>> -----END PGP SIGNATURE-----
>> _______________________________________________
>> rserpool mailing list
>> rserpool@ietf.org
>> https://www1.ietf.org/mailman/listinfo/rserpool
>
>
> _______________________________________________
> rserpool mailing list
> rserpool@ietf.org
> https://www1.ietf.org/mailman/listinfo/rserpool
>


_______________________________________________
rserpool mailing list
rserpool@ietf.org
https://www1.ietf.org/mailman/listinfo/rserpool


From rserpool-bounces@ietf.org  Tue Oct 12 15:56:16 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26012
	for <rserpool-archive@lists.ietf.org>; Tue, 12 Oct 2004 15:56:16 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CHSZW-00065d-Ac; Tue, 12 Oct 2004 15:44:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CHSUL-0003mv-5x
	for rserpool@megatron.ietf.org; Tue, 12 Oct 2004 15:39:13 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23748
	for <rserpool@ietf.org>; Tue, 12 Oct 2004 15:39:12 -0400 (EDT)
Received: from dpc674425142.direcpc.com ([67.44.25.142]
	helo=stewart.chicago.il.us)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHSf7-0005g5-ML
	for rserpool@ietf.org; Tue, 12 Oct 2004 15:50:23 -0400
Received: from stewart.chicago.il.us (localhost [127.0.0.1])
	by stewart.chicago.il.us (8.12.9p2/8.12.8) with ESMTP id i9CJcmKG018330;
	Tue, 12 Oct 2004 15:38:49 -0400 (EDT)
	(envelope-from randall@stewart.chicago.il.us)
Message-ID: <416C326C.8090407@stewart.chicago.il.us>
Date: Tue, 12 Oct 2004 15:37:16 -0400
From: Randall Stewart <randall@stewart.chicago.il.us>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040429
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Subject: Re: [Rserpool] PEER_ERROR message
References: <6F8DFFA2C996D711945800065BFC9E4A10C1FBBA@il02exm11>
	<200410121100.43398.dreibh@exp-math.uni-essen.de>
	<416BE972.10207@stewart.chicago.il.us>
	<F9644AB0-1C73-11D9-8955-000D932C78D8@lurchi.franken.de>
In-Reply-To: <F9644AB0-1C73-11D9-8955-000D932C78D8@lurchi.franken.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by stewart.chicago.il.us
	id i9CJcmKG018330
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f
Content-Transfer-Encoding: quoted-printable
Cc: Thomas Dreibholz <dreibh@exp-math.uni-essen.de>, rserpool@ietf.org
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Sender: rserpool-bounces@ietf.org
Errors-To: rserpool-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

Hmm.. that is a good point.. maybe it is
best just to leave the number..

However the error name ENRP_ERROR or PEER_ERROR needs
to be the same throughout the enrp doucment..

And if we have no use for it in ASAP.. then we may
want to get rid of it.. or if we do have a use then
lets write up how it is used :-D

I do like PEER_ERROR for both of them.. even though
it may mean something different :-o

R


Michael Tuexen wrote:
> Dear all,
>=20
> just a general thought.
>=20
> we decided to align the parameters between APAP and ENRP, that is why
> we have the common parameter ID. As far as I think, we also decided not
> to align the messages between ASAP and ENRP. This might become more
> complex in the future.
>=20
> So I'm not sure what it helps in aligning the type number, the error =20
> causes
> will be different and the code will also be different...
>=20
> Best regards
> Michael
>=20
> On Oct 12, 2004, at 16:25 Uhr, Randall Stewart wrote:
>=20
>> Thomas.. I have taken this
>> suggestion.
>>
>> Next revision we will make PEER_ERROR the same
>> error number (0xe)
>>
>> and then change all reference to ENRP_ERROR
>> to PEER_ERROR
>>
>> R
>>
>>
>> Thomas Dreibholz wrote:
>>
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>> On Monday 11 October 2004 22:46, Johnson Walter-CWJ002 wrote:
>>>
>>>> Any reference to the PEER_ERROR message should be removed from the =20
>>>> ASAP
>>>> protocol document since I believe it is not an ASAP message.
>>>
>>> It is useful to have this message type in ASAP, because e.g. a =20
>>> component (NS, PE or PU) could receive a bad message via ASAP. Then, =
=20
>>> it can report the sender that it does not understand/accept this =20
>>> message via a PEER_ERROR. This is useful for debugging.
>>> To make ASAP and ENRP PEER_ERROR more consistent, their definitions =20
>>> and especially the message type number (currently: 0x0e or ASAP,=20
>>> 0x0b  for ENRP) could be unified. For example, the message number=20
>>> could be  0xff for both.
>>> Best regards
>>> - -- =20
>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D
>>>  Dipl.-Inform. Thomas Dreibholz
>>>  University of Essen,                            Room ES210
>>>  Inst. for Experimental Mathematics              Ellernstra=DFe 29
>>>  Computer Networking Technology Group            D-45326 Essen/German=
y
>>> - =20
>>> ---------------------------------------------------------------------=
- -
>>>  E-Mail:     dreibh@exp-math.uni-essen.de
>>>  Homepage:   http://www.exp-math.uni-essen.de/~dreibh
>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D
>>> -----BEGIN PGP SIGNATURE-----
>>> Version: GnuPG v1.2.4 (GNU/Linux)
>>> iD8DBQFBa50632BbsHYPLWURAg5hAJwPJxLFPfWhNx0afzjntqKl/rmgagCdGO+G
>>> EDx/otU5qMtWX79xZKnCSxU=3D
>>> =3DK88g
>>> -----END PGP SIGNATURE-----
>>> _______________________________________________
>>> rserpool mailing list
>>> rserpool@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/rserpool
>>
>>
>>
>> _______________________________________________
>> rserpool mailing list
>> rserpool@ietf.org
>> https://www1.ietf.org/mailman/listinfo/rserpool
>>
>=20
>=20
>=20
>=20


_______________________________________________
rserpool mailing list
rserpool@ietf.org
https://www1.ietf.org/mailman/listinfo/rserpool


From rserpool-bounces@ietf.org  Tue Oct 12 17:38:03 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16913
	for <rserpool-archive@lists.ietf.org>; Tue, 12 Oct 2004 17:38:03 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CHTop-0004CC-Ui; Tue, 12 Oct 2004 17:04:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CHTH9-0006rJ-IH
	for rserpool@megatron.ietf.org; Tue, 12 Oct 2004 16:29:40 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02645
	for <rserpool@ietf.org>; Tue, 12 Oct 2004 16:29:38 -0400 (EDT)
Received: from ftpbox.mot.com ([129.188.136.101])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHTRx-0008GV-0h
	for rserpool@ietf.org; Tue, 12 Oct 2004 16:40:50 -0400
Received: from az33exr02.mot.com (az33exr02.mot.com [10.64.251.232])
	by ftpbox.mot.com (Motorola/Ftpbox) with ESMTP id i9CKTbYJ021794
	for <rserpool@ietf.org>; Tue, 12 Oct 2004 13:29:37 -0700 (MST)
Received: from il02exm11.corp.mot.com (il02exm11.corp.mot.com [10.0.111.22])
	by az33exr02.mot.com (Motorola/az33exr02) with ESMTP id i9CKRFNM017066
	for <rserpool@ietf.org>; Tue, 12 Oct 2004 15:27:15 -0500
Received: by il02exm11 with Internet Mail Service (5.5.2657.72)
	id <TD9ZPZCC>; Tue, 12 Oct 2004 15:29:36 -0500
Message-ID: <6F8DFFA2C996D711945800065BFC9E4A10D06ACF@il02exm11>
From: Johnson Walter-CWJ002 <Walter.Johnson@motorola.com>
To: "'Randall Stewart'" <randall@stewart.chicago.il.us>,
        "'Michael Tuexen'"
	<Michael.Tuexen@lurchi.franken.de>
Subject: RE: [Rserpool] PEER_ERROR message
Date: Tue, 12 Oct 2004 15:29:35 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: "'Thomas Dreibholz'" <dreibh@exp-math.uni-essen.de>,
        "'rserpool@ietf.org'" <rserpool@ietf.org>
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Sender: rserpool-bounces@ietf.org
Errors-To: rserpool-bounces@ietf.org

Randall Stewart <> wrote:
> Hmm.. that is a good point.. maybe it is
> best just to leave the number..
> 

Agreed.

> However the error name ENRP_ERROR or PEER_ERROR needs
> to be the same throughout the enrp doucment..
> 

Agreed.

> And if we have no use for it in ASAP.. then we may
> want to get rid of it.. or if we do have a use then
> lets write up how it is used :-D
> 

Agreed.

> I do like PEER_ERROR for both of them.. even though
> it may mean something different :-o
> 

Disagree, but really don't have a strong opinion. I know one can sort on the protocol and the message type to determine how to decode the message. But having separate names makes it clear to readers new to the ASAP and ENRP drafts that these are unique messages with unique uses. Within the drafts, the message names only act as tags for the real messages sent over the wire so why not make them as descriptive as possible. In this case, it might be best to make it ASAP_ERROR and ENRP_ERROR to identify the protocol error type.  For instance, an ENRP namespace server can potentially receive both types of errors and there might be a need to describe a situation where both are received. This would be much easier to explain using unique names than describing both as PEER_ERROR. Just my thought.

> R
> 
> 

Walter

_______________________________________________
rserpool mailing list
rserpool@ietf.org
https://www1.ietf.org/mailman/listinfo/rserpool


From rserpool-bounces@ietf.org  Wed Oct 13 04:40:07 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02255
	for <rserpool-archive@lists.ietf.org>; Wed, 13 Oct 2004 04:40:07 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CHeae-0003Ip-Sn; Wed, 13 Oct 2004 04:34:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CHeTH-0001MQ-1G
	for rserpool@megatron.ietf.org; Wed, 13 Oct 2004 04:26:55 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01480
	for <rserpool@ietf.org>; Wed, 13 Oct 2004 04:26:51 -0400 (EDT)
Received: from ns.iem.uni-due.de ([132.252.150.1]
	helo=pilz.exp-math.uni-essen.de)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHee7-0007PS-RH
	for rserpool@ietf.org; Wed, 13 Oct 2004 04:38:08 -0400
Received: from kappes.exp-math.uni-essen.de (kappes.exp-math.uni-essen.de
	[132.252.150.151])
	by pilz.exp-math.uni-essen.de (8.12.10/8.12.8) with ESMTP id
	i9D8QhOp030260; Wed, 13 Oct 2004 10:26:44 +0200
From: Thomas Dreibholz <dreibh@exp-math.uni-essen.de>
Organization: University of Essen, Institute for Experimental Mathematics
To: rserpool@ietf.org
Subject: Re: [Rserpool] PEER_ERROR message
Date: Wed, 13 Oct 2004 10:26:40 +0200
User-Agent: KMail/1.6.1
References: <6F8DFFA2C996D711945800065BFC9E4A10D06ACF@il02exm11>
In-Reply-To: <6F8DFFA2C996D711945800065BFC9E4A10D06ACF@il02exm11>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: Text/Plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable
Message-Id: <200410131026.44081.dreibh@exp-math.uni-essen.de>
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Content-Transfer-Encoding: quoted-printable
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Sender: rserpool-bounces@ietf.org
Errors-To: rserpool-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday 12 October 2004 22:29, Johnson Walter-CWJ002 wrote:
> Within the
> drafts, the message names only act as tags for the real messages sent over
> the wire so why not make them as descriptive as possible. In this case, it
> might be best to make it ASAP_ERROR and ENRP_ERROR to identify the protoc=
ol
> error type.

This is a good idea.


Best regards
=2D --=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
 Dipl.-Inform. Thomas Dreibholz

 University of Essen,                            Room ES210
 Inst. for Experimental Mathematics              Ellernstra=DFe 29
 Computer Networking Technology Group            D-45326 Essen/Germany
=2D -----------------------------------------------------------------------
 E-Mail:     dreibh@exp-math.uni-essen.de
 Homepage:   http://www.exp-math.uni-essen.de/~dreibh
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBbObD32BbsHYPLWURAg9XAJ9vEEkB/jDFHmGbES//iXSCmcaObgCggRLI
LmYzwgU86EPObK9OWdYrUeo=3D
=3D0RGl
=2D----END PGP SIGNATURE-----

_______________________________________________
rserpool mailing list
rserpool@ietf.org
https://www1.ietf.org/mailman/listinfo/rserpool


From rserpool-bounces@ietf.org  Wed Oct 13 04:58:24 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03569
	for <rserpool-archive@lists.ietf.org>; Wed, 13 Oct 2004 04:58:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CHeta-0006vW-0X; Wed, 13 Oct 2004 04:54:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CHekr-0005eZ-Sh
	for rserpool@megatron.ietf.org; Wed, 13 Oct 2004 04:45:05 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02656
	for <rserpool@ietf.org>; Wed, 13 Oct 2004 04:45:02 -0400 (EDT)
Received: from mail-n.franken.de
	([193.175.24.27] helo=ilsa.franken.de ident=postfix)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHevi-0007ka-S6
	for rserpool@ietf.org; Wed, 13 Oct 2004 04:56:19 -0400
Received: from [192.168.1.224] (p5089F67C.dip.t-dialin.net [80.137.246.124])
	by ilsa.franken.de (Postfix) with ESMTP
	id 5C6C8245D7; Wed, 13 Oct 2004 10:44:56 +0200 (CEST)
	(KNF account authenticated via SMTP-AUTH)
In-Reply-To: <200410131026.44081.dreibh@exp-math.uni-essen.de>
References: <6F8DFFA2C996D711945800065BFC9E4A10D06ACF@il02exm11>
	<200410131026.44081.dreibh@exp-math.uni-essen.de>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
Message-Id: <24664EC2-1CF4-11D9-8E42-000D932C78D8@lurchi.franken.de>
Content-Transfer-Encoding: quoted-printable
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Subject: Re: [Rserpool] PEER_ERROR message
Date: Wed, 13 Oct 2004 10:44:49 +0200
To: Thomas Dreibholz <dreibh@exp-math.uni-essen.de>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Content-Transfer-Encoding: quoted-printable
Cc: rserpool@ietf.org
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Sender: rserpool-bounces@ietf.org
Errors-To: rserpool-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

I like the idea, too.

Best regards
Michael

On Oct 13, 2004, at 10:26 Uhr, Thomas Dreibholz wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Tuesday 12 October 2004 22:29, Johnson Walter-CWJ002 wrote:
>> Within the
>> drafts, the message names only act as tags for the real messages sent =
=20
>> over
>> the wire so why not make them as descriptive as possible. In this =20
>> case, it
>> might be best to make it ASAP_ERROR and ENRP_ERROR to identify the =20=

>> protocol
>> error type.
>
> This is a good idea.
>
>
> Best regards
> - --
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>  Dipl.-Inform. Thomas Dreibholz
>
>  University of Essen,                            Room ES210
>  Inst. for Experimental Mathematics              Ellernstra=DFe 29
>  Computer Networking Technology Group            D-45326 Essen/Germany
> - =20
> =
-----------------------------------------------------------------------
>  E-Mail:     dreibh@exp-math.uni-essen.de
>  Homepage:   http://www.exp-math.uni-essen.de/~dreibh
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (GNU/Linux)
>
> iD8DBQFBbObD32BbsHYPLWURAg9XAJ9vEEkB/jDFHmGbES//iXSCmcaObgCggRLI
> LmYzwgU86EPObK9OWdYrUeo=3D
> =3D0RGl
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> rserpool mailing list
> rserpool@ietf.org
> https://www1.ietf.org/mailman/listinfo/rserpool
>


_______________________________________________
rserpool mailing list
rserpool@ietf.org
https://www1.ietf.org/mailman/listinfo/rserpool


From rserpool-bounces@ietf.org  Wed Oct 13 06:02:46 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA08128
	for <rserpool-archive@lists.ietf.org>; Wed, 13 Oct 2004 06:02:46 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CHftu-0003em-Gi; Wed, 13 Oct 2004 05:58:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CHfs3-0003FU-Dn
	for rserpool@megatron.ietf.org; Wed, 13 Oct 2004 05:56:35 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA07736
	for <rserpool@ietf.org>; Wed, 13 Oct 2004 05:56:30 -0400 (EDT)
Received: from dpc674425142.direcpc.com ([67.44.25.142]
	helo=stewart.chicago.il.us)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHg2t-0000hh-8f
	for rserpool@ietf.org; Wed, 13 Oct 2004 06:07:49 -0400
Received: from stewart.chicago.il.us (localhost [127.0.0.1])
	by stewart.chicago.il.us (8.12.9p2/8.12.8) with ESMTP id i9D9tuKG019986;
	Wed, 13 Oct 2004 05:55:59 -0400 (EDT)
	(envelope-from randall@stewart.chicago.il.us)
Message-ID: <416CFB4C.3060304@stewart.chicago.il.us>
Date: Wed, 13 Oct 2004 05:54:20 -0400
From: Randall Stewart <randall@stewart.chicago.il.us>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040429
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Subject: Re: [Rserpool] PEER_ERROR message
References: <6F8DFFA2C996D711945800065BFC9E4A10D06ACF@il02exm11>	<200410131026.44081.dreibh@exp-math.uni-essen.de>
	<24664EC2-1CF4-11D9-8E42-000D932C78D8@lurchi.franken.de>
In-Reply-To: <24664EC2-1CF4-11D9-8E42-000D932C78D8@lurchi.franken.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by stewart.chicago.il.us
	id i9D9tuKG019986
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Content-Transfer-Encoding: quoted-printable
Cc: Thomas Dreibholz <dreibh@exp-math.uni-essen.de>, rserpool@ietf.org
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Sender: rserpool-bounces@ietf.org
Errors-To: rserpool-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

Done

(even though I am not sure what a ASAP_ERROR is for)... maybe
we can discuss this in Washington and I can add
some text then..


R

Michael Tuexen wrote:
> I like the idea, too.
>=20
> Best regards
> Michael
>=20
> On Oct 13, 2004, at 10:26 Uhr, Thomas Dreibholz wrote:
>=20
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On Tuesday 12 October 2004 22:29, Johnson Walter-CWJ002 wrote:
>>
>>> Within the
>>> drafts, the message names only act as tags for the real messages=20
>>> sent  over
>>> the wire so why not make them as descriptive as possible. In this =20
>>> case, it
>>> might be best to make it ASAP_ERROR and ENRP_ERROR to identify the =20
>>> protocol
>>> error type.
>>
>>
>> This is a good idea.
>>
>>
>> Best regards
>> - --
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>  Dipl.-Inform. Thomas Dreibholz
>>
>>  University of Essen,                            Room ES210
>>  Inst. for Experimental Mathematics              Ellernstra=DFe 29
>>  Computer Networking Technology Group            D-45326 Essen/Germany
>> - =20
>> ----------------------------------------------------------------------=
-
>>  E-Mail:     dreibh@exp-math.uni-essen.de
>>  Homepage:   http://www.exp-math.uni-essen.de/~dreibh
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.2.4 (GNU/Linux)
>>
>> iD8DBQFBbObD32BbsHYPLWURAg9XAJ9vEEkB/jDFHmGbES//iXSCmcaObgCggRLI
>> LmYzwgU86EPObK9OWdYrUeo=3D
>> =3D0RGl
>> -----END PGP SIGNATURE-----
>>
>> _______________________________________________
>> rserpool mailing list
>> rserpool@ietf.org
>> https://www1.ietf.org/mailman/listinfo/rserpool
>>
>=20
>=20
> _______________________________________________
> rserpool mailing list
> rserpool@ietf.org
> https://www1.ietf.org/mailman/listinfo/rserpool
>=20
>=20
>=20


_______________________________________________
rserpool mailing list
rserpool@ietf.org
https://www1.ietf.org/mailman/listinfo/rserpool


From rserpool-bounces@ietf.org  Thu Oct 14 11:39:20 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00918
	for <rserpool-archive@lists.ietf.org>; Thu, 14 Oct 2004 11:39:20 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CI7eF-0000jN-I4; Thu, 14 Oct 2004 11:36:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CI7ca-0000D1-4J
	for rserpool@megatron.ietf.org; Thu, 14 Oct 2004 11:34:28 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00601
	for <rserpool@ietf.org>; Thu, 14 Oct 2004 11:34:25 -0400 (EDT)
From: Maureen.Stillman@nokia.com
Received: from mgw-x2.nokia.com ([131.228.20.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CI7nk-0004oM-Mh
	for rserpool@ietf.org; Thu, 14 Oct 2004 11:46:02 -0400
Received: from esdks004.ntc.nokia.com (esdks004.ntc.nokia.com [172.21.138.159])
	by mgw-x2.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	i9EFYLF15710
	for <rserpool@ietf.org>; Thu, 14 Oct 2004 18:34:21 +0300 (EET DST)
X-Scanned: Thu, 14 Oct 2004 18:34:15 +0300 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks004.ntc.nokia.com (8.12.9/8.12.9) id i9EFYFLk002941
	for <rserpool@ietf.org>; Thu, 14 Oct 2004 18:34:15 +0300
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks004.ntc.nokia.com 00mcoOXI; Thu, 14 Oct 2004 18:34:14 EEST
Received: from daebh001.NOE.Nokia.com (daebh001.americas.nokia.com
	[10.241.35.121])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	i9EFYCa26136
	for <rserpool@ietf.org>; Thu, 14 Oct 2004 18:34:13 +0300 (EET DST)
Received: from daebe007.NOE.Nokia.com ([10.241.35.107]) by
	daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Thu, 14 Oct 2004 10:34:11 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 14 Oct 2004 10:34:11 -0500
Message-ID: <57A26D272F67A743952F6B4371B8F81104090B06@daebe007.americas.nokia.com>
Thread-Topic: Make policies document a WG document?
Thread-Index: AcSyAz7PmVtw2O9MTrydbO/z6Qk7Nw==
To: <rserpool@ietf.org>
X-OriginalArrivalTime: 14 Oct 2004 15:34:11.0358 (UTC)
	FILETIME=[40B6BBE0:01C4B203]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: quoted-printable
Subject: [Rserpool] Make policies document a WG document?
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Sender: rserpool-bounces@ietf.org
Errors-To: rserpool-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

Here is text from the Rserpool minutes in San Diego.  We agreed to move
ASAP policies to this new policies document, but neglected to formally
ask for the policies document to be a WG document.=20

A policies draft was presented (draft-tuexen-rserpool-policies-00.txt).
This draft presents new policies for reliable server pooling. The
proposal was to take the pool policies currently included in the ASAP
draft and separate them into a separate policies draft. This allows the
stable base ASAP protocol specification to be separated from the pool
policies which are subject to further investigation and more substantial
changes. Consensus was reached in the meeting to make this change. We
will take the proposal to the mailing list.

Are there any objections to making draft-tuexen-rserpool-policies-00.txt
a WG document? =20

Please let us know promptly if you object.=20

Thanks.

-- Maureen

_______________________________________________
rserpool mailing list
rserpool@ietf.org
https://www1.ietf.org/mailman/listinfo/rserpool


From rserpool-bounces@ietf.org  Thu Oct 14 15:38:33 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19937
	for <rserpool-archive@lists.ietf.org>; Thu, 14 Oct 2004 15:38:33 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CIBOB-0004La-Od; Thu, 14 Oct 2004 15:35:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CIBJv-0002L0-MU
	for rserpool@megatron.ietf.org; Thu, 14 Oct 2004 15:31:27 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18860
	for <rserpool@ietf.org>; Thu, 14 Oct 2004 15:31:25 -0400 (EDT)
Received: from sccrmhc11.comcast.net ([204.127.202.55])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CIBV9-0001GM-8O
	for rserpool@ietf.org; Thu, 14 Oct 2004 15:43:03 -0400
Received: from [10.10.0.75] (c-24-13-174-21.client.comcast.net[24.13.174.21])
	by comcast.net (sccrmhc11) with ESMTP id <20041014193055011008bp59e>
	(Authid: peterlei); Thu, 14 Oct 2004 19:30:55 +0000
Message-ID: <416ED3ED.4070607@ieee.org>
Date: Thu, 14 Oct 2004 14:30:53 -0500
From: Peter Lei <peter.lei@ieee.org>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US;
	rv:1.7.3) Gecko/20040910
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Maureen.Stillman@nokia.com
Subject: Re: [Rserpool] Make policies document a WG document?
References: <57A26D272F67A743952F6B4371B8F81104090B06@daebe007.americas.nokia.com>
In-Reply-To: <57A26D272F67A743952F6B4371B8F81104090B06@daebe007.americas.nokia.com>
X-Enigmail-Version: 0.85.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
X-Spam-Score: 0.1 (/)
X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f
Cc: rserpool@ietf.org
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0548191697=="
Sender: rserpool-bounces@ietf.org
Errors-To: rserpool-bounces@ietf.org

This is a cryptographically signed message in MIME format.

--===============0548191697==
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature";
	micalg=sha1; boundary="------------ms020401040109080607060900"

This is a cryptographically signed message in MIME format.

--------------ms020401040109080607060900
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Sounds reasonable especially since the text comes from an existing
WG draft and helps other pool policies to be defined outside the
base protocol spec (as discussed in San Diego).

regards,
--peter

Maureen.Stillman@nokia.com wrote:
> Here is text from the Rserpool minutes in San Diego.  We agreed to move
> ASAP policies to this new policies document, but neglected to formally
> ask for the policies document to be a WG document. 
> 
> A policies draft was presented (draft-tuexen-rserpool-policies-00.txt).
> This draft presents new policies for reliable server pooling. The
> proposal was to take the pool policies currently included in the ASAP
> draft and separate them into a separate policies draft. This allows the
> stable base ASAP protocol specification to be separated from the pool
> policies which are subject to further investigation and more substantial
> changes. Consensus was reached in the meeting to make this change. We
> will take the proposal to the mailing list.
> 
> Are there any objections to making draft-tuexen-rserpool-policies-00.txt
> a WG document?  
> 
> Please let us know promptly if you object. 
> 
> Thanks.
> 
> -- Maureen
> 
> _______________________________________________
> rserpool mailing list
> rserpool@ietf.org
> https://www1.ietf.org/mailman/listinfo/rserpool
> 

--------------ms020401040109080607060900
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIII7TCC
AtEwggI6oAMCAQICAwvwrTANBgkqhkiG9w0BAQQFADBiMQswCQYDVQQGEwJaQTElMCMGA1UE
ChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNv
bmFsIEZyZWVtYWlsIElzc3VpbmcgQ0EwHhcNMDQwMzE3MjE1NjMzWhcNMDUwMzE3MjE1NjMz
WjBEMR8wHQYDVQQDExZUaGF3dGUgRnJlZW1haWwgTWVtYmVyMSEwHwYJKoZIhvcNAQkBFhJw
ZXRlci5sZWlAaWVlZS5vcmcwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDX4PR3
QP+rgEBZtv1Q4YhKjRXUZQSk+9xNzesbK7pyirmUxKnm209ZGibDUAb/yC0ghvl3GbvNv/72
cyfC7JVjiABrDxY19L9mRGLKzjlK/bgBPY8SIu4blM/RtyabN4CdYk24LoGPHuLLkJIvvvQR
LG0IJIfP8zvoHy0UGzyXOM/S4msxF1zDpBu7lYMe4Dpu5O9uaE2j1G/jswVmO2KMyQmffOGx
0Mw18tiGNMWkjMAwSJnXO2VSHzvh+I3OM71ReFo9ET2TtiXzqdDM5z0/LTsIyy1vP4Ib3Co9
xZNTe6JqVk2BsH7EZKPxi+oD7f/HctNWTZk0sesgba7D97jLAgMBAAGjLzAtMB0GA1UdEQQW
MBSBEnBldGVyLmxlaUBpZWVlLm9yZzAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBAUAA4GB
AB86WuVOs/pHjC4SPdbKb+obiQZVqR813FD3JcW+stkaZQHTPHoln/SYRd3TZcZIXageyme6
f5Gl3lOsamSUrtkov5u6B0vvtuDuMQH7deh1ARTQfC+R3hv29vVQ+uSPlLo/AGWaPcW030NW
Bp96xBIESmHBMWGuYWkxMDHII/R+MIIC0TCCAjqgAwIBAgIDC/CtMA0GCSqGSIb3DQEBBAUA
MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQu
MSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQTAeFw0wNDAz
MTcyMTU2MzNaFw0wNTAzMTcyMTU2MzNaMEQxHzAdBgNVBAMTFlRoYXd0ZSBGcmVlbWFpbCBN
ZW1iZXIxITAfBgkqhkiG9w0BCQEWEnBldGVyLmxlaUBpZWVlLm9yZzCCASIwDQYJKoZIhvcN
AQEBBQADggEPADCCAQoCggEBANfg9HdA/6uAQFm2/VDhiEqNFdRlBKT73E3N6xsrunKKuZTE
qebbT1kaJsNQBv/ILSCG+XcZu82//vZzJ8LslWOIAGsPFjX0v2ZEYsrOOUr9uAE9jxIi7huU
z9G3Jps3gJ1iTbgugY8e4suQki++9BEsbQgkh8/zO+gfLRQbPJc4z9LiazEXXMOkG7uVgx7g
Om7k725oTaPUb+OzBWY7YozJCZ984bHQzDXy2IY0xaSMwDBImdc7ZVIfO+H4jc4zvVF4Wj0R
PZO2JfOp0MznPT8tOwjLLW8/ghvcKj3Fk1N7ompWTYGwfsRko/GL6gPt/8dy01ZNmTSx6yBt
rsP3uMsCAwEAAaMvMC0wHQYDVR0RBBYwFIEScGV0ZXIubGVpQGllZWUub3JnMAwGA1UdEwEB
/wQCMAAwDQYJKoZIhvcNAQEEBQADgYEAHzpa5U6z+keMLhI91spv6huJBlWpHzXcUPclxb6y
2RplAdM8eiWf9JhF3dNlxkhdqB7KZ7p/kaXeU6xqZJSu2Si/m7oHS++24O4xAft16HUBFNB8
L5HeG/b29VD65I+Uuj8AZZo9xbTfQ1YGn3rEEgRKYcExYa5haTEwMcgj9H4wggM/MIICqKAD
AgECAgENMA0GCSqGSIb3DQEBBQUAMIHRMQswCQYDVQQGEwJaQTEVMBMGA1UECBMMV2VzdGVy
biBDYXBlMRIwEAYDVQQHEwlDYXBlIFRvd24xGjAYBgNVBAoTEVRoYXd0ZSBDb25zdWx0aW5n
MSgwJgYDVQQLEx9DZXJ0aWZpY2F0aW9uIFNlcnZpY2VzIERpdmlzaW9uMSQwIgYDVQQDExtU
aGF3dGUgUGVyc29uYWwgRnJlZW1haWwgQ0ExKzApBgkqhkiG9w0BCQEWHHBlcnNvbmFsLWZy
ZWVtYWlsQHRoYXd0ZS5jb20wHhcNMDMwNzE3MDAwMDAwWhcNMTMwNzE2MjM1OTU5WjBiMQsw
CQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoG
A1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0EwgZ8wDQYJKoZIhvcN
AQEBBQADgY0AMIGJAoGBAMSmPFVzVftOucqZWh5owHUEcJ3f6f+jHuy9zfVb8hp2vX8MOmHy
v1HOAdTlUAow1wJjWiyJFXCO3cnwK4Vaqj9xVsuvPAsH5/EfkTYkKhPPK9Xzgnc9A74r/rsY
Pge/QIACZNenprufZdHFKlSFD0gEf6e20TxhBEAeZBlyYLf7AgMBAAGjgZQwgZEwEgYDVR0T
AQH/BAgwBgEB/wIBADBDBgNVHR8EPDA6MDigNqA0hjJodHRwOi8vY3JsLnRoYXd0ZS5jb20v
VGhhd3RlUGVyc29uYWxGcmVlbWFpbENBLmNybDALBgNVHQ8EBAMCAQYwKQYDVR0RBCIwIKQe
MBwxGjAYBgNVBAMTEVByaXZhdGVMYWJlbDItMTM4MA0GCSqGSIb3DQEBBQUAA4GBAEiM0VCD
6gsuzA2jZqxnD3+vrL7CF6FDlpSdf0whuPg2H6otnzYvwPQcUCCTcDz9reFhYsPZOhl+hLGZ
GwDFGguCdJ4lUJRix9sncVcljd2pnDmOjCBPZV+V2vf3h9bGCE6u9uo05RAaWzVNd+NWIXiC
3CEZNd4ksdMdRv9dX2VPMYIDOzCCAzcCAQEwaTBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMc
VGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFs
IEZyZWVtYWlsIElzc3VpbmcgQ0ECAwvwrTAJBgUrDgMCGgUAoIIBpzAYBgkqhkiG9w0BCQMx
CwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wNDEwMTQxOTMwNTNaMCMGCSqGSIb3DQEJ
BDEWBBTMg/CwMooD6CXlatBigD2olieHyDBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMH
MA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIB
KDB4BgkrBgEEAYI3EAQxazBpMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29u
c3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwg
SXNzdWluZyBDQQIDC/CtMHoGCyqGSIb3DQEJEAILMWugaTBiMQswCQYDVQQGEwJaQTElMCMG
A1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBl
cnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECAwvwrTANBgkqhkiG9w0BAQEFAASCAQAL7uq2
0kncwMhiUhGekCFKv+kMmtD9UquX9sEEuQJtBJRdIo8ZrXvOyjHeZRwqqbo0rjai/ZC0z4hg
xBvBRckoEdHm8GUcnTwvV3btAl8VgSx85W4hZp4iwUeRFEPqJEAxCrW+GE3gl6hkjkrSGWyg
Oil673TuY4XwGCzMtRpYneXwrYTaCgQ9OaMg9SuGCWDPkv1rifPOMdMJafIPsRNyzqFJ+vCF
1PK71VMgpfDF/qML9kJ0PEk7nHpkDm/Yik9x/3IJNp1T3f73Ng3kvuatqURKh24g1QX6Ciz8
mh1+z7YeunQO1S3ztcAqO4gGlyxK73vIl6VbTqKDbKB6fFTQAAAAAAAA
--------------ms020401040109080607060900--


--===============0548191697==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
rserpool mailing list
rserpool@ietf.org
https://www1.ietf.org/mailman/listinfo/rserpool

--===============0548191697==--



From rserpool-bounces@ietf.org  Thu Oct 14 17:17:57 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06720
	for <rserpool-archive@lists.ietf.org>; Thu, 14 Oct 2004 17:17:57 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CICO8-0006xV-W3; Thu, 14 Oct 2004 16:39:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CIC8Q-0001lx-T8
	for rserpool@megatron.ietf.org; Thu, 14 Oct 2004 16:23:38 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26021
	for <rserpool@ietf.org>; Thu, 14 Oct 2004 16:23:36 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CICJd-0002kI-Jp
	for rserpool@ietf.org; Thu, 14 Oct 2004 16:35:15 -0400
Received: from az33exr04.mot.com (pobox4.mot.com [10.64.251.243])
	by motgate8.mot.com (Motorola/Motgate8) with ESMTP id i9EKOqG2014687
	for <rserpool@ietf.org>; Thu, 14 Oct 2004 13:24:52 -0700 (MST)
Received: from il02exm11.corp.mot.com (il02exm11.corp.mot.com [10.0.111.22])
	by az33exr04.mot.com (Motorola/az33exr04) with ESMTP id i9EINAmm031757
	for <rserpool@ietf.org>; Thu, 14 Oct 2004 13:23:10 -0500
Received: by il02exm11 with Internet Mail Service (5.5.2657.72)
	id <TD9ZR60T>; Thu, 14 Oct 2004 15:23:30 -0500
Message-ID: <6F8DFFA2C996D711945800065BFC9E4A10EAA47A@il02exm11>
From: Johnson Walter-CWJ002 <Walter.Johnson@motorola.com>
To: "'rserpool@ietf.org'" <rserpool@ietf.org>
Date: Thu, 14 Oct 2004 15:23:28 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.1 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Subject: [Rserpool] Elimination of Registration Response Success /w
	Warning/Modificat ion from ASAP draft 
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Sender: rserpool-bounces@ietf.org
Errors-To: rserpool-bounces@ietf.org

Currently the registration procedure of the ASAP draft in section 3.1 supports three cases. 

1) Success
2) Success /w warnings/modifications
3) Failure

I believe that the registration procedure should only result in either success or failure eliminating case 2. 

Let me explain.

For instance, let say the PE can't adapt its policy from the policy sent in the registration message. If the PE receives a registration success /w warnings/modifications and can't adapt, it should remove itself from the pool. Then the PE would need to deregister or not re-register itself to be removed from the pool. This would cause updates to happen across all peer ENRP servers since the PE would need to be removed from the pool to which it was recently added, resulting in many messages being sent to maintain namespace synchronization. Also before this deregistration occurred, several PUs could have starting using this PE for service which results in its own problems. 

If instead the registration was rejected using the operation error codes regarding the problem, the PE could simply send a single message to register again if changes could be made. Otherwise no message would be sent if the PE couldn't adapt. 

I believe this is much simpler and would result in fewer overall messages being sent within the RSerPool architecture and would result in a cleaner ASAP implementation. 

What does everyone think? 

_______________________________________________
rserpool mailing list
rserpool@ietf.org
https://www1.ietf.org/mailman/listinfo/rserpool


From rserpool-bounces@ietf.org  Thu Oct 14 17:44:56 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10020
	for <rserpool-archive@lists.ietf.org>; Thu, 14 Oct 2004 17:44:56 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CIDLC-0003kb-UG; Thu, 14 Oct 2004 17:40:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CIDIE-0002l5-Nb
	for rserpool@megatron.ietf.org; Thu, 14 Oct 2004 17:37:50 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09376
	for <rserpool@ietf.org>; Thu, 14 Oct 2004 17:37:48 -0400 (EDT)
Received: from motgate.mot.com ([129.188.136.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CIDTS-0006gZ-Gs
	for rserpool@ietf.org; Thu, 14 Oct 2004 17:49:27 -0400
Received: from az33exr03.mot.com (az33exr03.mot.com [10.64.251.233])
	by motgate.mot.com (Motorola/Motgate) with ESMTP id i9ELblEh000460
	for <rserpool@ietf.org>; Thu, 14 Oct 2004 14:37:48 -0700 (MST)
Received: from il02exm12.corp.mot.com (il02exm12.corp.mot.com [10.0.111.23])
	by az33exr03.mot.com (Motorola/az33exr03) with ESMTP id i9ELbU6I002817
	for <rserpool@ietf.org>; Thu, 14 Oct 2004 16:37:30 -0500
Received: by il02exm12 with Internet Mail Service (5.5.2657.72)
	id <TKCMATC9>; Thu, 14 Oct 2004 16:37:46 -0500
Message-ID: <FD52892BD296D71183B400065BFCB6901067DFCD@il02exm12>
From: Silverton Aron-C1710C <Aron.J.Silverton@motorola.com>
To: Johnson Walter-CWJ002 <Walter.Johnson@motorola.com>, rserpool@ietf.org
Subject: RE: [Rserpool] Elimination of Registration Response Success /w Wa
	rning/Modificat ion from ASAP draft 
Date: Thu, 14 Oct 2004 16:37:37 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Sender: rserpool-bounces@ietf.org
Errors-To: rserpool-bounces@ietf.org

I agree with the proposal below.  The current method assumes that the PE is capable of supporting whichever pool policy is returned in the warnings/modifications.  I don't think that this is a safe assumption, so I support the change.

Aron

-----Original Message-----
From: rserpool-bounces@ietf.org [mailto:rserpool-bounces@ietf.org] On Behalf Of Johnson Walter-CWJ002
Sent: Thursday, October 14, 2004 3:23 PM
To: rserpool@ietf.org
Subject: [Rserpool] Elimination of Registration Response Success /w Warning/Modificat ion from ASAP draft 


Currently the registration procedure of the ASAP draft in section 3.1 supports three cases. 

1) Success
2) Success /w warnings/modifications
3) Failure

I believe that the registration procedure should only result in either success or failure eliminating case 2. 

Let me explain.

For instance, let say the PE can't adapt its policy from the policy sent in the registration message. If the PE receives a registration success /w warnings/modifications and can't adapt, it should remove itself from the pool. Then the PE would need to deregister or not re-register itself to be removed from the pool. This would cause updates to happen across all peer ENRP servers since the PE would need to be removed from the pool to which it was recently added, resulting in many messages being sent to maintain namespace synchronization. Also before this deregistration occurred, several PUs could have starting using this PE for service which results in its own problems. 

If instead the registration was rejected using the operation error codes regarding the problem, the PE could simply send a single message to register again if changes could be made. Otherwise no message would be sent if the PE couldn't adapt. 

I believe this is much simpler and would result in fewer overall messages being sent within the RSerPool architecture and would result in a cleaner ASAP implementation. 

What does everyone think? 

_______________________________________________
rserpool mailing list
rserpool@ietf.org
https://www1.ietf.org/mailman/listinfo/rserpool

_______________________________________________
rserpool mailing list
rserpool@ietf.org
https://www1.ietf.org/mailman/listinfo/rserpool


From rserpool-bounces@ietf.org  Thu Oct 14 18:24:16 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14600
	for <rserpool-archive@lists.ietf.org>; Thu, 14 Oct 2004 18:24:16 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CIDw6-0000k7-Ey; Thu, 14 Oct 2004 18:19:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CIDsk-0007FY-2g
	for rserpool@megatron.ietf.org; Thu, 14 Oct 2004 18:15:34 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13214
	for <rserpool@ietf.org>; Thu, 14 Oct 2004 18:15:31 -0400 (EDT)
Received: from mail-n.franken.de
	([193.175.24.27] helo=ilsa.franken.de ident=postfix)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CIE3x-0007WG-RD
	for rserpool@ietf.org; Thu, 14 Oct 2004 18:27:11 -0400
Received: from [192.168.1.22] (p5089E64D.dip.t-dialin.net [80.137.230.77])
	by ilsa.franken.de (Postfix) with ESMTP
	id BE4C5245F3; Fri, 15 Oct 2004 00:15:29 +0200 (CEST)
	(KNF account authenticated via SMTP-AUTH)
In-Reply-To: <FD52892BD296D71183B400065BFCB6901067DFCD@il02exm12>
References: <FD52892BD296D71183B400065BFCB6901067DFCD@il02exm12>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <894BF7E5-1E2E-11D9-9819-000D932C78D8@lurchi.franken.de>
Content-Transfer-Encoding: 7bit
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Subject: Re: [Rserpool] Elimination of Registration Response Success /w Wa
	rning/Modificat ion from ASAP draft 
Date: Fri, 15 Oct 2004 00:15:20 +0200
To: Silverton Aron-C1710C <Aron.J.Silverton@motorola.com>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.3 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Content-Transfer-Encoding: 7bit
Cc: rserpool@ietf.org
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Sender: rserpool-bounces@ietf.org
Errors-To: rserpool-bounces@ietf.org
Content-Transfer-Encoding: 7bit

I also support this. It makes the protocol simpler.

Best regards
Michael

On Oct 14, 2004, at 23:37 Uhr, Silverton Aron-C1710C wrote:

> I agree with the proposal below.  The current method assumes that the 
> PE is capable of supporting whichever pool policy is returned in the 
> warnings/modifications.  I don't think that this is a safe assumption, 
> so I support the change.
>
> Aron
>
> -----Original Message-----
> From: rserpool-bounces@ietf.org [mailto:rserpool-bounces@ietf.org] On 
> Behalf Of Johnson Walter-CWJ002
> Sent: Thursday, October 14, 2004 3:23 PM
> To: rserpool@ietf.org
> Subject: [Rserpool] Elimination of Registration Response Success /w 
> Warning/Modificat ion from ASAP draft
>
>
> Currently the registration procedure of the ASAP draft in section 3.1 
> supports three cases.
>
> 1) Success
> 2) Success /w warnings/modifications
> 3) Failure
>
> I believe that the registration procedure should only result in either 
> success or failure eliminating case 2.
>
> Let me explain.
>
> For instance, let say the PE can't adapt its policy from the policy 
> sent in the registration message. If the PE receives a registration 
> success /w warnings/modifications and can't adapt, it should remove 
> itself from the pool. Then the PE would need to deregister or not 
> re-register itself to be removed from the pool. This would cause 
> updates to happen across all peer ENRP servers since the PE would need 
> to be removed from the pool to which it was recently added, resulting 
> in many messages being sent to maintain namespace synchronization. 
> Also before this deregistration occurred, several PUs could have 
> starting using this PE for service which results in its own problems.
>
> If instead the registration was rejected using the operation error 
> codes regarding the problem, the PE could simply send a single message 
> to register again if changes could be made. Otherwise no message would 
> be sent if the PE couldn't adapt.
>
> I believe this is much simpler and would result in fewer overall 
> messages being sent within the RSerPool architecture and would result 
> in a cleaner ASAP implementation.
>
> What does everyone think?
>
> _______________________________________________
> rserpool mailing list
> rserpool@ietf.org
> https://www1.ietf.org/mailman/listinfo/rserpool
>
> _______________________________________________
> rserpool mailing list
> rserpool@ietf.org
> https://www1.ietf.org/mailman/listinfo/rserpool
>


_______________________________________________
rserpool mailing list
rserpool@ietf.org
https://www1.ietf.org/mailman/listinfo/rserpool


From rserpool-bounces@ietf.org  Thu Oct 14 20:18:41 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA23982
	for <rserpool-archive@lists.ietf.org>; Thu, 14 Oct 2004 20:18:41 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CIFiR-0002Vw-2P; Thu, 14 Oct 2004 20:13:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CIFhZ-0002II-H4
	for rserpool@megatron.ietf.org; Thu, 14 Oct 2004 20:12:09 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA23756
	for <rserpool@ietf.org>; Thu, 14 Oct 2004 20:12:07 -0400 (EDT)
Received: from motgate6.mot.com ([144.189.100.106])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CIFsm-0001QR-FZ
	for rserpool@ietf.org; Thu, 14 Oct 2004 20:23:47 -0400
Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231])
	by motgate6.mot.com (Motorola/Motgate6) with ESMTP id i9F0C33x025414;
	Thu, 14 Oct 2004 17:12:03 -0700 (MST)
Received: from motorola.com (d1421-0a1071e2.cig.mot.com [10.16.113.226])
	by az33exr01.mot.com (Motorola/az33exr01) with ESMTP id i9F042tD027451; 
	Thu, 14 Oct 2004 19:04:02 -0500
Message-ID: <416F1649.5060007@motorola.com>
Date: Thu, 14 Oct 2004 19:14:01 -0500
From: Qiaobing Xie <Qiaobing.Xie@motorola.com>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Subject: Re: [Rserpool] Elimination of Registration Response Success /w Wa
	rning/Modificat ion from ASAP draft
References: <FD52892BD296D71183B400065BFCB6901067DFCD@il02exm12>
	<894BF7E5-1E2E-11D9-9819-000D932C78D8@lurchi.franken.de>
In-Reply-To: <894BF7E5-1E2E-11D9-9819-000D932C78D8@lurchi.franken.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Content-Transfer-Encoding: 7bit
Cc: rserpool@ietf.org, Silverton Aron-C1710C <Aron.J.Silverton@motorola.com>
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Sender: rserpool-bounces@ietf.org
Errors-To: rserpool-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Sounds good to me.

-Q

Michael Tuexen wrote:

> I also support this. It makes the protocol simpler.
> 
> Best regards
> Michael
> 
> On Oct 14, 2004, at 23:37 Uhr, Silverton Aron-C1710C wrote:
> 
>> I agree with the proposal below.  The current method assumes that the 
>> PE is capable of supporting whichever pool policy is returned in the 
>> warnings/modifications.  I don't think that this is a safe assumption, 
>> so I support the change.
>>
>> Aron
>>
>> -----Original Message-----
>> From: rserpool-bounces@ietf.org [mailto:rserpool-bounces@ietf.org] On 
>> Behalf Of Johnson Walter-CWJ002
>> Sent: Thursday, October 14, 2004 3:23 PM
>> To: rserpool@ietf.org
>> Subject: [Rserpool] Elimination of Registration Response Success /w 
>> Warning/Modificat ion from ASAP draft
>>
>>
>> Currently the registration procedure of the ASAP draft in section 3.1 
>> supports three cases.
>>
>> 1) Success
>> 2) Success /w warnings/modifications
>> 3) Failure
>>
>> I believe that the registration procedure should only result in either 
>> success or failure eliminating case 2.
>>
>> Let me explain.
>>
>> For instance, let say the PE can't adapt its policy from the policy 
>> sent in the registration message. If the PE receives a registration 
>> success /w warnings/modifications and can't adapt, it should remove 
>> itself from the pool. Then the PE would need to deregister or not 
>> re-register itself to be removed from the pool. This would cause 
>> updates to happen across all peer ENRP servers since the PE would need 
>> to be removed from the pool to which it was recently added, resulting 
>> in many messages being sent to maintain namespace synchronization. 
>> Also before this deregistration occurred, several PUs could have 
>> starting using this PE for service which results in its own problems.
>>
>> If instead the registration was rejected using the operation error 
>> codes regarding the problem, the PE could simply send a single message 
>> to register again if changes could be made. Otherwise no message would 
>> be sent if the PE couldn't adapt.
>>
>> I believe this is much simpler and would result in fewer overall 
>> messages being sent within the RSerPool architecture and would result 
>> in a cleaner ASAP implementation.
>>
>> What does everyone think?
>>
>> _______________________________________________
>> rserpool mailing list
>> rserpool@ietf.org
>> https://www1.ietf.org/mailman/listinfo/rserpool
>>
>> _______________________________________________
>> rserpool mailing list
>> rserpool@ietf.org
>> https://www1.ietf.org/mailman/listinfo/rserpool
>>
> 
> 
> _______________________________________________
> rserpool mailing list
> rserpool@ietf.org
> https://www1.ietf.org/mailman/listinfo/rserpool
> 


_______________________________________________
rserpool mailing list
rserpool@ietf.org
https://www1.ietf.org/mailman/listinfo/rserpool


From rserpool-bounces@ietf.org  Fri Oct 15 05:49:29 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA11210
	for <rserpool-archive@lists.ietf.org>; Fri, 15 Oct 2004 05:49:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CIOfD-0000tD-21; Fri, 15 Oct 2004 05:46:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CIOeU-0000jp-1M
	for rserpool@megatron.ietf.org; Fri, 15 Oct 2004 05:45:34 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10853
	for <rserpool@ietf.org>; Fri, 15 Oct 2004 05:45:31 -0400 (EDT)
Received: from ns.iem.uni-due.de ([132.252.150.1]
	helo=pilz.exp-math.uni-essen.de)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CIOpo-0002O7-SF
	for rserpool@ietf.org; Fri, 15 Oct 2004 05:57:17 -0400
Received: from kappes.exp-math.uni-essen.de (kappes.exp-math.uni-essen.de
	[132.252.150.151])
	by pilz.exp-math.uni-essen.de (8.12.10/8.12.8) with ESMTP id
	i9F9jAOp063438; Fri, 15 Oct 2004 11:45:11 +0200
From: Thomas Dreibholz <dreibh@exp-math.uni-essen.de>
Organization: University of Essen, Institute for Experimental Mathematics
To: rserpool@ietf.org
Subject: Re: [Rserpool] Elimination of Registration Response Success /w
	Warning/Modificat ion from ASAP draft
Date: Fri, 15 Oct 2004 11:28:16 +0200
User-Agent: KMail/1.6.1
References: <6F8DFFA2C996D711945800065BFC9E4A10EAA47A@il02exm11>
In-Reply-To: <6F8DFFA2C996D711945800065BFC9E4A10EAA47A@il02exm11>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: Text/Plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable
Message-Id: <200410151128.19863.dreibh@exp-math.uni-essen.de>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Content-Transfer-Encoding: quoted-printable
Cc: "'rserpool@ietf.org'" <rserpool@ietf.org>
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Sender: rserpool-bounces@ietf.org
Errors-To: rserpool-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 14 October 2004 22:23, Johnson Walter-CWJ002 wrote:
> Currently the registration procedure of the ASAP draft in section 3.1
> supports three cases.
>
> 1) Success
> 2) Success /w warnings/modifications
> 3) Failure
>
> I believe that the registration procedure should only result in either
> success or failure eliminating case 2.
>
> Let me explain.
>
> For instance, let say the PE can't adapt its policy from the policy sent =
in
> the registration message. If the PE receives a registration success /w
> warnings/modifications and can't adapt, it should remove itself from the
> pool. Then the PE would need to deregister or not re-register itself to be
> removed from the pool. This would cause updates to happen across all peer
> ENRP servers since the PE would need to be removed from the pool to which
> it was recently added, resulting in many messages being sent to maintain
> namespace synchronization. Also before this deregistration occurred,
> several PUs could have starting using this PE for service which results in
> its own problems.
>
> If instead the registration was rejected using the operation error codes
> regarding the problem, the PE could simply send a single message to
> register again if changes could be made. Otherwise no message would be se=
nt
> if the PE couldn't adapt.
>
> I believe this is much simpler and would result in fewer overall messages
> being sent within the RSerPool architecture and would result in a cleaner
> ASAP implementation.
>
> What does everyone think?

This is useful. The rsplib prototype already does not try to adapt a PE's=20
policy to another one and directly rejects the registration with an=20
appropriate error code.


Best regards
=2D --=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
 Dipl.-Inform. Thomas Dreibholz

 University of Essen,                            Room ES210
 Inst. for Experimental Mathematics              Ellernstra=DFe 29
 Computer Networking Technology Group            D-45326 Essen/Germany
=2D -----------------------------------------------------------------------
 E-Mail:     dreibh@exp-math.uni-essen.de
 Homepage:   http://www.exp-math.uni-essen.de/~dreibh
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBb5gz32BbsHYPLWURAmveAJ47qMvbDioUFPj4as29rHoxzUHHVwCfTOWr
ExhfTnrZhoDVenpk557TSy8=3D
=3DUiUO
=2D----END PGP SIGNATURE-----

_______________________________________________
rserpool mailing list
rserpool@ietf.org
https://www1.ietf.org/mailman/listinfo/rserpool


From rserpool-bounces@ietf.org  Fri Oct 15 17:04:42 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19346
	for <rserpool-archive@lists.ietf.org>; Fri, 15 Oct 2004 17:04:42 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CIYSy-0000H5-GK; Fri, 15 Oct 2004 16:14:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CIY7J-0002mb-6Z; Fri, 15 Oct 2004 15:51:57 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04192;
	Fri, 15 Oct 2004 15:51:54 -0400 (EDT)
Message-Id: <200410151951.PAA04192@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Fri, 15 Oct 2004 15:51:54 -0400
Cc: rserpool@ietf.org
Subject: [Rserpool] I-D ACTION:draft-ietf-rserpool-asap-10.txt
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Sender: rserpool-bounces@ietf.org
Errors-To: rserpool-bounces@ietf.org

--NextPart

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-10.txt
	Pages		: 43
	Date		: 2004-10-15
	
Aggregate Server Access Protocol (ASAP) in conjunction with the
   Endpoint Name Resolution Protocol (ENRP) [7] provides a high
   availability data transfer mechanism over IP networks.  ASAP uses a
   name-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.

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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@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-asap-10.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-rserpool-asap-10.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2004-10-15154233.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rserpool-asap-10.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-rserpool-asap-10.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2004-10-15154233.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
rserpool mailing list
rserpool@ietf.org
https://www1.ietf.org/mailman/listinfo/rserpool

--NextPart--





From rserpool-bounces@ietf.org  Fri Oct 15 17:07:52 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20157
	for <rserpool-archive@lists.ietf.org>; Fri, 15 Oct 2004 17:07:52 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CIYT3-0000Lx-EN; Fri, 15 Oct 2004 16:14:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CIY7n-00037f-Ot; Fri, 15 Oct 2004 15:52:27 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04245;
	Fri, 15 Oct 2004 15:52:25 -0400 (EDT)
Message-Id: <200410151952.PAA04245@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Fri, 15 Oct 2004 15:52:25 -0400
Cc: rserpool@ietf.org
Subject: [Rserpool] I-D ACTION:draft-ietf-rserpool-common-param-07.txt
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Sender: rserpool-bounces@ietf.org
Errors-To: rserpool-bounces@ietf.org

--NextPart

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 
			  Name Resolution (ENRP) Parameters
	Author(s)	: R. Stewart, et al.
	Filename	: draft-ietf-rserpool-common-param-07.txt
	Pages		: 24
	Date		: 2004-10-15
	
This document details the parameters of the Aggregate Server Access
Protocol (ASAP) and Endpoint Name Resolution 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-07.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@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-07.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-rserpool-common-param-07.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2004-10-15154240.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rserpool-common-param-07.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-rserpool-common-param-07.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2004-10-15154240.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
rserpool mailing list
rserpool@ietf.org
https://www1.ietf.org/mailman/listinfo/rserpool

--NextPart--





From rserpool-bounces@ietf.org  Fri Oct 15 17:12:01 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21260
	for <rserpool-archive@lists.ietf.org>; Fri, 15 Oct 2004 17:12:01 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CIYT8-0000R7-78; Fri, 15 Oct 2004 16:14:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CIY8C-0003GS-Qa; Fri, 15 Oct 2004 15:52:52 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04299;
	Fri, 15 Oct 2004 15:52:50 -0400 (EDT)
Message-Id: <200410151952.PAA04299@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Fri, 15 Oct 2004 15:52:50 -0400
Cc: rserpool@ietf.org
Subject: [Rserpool] I-D ACTION:draft-ietf-rserpool-enrp-10.txt
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Sender: rserpool-bounces@ietf.org
Errors-To: rserpool-bounces@ietf.org

--NextPart

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		: Enpoint Name Resolution Protocol (ENRP)
	Author(s)	: Q. Xie, et al.
	Filename	: draft-ietf-rserpool-enrp-10.txt
	Pages		: 45
	Date		: 2004-10-15
	
Endpoint Name Resolution 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-10.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@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-enrp-10.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-rserpool-enrp-10.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2004-10-15154247.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rserpool-enrp-10.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-rserpool-enrp-10.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2004-10-15154247.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
rserpool mailing list
rserpool@ietf.org
https://www1.ietf.org/mailman/listinfo/rserpool

--NextPart--





From rserpool-bounces@ietf.org  Thu Oct 21 20:21:47 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA10800
	for <rserpool-archive@lists.ietf.org>; Thu, 21 Oct 2004 20:21:47 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CKl6k-0005O3-CV; Thu, 21 Oct 2004 18:08:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CKj7T-0002uo-FC; Thu, 21 Oct 2004 16:01:07 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14159;
	Thu, 21 Oct 2004 16:01:05 -0400 (EDT)
Message-Id: <200410212001.QAA14159@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Thu, 21 Oct 2004 16:01:05 -0400
Cc: rserpool@ietf.org
Subject: [Rserpool] I-D ACTION:draft-ietf-rserpool-policies-00.txt
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Sender: rserpool-bounces@ietf.org
Errors-To: rserpool-bounces@ietf.org

--NextPart

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-00.txt
	Pages		: 13
	Date		: 2004-10-20
	
This document describes server pool policies for Reliable Server
   Pooling including considerations for implementing them at name
   servers and pool users.

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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@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-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-rserpool-policies-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2004-10-21154752.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rserpool-policies-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-rserpool-policies-00.txt"; site="ftp.ietf.org";
	access-type="anon-ftp"; directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2004-10-21154752.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
rserpool mailing list
rserpool@ietf.org
https://www1.ietf.org/mailman/listinfo/rserpool

--NextPart--





From rserpool-bounces@ietf.org  Fri Oct 22 13:54:46 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24682
	for <rserpool-archive@lists.ietf.org>; Fri, 22 Oct 2004 13:54:46 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CL3V9-0003Vv-6I; Fri, 22 Oct 2004 13:46:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CL3RP-00027M-4f
	for rserpool@megatron.ietf.org; Fri, 22 Oct 2004 13:43:03 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23780
	for <rserpool@ietf.org>; Fri, 22 Oct 2004 13:43:00 -0400 (EDT)
From: Maureen.Stillman@nokia.com
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CL3eD-000305-6w
	for rserpool@ietf.org; Fri, 22 Oct 2004 13:56:18 -0400
Received: from esdks002.ntc.nokia.com (esdks002.ntc.nokia.com [172.21.138.121])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	i9MHgu303909
	for <rserpool@ietf.org>; Fri, 22 Oct 2004 20:42:56 +0300 (EET DST)
X-Scanned: Fri, 22 Oct 2004 20:42:51 +0300 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks002.ntc.nokia.com (8.12.9/8.12.9) id i9MHgptK013017
	for <rserpool@ietf.org>; Fri, 22 Oct 2004 20:42:51 +0300
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks002.ntc.nokia.com 00wxSeAg; Fri, 22 Oct 2004 20:42:49 EEST
Received: from daebh002.NOE.Nokia.com (daebh002.americas.nokia.com
	[10.241.35.122])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	i9MHgma25503
	for <rserpool@ietf.org>; Fri, 22 Oct 2004 20:42:48 +0300 (EET DST)
Received: from daebe007.NOE.Nokia.com ([10.241.35.107]) by
	daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Fri, 22 Oct 2004 12:42:38 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 22 Oct 2004 12:42:38 -0500
Message-ID: <57A26D272F67A743952F6B4371B8F8110409101B@daebe007.americas.nokia.com>
Thread-Topic: remind authors to update their IPR boilerplate, please!
Thread-Index: AcS4VGfSxgBJgqN2SzClFhVv12w1PwACbYqA
To: <rserpool@ietf.org>
X-OriginalArrivalTime: 22 Oct 2004 17:42:39.0137 (UTC)
	FILETIME=[86367910:01C4B85E]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: quoted-printable
Subject: [Rserpool] FW: remind authors to update their IPR boilerplate,
	please!
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Sender: rserpool-bounces@ietf.org
Errors-To: rserpool-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

This is a reminder from the transport ADs to ask everyone to comply with
the new IPR boilerplate for internet drafts.  RFC 3667 is now being
enforced.

-- Maureen

-----Original Message-----
From: ext Allison Mankin [mailto:mankin@psg.com]=20
Sent: Friday, October 22, 2004 12:26 PM
To: tsv-chairs@ietf.org
Subject: remind authors to update their IPR boilerplate, please!

Folks,

Please please remind everyone to update their IPR boilerplate to
RFC 3667, or, even better, the fixed version, as documented in
http://www.ietf.org/ietf/1id-guidelines.txt. =20

So please get all authors to be extra careful!

Allison and Jon

_______________________________________________
rserpool mailing list
rserpool@ietf.org
https://www1.ietf.org/mailman/listinfo/rserpool


From rserpool-bounces@ietf.org  Fri Oct 22 14:54:55 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29199
	for <rserpool-archive@lists.ietf.org>; Fri, 22 Oct 2004 14:54:55 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CL4Vq-0005Ke-LJ; Fri, 22 Oct 2004 14:51:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CL4QN-00033w-Uk
	for rserpool@megatron.ietf.org; Fri, 22 Oct 2004 14:46:04 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28444
	for <rserpool@ietf.org>; Fri, 22 Oct 2004 14:46:00 -0400 (EDT)
From: Maureen.Stillman@nokia.com
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CL4dC-00049v-H0
	for rserpool@ietf.org; Fri, 22 Oct 2004 14:59:19 -0400
Received: from esdks001.ntc.nokia.com (esdks001.ntc.nokia.com [172.21.138.120])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	i9MIjvo27617
	for <rserpool@ietf.org>; Fri, 22 Oct 2004 21:45:57 +0300 (EET DST)
X-Scanned: Fri, 22 Oct 2004 21:45:41 +0300 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks001.ntc.nokia.com (8.12.9/8.12.9) id i9MIjfdG028783
	for <rserpool@ietf.org>; Fri, 22 Oct 2004 21:45:41 +0300
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks001.ntc.nokia.com 00exP51i; Fri, 22 Oct 2004 21:45:24 EEST
Received: from daebh002.NOE.Nokia.com (daebh002.americas.nokia.com
	[10.241.35.122])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	i9MIjLa14960
	for <rserpool@ietf.org>; Fri, 22 Oct 2004 21:45:22 +0300 (EET DST)
Received: from daebe007.NOE.Nokia.com ([10.241.35.107]) by
	daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Fri, 22 Oct 2004 13:44:53 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 22 Oct 2004 13:44:52 -0500
Message-ID: <57A26D272F67A743952F6B4371B8F81104091029@daebe007.americas.nokia.com>
Thread-Topic: Agenda for IETF #61 in Wash DC
Thread-Index: AcS4Zv5lckWds0HYQISeuhTq7liwiQ==
To: <rserpool@ietf.org>
X-OriginalArrivalTime: 22 Oct 2004 18:44:54.0029 (UTC)
	FILETIME=[3861C3D0:01C4B867]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 6d62ab47271805379d7172ee693a45db
Content-Transfer-Encoding: quoted-printable
Subject: [Rserpool] Agenda for IETF #61 in Wash DC
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Sender: rserpool-bounces@ietf.org
Errors-To: rserpool-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

Please send proposed agenda items for IETF #61.

Thanks.

-- Maureen

_______________________________________________
rserpool mailing list
rserpool@ietf.org
https://www1.ietf.org/mailman/listinfo/rserpool


From rserpool-bounces@ietf.org  Mon Oct 25 19:05:11 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09495
	for <rserpool-archive@lists.ietf.org>; Mon, 25 Oct 2004 19:05:11 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CMBUV-0004bO-Io; Mon, 25 Oct 2004 16:30:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CMB6y-0007Mr-Q6; Mon, 25 Oct 2004 16:06:36 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29870;
	Mon, 25 Oct 2004 16:06:34 -0400 (EDT)
Message-Id: <200410252006.QAA29870@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Mon, 25 Oct 2004 16:06:34 -0400
Cc: rserpool@ietf.org
Subject: [Rserpool] I-D ACTION:draft-ietf-rserpool-arch-08.txt
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Sender: rserpool-bounces@ietf.org
Errors-To: rserpool-bounces@ietf.org

--NextPart

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		: Architecture for Reliable Server Pooling
	Author(s)	: M. Tuexen, et al.
	Filename	: draft-ietf-rserpool-arch-08.txt
	Pages		: 21
	Date		: 2004-10-25
	
This document describes an architecture and protocols for the
management and operation of server pools supporting highly reliable
applications, and for client access mechanisms to a server pool.

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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@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-arch-08.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-rserpool-arch-08.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2004-10-25162213.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rserpool-arch-08.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-rserpool-arch-08.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2004-10-25162213.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
rserpool mailing list
rserpool@ietf.org
https://www1.ietf.org/mailman/listinfo/rserpool

--NextPart--





From rserpool-bounces@ietf.org  Thu Oct 28 22:32:51 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA24260
	for <rserpool-archive@lists.ietf.org>; Thu, 28 Oct 2004 22:32:51 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CNKCc-0001o9-8t; Thu, 28 Oct 2004 20:01:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CNIiA-0002oR-0O
	for rserpool@megatron.ietf.org; Thu, 28 Oct 2004 18:25:38 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28989
	for <rserpool@ietf.org>; Thu, 28 Oct 2004 18:25:35 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNIwH-0008W4-Mz
	for rserpool@ietf.org; Thu, 28 Oct 2004 18:40:16 -0400
Received: from il06exr06.mot.com (il06exr06.mot.com [129.188.137.136])
	by motgate8.mot.com (Motorola/Motgate8) with ESMTP id i9SMQlG2002825
	for <rserpool@ietf.org>; Thu, 28 Oct 2004 15:26:47 -0700 (MST)
Received: from il02exm11.corp.mot.com (il02exm11.corp.mot.com [10.0.111.22])
	by il06exr06.mot.com (Motorola/il06exr06) with ESMTP id i9SMPMZX018958
	for <rserpool@ietf.org>; Thu, 28 Oct 2004 17:25:23 -0500
Received: by il02exm11 with Internet Mail Service (5.5.2657.72)
	id <TD9Z97HN>; Thu, 28 Oct 2004 17:25:22 -0500
Message-ID: <6F8DFFA2C996D711945800065BFC9E4A119D4E6B@il02exm11>
From: Johnson Walter-CWJ002 <Walter.Johnson@motorola.com>
To: "'rserpool@ietf.org'" <rserpool@ietf.org>
Date: Thu, 28 Oct 2004 17:25:20 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Subject: [Rserpool] ENRP Server Hunt Timer
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Sender: rserpool-bounces@ietf.org
Errors-To: rserpool-bounces@ietf.org

Currently the draft states in ENRP server hunt procedure of section 3.6 bullet item SH5 on page 21 that

SH5) If the T5-Serverhunt timer expires the following should be
      performed:

      SH5.1) The endpoint MUST double the value of the T5-Serverhunt
         timer.
      SH5.2) The endpoint SHOULD stop the establishment of associations
         and connections.
      SH5.2) The endpoint SHOULD repeat trying to establish an
         association or connection by proceeding to step SH1.  It SHOULD
         attempt to select a different set of transport addresses to
         connect to.

Currently the T5-Serverhunt timer keeps on doubling and there is no upper limit on this so it appears it could go on forever. It would seem reasonable to add a ceiling on the max value that the T5-Serverhunt can reach (e.g. a variable max.severhunt.value to section 5.1) or place to place a threshold of attempts to make called MAX-SERVER-HUNTS in section 5.3. If either max is reached, a signal could be sent to an ASAP application of the failure to find a home ENRP server. 

If people feel this is a good change I can craft the text for it.

_______________________________________________
rserpool mailing list
rserpool@ietf.org
https://www1.ietf.org/mailman/listinfo/rserpool


From rserpool-bounces@ietf.org  Fri Oct 29 06:36:29 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA15383
	for <rserpool-archive@lists.ietf.org>; Fri, 29 Oct 2004 06:36:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CNTiP-0006LV-Ud; Fri, 29 Oct 2004 06:10:37 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CNTOb-00037E-6x
	for rserpool@megatron.ietf.org; Fri, 29 Oct 2004 05:50:09 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12779
	for <rserpool@ietf.org>; Fri, 29 Oct 2004 05:50:06 -0400 (EDT)
Received: from ms.exp-math.uni-essen.de ([132.252.150.1]
	helo=pilz.exp-math.uni-essen.de)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNTcq-0002FM-MO
	for rserpool@ietf.org; Fri, 29 Oct 2004 06:04:53 -0400
Received: from kappes.exp-math.uni-essen.de (kappes.exp-math.uni-essen.de
	[132.252.150.151])
	by pilz.exp-math.uni-essen.de (8.12.10/8.12.8) with ESMTP id
	i9T9njlV033782; Fri, 29 Oct 2004 11:49:45 +0200
From: Thomas Dreibholz <dreibh@exp-math.uni-essen.de>
Organization: University of Essen, Institute for Experimental Mathematics
To: rserpool@ietf.org
Subject: Re: [Rserpool] ENRP Server Hunt Timer
Date: Fri, 29 Oct 2004 11:49:42 +0200
User-Agent: KMail/1.6.1
References: <6F8DFFA2C996D711945800065BFC9E4A119D4E6B@il02exm11>
In-Reply-To: <6F8DFFA2C996D711945800065BFC9E4A119D4E6B@il02exm11>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: Text/Plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable
Message-Id: <200410291149.45463.dreibh@exp-math.uni-essen.de>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Content-Transfer-Encoding: quoted-printable
Cc: "'rserpool@ietf.org'" <rserpool@ietf.org>
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Sender: rserpool-bounces@ietf.org
Errors-To: rserpool-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 29 October 2004 00:25, Johnson Walter-CWJ002 wrote:
> Currently the draft states in ENRP server hunt procedure of section 3.6
> bullet item SH5 on page 21 that
>
> SH5) If the T5-Serverhunt timer expires the following should be
>       performed:
>
>       SH5.1) The endpoint MUST double the value of the T5-Serverhunt
>          timer.
>       SH5.2) The endpoint SHOULD stop the establishment of associations
>          and connections.
>       SH5.2) The endpoint SHOULD repeat trying to establish an
>          association or connection by proceeding to step SH1.  It SHOULD
>          attempt to select a different set of transport addresses to
>          connect to.
>
> Currently the T5-Serverhunt timer keeps on doubling and there is no upper
> limit on this so it appears it could go on forever. It would seem
> reasonable to add a ceiling on the max value that the T5-Serverhunt can
> reach (e.g. a variable max.severhunt.value to section 5.1) or place to
> place a threshold of attempts to make called MAX-SERVER-HUNTS in section
> 5.3. If either max is reached, a signal could be sent to an ASAP
> application of the failure to find a home ENRP server.

An upper limit for doubling the timeout is useful.=20

But it may be useful to keep on trying to connect to a NS even when the=20
maximum timeout has been reached, because it may be better for the=20
application to wait instead of failing. For this case, the number of trials=
=20
must also be limited (this could be a configuration option, to be set by th=
e=20
application - I have implemented this behavior in the rsplib prototype).

Example:
TimeoutLimit=3D4s
MaxTrials=3D100

Trail #1: timeout=3D1s
Trail #2: timeout=3D2s
Trail #3: timeout=3D4s (no more doubling)
Trail #4: timeout=3D4s
=2E..
Trail #100: timeout=3D4s  =3D> After this trial, signal failure to the user.


Best regards
=2D --=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
 Dipl.-Inform. Thomas Dreibholz

 University of Essen,                            Room ES210
 Inst. for Experimental Mathematics              Ellernstra=DFe 29
 Computer Networking Technology Group            D-45326 Essen/Germany
=2D -----------------------------------------------------------------------
 E-Mail:     dreibh@exp-math.uni-essen.de
 Homepage:   http://www.exp-math.uni-essen.de/~dreibh
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBghI232BbsHYPLWURAiX8AKDPMGqdnaEzkEe4Jncw0rItrMD/6QCeJgHz
obx1jzEZegkuMyaM2C+m/kE=3D
=3DRjHb
=2D----END PGP SIGNATURE-----

_______________________________________________
rserpool mailing list
rserpool@ietf.org
https://www1.ietf.org/mailman/listinfo/rserpool


From rserpool-bounces@ietf.org  Fri Oct 29 11:05:32 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07559
	for <rserpool-archive@lists.ietf.org>; Fri, 29 Oct 2004 11:05:32 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CNY1r-0007Ph-AB; Fri, 29 Oct 2004 10:46:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CNXkv-0005Fl-AW
	for rserpool@megatron.ietf.org; Fri, 29 Oct 2004 10:29:29 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04470
	for <rserpool@ietf.org>; Fri, 29 Oct 2004 10:29:27 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNXzD-00005G-LN
	for rserpool@ietf.org; Fri, 29 Oct 2004 10:44:16 -0400
Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133])
	by motgate8.mot.com (Motorola/Motgate8) with ESMTP id i9TEUhG2004414
	for <rserpool@ietf.org>; Fri, 29 Oct 2004 07:30:46 -0700 (MST)
Received: from il02exm11.corp.mot.com (il02exm11.corp.mot.com [10.0.111.22])
	by il06exr03.mot.com (Motorola/il06exr03) with ESMTP id i9TET3bs028118
	for <rserpool@ietf.org>; Fri, 29 Oct 2004 09:29:03 -0500
Received: by il02exm11 with Internet Mail Service (5.5.2657.72)
	id <TD9Z0PXY>; Fri, 29 Oct 2004 09:29:03 -0500
Message-ID: <6F8DFFA2C996D711945800065BFC9E4A119D542C@il02exm11>
From: Johnson Walter-CWJ002 <Walter.Johnson@motorola.com>
To: "'Thomas Dreibholz'" <dreibh@exp-math.uni-essen.de>,
        "'rserpool@ietf.org'" <rserpool@ietf.org>
Subject: RE: [Rserpool] ENRP Server Hunt Timer
Date: Fri, 29 Oct 2004 09:29:02 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Sender: rserpool-bounces@ietf.org
Errors-To: rserpool-bounces@ietf.org

Thomas Dreibholz <mailto:dreibh@exp-math.uni-essen.de> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Friday 29 October 2004 00:25, Johnson Walter-CWJ002 wrote:
>> Currently the draft states in ENRP server hunt procedure of section
>> 3.6 bullet item SH5 on page 21 that
>> 
>> SH5) If the T5-Serverhunt timer expires the following should be     
>> performed: 
>> 
>>       SH5.1) The endpoint MUST double the value of the T5-Serverhunt
>>       timer. SH5.2) The endpoint SHOULD stop the establishment of
>>       associations          and connections. SH5.2) The endpoint
>>          SHOULD repeat trying to establish an association or
>>          connection by proceeding to step SH1.  It SHOULD attempt to
>> select a different set of transport addresses to          connect
>> to.  
>> 
>> Currently the T5-Serverhunt timer keeps on doubling and there is no
>> upper limit on this so it appears it could go on forever. It would
>> seem reasonable to add a ceiling on the max value that the
>> T5-Serverhunt can reach (e.g. a variable max.severhunt.value to
>> section 5.1) or place to place a threshold of attempts to make called
>> MAX-SERVER-HUNTS in section 5.3. If either max is reached, a signal
>> could be sent to an ASAP application of the failure to find a home
>> ENRP server.
> 
> An upper limit for doubling the timeout is useful.
> 
> But it may be useful to keep on trying to connect to a NS even when
> the maximum timeout has been reached, because it may be better for the
> application to wait instead of failing. For this case, the number of
> trials must also be limited (this could be a configuration option, to
> be set by the application - I have implemented this behavior in the
> rsplib prototype). 
> 
> Example:
> TimeoutLimit=4s
> MaxTrials=100
> 
> Trail #1: timeout=1s
> Trail #2: timeout=2s
> Trail #3: timeout=4s (no more doubling)
> Trail #4: timeout=4s
> ...
> Trail #100: timeout=4s  => After this trial, signal failure to the
> user. 
> 


I agree with your proposal above.

_______________________________________________
rserpool mailing list
rserpool@ietf.org
https://www1.ietf.org/mailman/listinfo/rserpool


From rserpool-bounces@ietf.org  Fri Oct 29 12:02:57 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11289
	for <rserpool-archive@lists.ietf.org>; Fri, 29 Oct 2004 12:02:57 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CNZ1R-0001q0-P5; Fri, 29 Oct 2004 11:50:37 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CNYwk-0007c7-7G
	for rserpool@megatron.ietf.org; Fri, 29 Oct 2004 11:45:46 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10215
	for <rserpool@ietf.org>; Fri, 29 Oct 2004 11:45:43 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNZB2-0001p3-1u
	for rserpool@ietf.org; Fri, 29 Oct 2004 12:00:33 -0400
Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133])
	by motgate8.mot.com (Motorola/Motgate8) with ESMTP id i9TFl2G2004105
	for <rserpool@ietf.org>; Fri, 29 Oct 2004 08:47:02 -0700 (MST)
Received: from il02exm11.corp.mot.com (il02exm11.corp.mot.com [10.0.111.22])
	by il06exr03.mot.com (Motorola/il06exr03) with ESMTP id i9TFjcbs014237
	for <rserpool@ietf.org>; Fri, 29 Oct 2004 10:45:38 -0500
Received: by il02exm11 with Internet Mail Service (5.5.2657.72)
	id <TD9Z0SLP>; Fri, 29 Oct 2004 10:45:38 -0500
Message-ID: <6F8DFFA2C996D711945800065BFC9E4A11AB1B5F@il02exm11>
From: Johnson Walter-CWJ002 <Walter.Johnson@motorola.com>
To: "'rserpool@ietf.org'" <rserpool@ietf.org>
Date: Fri, 29 Oct 2004 10:45:36 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Subject: [Rserpool] ASAP Deregistration procedure
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rserpool>,
	<mailto:rserpool-request@ietf.org?subject=subscribe>
Sender: rserpool-bounces@ietf.org
Errors-To: rserpool-bounces@ietf.org

What happens if the registration life sent by a PE in the REGISTRATION message expires due to the inability to communicate with the namespace?

According to the drafts the PE is removed from the namespace by the home ENRP server by sending a PEER_NAME_UPDATE. But the PE has no way to know it has been deregistered from the namespace since there are no threshold of attempts like MAX-REG-ATTEMPTS as used in the registration procedure or a timer called T8-Registrationlife that expires to signal the PE was removed from the namespace. So the PE's ASAP layer would continue attempting deregistration. 

I believe a timer for the registration life should be added.

+++++++++++++++=

Another small change: The ASAP draft section 3.2 occurrence of REGISTRATION_RESPONSE should be DEREGISTRATION_RESPONSE.


_______________________________________________
rserpool mailing list
rserpool@ietf.org
https://www1.ietf.org/mailman/listinfo/rserpool


