Re: [Rserpool] ENRP Name Server Takeover Problem
Qiaobing Xie <Qiaobing.Xie@motorola.com> Fri, 27 August 2004 16:01 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 MAA11850 for <rserpool-archive@lists.ietf.org>; Fri, 27 Aug 2004 12:01:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C0j6r-0003Cx-Vu; Fri, 27 Aug 2004 11:57:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C0ixn-000146-1W for rserpool@megatron.ietf.org; Fri, 27 Aug 2004 11:48: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 LAA11048 for <rserpool@ietf.org>; Fri, 27 Aug 2004 11:48:24 -0400 (EDT)
Received: from motgate4.mot.com ([144.189.100.102]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C0iyl-0004hZ-Az for rserpool@ietf.org; Fri, 27 Aug 2004 11:49:40 -0400
Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231]) by motgate4.mot.com (Motorola/Motgate4) with ESMTP id i7RFm9ck023750; Fri, 27 Aug 2004 08:48:10 -0700 (MST)
Received: from motorola.com ([163.14.20.74]) by az33exr01.mot.com (Motorola/az33exr01) with ESMTP id i7RFe5bK014224; Fri, 27 Aug 2004 10:40:08 -0500
Message-ID: <412F580D.2010609@motorola.com>
Date: Fri, 27 Aug 2004 23:49:33 +0800
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] ENRP Name Server Takeover Problem
References: <200408231411.06156.dreibh@exp-math.uni-essen.de> <412D7E9A.9080208@motorola.com> <B257E26E-F748-11D8-9E16-000D932C78D8@lurchi.franken.de>
In-Reply-To: <B257E26E-F748-11D8-9E16-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 motgate4.mot.com id i7RFm9ck023750
X-Spam-Score: 0.0 (/)
X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab
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
Hi, Michael, Michael Tuexen wrote: > Qiaobing, > > I discussed this with Thomas yesterday on the phone and we came to > the same conclusion. Since this ASAP Transport Param is not required > for registration it should be an optional parameter, I think. > > So I'm suggesting to modify the PE parameter to > > 0 1 2 3 > 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Type = 0x8 | Length=variable | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | PE Identifier | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Home ENRP Server Identifier | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Registration Life | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > : User Transport param : > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > : Member Selection Policy param : > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > : ASAP Transport param : > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > > and the ASAP transport parameter > - MUST be an SCTP transport parameter > - is optional. > > Do you agree on that? If yes, I can update the common parameter doc. Yes, I agree. But the ASAP Trans Param probably need to have its own type/length with its data an SCTP trans param. Otherwise you won't be able to receive it if the order is allowed to be flexible (as you suggest below). > > Another point came up on the discussion with Thomas. It is regarding > the sequence of TLV fields in parameters/messages. Is the sequence > required to be the one shown in the documents or are other > sequences also acceptable? > I would argue that they should be sent like they are shown, but the > receiver should accepts them also in other orderings. But we have > to state that somewhere ... after agreeing on a way to handle that. This makes sense to me. regards, -Qiaobing > > Best regards > Michael > > > On Aug 26, 2004, at 8:09 AM, Qiaobing Xie wrote: > >> Thomas, >> >> This makes a lot of sense to me. My recommendation is to add a "ASAP >> Transport Param" field to the PE parameter that is a full SCTP >> transport TLV. Simply adding a SCTP port number field may be too >> restrictive since some PEs may want to use a separate NIC for its >> ASAP communications. >> >> regards, >> -Qiaobing >> >> Thomas Dreibholz wrote: >> >>> -----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 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] 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