draft-ietf-forces-ceha-02.txt   draft-ietf-forces-ceha-03.txt 
Network Working Group K. Ogawa Network Working Group K. Ogawa
Internet-Draft NTT Corporation Internet-Draft NTT Corporation
Intended status: Standards Track W. M. Wang Intended status: Standards Track W. M. Wang
Expires: February 25, 2012 Zhejiang Gongshang University Expires: August 23, 2012 Zhejiang Gongshang University
E. Haleplidis E. Haleplidis
University of Patras University of Patras
J. Hadi Salim J. Hadi Salim
Mojatatu Networks Mojatatu Networks
August 24, 2011 February 20, 2012
ForCES Intra-NE High Availability ForCES Intra-NE High Availability
draft-ietf-forces-ceha-02 draft-ietf-forces-ceha-03
Abstract Abstract
This document discusses CE High Availability within a ForCES NE. This document discusses CE High Availability within a ForCES NE.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on February 25, 2012. This Internet-Draft will expire on August 23, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 18 skipping to change at page 2, line 18
1. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Document Scope . . . . . . . . . . . . . . . . . . . . . . 5 2.1. Document Scope . . . . . . . . . . . . . . . . . . . . . . 5
2.2. Quantifying Problem Scope . . . . . . . . . . . . . . . . 5 2.2. Quantifying Problem Scope . . . . . . . . . . . . . . . . 5
3. RFC5810 CE HA Framework . . . . . . . . . . . . . . . . . . . 6 3. RFC5810 CE HA Framework . . . . . . . . . . . . . . . . . . . 6
3.1. Current CE High Availability Support . . . . . . . . . . . 6 3.1. Current CE High Availability Support . . . . . . . . . . . 6
3.1.1. Cold Standby Interaction with ForCES Protocol . . . . 7 3.1.1. Cold Standby Interaction with ForCES Protocol . . . . 7
3.1.2. Responsibilities for HA . . . . . . . . . . . . . . . 9 3.1.2. Responsibilities for HA . . . . . . . . . . . . . . . 9
4. CE HA Hot Standby . . . . . . . . . . . . . . . . . . . . . . 10 4. CE HA Hot Standby . . . . . . . . . . . . . . . . . . . . . . 10
4.1. Changes to the FEPO model . . . . . . . . . . . . . . . . 10 4.1. Changes to the FEPO model . . . . . . . . . . . . . . . . 10
4.2. FEPO processing . . . . . . . . . . . . . . . . . . . . . 10 4.2. FEPO processing . . . . . . . . . . . . . . . . . . . . . 11
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
6. Security Considerations . . . . . . . . . . . . . . . . . . . 14 6. Security Considerations . . . . . . . . . . . . . . . . . . . 16
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16
7.1. Normative References . . . . . . . . . . . . . . . . . . . 14 7.1. Normative References . . . . . . . . . . . . . . . . . . . 16
7.2. Informative References . . . . . . . . . . . . . . . . . . 15 7.2. Informative References . . . . . . . . . . . . . . . . . . 16
Appendix 1. Appendix I - New FEPO version . . . . . . . . . . . . 15 Appendix 1. Appendix I - New FEPO version . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 22 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 24
1. Definitions 1. Definitions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119. document are to be interpreted as described in RFC 2119.
The following definitions are taken from [RFC3654]and [RFC3746]: The following definitions are taken from [RFC3654]and [RFC3746]:
Logical Functional Block (LFB) -- A template that represents a fine- Logical Functional Block (LFB) -- A template that represents a fine-
skipping to change at page 8, line 10 skipping to change at page 8, line 10
connection recovery. connection recovery.
The FE connects to the CE specified on FEPO CEID component. If it The FE connects to the CE specified on FEPO CEID component. If it
fails to connect to the defined CE, it moves it to the bottom of fails to connect to the defined CE, it moves it to the bottom of
table BackupCEs and sets its CEID component to be the first CE table BackupCEs and sets its CEID component to be the first CE
retrieved from table BackupCEs. The FE then attempts to associate retrieved from table BackupCEs. The FE then attempts to associate
with the CE designated as the new primary CE. The FE continues with the CE designated as the new primary CE. The FE continues
through this procedure until it successfully connects to one of the through this procedure until it successfully connects to one of the
CEs. CEs.
(CE issues Teardown || +-----------------+ FE tries to associate
+-->-----+
| |
(CE issues Teardown || +---+--------v----+
Lost association) && | Pre-Association | Lost association) && | Pre-Association |
CE failover policy = 0 | (Association | CE failover policy = 0 | (Association |
+------------>-->-->| in +<----+ +------------>-->-->| in +<----+
| | progress) | | | | progress) | |
| CE Issues +--------+--------+ | | CE Issues +--------+--------+ |
| Association | | CEFTI | Association | | CEFTI
| Response V | timer | Response V | timer
| ___________________+ | expires | ___________________+ | expires
| | | | | ^
| V ^ | V |
+-+-----------+ +-------+-----+ +-+-----------+ +------+-----+
| | | Not | | | | Not |
| | (CE issues Teardown || | Associated | | | (CE issues Teardown || | Associated |
| | Lost association) && | | | | Lost association) && | +->---+
| Associated | CE Failover Policy = 1 | (May | | Associated | CE Failover Policy = 1 |(May | FE |
| | | Continue | | | | Continue |try v
| |---------->------->------>| Forwarding)| | |-------->------->------>| Forwarding)|assn |
| | | | | | | |-<---+
+-------------+ +-------------+ | | | |
^ V +-------------+ +-------+-----+
| | ^ |
| CE Issues | | CE Issues v
| Association | | Association |
| Setup | | Setup |
+_________________________________________+ +_________________________________________+
Figure 3: FE State Machine considering HA Figure 3: FE State Machine considering HA
When communication fails between the FE and CE (which can be caused When communication fails between the FE and CE (which can be caused
by either the CE or link failure but not FE related), either the TML by either the CE or link failure but not FE related), either the TML
on the FE will trigger the FE PL regarding this failure or it will be on the FE will trigger the FE PL regarding this failure or it will be
detected using the HB messages between FEs and CEs. The detected using the HB messages between FEs and CEs. The
skipping to change at page 9, line 20 skipping to change at page 9, line 22
during this state. It MAY also recycle through any configured backup during this state. It MAY also recycle through any configured backup
CEs in a round-robin fashion. It first adds its primary CE to the CEs in a round-robin fashion. It first adds its primary CE to the
bottom of table BackupCEs and sets its CEID component to be the first bottom of table BackupCEs and sets its CEID component to be the first
secondary retrieved from table BackupCEs. The FE then attempts to secondary retrieved from table BackupCEs. The FE then attempts to
associate with the CE designated as the new primary CE. If it fails associate with the CE designated as the new primary CE. If it fails
to re-associate with any CE and the CEFTI expires, the FE then to re-associate with any CE and the CEFTI expires, the FE then
transitions to the pre-association state. transitions to the pre-association state.
If the FE, while in the not associated state, manages to reconnect to If the FE, while in the not associated state, manages to reconnect to
a new primary CE before CEFTI expires it transitions to the a new primary CE before CEFTI expires it transitions to the
Associated state. Once re-associated, the FE tries to recover any Associated state. Once re-associated, the CE tries to synchronize
state that may have been lost during the not associated state. How any state that the FE may have lost during the not associated state.
the FE re-synchronizes state is out of scope for the current ForCES How the CE re-synchronizes such state is out of scope for the current
architecture. ForCES architecture but would include issuing new configs and
queries.
An explicit message (a Config message setting Primary CE component in An explicit message (a Config message setting Primary CE component in
ForCES Protocol object) from the primary CE, can also be used to ForCES Protocol object) from the primary CE, can also be used to
change the Primary CE for an FE during normal protocol operation. In change the Primary CE for an FE during normal protocol operation. In
this case, the FE transitions to the Not Associated State and this case, the FE transitions to the Not Associated State and
attempts to Associate with the new CE. attempts to Associate with the new CE.
3.1.2. Responsibilities for HA 3.1.2. Responsibilities for HA
TML Level: TML Level:
skipping to change at page 10, line 43 skipping to change at page 10, line 46
(Lost_Connection) and 4 (Unreachable). (Lost_Connection) and 4 (Unreachable).
2. Change Component BackupCEs (9) to AllCEs and instead of an Array 2. Change Component BackupCEs (9) to AllCEs and instead of an Array
of unsigned integers(CEID), it MUST be an Array of unsigned of unsigned integers(CEID), it MUST be an Array of unsigned
integers (CEID) and unsigned char (status) for each CE. integers (CEID) and unsigned char (status) for each CE.
3. Add two special values to the CEFailoverPolicyValues. 2 (High 3. Add two special values to the CEFailoverPolicyValues. 2 (High
availability without Graceful restart) and 3 (High availability availability without Graceful restart) and 3 (High availability
with Graceful restart). with Graceful restart).
4. Added one additional Event, the HAPrimaryCEDown event which
reports last known CEID and tentative new master CEID.
As the FEPO component 9 is not backwards compatible with the previous
version there is the issue of interoperability between CE and FE.
However this is a pre-association version mismatch and the managers
have to identify the issue and not allow an association that would
fail or cause problems.
4.2. FEPO processing 4.2. FEPO processing
The FE's FEPO LFB version 2 AllCEs table (previously BackupCEs) The FE's FEPO LFB version 2 AllCEs table (previously BackupCEs)
contains all the CEIDs that the FE may connect and associate with. contains all the CEIDs that the FE may connect and associate with.
The ordering of the CE IDs in this table defines the priority order The ordering of the CE IDs in this table defines the priority order
in which an FE will connect to the CEs. In the pre-association in which an FE will connect to the CEs. In the pre-association
phase, the first CE ID (lowest table index) in the AllCEs table MUST phase, the first CE ID (lowest table index) in the AllCEs table MUST
be the first CE ID that the FE will attempt to connect and associate be the first CE ID that the FE will attempt to connect and associate
with. If the FE fails to connect and associate with the first CE ID, with. If the FE fails to connect and associate with the first CE ID,
it will attempt to connect to the second CE ID and so forth, and it will attempt to connect to the second CE ID and so forth, and
cycles back to the beggining of the list until there is a connection cycles back to the beggining of the list until there is a connection
and an association. The FE MUST associate with at least one CE. and an association. The FE MUST associate with at least one CE.
Upon a successful association, the FEPO's CEID component identifies Upon a successful association, the FEPO's CEID component identifies
the current associated master CE. the current associated master CE.
For the sake of simplicity, the FE MUST respond to messages issued
only by the master CE. This simplifies the synchronization and
avoids the concept of locking FE state. i.e the FE MUST drop any
messages from backup CEs. However, asynchronous events that the
master CE has subscribed to, as well as heartbeats are sent to all
associated-to CEs. Packet redirects continue to be sent only to the
master CE. The Heartbeat Interval, the CEHB Policy and the FEHB
Policy MUST be the same for all CEs.
Figure 4 illustrates the state machine that facilitates connection
recovery with High Availability enabled.
FE tries to associate
+-->-----+
| |
^ v
(CE issues Teardown || +----+--------+---+
Lost association) && | Pre-Association |
CE failover policy = 0 | (Association +<-------------------+
+------------>-->-->| in +<-----+ |
| | progress) | | |
| CE Issues +--------+--------+ | |
| Association | | |
| Response V Not Found || CEFTI |
| ___________________+ timer expires |
| | | |
| V ^ |
+-+-----------+ +------+------+ |
| | | Not | |
| | (CE issues Teardown || | Associated | |
| | Lost association) && | | CEFTI
| Associated | (CE Failover Policy=2|| | (May | timer
| | CE Failover Policy=3) | Continue | expires
| +---------->------->----->| Forwarding)| |
| | | | |
| | | Search for | |
| | +--------->| next | |
| | | | associated | |
| | | | CE | |
+-------------+ | +-------------+ |
^ | V |
| | | |
| | Found CE |
| CEHDI Expires Send Event of |
| | New CE ID. |
| | | |
| | V |
| | +------+------+ |
| ^---------+ Confirm +-------^
| | State |
| Received +---->| |
| different | | Wait for CE |
| CE ID. ^ | to confirm |
| Resend Event | | new CE ID |
| +----<| |
| +-----+-------+
| Received same CE ID |
+_______________________________________+
Figure 4: FE State Machine considering HA
Once the FE has associated with a master CE it moves to the post- Once the FE has associated with a master CE it moves to the post-
association phase. In the post-association phase, the master CE MAY association phase (Associated state). In this state, the master CE
update the list of backup CEs. It MAY also instruct the FE to use a MAY update the list of backup CEs. It MAY also instruct the FE to
different master CE. It is assumed that the master CE will use a different master CE. It is assumed that the master CE will
communicate with other CEs within the NE for the purpose of communicate with other CEs within the NE for the purpose of
synchronization via the CE-CE interface. The CE-CE interface is out synchronization via the CE-CE interface. The CE-CE interface is out
of scope for this document. of scope for this document.
FE CE#1 CE#2 ... CE#N FE CE#1 CE#2 ... CE#N
| | | | | | | |
| Asso Estb,Caps exchg | | | | Asso Estb,Caps exchg | | |
1 |<-------------------->| | | 1 |<-------------------->| | |
| | | | | | | |
| state update | | | | state update | | |
skipping to change at page 11, line 39 skipping to change at page 13, line 34
... ... ... ... ... ... ... ...
| Asso Estb,Caps exchg | | Asso Estb,Caps exchg |
3N|<------------------------------------------>| 3N|<------------------------------------------>|
| | | | | | | |
4 |<-------------------->| | | 4 |<-------------------->| | |
. . . . . . . .
4x|<-------------------->| | | 4x|<-------------------->| | |
| FAILURE | | | FAILURE | |
| | | | | | | |
| Event Report (CE#2 is new master) | | | Event Report (CE#2 is new master) | |
5 |--------------------->|----------->|------->| 5 |---------------------------------->|------->|
| | | | | |
| Config (Set CEID to CEID of CE#3) | | | Config (Set CEID to CEID of CE#2) | |
6 |<----------------------------------| | 6 |<----------------------------------| |
7 |<--------------------------------->| | 7 |<--------------------------------->| |
. . . . . . . .
7x|<--------------------------------->| | 7x|<--------------------------------->| |
. . . . . . . .
Figure 4: CE Failover for Hot Standby Figure 5: CE Failover for Hot Standby
XXX: We need to have a figure3' to match the new FEPO SM
While in the post-association phase, if the CE Failover Policy is set While in the post-association phase, if the CE Failover Policy is set
to 2 (High Availability without Graceful Restart) or 3 (High to 2 (High Availability without Graceful Restart) or 3 (High
Availability with Graceful Restart) then the FE, after succesfully Availability with Graceful Restart) then the FE, after succesfully
associating with the master CE, MUST attempt to connect and associate associating with the master CE, MUST attempt to connect and associate
with all the CEs that it becomes aware of. Figure 4 steps #1 and #2 with all the CEs that is aware of. Figure 5 steps #1 and #2
illustrates the FE associating with CE#1 as the master and then illustrates the FE associating with CE#1 as the master and then
proceeding to steps #3I to #3N the association with backup CE's CE#2 proceeding to steps #3I to #3N the association with backup CE's CE#2
to CE#N. If the FE fails to connect or associate with some CEs, the to CE#N. If the FE fails to connect or associate with some CEs, the
FE MAY flag them as unreachable to avoid continuous attempts to FE MAY flag them as unreachable to avoid continuous attempts to
connect. The FE may retry to reassociate with unreachable CEs when connect. The FE MAY retry to reassociate with unreachable CEs when
possible. possible.
When the master CE for any reason is considered to be down, then the When the master CE for any reason is considered to be down, then the
FE will try to find the first associated CE from the list of all CEs FE will try to find the first associated CE from the list of all CEs
in a round-robin fashion. in a round-robin fashion.
If the FE is unable to find an associated FE in its list of CEs, then If the FE is unable to find an associated FE in its list of CEs, then
it will attempt to connect and associate with the first from the list it will attempt to connect and associate with the first from the list
of all CEs and continue in a round-robin fashion until it connects of all CEs and continue in a round-robin fashion until it connects
and associates with a CE. and associates with a CE.
Once the FE selects the associated CE to use as the new master, the Once the FE selects the associated CE to use as the new master, the
FE then sends the Primary CE Down Event Notification to all FE then sends a High Availability Primary CE Changed Event
associated CEs to notify them that the FE considers this CE as the Notification to all associated CEs to notifying them that the primary
new master CE. CE is down as well as which CE the reporting FE considers to be the
new master.
The new master CE MUST configure the CEID component of the FE within The new master CE MUST configure the CEID component of the FE within
the time limit defined in the FEPO Failover Timeout as a confirmation the time limit defined in the CEHDI Failover Timeout as a
that the FE made the right choice. confirmation that the FE made the right choice.
FE CE#1 CE#2 ... CE#N FE CE#1 CE#2 ... CE#N
| | | | | | | |
| Asso Estb,Caps exchg | | | | Asso Estb,Caps exchg | | |
1 |<-------------------->| | | 1 |<-------------------->| | |
| | | | | | | |
| state update | | | | state update | | |
2 |<-------------------->| | | 2 |<-------------------->| | |
| | | | | | | |
| Asso Estb,Caps exchg | | | Asso Estb,Caps exchg | |
skipping to change at page 13, line 26 skipping to change at page 15, line 26
... ... ... ... ... ... ... ...
| Asso Estb,Caps exchg | | Asso Estb,Caps exchg |
3N|<------------------------------------------>| 3N|<------------------------------------------>|
| | | | | | | |
4 |<-------------------->| | | 4 |<-------------------->| | |
. . . . . . . .
4x|<-------------------->| | | 4x|<-------------------->| | |
| FAILURE | | | FAILURE | |
| | | | | | | |
| Event Report (CE#2 is new master) | | | Event Report (CE#2 is new master) | |
5 |--------------------->|----------->|------->| 5 |---------------------------------->|------->|
| | | | | | | |
| FEPO Failover Timeout | | | CEHDI Failover Timeout | |
| | | | | | | |
| Event Report (CE#N is new master) | | | Event Report (CE#N is new master) | |
6 |--------------------->|----------->|------->| 6 |---------------------------------->|------->|
| | | | | | | |
| Config (Set CEID to CEID of CE#N) | | Config (Set CEID to CEID of CE#N) |
7 |<-------------------------------------------| 7 |<-------------------------------------------|
8a|<------------------------------------------>| 8a|<------------------------------------------>|
. . . . . . . .
8x|<------------------------------------------>| 8x|<------------------------------------------>|
Figure 5: CE Failover for Hot Standby Figure 6: CE Failover for Hot Standby
If the FE does not get confirmation within the FEPO Failover Timeout, If the FE does not get confirmation within the CEHDI Failover
it picks the next CE on its list and advertises it as the new master. Timeout, it picks the next CE on its list and advertises it as the
Figure 5 illustrates in step #5 selecting CE#2 as its new master. In new master. Figure 6 illustrates in step #5 selecting CE#2 as its
step #6, the timeout occurs and it picks CE#N as its new master. The new master. In step #6, the timeout occurs and it picks CE#N as its
FE receives confirmation that CE#N is the new master in step #7. new master. The FE receives confirmation that CE#N is the new master
in step #7.
If the CE the FE assumed to be the master discovers that it should If the CE the FE assumed to be the master discovers that it should
not be the new master CE, then it will configure the CEID with the ID not be the new master CE, then it will configure the CEID with the ID
of the proper master CE. How the CE decides who the new master CE of the proper master CE. How the CE decides who the new master CE
is, is also out of scope of this document and is assumed to be done is, is also out of scope of this document and is assumed to be done
via a CE-CE communication protocol. The FE must then associate with via a CE-CE communication protocol. The FE must then associate with
then new CE. then new CE.
If the CEFTI timer expires at either the not-associated or confirm
states without a new master CE confirmed, then the FE MUST revert to
the pre-association stage.
In most High Availability architectures there exists the possibility In most High Availability architectures there exists the possibility
of split-brain. However, since in our setup the FE will never accept of split-brain. However, since in our setup the FE will never accept
any configuration messages from any other than the master CE, we any configuration messages from any other than the master CE, we
consider the FE as fenced against data corruption from the other CEs consider the FE as fenced against data corruption from the other CEs
that consider themselves as the master. The split-brain issue that consider themselves as the master. The split-brain issue
becomes mostly a CE-CE communication problem which is considered to becomes mostly a CE-CE communication problem which is considered to
be out of scope. be out of scope.
By virtue of having multiple CE connections, the FE switchover to a By virtue of having multiple CE connections, the FE switchover to a
new master CE will be relatively much faster. The overall effect is new master CE will be relatively much faster. The overall effect is
improving the NE recovery time in case of communication failure or improving the NE recovery time in case of communication failure or
faults of the master CE. This satisfies the requirement we set to faults of the master CE. This satisfies the requirement we set to
achieve. achieve.
For the sake of simplicity, the FE MUST respond to messages issued
only by the master CE. This simplifies the synchronization and
avoids the concept of locking FE state. The FE MUST drop any
messages from backup CEs. However, asynchronous events that the
master CE has subscribed to, as well as heartbeats are sent to all
associated-to CEs. Packet redirects continue to be sent only to the
master CE. The Heartbeat Interval, the CEHB Policy and the FEHB
Policy MUST be the same for all CEs.
5. IANA Considerations 5. IANA Considerations
TBA TBA
6. Security Considerations 6. Security Considerations
TBA TBA
7. References 7. References
skipping to change at page 22, line 4 skipping to change at page 23, line 45
</capability> </capability>
</capabilities> </capabilities>
<events baseID="61"> <events baseID="61">
<event eventID="1"> <event eventID="1">
<name>PrimaryCEDown</name> <name>PrimaryCEDown</name>
<synopsis> <synopsis>
The pimary CE has changed The pimary CE has changed
</synopsis> </synopsis>
<eventTarget> <eventTarget>
<eventField>LastCEID</eventField> <eventField>LastCEID</eventField>
</eventTarget> </eventTarget>
<eventChanged/> <eventChanged/>
<eventReports> <eventReports>
<eventReport> <eventReport>
<eventField>LastCEID</eventField> <eventField>LastCEID</eventField>
</eventReport> </eventReport>
</eventReports> </eventReports>
</event> </event>
<event eventID="2">
<name>HAPrimaryCEDown</name>
<synopsis>The primary CE has changed</synopsis>
<eventTarget>
<eventField>LastCEID</eventField>
</eventTarget>
<eventChanged/>
<eventReports>
<eventReport>
<eventField>CEID</eventField>
<eventField>LastCEID</eventField>
</eventReport>
</eventReports>
</event>
</events> </events>
</LFBClassDef> </LFBClassDef>
</LFBClassDefs> </LFBClassDefs>
</LFBLibrary> </LFBLibrary>
Authors' Addresses Authors' Addresses
Kentaro Ogawa Kentaro Ogawa
NTT Corporation NTT Corporation
3-9-11 Midori-cho 3-9-11 Midori-cho
 End of changes. 30 change blocks. 
65 lines changed or deleted 149 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/