Re: [Forces-protocol] FE Protocol LFB, FE LFB, CE LFB (draft sections) to review.

Robert Haas <rha@zurich.ibm.com> Sat, 23 October 2004 19:25 UTC

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 PAA17477 for <forces-protocol-web-archive@ietf.org>; Sat, 23 Oct 2004 15:25:59 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CLRjh-0002Ub-DZ for forces-protocol-web-archive@ietf.org; Sat, 23 Oct 2004 15:39:33 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CLRPZ-0005xU-8h; Sat, 23 Oct 2004 15:18:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CLRNm-0004OE-Pm for forces-protocol@megatron.ietf.org; Sat, 23 Oct 2004 15:16:54 -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 PAA16893 for <forces-protocol@ietf.org>; Sat, 23 Oct 2004 15:16:52 -0400 (EDT)
Received: from e1.ny.us.ibm.com ([32.97.182.101]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CLRar-0002Ml-AI for forces-protocol@ietf.org; Sat, 23 Oct 2004 15:30:26 -0400
Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234]) by e1.ny.us.ibm.com (8.12.10/NS PXFA) with ESMTP id i9NJGAUl417040; Sat, 23 Oct 2004 15:16:10 -0400
Received: from sihl.zurich.ibm.com (d01av02.pok.ibm.com [9.56.224.216]) by d01relay02.pok.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id i9NJG90v098072; Sat, 23 Oct 2004 15:16:09 -0400
Received: from [9.4.69.18] (dhcp69-18.zurich.ibm.com [9.4.69.18]) by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id VAA73032; Sat, 23 Oct 2004 21:16:08 +0200
Message-ID: <417AADED.9080605@zurich.ibm.com>
Date: Sat, 23 Oct 2004 21:15:57 +0200
From: Robert Haas <rha@zurich.ibm.com>
Organization: IBM Research Lab
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: avri@psg.com
Subject: Re: [Forces-protocol] FE Protocol LFB, FE LFB, CE LFB (draft sections) to review.
References: <468F3FDA28AA87429AD807992E22D07E02579210@orsmsx408> <1E526654-24BF-11D9-9DB1-000393CC2112@psg.com> <417A23E6.7010504@zurich.ibm.com> <C4CB0B3C-251F-11D9-9DB1-000393CC2112@psg.com>
In-Reply-To: <C4CB0B3C-251F-11D9-9DB1-000393CC2112@psg.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by e1.ny.us.ibm.com id i9NJGAUl417040
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ec7c6dab5a62df223002ae71b5179d41
Content-Transfer-Encoding: quoted-printable
Cc: "Khosravi, Hormuzd M" <hormuzd.m.khosravi@intel.com>, ram.gopal@nokia.com, Ligang Dong <donglg@mail.hzic.edu.cn>, forces-protocol@ietf.org, hadi@znyx.com, Weiming Wang <wmwang@mail.hzic.edu.cn>
X-BeenThere: forces-protocol@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: forces-protocol <forces-protocol.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/forces-protocol>, <mailto:forces-protocol-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/forces-protocol>
List-Post: <mailto:forces-protocol@ietf.org>
List-Help: <mailto:forces-protocol-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/forces-protocol>, <mailto:forces-protocol-request@ietf.org?subject=subscribe>
Sender: forces-protocol-bounces@ietf.org
Errors-To: forces-protocol-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 311e798ce51dbeacf5cdfcc8e9fda21b
Content-Transfer-Encoding: quoted-printable

Thanks Avri.  I sent out a note with my updated section after Weiming's 
comments, your note crossed mine ... So I've added a diff below so you 
can edit the text more easily now.

A few comments:
 Remove section 3.3.2 (FE Protocol Object)
 Rename current section 3.3.3 (FE Object) to "FE, FE, and FE Protocol LFBs"
 Typo "An short description" in section above
 Text I wrote with [] should be transformed into Editorial notes (and 
maybe rephrase them to look less stupid ;-)


rha@aigle:~$ diff -B -b --unified LFBs-rha.txt.old LFBs-rha.txt.new
--- LFBs-rha.txt.old    2004-10-23 20:57:18.000000000 +0200
+++ LFBs-rha.txt.new    2004-10-23 20:56:24.000000000 +0200
@@ -18,11 +18,12 @@

 Chapter X: FE, CE, and Protocol LFBs.

-The following LFBs are used to control the operation of the ForCES 
protocol and interact with FEs and CEs.
+The FE LFB, CE LFB, and FE Protocol LFB are used to control the 
operation of the ForCES protocol and interact with FEs and CEs.
+Although these LFBs have the same form and interface as other LFBs, 
they are special in many respects: they have fixed well-known LFB Class 
and Instance IDs. They are statically defined (no dynamic instantiation 
allowed) and their status cannot be changed by the protocol: any 
operation to change the state of such LFBs (for instance, in order to 
disable the LFB) must result in an error. Moreover, these LFBs must 
exist before the first ForCES message can be sent or received. All 
attributes in these LFBs must have pre-defined default values. Finally, 
these LFBs do not have input nor output ports and do not integrate into 
the intra-FE LFB topology.

 Section X.1 FE Protocol LFB

