From mailman-bounces@ietf.org Thu Jul 1 08:25:44 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 IAA19461 for ; Thu, 1 Jul 2004 08:25:44 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bfxqr-0001uB-IE for rserpool-archive@lists.ietf.org; Thu, 01 Jul 2004 05:27:29 -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: Date: Thu, 01 Jul 2004 05:07:28 -0400 Precedence: bulk X-BeenThere: mailman@lists.ietf.org X-Mailman-Version: 2.1.5 List-Id: Mailman site list 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 Jul 5 13: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 NAA08485 for ; Mon, 5 Jul 2004 13: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 1BhXIC-0001B4-T6; Mon, 05 Jul 2004 13:30:12 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BhX9x-0000Vr-Mf for rserpool@megatron.ietf.org; Mon, 05 Jul 2004 13:21:41 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07689 for ; Mon, 5 Jul 2004 13:21:35 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BhX9r-0005Ai-MQ for rserpool@ietf.org; Mon, 05 Jul 2004 13:21:35 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BhX8v-0004sj-00 for rserpool@ietf.org; Mon, 05 Jul 2004 13:20:38 -0400 Received: from mail-n.franken.de ([193.175.24.27] helo=ilsa.franken.de ident=postfix) by ietf-mx with esmtp (Exim 4.12) id 1BhX8X-0004aR-00 for rserpool@ietf.org; Mon, 05 Jul 2004 13:20:13 -0400 Received: from [192.168.1.218] (pD9FF1A57.dip.t-dialin.net [217.255.26.87]) by ilsa.franken.de (Postfix) with ESMTP id C8895245CF for ; Mon, 5 Jul 2004 19:17:39 +0200 (CEST) (KNF account authenticated via SMTP-AUTH) Mime-Version: 1.0 (Apple Message framework v618) Content-Transfer-Encoding: 7bit Message-Id: <8F2B3A55-CEA7-11D8-AE6C-000D932C78D8@lurchi.franken.de> Content-Type: text/plain; charset=US-ASCII; format=flowed To: rserpool@ietf.org From: Michael Tuexen Date: Mon, 5 Jul 2004 19:20:06 +0200 X-Mailer: Apple Mail (2.618) X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Subject: [Rserpool] Packet format in ENRP X-BeenThere: rserpool@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Reliable Server Pooling List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: rserpool-bounces@ietf.org Errors-To: rserpool-bounces@ietf.org Content-Transfer-Encoding: 7bit Dear all, while writing the ethereal dissector for ENRP I found some things I would like to change: Section 3.1 The length field is shown as 'Message Length = 0xC' which is not correct because there can be some parameters. Section 3.3 Could we exchange the R and M bit? This would align the R bit position with the reject bit in a PEER_LIST_RESONSE message. Section 3.4 To have a similar layout of the packets i would suggest to change it 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 = 0x4 |0|0|0|0|0|0|0|0| Message Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Sender Server's ID | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Receiver Server's ID | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Update Action | (reserved) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ : Pool handle : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ : Pool Element : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Best regards Michael PS.: ethereal version 0.10.5 will support both ASAP and ENRP... _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From rserpool-bounces@ietf.org Tue Jul 6 16:01: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 QAA18324 for ; Tue, 6 Jul 2004 16:01: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 1Bhvd7-0008GC-UP; Tue, 06 Jul 2004 15:29:25 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bhv7Q-0007am-3J for rserpool@megatron.ietf.org; Tue, 06 Jul 2004 14:56:40 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12391 for ; Tue, 6 Jul 2004 14:56:33 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1Bhv7J-0003xy-SV for rserpool@ietf.org; Tue, 06 Jul 2004 14:56:33 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Bhv5t-0003NS-00 for rserpool@ietf.org; Tue, 06 Jul 2004 14:55:05 -0400 Received: from mail-n.franken.de ([193.175.24.27] helo=ilsa.franken.de ident=postfix) by ietf-mx with esmtp (Exim 4.12) id 1Bhv4S-0002tc-00 for rserpool@ietf.org; Tue, 06 Jul 2004 14:53:36 -0400 Received: from [192.168.1.218] (pD9FF1C4F.dip.t-dialin.net [217.255.28.79]) by ilsa.franken.de (Postfix) with ESMTP id 33DAA245D4 for ; Tue, 6 Jul 2004 20:51:01 +0200 (CEST) (KNF account authenticated via SMTP-AUTH) Mime-Version: 1.0 (Apple Message framework v618) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; format=flowed To: rserpool@ietf.org From: Michael Tuexen Date: Tue, 6 Jul 2004 20:53:22 +0200 X-Mailer: Apple Mail (2.618) X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Subject: [Rserpool] draft-tuexen-rserpool-policies-00.txt X-BeenThere: rserpool@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Reliable Server Pooling List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: rserpool-bounces@ietf.org Errors-To: rserpool-bounces@ietf.org Content-Transfer-Encoding: 7bit Dear all, I just submitted a new ID, an individual submission to the RSerPool WG regarding server pool policies. The ID is also available from http://www.sctp.de/internet-drafts.html Best regards Michael _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From rserpool-bounces@ietf.org Wed Jul 7 10:48:05 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 KAA23787 for ; Wed, 7 Jul 2004 10:48:05 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BiDDW-0005lM-Lt; Wed, 07 Jul 2004 10:16:10 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BiCuj-0003hK-E7 for rserpool@megatron.ietf.org; Wed, 07 Jul 2004 09:56:45 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20097 for ; Wed, 7 Jul 2004 09:56:43 -0400 (EDT) From: Maureen.Stillman@nokia.com Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BiCui-0002MS-Qw for rserpool@ietf.org; Wed, 07 Jul 2004 09:56:44 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BiCto-00020m-00 for rserpool@ietf.org; Wed, 07 Jul 2004 09:55:49 -0400 Received: from mgw-x3.nokia.com ([131.228.20.26]) by ietf-mx with esmtp (Exim 4.12) id 1BiCt9-0001dw-00 for rserpool@ietf.org; Wed, 07 Jul 2004 09:55:07 -0400 Received: from esdks001.ntc.nokia.com (esdks001.ntc.nokia.com [172.21.138.120]) by mgw-x3.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i67Dt2226392 for ; Wed, 7 Jul 2004 16:55:02 +0300 (EET DST) X-Scanned: Wed, 7 Jul 2004 16:54:57 +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 i67DsvtU018658 for ; Wed, 7 Jul 2004 16:54:57 +0300 Received: from mgw-int1.ntc.nokia.com (172.21.143.96) by esdks001.ntc.nokia.com 00Tj5BjL; Wed, 07 Jul 2004 16:54:55 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 i67DsYH18820 for ; Wed, 7 Jul 2004 16:54:34 +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); Wed, 7 Jul 2004 08:54:33 -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="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Wed, 7 Jul 2004 08:54:32 -0500 Message-ID: <57A26D272F67A743952F6B4371B8F81102496DBC@daebe007.americas.nokia.com> Thread-Topic: Agenda for IETF #60 Thread-Index: AcRkKe6axgGBvqtJR4SOxf6qV4I/5A== To: X-OriginalArrivalTime: 07 Jul 2004 13:54:33.0538 (UTC) FILETIME=[EEC28A20:01C46429] X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL, NO_REAL_NAME autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Subject: [Rserpool] Agenda for IETF #60 X-BeenThere: rserpool@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Reliable Server Pooling List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: rserpool-bounces@ietf.org Errors-To: rserpool-bounces@ietf.org Content-Transfer-Encoding: quoted-printable Please send any agenda items. We are scheduled for Thursday afternoon = in San Diego. Thanks. -- maureen _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From rserpool-bounces@ietf.org Wed Jul 7 16:30:00 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 QAA15440 for ; Wed, 7 Jul 2004 16:30:00 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BiITW-0000pN-FF; Wed, 07 Jul 2004 15:53:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BiI7A-0001fm-Th for rserpool@megatron.ietf.org; Wed, 07 Jul 2004 15:29:56 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11995 for ; Wed, 7 Jul 2004 15:29:49 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BiI74-00054L-MD for rserpool@ietf.org; Wed, 07 Jul 2004 15:29:50 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BiI5e-0004TY-00 for rserpool@ietf.org; Wed, 07 Jul 2004 15:28:23 -0400 Received: from motgate6.mot.com ([144.189.100.106]) by ietf-mx with esmtp (Exim 4.12) id 1BiI4i-00044j-00 for rserpool@ietf.org; Wed, 07 Jul 2004 15:27:24 -0400 Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231]) by motgate6.mot.com (Motorola/Motgate6) with ESMTP id i67JRNDq008576; Wed, 7 Jul 2004 12:27:23 -0700 (MST) Received: from motorola.com (d1421-0a1071e2.cig.mot.com [10.16.113.226]) by az33exr01.mot.com (Motorola/az33exr01) with ESMTP id i67JKEsq000609; Wed, 7 Jul 2004 14:20:15 -0500 Message-ID: <40EC4EDB.1000102@motorola.com> Date: Wed, 07 Jul 2004 14:28:27 -0500 From: Qiaobing Xie 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 Subject: Re: [Rserpool] Packet format in ENRP References: <8F2B3A55-CEA7-11D8-AE6C-000D932C78D8@lurchi.franken.de> In-Reply-To: <8F2B3A55-CEA7-11D8-AE6C-000D932C78D8@lurchi.franken.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60 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 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: rserpool-bounces@ietf.org Errors-To: rserpool-bounces@ietf.org Content-Transfer-Encoding: 7bit Michael, Michael Tuexen wrote: > Dear all, > > while writing the ethereal dissector for ENRP I found some > things I would like to change: > > Section 3.1 > > The length field is shown as 'Message Length = 0xC' which > is not correct because there can be some parameters. good catch. > > Section 3.3 > > Could we exchange the R and M bit? This would align the > R bit position with the reject bit in a PEER_LIST_RESONSE > message. I agree. Better alignment is always good :-) > > Section 3.4 > > To have a similar layout of the packets i would suggest to > change it 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 = 0x4 |0|0|0|0|0|0|0|0| Message Length | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Sender Server's ID | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Receiver Server's ID | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Update Action | (reserved) | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > : Pool handle : > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > : Pool Element : > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Makes sense to me. I agree. regards, -Qiaobing > > Best regards > Michael > > PS.: ethereal version 0.10.5 will support both ASAP and ENRP... > > > _______________________________________________ > 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 Jul 7 19:18:15 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 TAA26985 for ; Wed, 7 Jul 2004 19:18:15 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BiKQh-00029d-Hu; Wed, 07 Jul 2004 17:58:15 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BiJFk-0004fO-Im for rserpool@megatron.ietf.org; Wed, 07 Jul 2004 16:42:52 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16272 for ; Wed, 7 Jul 2004 16:42:44 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BiJFe-0005wh-6p for rserpool@ietf.org; Wed, 07 Jul 2004 16:42:46 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BiJEi-0005cf-00 for rserpool@ietf.org; Wed, 07 Jul 2004 16:41:48 -0400 Received: from motgate7.mot.com ([129.188.136.7]) by ietf-mx with esmtp (Exim 4.12) id 1BiJDj-0005Ho-00 for rserpool@ietf.org; Wed, 07 Jul 2004 16:40:47 -0400 Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231]) by motgate7.mot.com (Motorola/Motgate7) with ESMTP id i67KZGLM018185 for ; Wed, 7 Jul 2004 13:35:17 -0700 (MST) Received: from il02exm12.corp.mot.com (il02exm12.corp.mot.com [10.0.111.23]) by az33exr01.mot.com (Motorola/az33exr01) with ESMTP id i67KXcsq028723 for ; Wed, 7 Jul 2004 15:33:38 -0500 Received: by il02exm12 with Internet Mail Service (5.5.2657.72) id ; Wed, 7 Jul 2004 15:40:44 -0500 Message-ID: From: Silverton Aron-C1710C To: Xie Qiaobing-QXIE1 , Michael Tuexen Subject: RE: [Rserpool] Packet format in ENRP Date: Wed, 7 Jul 2004 15:40:43 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Cc: rserpool@ietf.org X-BeenThere: rserpool@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Reliable Server Pooling List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: rserpool-bounces@ietf.org Errors-To: rserpool-bounces@ietf.org Michael, The rest of here at Motorola discussed your comments this morning and we, too, agree on all accounts. Do we need to wait for further agreement, or should we proceed with updating our documentation and implementations? Regards, Aron Qiaobing Xie <> wrote: > Michael, > > Michael Tuexen wrote: > >> Dear all, >> >> while writing the ethereal dissector for ENRP I found some things I >> would like to change: >> >> Section 3.1 >> >> The length field is shown as 'Message Length = 0xC' which >> is not correct because there can be some parameters. > > good catch. > >> >> Section 3.3 >> >> Could we exchange the R and M bit? This would align the >> R bit position with the reject bit in a PEER_LIST_RESONSE message. > > I agree. Better alignment is always good :-) > >> >> Section 3.4 >> >> To have a similar layout of the packets i would suggest to change it >> 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 = 0x4 |0|0|0|0|0|0|0|0| Message Length | >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | >> Sender Server's ID | >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | >> Receiver Server's ID | >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | >> Update Action | (reserved) | >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ : >> Pool handle : >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ : >> Pool Element : >> >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > > Makes sense to me. I agree. > > regards, > -Qiaobing > >> >> Best regards >> Michael >> >> PS.: ethereal version 0.10.5 will support both ASAP and ENRP... >> >> >> _______________________________________________ >> 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 Wed Jul 7 21:32: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 VAA03260 for ; Wed, 7 Jul 2004 21:32: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 1BiLk3-0003Gx-8B; Wed, 07 Jul 2004 19:22:19 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BiKfu-0001VC-4S for rserpool@megatron.ietf.org; Wed, 07 Jul 2004 18:13:58 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21524 for ; Wed, 7 Jul 2004 18:13:49 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BiKfn-0004fV-LJ for rserpool@ietf.org; Wed, 07 Jul 2004 18:13:51 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BiKew-0004Mn-00 for rserpool@ietf.org; Wed, 07 Jul 2004 18:12:59 -0400 Received: from motgate2.mot.com ([144.189.100.101]) by ietf-mx with esmtp (Exim 4.12) id 1BiKeS-00043a-00 for rserpool@ietf.org; Wed, 07 Jul 2004 18:12:28 -0400 Received: from az33exr04.mot.com (pobox4.mot.com [10.64.251.243]) by motgate2.mot.com (Motorola/Motgate2) with ESMTP id i67M8GWK008050 for ; Wed, 7 Jul 2004 15:08:17 -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 i67KCOjo017828 for ; Wed, 7 Jul 2004 15:12:25 -0500 Received: by il02exm11 with Internet Mail Service (5.5.2657.72) id ; Wed, 7 Jul 2004 17:12:26 -0500 Message-ID: <6F8DFFA2C996D711945800065BFC9E4A0CABD53D@il02exm11> From: Johnson Walter-CWJ002 To: Xie Qiaobing-QXIE1 , "'Michael Tuexen'" Subject: RE: [Rserpool] Packet format in ENRP Date: Wed, 7 Jul 2004 17:12:26 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=LINES_OF_YELLING autolearn=no version=2.60 Cc: "'rserpool@ietf.org'" X-BeenThere: rserpool@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Reliable Server Pooling List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: rserpool-bounces@ietf.org Errors-To: rserpool-bounces@ietf.org I agree with all the changes but would like to suggest another. Much like Michael's suggestion in section 3.3 to align the R bit in PEER_NAME_TABLE_RESPONSE with PEER_PRESENCE and PEER_LIST_RESPONSE. How about the following for the 8 bit flag field. Define bit 15 to be the R flag bit, bit 14 to be the M flag bit, and bit 13 to be W flag bit as shown below the pertinent ENRP protocol messages. This would allow a single mask at least until the time that more than 8 flags were required. PEER_PRESENCE 0000000R PEER_NAME_TABLE 00000W00 PEER_NAME_TABLE_RESPONSE 000000MR (Change as suggested by Michael) PEER_LIST_RESPONSE 0000000R This would also work for the ASAP protocol messages as currently defined. REGISTRATION_RESPONSE 0000000R Walter Qiaobing Xie <> wrote: > Michael, > > Michael Tuexen wrote: > >> Dear all, >> >> while writing the ethereal dissector for ENRP I found some things I >> would like to change: >> >> Section 3.1 >> >> The length field is shown as 'Message Length = 0xC' which >> is not correct because there can be some parameters. > > good catch. > >> >> Section 3.3 >> >> Could we exchange the R and M bit? This would align the >> R bit position with the reject bit in a PEER_LIST_RESONSE message. > > I agree. Better alignment is always good :-) > >> >> Section 3.4 >> >> To have a similar layout of the packets i would suggest to change it >> 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 = 0x4 |0|0|0|0|0|0|0|0| Message Length | >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | >> Sender Server's ID | >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | >> Receiver Server's ID | >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | >> Update Action | (reserved) | >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ : >> Pool handle : >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ : >> Pool Element : >> >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > > Makes sense to me. I agree. > > regards, > -Qiaobing > >> >> Best regards >> Michael >> >> PS.: ethereal version 0.10.5 will support both ASAP and ENRP... >> >> >> _______________________________________________ >> 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 Jul 8 08:43:25 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 IAA17638 for ; Thu, 8 Jul 2004 08:43:25 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BiXVi-0000U4-VH; Thu, 08 Jul 2004 07:56:18 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BiX5b-0000Dx-Nv for rserpool@megatron.ietf.org; Thu, 08 Jul 2004 07:29:20 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14507 for ; Thu, 8 Jul 2004 07:29:18 -0400 (EDT) From: dreibh@exp-math.uni-essen.de Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BiX5b-0002xY-6H for rserpool@ietf.org; Thu, 08 Jul 2004 07:29:19 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BiX4c-0002e9-00 for rserpool@ietf.org; Thu, 08 Jul 2004 07:28:19 -0400 Received: from ns.exp-math.uni-essen.de ([132.252.150.1] helo=pilz.exp-math.uni-essen.de) by ietf-mx with esmtp (Exim 4.12) id 1BiX3c-0002Do-00 for rserpool@ietf.org; Thu, 08 Jul 2004 07:27:16 -0400 Received: from tdrwww.exp-math.uni-essen.de (tdrwww.exp-math.uni-essen.de [132.252.150.129]) by pilz.exp-math.uni-essen.de (8.12.10/8.12.8) with ESMTP id i68BRDFc099094; Thu, 8 Jul 2004 13:27:13 +0200 Received: by tdrwww.exp-math.uni-essen.de (Postfix, from userid 78) id D91BB588D8; Thu, 8 Jul 2004 09:21:36 -0400 (EDT) Received: from host217-41-100-225.in-addr.btopenworld.com (host217-41-100-225.in-addr.btopenworld.com [217.41.100.225]) by tdrwww.exp-math.uni-essen.de (IMP) with HTTP for ; Thu, 8 Jul 2004 15:21:36 +0200 Message-ID: <1089292896.40ed4a60aae0d@tdrwww.exp-math.uni-essen.de> Date: Thu, 8 Jul 2004 15:21:36 +0200 To: Johnson Walter-CWJ002 Subject: RE: [Rserpool] Packet format in ENRP References: <6F8DFFA2C996D711945800065BFC9E4A0CABD53D@il02exm11> In-Reply-To: <6F8DFFA2C996D711945800065BFC9E4A0CABD53D@il02exm11> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.4 X-Originating-IP: 217.41.100.225 X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.3 required=5.0 tests=NO_REAL_NAME autolearn=no version=2.60 Content-Transfer-Encoding: 8bit Cc: "'Michael Tuexen'" , "'rserpool@ietf.org'" , Xie Qiaobing-QXIE1 X-BeenThere: rserpool@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Reliable Server Pooling List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: rserpool-bounces@ietf.org Errors-To: rserpool-bounces@ietf.org Content-Transfer-Encoding: 8bit Zitat von Johnson Walter-CWJ002 : > I agree with all the changes but would like to suggest another. Much like > Michael's suggestion in section 3.3 to align the R bit in > PEER_NAME_TABLE_RESPONSE with PEER_PRESENCE and PEER_LIST_RESPONSE. How about > the following for the 8 bit flag field. Define bit 15 to be the R flag bit, > bit 14 to be the M flag bit, and bit 13 to be W flag bit as shown below the > pertinent ENRP protocol messages. This would allow a single mask at least > until the time that more than 8 flags were required. > > PEER_PRESENCE 0000000R > PEER_NAME_TABLE 00000W00 > PEER_NAME_TABLE_RESPONSE 000000MR (Change as suggested by Michael) > PEER_LIST_RESPONSE 0000000R > > This would also work for the ASAP protocol messages as currently defined. > > REGISTRATION_RESPONSE 0000000R This change is a good idea. I support this. Best regards Thomas Dreibholz ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From rserpool-bounces@ietf.org Thu Jul 8 11:00:14 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 LAA28526 for ; Thu, 8 Jul 2004 11:00:14 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BiZim-0005aI-KN; Thu, 08 Jul 2004 10:17:56 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BiZ6d-0005Hk-3k for rserpool@megatron.ietf.org; Thu, 08 Jul 2004 09:38:31 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21135 for ; Thu, 8 Jul 2004 09:38:24 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BiZ6X-00045f-F0 for rserpool@ietf.org; Thu, 08 Jul 2004 09:38:25 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BiZ5Z-0003m7-00 for rserpool@ietf.org; Thu, 08 Jul 2004 09:37:26 -0400 Received: from mail-n.franken.de ([193.175.24.27] helo=ilsa.franken.de ident=postfix) by ietf-mx with esmtp (Exim 4.12) id 1BiZ4U-0003Bz-00 for rserpool@ietf.org; Thu, 08 Jul 2004 09:36:18 -0400 Received: from [194.95.73.179] (unknown [194.95.73.179]) by ilsa.franken.de (Postfix) with ESMTP id 7187D245C4; Thu, 8 Jul 2004 15:33:39 +0200 (CEST) (KNF account authenticated via SMTP-AUTH) In-Reply-To: <6F8DFFA2C996D711945800065BFC9E4A0CABD53D@il02exm11> References: <6F8DFFA2C996D711945800065BFC9E4A0CABD53D@il02exm11> Mime-Version: 1.0 (Apple Message framework v618) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Michael Tuexen Subject: Re: [Rserpool] Packet format in ENRP Date: Thu, 8 Jul 2004 15:36:09 +0200 To: Johnson Walter-CWJ002 X-Mailer: Apple Mail (2.618) X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Cc: "'rserpool@ietf.org'" , Xie Qiaobing-QXIE1 X-BeenThere: rserpool@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Reliable Server Pooling List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: rserpool-bounces@ietf.org Errors-To: rserpool-bounces@ietf.org Content-Transfer-Encoding: 7bit Dear all, just one note: the R flag in the PEER_PRESENCE message means 'reply required' and in the PEER_NAME_TABLE_RESPONSE and PEER_LIST_RESPONSE it means 'reject'. So it is not just 'one bit'. On Jul 8, 2004, at 12:12 AM, Johnson Walter-CWJ002 wrote: > I agree with all the changes but would like to suggest another. Much > like Michael's suggestion in section 3.3 to align the R bit in > PEER_NAME_TABLE_RESPONSE with PEER_PRESENCE and PEER_LIST_RESPONSE. > How about the following for the 8 bit flag field. Define bit 15 to be > the R flag bit, bit 14 to be the M flag bit, and bit 13 to be W flag > bit as shown below the pertinent ENRP protocol messages. This would > allow a single mask at least until the time that more than 8 flags > were required. > > PEER_PRESENCE 0000000R > PEER_NAME_TABLE 00000W00 > PEER_NAME_TABLE_RESPONSE 000000MR (Change as suggested by Michael) > PEER_LIST_RESPONSE 0000000R > > This would also work for the ASAP protocol messages as currently > defined. > > REGISTRATION_RESPONSE 0000000R > > Walter > > Qiaobing Xie <> wrote: >> Michael, >> >> Michael Tuexen wrote: >> >>> Dear all, >>> >>> while writing the ethereal dissector for ENRP I found some things I >>> would like to change: >>> >>> Section 3.1 >>> >>> The length field is shown as 'Message Length = 0xC' which >>> is not correct because there can be some parameters. >> >> good catch. >> >>> >>> Section 3.3 >>> >>> Could we exchange the R and M bit? This would align the >>> R bit position with the reject bit in a PEER_LIST_RESONSE message. >> >> I agree. Better alignment is always good :-) >> >>> >>> Section 3.4 >>> >>> To have a similar layout of the packets i would suggest to change it >>> 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 = 0x4 |0|0|0|0|0|0|0|0| Message Length | >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | >>> Sender Server's ID | >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | >>> Receiver Server's ID | >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | >>> Update Action | (reserved) | >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ : >>> Pool handle : >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ : >>> Pool Element : >>> >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >> >> Makes sense to me. I agree. >> >> regards, >> -Qiaobing >> >>> >>> Best regards >>> Michael >>> >>> PS.: ethereal version 0.10.5 will support both ASAP and ENRP... >>> >>> >>> _______________________________________________ >>> 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 Jul 8 11:02: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 LAA28705 for ; Thu, 8 Jul 2004 11:02: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 1BiZxj-0002sp-3u; Thu, 08 Jul 2004 10:33:23 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BiZ8Z-0006Hx-78 for rserpool@megatron.ietf.org; Thu, 08 Jul 2004 09:40:31 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21173 for ; Thu, 8 Jul 2004 09:40:24 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BiZ8T-0004kK-FH for rserpool@ietf.org; Thu, 08 Jul 2004 09:40:25 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BiZ7U-0004Py-00 for rserpool@ietf.org; Thu, 08 Jul 2004 09:39:24 -0400 Received: from mail-n.franken.de ([193.175.24.27] helo=ilsa.franken.de ident=postfix) by ietf-mx with esmtp (Exim 4.12) id 1BiZ6P-0003oy-00 for rserpool@ietf.org; Thu, 08 Jul 2004 09:38:17 -0400 Received: from [194.95.73.179] (unknown [194.95.73.179]) by ilsa.franken.de (Postfix) with ESMTP id 158C7245C5; Thu, 8 Jul 2004 15:35:38 +0200 (CEST) (KNF account authenticated via SMTP-AUTH) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v618) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <0C614FC8-D0E4-11D8-838F-000D932C78D8@lurchi.franken.de> Content-Transfer-Encoding: 7bit From: Michael Tuexen Subject: Re: [Rserpool] Packet format in ENRP Date: Thu, 8 Jul 2004 15:38:08 +0200 To: Silverton Aron-C1710C X-Mailer: Apple Mail (2.618) X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Cc: rserpool@ietf.org, Xie Qiaobing-QXIE1 X-BeenThere: rserpool@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Reliable Server Pooling List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: rserpool-bounces@ietf.org Errors-To: rserpool-bounces@ietf.org Content-Transfer-Encoding: 7bit Aron, possibly we could update the ENRP ID before the IETF deadline. This is still one week away. Qiaobing, if the .xml source is in Randalls CVS, I can do the editing, if you want. I can also update the ethereal dissector and Thomas can update the rsplib. Best regards Michael On Jul 7, 2004, at 10:40 PM, Silverton Aron-C1710C wrote: > Michael, > > The rest of here at Motorola discussed your comments this morning and > we, too, agree on all accounts. Do we need to wait for further > agreement, or should we proceed with updating our documentation and > implementations? > > Regards, > > Aron > > Qiaobing Xie <> wrote: >> Michael, >> >> Michael Tuexen wrote: >> >>> Dear all, >>> >>> while writing the ethereal dissector for ENRP I found some things I >>> would like to change: >>> >>> Section 3.1 >>> >>> The length field is shown as 'Message Length = 0xC' which >>> is not correct because there can be some parameters. >> >> good catch. >> >>> >>> Section 3.3 >>> >>> Could we exchange the R and M bit? This would align the >>> R bit position with the reject bit in a PEER_LIST_RESONSE message. >> >> I agree. Better alignment is always good :-) >> >>> >>> Section 3.4 >>> >>> To have a similar layout of the packets i would suggest to change it >>> 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 = 0x4 |0|0|0|0|0|0|0|0| Message Length | >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | >>> Sender Server's ID | >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | >>> Receiver Server's ID | >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | >>> Update Action | (reserved) | >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ : >>> Pool handle : >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ : >>> Pool Element : >>> >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >> >> Makes sense to me. I agree. >> >> regards, >> -Qiaobing >> >>> >>> Best regards >>> Michael >>> >>> PS.: ethereal version 0.10.5 will support both ASAP and ENRP... >>> >>> >>> _______________________________________________ >>> 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 Jul 8 11:41:43 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 LAA03611 for ; Thu, 8 Jul 2004 11:41: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 1BiaiO-0006iS-R1; Thu, 08 Jul 2004 11:21:36 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BiaAW-0005rF-Og for rserpool@megatron.ietf.org; Thu, 08 Jul 2004 10:46:36 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27684 for ; Thu, 8 Jul 2004 10:46:29 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BiaAQ-0003ZN-U0 for rserpool@ietf.org; Thu, 08 Jul 2004 10:46:30 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Bia9T-0003Ek-00 for rserpool@ietf.org; Thu, 08 Jul 2004 10:45:31 -0400 Received: from motgate8.mot.com ([129.188.136.8]) by ietf-mx with esmtp (Exim 4.12) id 1Bia8Y-0002u7-00 for rserpool@ietf.org; Thu, 08 Jul 2004 10:44:34 -0400 Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133]) by motgate8.mot.com (Motorola/Motgate8) with ESMTP id i68EjHJW005849 for ; Thu, 8 Jul 2004 07:45:17 -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 i68EiX76018986 for ; Thu, 8 Jul 2004 09:44:33 -0500 Received: by il02exm11 with Internet Mail Service (5.5.2657.72) id ; Thu, 8 Jul 2004 09:44:33 -0500 Message-ID: <6F8DFFA2C996D711945800065BFC9E4A0CBA0BAD@il02exm11> From: Johnson Walter-CWJ002 To: "'Michael Tuexen'" Subject: RE: [Rserpool] Packet format in ENRP Date: Thu, 8 Jul 2004 09:44:32 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,LINES_OF_YELLING, LINES_OF_YELLING_2 autolearn=no version=2.60 Cc: "'rserpool@ietf.org'" , Xie Qiaobing-QXIE1 X-BeenThere: rserpool@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Reliable Server Pooling List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: rserpool-bounces@ietf.org Errors-To: rserpool-bounces@ietf.org Michael is right. So how about the move the R flag to bit 12 for PEER_PRESENCE and maybe change R flag to X flag for reject to avoid confusion in PEER_NAME_TABLE_RESPONSE, PEER_LIST_RESPONSE and ASAP's REGISTRATION_RESPONSE with the R flag of PEER_PRESENCE. Resulting in the following: PEER_PRESENCE 0000R000 PEER_NAME_TABLE 00000W00 PEER_NAME_TABLE_RESPONSE 000000MX PEER_LIST_RESPONSE 0000000X REGISTRATION_RESPONSE 0000000X Michael Tuexen wrote: > Dear all, > > just one note: > the R flag in the PEER_PRESENCE message means 'reply required' and in > the PEER_NAME_TABLE_RESPONSE and PEER_LIST_RESPONSE it means > 'reject'. So it is not just 'one bit'. > > > On Jul 8, 2004, at 12:12 AM, Johnson Walter-CWJ002 wrote: > >> I agree with all the changes but would like to suggest another. Much >> like Michael's suggestion in section 3.3 to align the R bit in >> PEER_NAME_TABLE_RESPONSE with PEER_PRESENCE and PEER_LIST_RESPONSE. >> How about the following for the 8 bit flag field. Define bit 15 to be >> the R flag bit, bit 14 to be the M flag bit, and bit 13 to be W flag >> bit as shown below the pertinent ENRP protocol messages. This would >> allow a single mask at least until the time that more than 8 flags >> were required. >> >> PEER_PRESENCE 0000000R >> PEER_NAME_TABLE 00000W00 >> PEER_NAME_TABLE_RESPONSE 000000MR (Change as suggested by Michael) >> PEER_LIST_RESPONSE 0000000R >> >> This would also work for the ASAP protocol messages as currently >> defined. >> >> REGISTRATION_RESPONSE 0000000R >> >> Walter >> >> Qiaobing Xie <> wrote: >>> Michael, >>> >>> Michael Tuexen wrote: >>> >>>> Dear all, >>>> >>>> while writing the ethereal dissector for ENRP I found some things >>>> I would like to change: >>>> >>>> Section 3.1 >>>> >>>> The length field is shown as 'Message Length = 0xC' which is not >>>> correct because there can be some parameters. >>> >>> good catch. >>> >>>> >>>> Section 3.3 >>>> >>>> Could we exchange the R and M bit? This would align the >>>> R bit position with the reject bit in a PEER_LIST_RESONSE message. >>> >>> I agree. Better alignment is always good :-) >>> >>>> >>>> Section 3.4 >>>> >>>> To have a similar layout of the packets i would suggest to change >>>> it 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 = 0x4 |0|0|0|0|0|0|0|0| Message Length | >>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | >>>> Sender Server's ID | >>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | >>>> Receiver Server's ID | >>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | >>>> Update Action | (reserved) | >>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ : >>>> Pool handle : >>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ : >>>> Pool Element : >>>> >>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> >>> Makes sense to me. I agree. >>> >>> regards, >>> -Qiaobing >>> >>>> >>>> Best regards >>>> Michael >>>> >>>> PS.: ethereal version 0.10.5 will support both ASAP and ENRP... >>>> >>>> >>>> _______________________________________________ >>>> 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 Jul 8 11:58:14 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 LAA04871 for ; Thu, 8 Jul 2004 11:58:13 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Biave-0002GL-RX; Thu, 08 Jul 2004 11:35:18 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BiaWN-0003ZP-Ew for rserpool@megatron.ietf.org; Thu, 08 Jul 2004 11:09:11 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29171 for ; Thu, 8 Jul 2004 11:09:04 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BiaWH-0003TH-MC for rserpool@ietf.org; Thu, 08 Jul 2004 11:09:05 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BiaV5-00034P-00 for rserpool@ietf.org; Thu, 08 Jul 2004 11:07:52 -0400 Received: from motgate7.mot.com ([129.188.136.7]) by ietf-mx with esmtp (Exim 4.12) id 1BiaUP-0002iv-00 for rserpool@ietf.org; Thu, 08 Jul 2004 11:07:09 -0400 Received: from il06exr06.mot.com (il06exr06.mot.com [129.188.137.136]) by motgate7.mot.com (Motorola/Motgate7) with ESMTP id i68F1cPA000532 for ; Thu, 8 Jul 2004 08:01:38 -0700 (MST) Received: from il02exm12.corp.mot.com (il02exm12.corp.mot.com [10.0.111.23]) by il06exr06.mot.com (Motorola/il06exr06) with ESMTP id i68F77dv007453 for ; Thu, 8 Jul 2004 10:07:08 -0500 Received: by il02exm12 with Internet Mail Service (5.5.2657.72) id ; Thu, 8 Jul 2004 10:07:08 -0500 Message-ID: From: Silverton Aron-C1710C To: "'Michael Tuexen'" Subject: RE: [Rserpool] Packet format in ENRP Date: Thu, 8 Jul 2004 10:07:07 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Cc: "'rserpool@ietf.org'" , Xie Qiaobing-QXIE1 X-BeenThere: rserpool@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Reliable Server Pooling List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: rserpool-bounces@ietf.org Errors-To: rserpool-bounces@ietf.org No big deal if we make the deadline, I just wanted to see if this discussion qualified as consensus so that I could have our internal documents and implementation updated. I don't mind if the IETF drafts lag behind. This just happens to be a convenient time for us to change our stuff. Aron Michael Tuexen <> wrote: > Aron, > > possibly we could update the ENRP ID before the IETF deadline. This > is still one week away. Qiaobing, if the .xml source is in Randalls > CVS, I can do the editing, if you want. > > I can also update the ethereal dissector and Thomas can update the > rsplib. > > Best regards > Michael > > On Jul 7, 2004, at 10:40 PM, Silverton Aron-C1710C wrote: > >> Michael, >> >> The rest of here at Motorola discussed your comments this morning and >> we, too, agree on all accounts. Do we need to wait for further >> agreement, or should we proceed with updating our documentation and >> implementations? >> >> Regards, >> >> Aron >> >> Qiaobing Xie <> wrote: >>> Michael, >>> >>> Michael Tuexen wrote: >>> >>>> Dear all, >>>> >>>> while writing the ethereal dissector for ENRP I found some things >>>> I would like to change: >>>> >>>> Section 3.1 >>>> >>>> The length field is shown as 'Message Length = 0xC' which is not >>>> correct because there can be some parameters. >>> >>> good catch. >>> >>>> >>>> Section 3.3 >>>> >>>> Could we exchange the R and M bit? This would align the >>>> R bit position with the reject bit in a PEER_LIST_RESONSE message. >>> >>> I agree. Better alignment is always good :-) >>> >>>> >>>> Section 3.4 >>>> >>>> To have a similar layout of the packets i would suggest to change >>>> it 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 = 0x4 |0|0|0|0|0|0|0|0| Message Length | >>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | >>>> Sender Server's ID | >>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | >>>> Receiver Server's ID | >>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | >>>> Update Action | (reserved) | >>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ : >>>> Pool handle : >>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ : >>>> Pool Element : >>>> >>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> >>> Makes sense to me. I agree. >>> >>> regards, >>> -Qiaobing >>> >>>> >>>> Best regards >>>> Michael >>>> >>>> PS.: ethereal version 0.10.5 will support both ASAP and ENRP... >>>> >>>> >>>> _______________________________________________ >>>> 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 Thu Jul 8 15:40:37 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 PAA23146 for ; Thu, 8 Jul 2004 15:40:37 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BiaxA-0003Fl-QT; Thu, 08 Jul 2004 11:36:52 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Biafe-0005TV-4t for rserpool@megatron.ietf.org; Thu, 08 Jul 2004 11:18:46 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00901 for ; Thu, 8 Jul 2004 11:18:38 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BiafY-0006lu-Bp for rserpool@ietf.org; Thu, 08 Jul 2004 11:18:40 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Biado-0006JJ-00 for rserpool@ietf.org; Thu, 08 Jul 2004 11:16:53 -0400 Received: from motgate7.mot.com ([129.188.136.7]) by ietf-mx with esmtp (Exim 4.12) id 1BiabR-0005Qp-00 for rserpool@ietf.org; Thu, 08 Jul 2004 11:14:25 -0400 Received: from az33exr04.mot.com (pobox4.mot.com [10.64.251.243]) by motgate7.mot.com (Motorola/Motgate7) with ESMTP id i68F8sPA003184 for ; Thu, 8 Jul 2004 08:08:54 -0700 (MST) Received: from il02exm12.corp.mot.com (il02exm12.corp.mot.com [10.0.111.23]) by az33exr04.mot.com (Motorola/az33exr04) with ESMTP id i68DELjo019572 for ; Thu, 8 Jul 2004 08:14:22 -0500 Received: by il02exm12 with Internet Mail Service (5.5.2657.72) id ; Thu, 8 Jul 2004 10:14:23 -0500 Message-ID: From: Silverton Aron-C1710C To: "'Michael Tuexen'" , Johnson Walter-CWJ002 Subject: RE: [Rserpool] Packet format in ENRP Date: Thu, 8 Jul 2004 10:14:22 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Cc: "'rserpool@ietf.org'" , Xie Qiaobing-QXIE1 X-BeenThere: rserpool@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Reliable Server Pooling List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: rserpool-bounces@ietf.org Errors-To: rserpool-bounces@ietf.org I think that the concept of a mask should apply to what bit you are trying to read. In one case, it's the 'reply required' bit and in the other it is the 'reject' bit, so these are really two different things. A single mask should definitely apply to the PEER_NAME_TABLE and PEER_NAME_TABLE_RESPONSE since it is the same flag. Now I am not so sure about the PEER_PRESENCE message since it is really something different. My question is, does it makes sense to abandon bits in one message because they are used in another? Or put another way, are the flags meant to be global across all ENRP messages, or contextual based on the specific message? Aron Michael Tuexen <> wrote: > Dear all, > > just one note: > the R flag in the PEER_PRESENCE message means 'reply required' and in > the PEER_NAME_TABLE_RESPONSE and PEER_LIST_RESPONSE it means > 'reject'. So it is not just 'one bit'. > > > On Jul 8, 2004, at 12:12 AM, Johnson Walter-CWJ002 wrote: > >> I agree with all the changes but would like to suggest another. Much >> like Michael's suggestion in section 3.3 to align the R bit in >> PEER_NAME_TABLE_RESPONSE with PEER_PRESENCE and PEER_LIST_RESPONSE. >> How about the following for the 8 bit flag field. Define bit 15 to be >> the R flag bit, bit 14 to be the M flag bit, and bit 13 to be W flag >> bit as shown below the pertinent ENRP protocol messages. This would >> allow a single mask at least until the time that more than 8 flags >> were required. >> >> PEER_PRESENCE 0000000R >> PEER_NAME_TABLE 00000W00 >> PEER_NAME_TABLE_RESPONSE 000000MR (Change as suggested by Michael) >> PEER_LIST_RESPONSE 0000000R >> >> This would also work for the ASAP protocol messages as currently >> defined. >> >> REGISTRATION_RESPONSE 0000000R >> >> Walter >> >> Qiaobing Xie <> wrote: >>> Michael, >>> >>> Michael Tuexen wrote: >>> >>>> Dear all, >>>> >>>> while writing the ethereal dissector for ENRP I found some things >>>> I would like to change: >>>> >>>> Section 3.1 >>>> >>>> The length field is shown as 'Message Length = 0xC' which is not >>>> correct because there can be some parameters. >>> >>> good catch. >>> >>>> >>>> Section 3.3 >>>> >>>> Could we exchange the R and M bit? This would align the >>>> R bit position with the reject bit in a PEER_LIST_RESONSE message. >>> >>> I agree. Better alignment is always good :-) >>> >>>> >>>> Section 3.4 >>>> >>>> To have a similar layout of the packets i would suggest to change >>>> it 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 = 0x4 |0|0|0|0|0|0|0|0| Message Length | >>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | >>>> Sender Server's ID | >>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | >>>> Receiver Server's ID | >>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | >>>> Update Action | (reserved) | >>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ : >>>> Pool handle : >>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ : >>>> Pool Element : >>>> >>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> >>> Makes sense to me. I agree. >>> >>> regards, >>> -Qiaobing >>> >>>> >>>> Best regards >>>> Michael >>>> >>>> PS.: ethereal version 0.10.5 will support both ASAP and ENRP... >>>> >>>> >>>> _______________________________________________ >>>> 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 Thu Jul 8 18:50: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 SAA10919 for ; Thu, 8 Jul 2004 18:50: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 1BiftX-0003RP-I9; Thu, 08 Jul 2004 16:53:27 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BidWV-0000fr-Jc for rserpool@megatron.ietf.org; Thu, 08 Jul 2004 14:21:31 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15256 for ; Thu, 8 Jul 2004 14:21:24 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BidWP-00074P-BZ for rserpool@ietf.org; Thu, 08 Jul 2004 14:21:25 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BidUy-0006Z6-00 for rserpool@ietf.org; Thu, 08 Jul 2004 14:19:56 -0400 Received: from mail-n.franken.de ([193.175.24.27] helo=ilsa.franken.de ident=postfix) by ietf-mx with esmtp (Exim 4.12) id 1BidTc-0005qH-00 for rserpool@ietf.org; Thu, 08 Jul 2004 14:18:32 -0400 Received: from [192.168.1.218] (p5089DD83.dip.t-dialin.net [80.137.221.131]) by ilsa.franken.de (Postfix) with ESMTP id 03A30245CA; Thu, 8 Jul 2004 20:15:52 +0200 (CEST) (KNF account authenticated via SMTP-AUTH) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v618) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <31D81F6C-D10B-11D8-8684-000D932C78D8@lurchi.franken.de> Content-Transfer-Encoding: 7bit From: Michael Tuexen Subject: Re: [Rserpool] Packet format in ENRP Date: Thu, 8 Jul 2004 20:18:21 +0200 To: Silverton Aron-C1710C X-Mailer: Apple Mail (2.618) X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Cc: "'rserpool@ietf.org'" , Xie Qiaobing-QXIE1 X-BeenThere: rserpool@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Reliable Server Pooling List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: rserpool-bounces@ietf.org Errors-To: rserpool-bounces@ietf.org Content-Transfer-Encoding: 7bit Dear all, I think aligning the bits through all ENRP (or ASAP) message is not the right way. It restricts us to 8 bits per protocol, not 8 bits per message and is not that simple to do. So I think it is not worth the effort we have to do. Nevertheless I suggest to use the rightmost bit in the PEER_NAME_TABLE_RESPONSE and PEER_LIST_RESPONSE message as the 'reject bit'. This cost nothing. Regarding putting these changes in an ID: I think it is easy to do and we have a document where you can look up the current state of the discussion. If not some people may just forget it while working on the next revision. From the experience with earlier IETF work done, it was quite helpful to get the ethereal dissectors (in the CVS) up to the current ID status. So I committed the changes as soon as the IDd where published. But it is just the way I handled that... As said, I'm volunteering to do the simple editorial work... Best regards Michael On Jul 8, 2004, at 5:14 PM, Silverton Aron-C1710C wrote: > I think that the concept of a mask should apply to what bit you are > trying to read. In one case, it's the 'reply required' bit and in the > other it is the 'reject' bit, so these are really two different > things. A single mask should definitely apply to the PEER_NAME_TABLE > and PEER_NAME_TABLE_RESPONSE since it is the same flag. Now I am not > so sure about the PEER_PRESENCE message since it is really something > different. > > My question is, does it makes sense to abandon bits in one message > because they are used in another? Or put another way, are the flags > meant to be global across all ENRP messages, or contextual based on > the specific message? > > Aron > > Michael Tuexen <> wrote: >> Dear all, >> >> just one note: >> the R flag in the PEER_PRESENCE message means 'reply required' and in >> the PEER_NAME_TABLE_RESPONSE and PEER_LIST_RESPONSE it means >> 'reject'. So it is not just 'one bit'. >> >> >> On Jul 8, 2004, at 12:12 AM, Johnson Walter-CWJ002 wrote: >> >>> I agree with all the changes but would like to suggest another. Much >>> like Michael's suggestion in section 3.3 to align the R bit in >>> PEER_NAME_TABLE_RESPONSE with PEER_PRESENCE and PEER_LIST_RESPONSE. >>> How about the following for the 8 bit flag field. Define bit 15 to be >>> the R flag bit, bit 14 to be the M flag bit, and bit 13 to be W flag >>> bit as shown below the pertinent ENRP protocol messages. This would >>> allow a single mask at least until the time that more than 8 flags >>> were required. >>> >>> PEER_PRESENCE 0000000R >>> PEER_NAME_TABLE 00000W00 >>> PEER_NAME_TABLE_RESPONSE 000000MR (Change as suggested by Michael) >>> PEER_LIST_RESPONSE 0000000R >>> >>> This would also work for the ASAP protocol messages as currently >>> defined. >>> >>> REGISTRATION_RESPONSE 0000000R >>> >>> Walter >>> >>> Qiaobing Xie <> wrote: >>>> Michael, >>>> >>>> Michael Tuexen wrote: >>>> >>>>> Dear all, >>>>> >>>>> while writing the ethereal dissector for ENRP I found some things >>>>> I would like to change: >>>>> >>>>> Section 3.1 >>>>> >>>>> The length field is shown as 'Message Length = 0xC' which is not >>>>> correct because there can be some parameters. >>>> >>>> good catch. >>>> >>>>> >>>>> Section 3.3 >>>>> >>>>> Could we exchange the R and M bit? This would align the >>>>> R bit position with the reject bit in a PEER_LIST_RESONSE message. >>>> >>>> I agree. Better alignment is always good :-) >>>> >>>>> >>>>> Section 3.4 >>>>> >>>>> To have a similar layout of the packets i would suggest to change >>>>> it 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 = 0x4 |0|0|0|0|0|0|0|0| Message Length | >>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | >>>>> Sender Server's ID | >>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | >>>>> Receiver Server's ID | >>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | >>>>> Update Action | (reserved) | >>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ : >>>>> Pool handle : >>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ : >>>>> Pool Element : >>>>> >>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>>> >>>> Makes sense to me. I agree. >>>> >>>> regards, >>>> -Qiaobing >>>> >>>>> >>>>> Best regards >>>>> Michael >>>>> >>>>> PS.: ethereal version 0.10.5 will support both ASAP and ENRP... >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 Thu Jul 8 19:35:00 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 TAA13929 for ; Thu, 8 Jul 2004 19:35:00 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BigKk-0002IW-09; Thu, 08 Jul 2004 17:21:34 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BifVr-0005hx-MB for rserpool@megatron.ietf.org; Thu, 08 Jul 2004 16:28:59 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26406 for ; Thu, 8 Jul 2004 16:28:56 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BifVp-0001v2-D5 for rserpool@ietf.org; Thu, 08 Jul 2004 16:28:57 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BifUx-0001YA-00 for rserpool@ietf.org; Thu, 08 Jul 2004 16:28:04 -0400 Received: from motgate7.mot.com ([129.188.136.7]) by ietf-mx with esmtp (Exim 4.12) id 1BifUK-0001B5-00 for rserpool@ietf.org; Thu, 08 Jul 2004 16:27:24 -0400 Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231]) by motgate7.mot.com (Motorola/Motgate7) with ESMTP id i68KLqPA002939; Thu, 8 Jul 2004 13:21:53 -0700 (MST) Received: from motorola.com (d1421-0a1071e2.cig.mot.com [10.16.113.226]) by az33exr01.mot.com (Motorola/az33exr01) with ESMTP id i68KKEsq006723; Thu, 8 Jul 2004 15:20:14 -0500 Message-ID: <40EDAE6C.9090000@motorola.com> Date: Thu, 08 Jul 2004 15:28:28 -0500 From: Qiaobing Xie 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 Subject: Re: [Rserpool] Packet format in ENRP References: <0C614FC8-D0E4-11D8-838F-000D932C78D8@lurchi.franken.de> In-Reply-To: <0C614FC8-D0E4-11D8-838F-000D932C78D8@lurchi.franken.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Cc: rserpool@ietf.org, Silverton Aron-C1710C X-BeenThere: rserpool@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Reliable Server Pooling List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: rserpool-bounces@ietf.org Errors-To: rserpool-bounces@ietf.org Content-Transfer-Encoding: 7bit Michael, I did send Randy the latest xml after my last update on ENRP. To be safe, you still probably want to double check that the version on the top of CVS matches the current I-D before doing editing. As to the several follow-up suggestions on further re-aligning the flag bits, I am a little hesitant to support it (but I won't violently oppose it either). We do not want to overdo it, since after all there is only 8 bits available and if one insists on using "one-bit-one-meaning" arrangement, we will not be able to go very far before we have to abandon the approach. In coding, the differece is no more than: if(flag_field & 00001000) { ... } vs. if(flag_field == 0x08) { ... } regards, -Qiaobing Michael Tuexen wrote: > Aron, > > possibly we could update the ENRP ID before the IETF deadline. This > is still one week away. Qiaobing, if the .xml source is in Randalls > CVS, I can do the editing, if you want. > > I can also update the ethereal dissector and Thomas can update > the rsplib. > > Best regards > Michael > > On Jul 7, 2004, at 10:40 PM, Silverton Aron-C1710C wrote: > >> Michael, >> >> The rest of here at Motorola discussed your comments this morning and >> we, too, agree on all accounts. Do we need to wait for further >> agreement, or should we proceed with updating our documentation and >> implementations? >> >> Regards, >> >> Aron >> >> Qiaobing Xie <> wrote: >> >>> Michael, >>> >>> Michael Tuexen wrote: >>> >>>> Dear all, >>>> >>>> while writing the ethereal dissector for ENRP I found some things I >>>> would like to change: >>>> >>>> Section 3.1 >>>> >>>> The length field is shown as 'Message Length = 0xC' which >>>> is not correct because there can be some parameters. >>> >>> >>> good catch. >>> >>>> >>>> Section 3.3 >>>> >>>> Could we exchange the R and M bit? This would align the >>>> R bit position with the reject bit in a PEER_LIST_RESONSE message. >>> >>> >>> I agree. Better alignment is always good :-) >>> >>>> >>>> Section 3.4 >>>> >>>> To have a similar layout of the packets i would suggest to change it >>>> 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 = 0x4 |0|0|0|0|0|0|0|0| Message Length | >>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | >>>> Sender Server's ID | >>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | >>>> Receiver Server's ID | >>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | >>>> Update Action | (reserved) | >>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ : >>>> Pool handle : >>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ : >>>> Pool Element : >>>> >>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> >>> >>> Makes sense to me. I agree. >>> >>> regards, >>> -Qiaobing >>> >>>> >>>> Best regards >>>> Michael >>>> >>>> PS.: ethereal version 0.10.5 will support both ASAP and ENRP... >>>> >>>> >>>> _______________________________________________ >>>> 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 Jul 9 01:00: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 BAA18253 for ; Fri, 9 Jul 2004 01:00: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 1Bin8J-0001Hs-3r; Fri, 09 Jul 2004 00:37:11 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bimq2-0005xN-OO for rserpool@megatron.ietf.org; Fri, 09 Jul 2004 00:18:18 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA16093 for ; Fri, 9 Jul 2004 00:18:10 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1Bimpv-0005OH-SA for rserpool@ietf.org; Fri, 09 Jul 2004 00:18:11 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Bimp1-00053J-00 for rserpool@ietf.org; Fri, 09 Jul 2004 00:17:16 -0400 Received: from sccrmhc13.comcast.net ([204.127.202.64]) by ietf-mx with esmtp (Exim 4.12) id 1Bimo0-0004Ku-00 for rserpool@ietf.org; Fri, 09 Jul 2004 00:16:12 -0400 Received: from [10.10.0.75] (c-24-13-174-21.client.comcast.net[24.13.174.21]) by comcast.net (sccrmhc13) with ESMTP id <2004070904154201600gbtgae> (Authid: peterlei); Fri, 9 Jul 2004 04:15:42 +0000 Message-ID: <40EE1BE7.5090809@ieee.org> Date: Thu, 08 Jul 2004 23:15:35 -0500 From: Peter Lei User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040616 X-Accept-Language: en-us, en MIME-Version: 1.0 To: rserpool@ietf.org Subject: Re: [Rserpool] Packet format in ENRP References: <0C614FC8-D0E4-11D8-838F-000D932C78D8@lurchi.franken.de> <40EDAE6C.9090000@motorola.com> In-Reply-To: <40EDAE6C.9090000@motorola.com> X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Cc: Michael Tuexen , Silverton Aron-C1710C , Qiaobing Xie X-BeenThere: rserpool@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Reliable Server Pooling List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2144670030==" Sender: rserpool-bounces@ietf.org Errors-To: rserpool-bounces@ietf.org This is a cryptographically signed message in MIME format. --===============2144670030== Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms070505070002060203050107" This is a cryptographically signed message in MIME format. --------------ms070505070002060203050107 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit I also agree w/Q and Michael on this... Trying to align the 8 bits across all exisiting and possible future messages may impose a severe limitation later. I'd prefer that the flags be contextual based on the specific messages, than global across the protocol. Aligning them where possible does make sense though, such as the "R"-bit in PEER_NAME_TABLE_RESPONSE and PEER_LIST_RESPONSE as suggested. thanks, --peter > As to the several follow-up suggestions on further re-aligning the flag > bits, I am a little hesitant to support it (but I won't violently oppose > it either). We do not want to overdo it, since after all there is only 8 > bits available and if one insists on using "one-bit-one-meaning" > arrangement, we will not be able to go very far before we have to > abandon the approach. > > In coding, the differece is no more than: > > if(flag_field & 00001000) { ... } > > vs. > > if(flag_field == 0x08) { ... } > > regards, > -Qiaobing > > Michael Tuexen wrote: > >> Aron, >> >> possibly we could update the ENRP ID before the IETF deadline. This >> is still one week away. Qiaobing, if the .xml source is in Randalls >> CVS, I can do the editing, if you want. >> >> I can also update the ethereal dissector and Thomas can update >> the rsplib. >> >> Best regards >> Michael >> >> On Jul 7, 2004, at 10:40 PM, Silverton Aron-C1710C wrote: >> >>> Michael, >>> >>> The rest of here at Motorola discussed your comments this morning and >>> we, too, agree on all accounts. Do we need to wait for further >>> agreement, or should we proceed with updating our documentation and >>> implementations? >>> >>> Regards, >>> >>> Aron >>> >>> Qiaobing Xie <> wrote: >>> >>>> Michael, >>>> >>>> Michael Tuexen wrote: >>>> >>>>> Dear all, >>>>> >>>>> while writing the ethereal dissector for ENRP I found some things I >>>>> would like to change: >>>>> >>>>> Section 3.1 >>>>> >>>>> The length field is shown as 'Message Length = 0xC' which >>>>> is not correct because there can be some parameters. >>>> >>>> >>>> >>>> good catch. >>>> >>>>> >>>>> Section 3.3 >>>>> >>>>> Could we exchange the R and M bit? This would align the >>>>> R bit position with the reject bit in a PEER_LIST_RESONSE message. >>>> >>>> >>>> >>>> I agree. Better alignment is always good :-) >>>> >>>>> >>>>> Section 3.4 >>>>> >>>>> To have a similar layout of the packets i would suggest to change it >>>>> 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 = 0x4 |0|0|0|0|0|0|0|0| Message Length | >>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | >>>>> Sender Server's ID | >>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | >>>>> Receiver Server's ID | >>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | >>>>> Update Action | (reserved) | >>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ : >>>>> Pool handle : >>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ : >>>>> Pool Element : >>>>> >>>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>>> >>>> >>>> >>>> Makes sense to me. I agree. >>>> >>>> regards, >>>> -Qiaobing >>>> >>>>> >>>>> Best regards >>>>> Michael >>>>> >>>>> PS.: ethereal version 0.10.5 will support both ASAP and ENRP... >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 > --------------ms070505070002060203050107 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 CwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wNDA3MDkwNDE1MzVaMCMGCSqGSIb3DQEJ BDEWBBSmHcuYBMP3rdU29hRHTgFxLRyFTDBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMH MA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIB KDB4BgkrBgEEAYI3EAQxazBpMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29u c3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwg SXNzdWluZyBDQQIDC/CtMHoGCyqGSIb3DQEJEAILMWugaTBiMQswCQYDVQQGEwJaQTElMCMG A1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBl cnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECAwvwrTANBgkqhkiG9w0BAQEFAASCAQAllHNq Fke1mzo5NfTjcyhWNEZ7wgor1i4LN4xVY/y975chSi3FxkFtmkzyOXj6Y9oVA4ncebUV9bAe lwGfSCuiQvPlJq9h/XxhpVdw6oUeuD7Z2w9KDsd4dcx6F5IamjM8NjUanrucyS3BrQlOlV0k c88BgodgwTZFYbGg4XOF8mICBmP/cJ9SyazAgTS/CVfWkZJM/XM2w4+mtp9dSXhzdMm/+un2 8hxAENnAHzIw2Z2FlaWW6cwcp9CyZCovOSELzTNbdIEOSbJGmFoeGITIrNn+Vc33w6QE+LNX jAjKaJFBSKt7+WT3W30QoJ2gh2z+VXoroxworqCjauNknltWAAAAAAAA --------------ms070505070002060203050107-- --===============2144670030== 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 --===============2144670030==-- From rserpool-bounces@ietf.org Tue Jul 13 23:14: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 XAA04626 for ; Tue, 13 Jul 2004 23:14:00 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BkVxq-0002rJ-Fj; Tue, 13 Jul 2004 18:41:30 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BkUpW-00019J-Hf for rserpool@megatron.ietf.org; Tue, 13 Jul 2004 17:28:50 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20664 for ; Tue, 13 Jul 2004 17:28:47 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BkUpU-0004SU-VV for rserpool@ietf.org; Tue, 13 Jul 2004 17:28:49 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BkUhS-0002bu-00 for rserpool@ietf.org; Tue, 13 Jul 2004 17:20:31 -0400 Received: from motgate2.mot.com ([144.189.100.101]) by ietf-mx with esmtp (Exim 4.12) id 1BkUbq-00018P-00 for rserpool@ietf.org; Tue, 13 Jul 2004 17:14:42 -0400 Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231]) by motgate2.mot.com (Motorola/Motgate2) with ESMTP id i6DLAVBV010826 for ; Tue, 13 Jul 2004 14:10:31 -0700 (MST) Received: from motorola.com (d1421-0a1071e2.cig.mot.com [10.16.113.226]) by az33exr01.mot.com (Motorola/az33exr01) with ESMTP id i6DL7Psq001181; Tue, 13 Jul 2004 16:07:26 -0500 Message-ID: <40F45105.6000605@motorola.com> Date: Tue, 13 Jul 2004 16:15:49 -0500 From: Qiaobing Xie 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: Rserpool list Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Subject: [Rserpool] on terminology X-BeenThere: rserpool@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Reliable Server Pooling List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: rserpool-bounces@ietf.org Errors-To: rserpool-bounces@ietf.org Content-Transfer-Encoding: 7bit All, While reading some past comments about RSERPOOL drafts, the term "name" and "namespace" seem to be at the center of a lot of debates and confusion. I always wonder if this is due to the fact that these two terms are heavily overloaded over the years. I think it might help if we: 1) insist on using "pool handle" as the official formal term and avoiding "pool name" (we can continue to use "pool name" informally of cause) 2) instead of "namespace", we use "Handle-space" and change "namespace server" to "Pool Registrar" Comments? regards, -Qiaobing _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From rserpool-bounces@ietf.org Wed Jul 14 01:11: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 BAA22017 for ; Wed, 14 Jul 2004 01:11: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 1BkbtA-0004Lj-4g; Wed, 14 Jul 2004 01:01:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bkbl3-0007FX-KW for rserpool@megatron.ietf.org; Wed, 14 Jul 2004 00:52:41 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA17975 for ; Wed, 14 Jul 2004 00:52:38 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1Bkbl1-0002K0-JH for rserpool@ietf.org; Wed, 14 Jul 2004 00:52:39 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BkbGo-0004mK-00 for rserpool@ietf.org; Wed, 14 Jul 2004 00:21:27 -0400 Received: from ftpbox.mot.com ([129.188.136.101]) by ietf-mx with esmtp (Exim 4.12) id 1BkaiY-0006XT-00 for rserpool@ietf.org; Tue, 13 Jul 2004 23:46:02 -0400 Received: from il06exr06.mot.com (il06exr06.mot.com [129.188.137.136]) by ftpbox.mot.com (Motorola/Ftpbox) with ESMTP id i6E3k3Qv007618 for ; Tue, 13 Jul 2004 20:46:03 -0700 (MST) Received: from il02exm12.corp.mot.com (il02exm12.corp.mot.com [10.0.111.23]) by il06exr06.mot.com (Motorola/il06exr06) with ESMTP id i6E3k1dv010895 for ; Tue, 13 Jul 2004 22:46:02 -0500 Received: by il02exm12 with Internet Mail Service (5.5.2657.72) id ; Tue, 13 Jul 2004 22:46:02 -0500 Message-ID: From: Silverton Aron-C1710C To: Xie Qiaobing-QXIE1 , "'Rserpool list'" Subject: RE: [Rserpool] on terminology Date: Tue, 13 Jul 2004 22:46:01 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 X-BeenThere: rserpool@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Reliable Server Pooling List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: rserpool-bounces@ietf.org Errors-To: rserpool-bounces@ietf.org Qiaobing Xie <> wrote: > All, > > While reading some past comments about RSERPOOL drafts, the term > "name" and "namespace" seem to be at the center of a lot of debates > and confusion. I always wonder if this is due to the fact that these > two terms are heavily overloaded over the years. > > I think it might help if we: > > 1) insist on using "pool handle" as the official formal term and > avoiding "pool name" (we can continue to use "pool name" informally > of cause) > This seems okay to me. > 2) instead of "namespace", we use "Handle-space" and change > "namespace server" to "Pool Registrar" > I prefer "namespace", but I can be swayed. "Pool Registrar" sound good. > Comments? FWIW, I have a draft in the works that attempts to collect all of the RSerPool terminology in one place and weed out inconsistencies until such a time that both protocols are combined into a single IETF document. I'm sorry that I didn't get a -00 version done in time for this next meeting. > > regards, > -Qiaobing Aron > > > _______________________________________________ > 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 Jul 14 13:48:49 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 NAA01427 for ; Wed, 14 Jul 2004 13:48:49 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bkndv-0001OC-BN; Wed, 14 Jul 2004 13:34:07 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BknZR-0000rV-Dd for rserpool@megatron.ietf.org; Wed, 14 Jul 2004 13:29:29 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00542 for ; Wed, 14 Jul 2004 13:29:26 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BknZQ-00008o-DJ for rserpool@ietf.org; Wed, 14 Jul 2004 13:29:28 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BknYR-0007by-00 for rserpool@ietf.org; Wed, 14 Jul 2004 13:28:27 -0400 Received: from sjmail.ciena.com ([12.7.169.25] helo=w2ksjexg01.ciena.com) by ietf-mx with esmtp (Exim 4.12) id 1BknXV-0007Hz-00 for rserpool@ietf.org; Wed, 14 Jul 2004 13:27:29 -0400 Received: by w2ksjexg01.ciena.com with Internet Mail Service (5.5.2657.72) id <38GW6399>; Wed, 14 Jul 2004 10:26:57 -0700 Message-ID: <829F074A10F98943A218DC363D09C92A01E56CD4@w2ksjexg06.ciena.com> From: "Ong, Lyndon" To: "'Silverton Aron-C1710C'" , Xie Qiaobing-QXIE1 , "'Rserpool list'" Subject: RE: [Rserpool] on terminology Date: Wed, 14 Jul 2004 10:27:27 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 X-BeenThere: rserpool@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Reliable Server Pooling List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: rserpool-bounces@ietf.org Errors-To: rserpool-bounces@ietf.org This sounds like a good idea to me as well. Lyndon -----Original Message----- From: Silverton Aron-C1710C [mailto:Aron.J.Silverton@motorola.com] Sent: Tuesday, July 13, 2004 8:46 PM To: Xie Qiaobing-QXIE1; 'Rserpool list' Subject: RE: [Rserpool] on terminology Qiaobing Xie <> wrote: > All, > > While reading some past comments about RSERPOOL drafts, the term > "name" and "namespace" seem to be at the center of a lot of debates > and confusion. I always wonder if this is due to the fact that these > two terms are heavily overloaded over the years. > > I think it might help if we: > > 1) insist on using "pool handle" as the official formal term and > avoiding "pool name" (we can continue to use "pool name" informally > of cause) > This seems okay to me. > 2) instead of "namespace", we use "Handle-space" and change > "namespace server" to "Pool Registrar" > I prefer "namespace", but I can be swayed. "Pool Registrar" sound good. > Comments? FWIW, I have a draft in the works that attempts to collect all of the RSerPool terminology in one place and weed out inconsistencies until such a time that both protocols are combined into a single IETF document. I'm sorry that I didn't get a -00 version done in time for this next meeting. > > regards, > -Qiaobing Aron > > > _______________________________________________ > 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 Mon Jul 19 12:58:00 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 MAA05805 for ; Mon, 19 Jul 2004 12:58:00 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BmbC1-00069W-Ug; Mon, 19 Jul 2004 12:40:45 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bmayy-0003Fz-Bm for rserpool@megatron.ietf.org; Mon, 19 Jul 2004 12:27:16 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02559 for ; Mon, 19 Jul 2004 12:27:13 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1Bmayx-0004lx-GP for rserpool@ietf.org; Mon, 19 Jul 2004 12:27:15 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Bmay0-0004U5-00 for rserpool@ietf.org; Mon, 19 Jul 2004 12:26:16 -0400 Received: from ms.exp-math.uni-essen.de ([132.252.150.1] helo=pilz.exp-math.uni-essen.de) by ietf-mx with esmtp (Exim 4.12) id 1BmaxC-00042f-00 for rserpool@ietf.org; Mon, 19 Jul 2004 12:25:26 -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 i6JGLfFc189790 for ; Mon, 19 Jul 2004 18:25:25 +0200 From: Thomas Dreibholz To: "'rserpool@ietf.org'" Date: Mon, 19 Jul 2004 18:21:00 +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: <200407191821.02195.dreibh@exp-math.uni-essen.de> X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Subject: [Rserpool] ASAP Server Announce X-BeenThere: rserpool@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Reliable Server Pooling List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: rserpool-bounces@ietf.org Errors-To: rserpool-bounces@ietf.org Content-Transfer-Encoding: quoted-printable =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear all, it would be useful when the ASAP Server Announce contains the announced ENR= P=20 server's server ID. Then, a PE or PU can store an internal set of available= =20 ENRP servers sorted by ID. When a new announcement comes in, it is then muc= h=20 easier possible to check if an entry is already existing. Otherwise, this h= as=20 to be done by comparing addresses, which is much more inefficient. It seems to be further useful to define that an ASAP Server Announce MUST=20 contain exactly one SCTP Transport Parameter. Every ENRP server must have a= =20 SCTP endpoint (since PEs must use SCTP), it seems to make no sense to have= =20 several separate SCTP endpoints for the same ENRP server. Having the=20 possibility to have more than one SCTP transport parameters only makes it=20 difficult for a PE/PU to choose the right one. 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) iD8DBQFA+/Ts32BbsHYPLWURAnD0AKCgk4GwUu0wxG8IAzW0TpYXNrlgBgCfeSlu SwbCz2FHCkwhXdEa3/TosSI=3D =3DmurA =2D----END PGP SIGNATURE----- _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From rserpool-bounces@ietf.org Mon Jul 19 14:18:14 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 OAA12978 for ; Mon, 19 Jul 2004 14:18:14 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bmcbf-0003sU-Nh; Mon, 19 Jul 2004 14:11:19 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BmcU5-0002sA-KW for rserpool@megatron.ietf.org; Mon, 19 Jul 2004 14:03:29 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11847 for ; Mon, 19 Jul 2004 14:03:27 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BmcU4-0002JA-Jl for rserpool@ietf.org; Mon, 19 Jul 2004 14:03:28 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BmcTB-00022a-00 for rserpool@ietf.org; Mon, 19 Jul 2004 14:02:33 -0400 Received: from mail-n.franken.de ([193.175.24.27] helo=ilsa.franken.de ident=postfix) by ietf-mx with esmtp (Exim 4.12) id 1BmcSP-0001lJ-00 for rserpool@ietf.org; Mon, 19 Jul 2004 14:01:45 -0400 Received: from [192.168.1.22] (p5089E373.dip.t-dialin.net [80.137.227.115]) by ilsa.franken.de (Postfix) with ESMTP id B3A0D245D7; Mon, 19 Jul 2004 19:58:44 +0200 (CEST) (KNF account authenticated via SMTP-AUTH) In-Reply-To: <200407191821.02195.dreibh@exp-math.uni-essen.de> References: <200407191821.02195.dreibh@exp-math.uni-essen.de> Mime-Version: 1.0 (Apple Message framework v618) Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: quoted-printable From: Michael Tuexen Subject: Re: [Rserpool] ASAP Server Announce Date: Mon, 19 Jul 2004 20:01:20 +0200 To: Thomas Dreibholz X-Mailer: Apple Mail (2.618) X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 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 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: rserpool-bounces@ietf.org Errors-To: rserpool-bounces@ietf.org Content-Transfer-Encoding: quoted-printable Hi Thomas, see my comments in-line. Best regards Michael On Jul 19, 2004, at 6:21 PM, Thomas Dreibholz wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Dear all, > > it would be useful when the ASAP Server Announce contains the =20 > announced ENRP > server's server ID. Then, a PE or PU can store an internal set of =20 > available > ENRP servers sorted by ID. When a new announcement comes in, it is =20 > then much > easier possible to check if an entry is already existing. Otherwise, =20= > this has > to be done by comparing addresses, which is much more inefficient. > You could also store it by a hash of the IP-address... But from my point of view, we can add that. What do others think? > It seems to be further useful to define that an ASAP Server Announce =20= > MUST > contain exactly one SCTP Transport Parameter. Every ENRP server must =20= > have a > SCTP endpoint (since PEs must use SCTP), it seems to make no sense to =20= > have > several separate SCTP endpoints for the same ENRP server. Having the > possibility to have more than one SCTP transport parameters only makes = =20 > it > difficult for a PE/PU to choose the right one. But not all PUs talk SCTP. To support them an ENRP server might listen on a TCP and on a SCTP socket. Furthermore we use different port numbers for ASAP/TLS and ENRP/TLS compared to ASAP and ENRP not running over TLS. So I think an ENRP server might announce 4 transport addresses. > > > 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) > > iD8DBQFA+/Ts32BbsHYPLWURAnD0AKCgk4GwUu0wxG8IAzW0TpYXNrlgBgCfeSlu > SwbCz2FHCkwhXdEa3/TosSI=3D > =3DmurA > -----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 Fri Jul 23 04:16: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 EAA29535 for ; Fri, 23 Jul 2004 04:16: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 1BnuvY-0008Bc-5s; Fri, 23 Jul 2004 03:57:12 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bnut9-000706-Fi for rserpool@megatron.ietf.org; Fri, 23 Jul 2004 03:54:43 -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 DAA27268 for ; Fri, 23 Jul 2004 03:54:41 -0400 (EDT) Received: from ns.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 1Bnutr-0008W7-9b for rserpool@ietf.org; Fri, 23 Jul 2004 03:55:28 -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 i6N7sdFc192672 for ; Fri, 23 Jul 2004 09:54:39 +0200 From: Thomas Dreibholz To: "'rserpool@ietf.org'" Date: Fri, 23 Jul 2004 09:54:34 +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: <200407230954.38975.dreibh@exp-math.uni-essen.de> X-Spam-Score: 0.0 (/) X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8 Content-Transfer-Encoding: quoted-printable Subject: [Rserpool] ASAP Name Resolution X-BeenThere: rserpool@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Reliable Server Pooling List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: rserpool-bounces@ietf.org Errors-To: rserpool-bounces@ietf.org Content-Transfer-Encoding: quoted-printable =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear all, for the ASAP NAME_RESOLUTION message, it would be useful if a PU could spec= ify=20 an upper limit on how many PE entries the NS should reply. Consider an=20 example having a pool of 100 PEs. When a PU requires only one or two PEs as= =20 answer to its name resolution, it does not make any sense to reply more. Th= is=20 only wastes CPU cylces at the NS (selecting too many PEs from the pool) and= =20 bandwidth. Proposed NAME_RESOLUTION message definition: 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 =3D 0x5 |0|0|0|0|0|0|0|0| Message Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Max Name Resolution Items | (unused) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ : Pool Handle Parameter : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Max Name Resolution Items: 16 bit The NS SHOULD not reply more Pool Element Parameters in its response than specified here. 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) iD8DBQFBAMQ632BbsHYPLWURAkdSAJ96SlMvte2+807W2HWLmXoiOEZ4uACfULJ+ LcKxj3MEMNZm7szK7Rjdr+s=3D =3D0Spz =2D----END PGP SIGNATURE----- _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From rserpool-bounces@ietf.org Fri Jul 23 10:56:36 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 KAA29795 for ; Fri, 23 Jul 2004 10:56:36 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bo1RF-0005zj-8J; Fri, 23 Jul 2004 10:54:21 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bo1NG-0004Zt-P1 for rserpool@megatron.ietf.org; Fri, 23 Jul 2004 10:50:14 -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 KAA29219 for ; Fri, 23 Jul 2004 10:50:12 -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 1Bo1O2-000807-Fy for rserpool@ietf.org; Fri, 23 Jul 2004 10:51:03 -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 i6NEoBj03432 for ; Fri, 23 Jul 2004 17:50:11 +0300 (EET DST) X-Scanned: Fri, 23 Jul 2004 17:50:05 +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 i6NEo5fL032217 for ; Fri, 23 Jul 2004 17:50:05 +0300 Received: from mgw-int1.ntc.nokia.com (172.21.143.96) by esdks001.ntc.nokia.com 00ziCIJc; Fri, 23 Jul 2004 17:50:04 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 i6NEnwn01124 for ; Fri, 23 Jul 2004 17:49:58 +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); Fri, 23 Jul 2004 09:49:54 -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="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Fri, 23 Jul 2004 09:49:53 -0500 Message-ID: <57A26D272F67A743952F6B4371B8F811021D0399@daebe007.americas.nokia.com> Thread-Topic: Draft Rserpool Agenda for IETF #60 Thread-Index: AcRwxFA05jpO7AW1SA2aTqIHDiLg/w== To: X-OriginalArrivalTime: 23 Jul 2004 14:49:54.0588 (UTC) FILETIME=[50DE8DC0:01C470C4] X-Spam-Score: 0.3 (/) X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab Content-Transfer-Encoding: quoted-printable Subject: [Rserpool] Draft Rserpool Agenda for IETF #60 X-BeenThere: rserpool@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Reliable Server Pooling List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: rserpool-bounces@ietf.org Errors-To: rserpool-bounces@ietf.org Content-Transfer-Encoding: quoted-printable Please send any comments very soon. This is due on Monday to the IETF = agenda person. -- maureen Reliable Server Pooling WG (rserpool) =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D CHAIRs: Lyndon Ong =20 Maureen Stillman AGENDA: Opening Remarks Lyndon Ong, Maureen Stillman Rserpool services http://www.ietf.org/internet-drafts/draft-ietf-rserpool-service-01.txt Peter Lei, 10 minutes Rserpool comparison=20 http://www.ietf.org/internet-drafts/draft-ietf-rserpool-comp-07.txt John Loughney, 10 minutes Rserpool policies http://www.ietf.org/internet-drafts/draft-tuexen-rserpool-policies-00.txt= Thomas Dreibholz, 20 minutes ASAP update http://www.ietf.org/internet-drafts/draft-ietf-rserpool-asap-09.txt Randy Stewart, 10 minutes ENRP update http://www.ietf.org/internet-drafts/draft-ietf-rserpool-enrp-09.txt Qiaobing Xie, 10 minutes Rserpool architecture http://www.ietf.org/internet-drafts/draft-ietf-rserpool-arch-07.txt Michael Tuexen, 10 min. Rserpool applicability statement http://www.ietf.org/internet-drafts/draft-ietf-rserpool-applic-02.txt Lode Cone, 10 min. Rserpool Implementations Update Aron Silverton, 10 minutes Security http://www.ietf.org/internet-drafts/draft-ietf-rserpool-threats-03.txt Maureen Stillman, 5 min. Closing Remarks Lyndon Ong, Maureen Stillman _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From rserpool-bounces@ietf.org Fri Jul 23 14:52:08 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 OAA18099 for ; Fri, 23 Jul 2004 14:52:08 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bo54k-00013H-FP; Fri, 23 Jul 2004 14:47:22 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bo4zZ-0007Sr-CV for rserpool@megatron.ietf.org; Fri, 23 Jul 2004 14:42:01 -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 OAA17362 for ; Fri, 23 Jul 2004 14:42:00 -0400 (EDT) Received: from motgate4.mot.com ([144.189.100.102]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bo50L-00046H-5T for rserpool@ietf.org; Fri, 23 Jul 2004 14:42:52 -0400 Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231]) by motgate4.mot.com (Motorola/Motgate4) with ESMTP id i6NIfrCZ002328; Fri, 23 Jul 2004 11:41:54 -0700 (MST) Received: from motorola.com (d1421-0a1071e2.cig.mot.com [10.16.113.226]) by az33exr01.mot.com (Motorola/az33exr01) with ESMTP id i6NIYGRh019782; Fri, 23 Jul 2004 13:34:16 -0500 Message-ID: <41015C30.8050703@motorola.com> Date: Fri, 23 Jul 2004 13:42:56 -0500 From: Qiaobing Xie 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: Thomas Dreibholz Subject: Re: [Rserpool] ASAP Name Resolution References: <200407230954.38975.dreibh@exp-math.uni-essen.de> In-Reply-To: <200407230954.38975.dreibh@exp-math.uni-essen.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 i6NIfrCZ002328 X-Spam-Score: 0.0 (/) X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1 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 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: rserpool-bounces@ietf.org Errors-To: rserpool-bounces@ietf.org Content-Transfer-Encoding: quoted-printable Hi, Thomas, Similar suggestions were made in the past but no consensus was reached. P= art of the reason=20 was that (if I remember it right), on the surface this is a simple change= that is not hard=20 to implement, but there are some fundamental implications to the current = load balancing,=20 redundancy/failover models. For example, how the NS is going to select th= e 1 or 2 PEs from=20 the 100 PEs in the pool? What algorithm NS should use? How will this algo= rithm work with=20 (instead of against) the load balance and redundancy policy of the pool? = How will it work=20 with (instead of against) the failover rules at the PU? Your intention is= to save some CPU=20 cycle at the NS. But you may end up with burning much more NS CPU cycles = if this selection=20 algorithm brings substantial implementation and processing complexity to = the NS. We can discuss about this more at the meeting. regards, -Qiaobing Thomas Dreibholz wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 >=20 > Dear all, >=20 > for the ASAP NAME_RESOLUTION message, it would be useful if a PU could = specify=20 > an upper limit on how many PE entries the NS should reply. Consider an=20 > example having a pool of 100 PEs. When a PU requires only one or two PE= s as=20 > answer to its name resolution, it does not make any sense to reply more= . This=20 > only wastes CPU cylces at the NS (selecting too many PEs from the pool)= and=20 > bandwidth. >=20 > Proposed NAME_RESOLUTION message definition: >=20 > 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 =3D 0x5 |0|0|0|0|0|0|0|0| Message Length | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Max Name Resolution Items | (unused) | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > : Pool Handle Parameter : > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >=20 > Max Name Resolution Items: 16 bit >=20 > The NS SHOULD not reply more Pool Element Parameters in its > response than specified here. >=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 > iD8DBQFBAMQ632BbsHYPLWURAkdSAJ96SlMvte2+807W2HWLmXoiOEZ4uACfULJ+ > LcKxj3MEMNZm7szK7Rjdr+s=3D > =3D0Spz > -----END PGP SIGNATURE----- >=20 > _______________________________________________ > rserpool mailing list > rserpool@ietf.org > https://www1.ietf.org/mailman/listinfo/rserpool >=20 _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From rserpool-bounces@ietf.org Fri Jul 23 16:17:21 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 QAA24799 for ; Fri, 23 Jul 2004 16:17:21 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bo6PS-0003Xg-51; Fri, 23 Jul 2004 16:12:50 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bo6Kr-0002pZ-51 for rserpool@megatron.ietf.org; Fri, 23 Jul 2004 16:08: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 QAA24397 for ; Fri, 23 Jul 2004 16:08:03 -0400 (EDT) Received: from rwcrmhc13.comcast.net ([204.127.198.39]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bo6Le-00060Z-O7 for rserpool@ietf.org; Fri, 23 Jul 2004 16:08:57 -0400 Received: from [10.10.0.75] (c-24-13-174-21.client.comcast.net[24.13.174.21]) by comcast.net (rwcrmhc13) with ESMTP id <2004072320073001500o6158e> (Authid: peterlei); Fri, 23 Jul 2004 20:07:31 +0000 Message-ID: <41016FF4.7050208@ieee.org> Date: Fri, 23 Jul 2004 15:07:16 -0500 From: Peter Lei User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040616 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Maureen.Stillman@nokia.com Subject: Re: [Rserpool] Draft Rserpool Agenda for IETF #60 References: <57A26D272F67A743952F6B4371B8F811021D0399@daebe007.americas.nokia.com> In-Reply-To: <57A26D272F67A743952F6B4371B8F811021D0399@daebe007.americas.nokia.com> X-Spam-Score: 0.1 (/) X-Scan-Signature: 93e7fb8fef2e780414389440f367c879 Cc: rserpool@ietf.org X-BeenThere: rserpool@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Reliable Server Pooling List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1887308945==" Sender: rserpool-bounces@ietf.org Errors-To: rserpool-bounces@ietf.org This is a cryptographically signed message in MIME format. --===============1887308945== Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms030701030901080503010708" This is a cryptographically signed message in MIME format. --------------ms030701030901080503010708 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Looks good to me... Maureen.Stillman@nokia.com wrote: > Please send any comments very soon. This is due on Monday to the IETF agenda person. > > -- maureen > > Reliable Server Pooling WG (rserpool) > > ================================= > > CHAIRs: > Lyndon Ong > Maureen Stillman > > AGENDA: > > Opening Remarks > Lyndon Ong, Maureen Stillman > > > Rserpool services > http://www.ietf.org/internet-drafts/draft-ietf-rserpool-service-01.txt > Peter Lei, 10 minutes > > Rserpool comparison > http://www.ietf.org/internet-drafts/draft-ietf-rserpool-comp-07.txt > John Loughney, 10 minutes > > Rserpool policies > http://www.ietf.org/internet-drafts/draft-tuexen-rserpool-policies-00.txt > Thomas Dreibholz, 20 minutes > > ASAP update > http://www.ietf.org/internet-drafts/draft-ietf-rserpool-asap-09.txt > Randy Stewart, 10 minutes > > ENRP update > http://www.ietf.org/internet-drafts/draft-ietf-rserpool-enrp-09.txt > Qiaobing Xie, 10 minutes > > > Rserpool architecture > http://www.ietf.org/internet-drafts/draft-ietf-rserpool-arch-07.txt > Michael Tuexen, 10 min. > > Rserpool applicability statement > http://www.ietf.org/internet-drafts/draft-ietf-rserpool-applic-02.txt > Lode Cone, 10 min. > > Rserpool Implementations Update > Aron Silverton, 10 minutes > > Security > http://www.ietf.org/internet-drafts/draft-ietf-rserpool-threats-03.txt > Maureen Stillman, 5 min. > > Closing Remarks > Lyndon Ong, Maureen Stillman > > _______________________________________________ > rserpool mailing list > rserpool@ietf.org > https://www1.ietf.org/mailman/listinfo/rserpool > --------------ms030701030901080503010708 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 CwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wNDA3MjMyMDA3MTZaMCMGCSqGSIb3DQEJ BDEWBBQBkkgq3OHc8yqF5qVU2p37L/wdPzBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMH MA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIB KDB4BgkrBgEEAYI3EAQxazBpMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29u c3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwg SXNzdWluZyBDQQIDC/CtMHoGCyqGSIb3DQEJEAILMWugaTBiMQswCQYDVQQGEwJaQTElMCMG A1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBl cnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECAwvwrTANBgkqhkiG9w0BAQEFAASCAQDE+loT /fTvRpV4v3IroBAI92G1aLMp3h2VkgGgDYREQOCI156UwSKqbmlRADGv23N5Ojd/OjzWFqBu JogmrfrFJGIUrLwkYdSbkSLlJWAN/bgR6f5CsS2Qi5WZt5sLo69Mspja4nsyzJqS4bR4wiV3 LT3tDNDDlqR6yJ3qX+fSEon+ZVPolgf9Pl+2ATxaBMih++8NymDkSBdhkRj0m4MM73o3URuM lKXBlVdTwoGKNj+8A8JbYf6Yf39yuOimvv2eEw9uPpb/TAij+docilK0zHB1rB0+Fj+EsK9X xSi/R7qF6vTXXlOoUIAEJ6lorl1NjVufnyO+rkewsnUt3IHLAAAAAAAA --------------ms030701030901080503010708-- --===============1887308945== 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 --===============1887308945==-- From rserpool-bounces@ietf.org Mon Jul 26 04:38: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 EAA09083 for ; Mon, 26 Jul 2004 04:38: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 1Bp0yO-0007r0-Mk; Mon, 26 Jul 2004 04:36:40 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bp0tl-0007B6-8P for rserpool@megatron.ietf.org; Mon, 26 Jul 2004 04:31:53 -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 EAA08844 for ; Mon, 26 Jul 2004 04:31:51 -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 1Bp0v5-00026d-IO for rserpool@ietf.org; Mon, 26 Jul 2004 04:33:17 -0400 Received: from localhost (werner.exp-math.uni-essen.de [132.252.150.17]) by pilz.exp-math.uni-essen.de (8.12.10/8.12.8) with ESMTP id i6Q8VlFc277930 for ; Mon, 26 Jul 2004 10:31:48 +0200 From: Thomas Dreibholz To: Date: Mon, 26 Jul 2004 10:31:46 +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: <200407261031.47581.dreibh@exp-math.uni-essen.de> X-Spam-Score: 0.3 (/) X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1 Content-Transfer-Encoding: quoted-printable Subject: [Rserpool] ENRP Port Number X-BeenThere: rserpool@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Reliable Server Pooling List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: rserpool-bounces@ietf.org Errors-To: rserpool-bounces@ietf.org Content-Transfer-Encoding: quoted-printable =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear all, is there a reserved port number for ENRP, especially ENRP via UDP? The=20 reserved port number for ASAP is 3863, for ASAP TLS via UDP (this does not= =20 make any sense, TLS does not work with UDP!) it is 3864. What about using=20 3864 for ENRP via UDP? 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 =A0Dipl.-Inform. Thomas Dreibholz =A0University of Duisburg-Essen =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Room E= S210 =A0Inst. for Experimental Mathematics =A0 =A0 =A0 =A0 =A0 =A0 =A0Ellernstra= =DFe 29 =A0Computer Networking Technology Group =A0 =A0 =A0 =A0 =A0 =A0D-45326 Esse= n/Germany =2D ----------------------------------------------------------------------- =A0E-Mail: =A0 =A0 dreibh@exp-math.uni-essen.de =A0Homepage: =A0 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) iD8DBQFBBMFy32BbsHYPLWURAq+eAJ0RDI0Hdc3/4LfhLt7ELdYeCjCUkACffXNS SxxfzHr5c3M10wmImZ7CDYM=3D =3Drm1f =2D----END PGP SIGNATURE----- _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From rserpool-bounces@ietf.org Tue Jul 27 05:25:38 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 FAA00120 for ; Tue, 27 Jul 2004 05:25:38 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BpOBM-0006fO-OC; Tue, 27 Jul 2004 05:23:36 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BpOAu-0006Xf-Ii for rserpool@megatron.ietf.org; Tue, 27 Jul 2004 05:23:08 -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 FAA29756 for ; Tue, 27 Jul 2004 05:23: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 1BpOCS-0003jx-TB for rserpool@ietf.org; Tue, 27 Jul 2004 05:24:46 -0400 Received: from localhost (werner.exp-math.uni-essen.de [132.252.150.17]) by pilz.exp-math.uni-essen.de (8.12.10/8.12.8) with ESMTP id i6R9N3x8119248 for ; Tue, 27 Jul 2004 11:23:03 +0200 From: Thomas Dreibholz To: Date: Tue, 27 Jul 2004 11:22:05 +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: <200407271122.06681.dreibh@exp-math.uni-essen.de> X-Spam-Score: 0.3 (/) X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002 Content-Transfer-Encoding: quoted-printable Subject: [Rserpool] ENRP Peer Name Update X-BeenThere: rserpool@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Reliable Server Pooling List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: rserpool-bounces@ietf.org Errors-To: rserpool-bounces@ietf.org Content-Transfer-Encoding: quoted-printable =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear all, ENRP PEER_NAME_UPDATE contains the full Pool Element Parameter even in case= of=20 deregistrations. ASAP DEREGISTRATION only uses a PE Identifier Parameter to= =20 identify the PE. This is sufficient to identify and remove the PE. So, what= =20 about defining to also use a PE Identifier parameter for deregistrations in= =20 the PEER_NAME_UPDATE? That is, in case of registrations PEER_NAME_UPDATE=20 would contain a Pool Element Parameter and in case of deregistrations a PE= =20 Identifier Parameter. May be, it would be a good idea to split up PEER_NAME_UPDATE into a=20 PEER_NAME_REGISTRATION and PEER_NAME_DEREGISTRATION. Then, it would be=20 consistent to ASAP's message types. 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 =A0Dipl.-Inform. Thomas Dreibholz =A0University of Duisburg-Essen =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Room E= S210 =A0Inst. for Experimental Mathematics =A0 =A0 =A0 =A0 =A0 =A0 =A0Ellernstra= =DFe 29 =A0Computer Networking Technology Group =A0 =A0 =A0 =A0 =A0 =A0D-45326 Esse= n/Germany =2D ----------------------------------------------------------------------- =A0E-Mail: =A0 =A0 dreibh@exp-math.uni-essen.de =A0Homepage: =A0 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) iD8DBQFBBh6932BbsHYPLWURAg7UAKC4k1L1fC4kyMB/1cxkLeksxePL+QCePM78 uDbdR+0wptVWbmoGNv5v60c=3D =3Dg//Z =2D----END PGP SIGNATURE----- _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool