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

Robert,

----- Original Message -----
From: "Robert Haas" <rha@zurich.ibm.com>

> @@ -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 ?]
[Weiming] I agree your idea that these two may be merged. Say it as 'CE and FE
failover policy' ?

> +
> +[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]
[Weiming] this editorial note is not needed anymore, fore I'v already removed
the following items.

>     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]


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