[Rserpool] ENRP Name Server Takeover Problem
Thomas Dreibholz <dreibh@exp-math.uni-essen.de> Mon, 23 August 2004 12:56 UTC
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA05978 for <rserpool-archive@lists.ietf.org>; Mon, 23 Aug 2004 08:56: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 1BzDvg-0008H4-Ic; Mon, 23 Aug 2004 08:28:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BzDfP-00062a-EH for rserpool@megatron.ietf.org; Mon, 23 Aug 2004 08:11: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 IAA02708 for <rserpool@ietf.org>; Mon, 23 Aug 2004 08:11:09 -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 1BzDfc-0003Z2-8V for rserpool@ietf.org; Mon, 23 Aug 2004 08:11:29 -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 i7NCB6gG031610 for <rserpool@ietf.org>; Mon, 23 Aug 2004 14:11:06 +0200
From: Thomas Dreibholz <dreibh@exp-math.uni-essen.de>
To: rserpool@ietf.org
Date: Mon, 23 Aug 2004 14:11:02 +0200
User-Agent: KMail/1.6.2
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: Text/Plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Message-Id: <200408231411.06156.dreibh@exp-math.uni-essen.de>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Content-Transfer-Encoding: quoted-printable
Subject: [Rserpool] ENRP Name Server Takeover Problem
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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear all, when a NS takes over the ownership of PEs owned by a failed NS, it sends an ENDPOINT_KEEP_ALIVE message to each of the PEs which change their ownership. As defined in KA2.4 of section 3.4 of the ASAP draft, the PE should adapt the sender of an ENDPOINT_KEEP_ALIVE message as its new NS. But, how does the new NS know the PEs' ASAP endpoint, that is especially the SCTP port number the PE is listening on for ASAP ENDPOINT_KEEP_ALIVES? The old (failed) NS has this information, because the PE established an association to it. But the new NS does not know. Therefore, a specification of the PE's ASAP endpoint must be added to the Pool Element Parameter. Simply adding a field for the SCTP port number should already be sufficient. The addresses to be used can be assumed to be the same as specified in the User Transport parameter. Best regards - -- ======================================================================= Dipl.-Inform. Thomas Dreibholz University of Essen, Room ES210 Inst. for Experimental Mathematics Ellernstraße 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 ======================================================================= -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBKd7Z32BbsHYPLWURAtToAKCrnGWS5cBOmqv/PNXPvkxKxVhWEACeNaM2 rLi5vLWX8fIYJ9py+2iO1MA= =T53y -----END PGP SIGNATURE----- _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool
- [Rserpool] ENRP Name Server Takeover Problem Thomas Dreibholz
- Re: [Rserpool] ENRP Name Server Takeover Problem Qiaobing Xie
- Re: [Rserpool] ENRP Name Server Takeover Problem Thomas Dreibholz
- Re: [Rserpool] ENRP Name Server Takeover Problem Michael Tuexen
- Re: [Rserpool] ENRP Name Server Takeover Problem Qiaobing Xie
- Re: [Rserpool] ENRP Name Server Takeover Problem Thomas Dreibholz