-The FE Protocol LFB is a logical entity in each FE that is used to 
control the ForCES protocol. The FE Protocol LFB can be manipulated 
using the standard PL messages. The FE Protocol LFB Class ID is assigned 
the value 0x1. The FE LFB Instance ID is assigned the value 0x1. There 
must always be one and only one instance of the FE Protocol LFB in an 
FE. The values of the attributes in the FE Protocol LFB have pre-defined 
default values that are specified here. Unless explicit changes are made 
to these values using Config messages from the CE, these default values 
MUST be used for the operation of the protocol.
[diff is removal of the sentence "The FE Protocol LFB can be manipulated 
using the standard PL messages."]
+The FE Protocol LFB is a logical entity in each FE that is used to 
control the ForCES protocol. The FE Protocol LFB Class ID is assigned 
the value 0x1. The FE LFB Instance ID is assigned the value 0x1. There 
must always be one and only one instance of the FE Protocol LFB in an 
FE. The values of the attributes in the FE Protocol LFB have pre-defined 
default values that are specified here. Unless explicit changes are made 
to these values using Config messages from the CE, these default values 
MUST be used for the operation of the protocol.

 The FE Protocol Object consists of the following elements:

@@ -33,15 +34,18 @@
    Current version of the ForCES protocol
    Current version of the FE model
-   FE unicast ID(s) (list)
+  FE unicast ID
    FE multicast ID(s) (list)
    Association Expiry Timer
    Heartbeat Interval
    Primary CE
    FE failover and restart policy
+  CE failover and restart policy [XXX: what is the diff with FE failover ?]
+
+[TBD: define default values for each attribute if applicable]

 Section X.2

@@ -53,11 +57,12 @@
    FEStatusChange (events that signal FE Up/Down/Active/Inactive/Failover)
    FE DoS alert
    FE capability change
  FE attributes:
-   FEStatusChange (to set the FE in Active, Inactive, or Shutdown mode 
[Note: this replies the State Maintenance messages])
+  FEStatusChange (to set the FE in Active, Inactive, or Shutdown mode 
[Note: this replaces the State Maintenance messages])
    MIID table (a list of virtual LFB Instance IDs that map to a list of 
Instance IDs of LFBs in that FE [Refer to Zsolt's note])
    FE Behavior Exp. Timer
    HA Mode
+  FE DoS protection policy
    [the attributes below were previously under Query message]
    Inter-FE topology
    Intra-FE topology
@@ -67,8 +72,8 @@

 The CE LFB is a logical entity in each CE and contains attributes 
relative to the CE itself, and not to the operation of the ForCES protocol.

- The FE LFB consists of the following elements:
+The CE LFB consists of the following elements:
  CE Events:
    CEAllEvents (subscribing to this corresponds to subscribing to all 
events below) [Do we want to allow an FE to explicitely subscribe to CE 
events ?]
    CEStatusChange (events that signal CE 
Up/Down/Active/Inactive/Failover)  [Such events do not necessarily need 
to be subscribed to, they can fire even without subscription and inform 
the FE]




Regards.
-Robert


avri@psg.com wrote:

>
> On 23 okt 2004, at 05.27, Robert Haas wrote:
>
>> All,
>> Below is a new draft of the sections related to FE/Protocol LFBs. 
>> Please review.
>
>
> http://psg.com/~avri/forces/draft/draft-ietf-forces-protocol-01-4.txt
> includes changes i have received so far and includes the text you sent.
>
>>
>> I will also try to add a table summarizing the operations allowed in 
>> each type of PL message. I sent it in a previous message.
>
>
> i missed that.  do you want me to build the table?
>
>>
>> BTW, I find it a bit odd to have Query messages defined before Config 
>> messages in Section "Protocol Messages". Does anyone mind changing 
>> the order ?
>
>
> Moved.
>
>>
>> Avri,
>> Please send the xml files once you have updated them. I'll then 
>> incorporate my text below directly taking suggestions/comments into 
>> account, unless you want to do it ;-)
>
>
> with 1-2 days left to finish, i don't mind making the changes.  as i 
> will be going through cleaning up format, fixing some xrefs and doing 
> a language edit, it would be easiest at this point if people just send 
> me text changes.
>
> i.e. not whole new text, but something of the sort:
>
> old text:
> bla bla bla
>
> new text:
> better bla, better bla, better bla.
>
> (regular unix diffs work just fine. :-)
>
> but if this is not ok with you, then i will send youi the changed xml 
> files.
>
>>
>> BTW, we'll have to remove the State maintenance section and add a new 
>> chapter for these LFBs (new xml file ?).
>>
>>
>
> At an earlier request, i removed the State maintenance section (i 
> think).  let me know what you want inserted.
>
> i will probably put out another version later today/tonight.
>
>
> cheers
> a.
>
>
>

-- 
Robert Haas
IBM Zurich Research Laboratory
Säumerstrasse 4
CH-8803 Rüschlikon/Switzerland
phone +41-1-724-8698  fax +41-1-724-8578  http://www.zurich.ibm.com/~rha


_______________________________________________
Forces-protocol mailing list
Forces-protocol@ietf.org
https://www1.ietf.org/mailman/listinfo/forces-protocol