1 / 11

by Ram Gopal, Alex Audu, Chaoping Wu, Hormuzd Khosravi

Forwarding and Control Element Protocol (FACT). by Ram Gopal, Alex Audu, Chaoping Wu, Hormuzd Khosravi. <draft-gopal-forces-fact-03.txt>. Protocol Overview. Protocol to support communication between CE and FE in a distributed fault-tolerant architecture.

robertjheath
Download Presentation

by Ram Gopal, Alex Audu, Chaoping Wu, Hormuzd Khosravi

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Forwarding and Control Element Protocol (FACT) by Ram Gopal, Alex Audu, Chaoping Wu, Hormuzd Khosravi <draft-gopal-forces-fact-03.txt>

  2. Protocol Overview • Protocol to support communication between CE and FEin a distributed fault-tolerant architecture. • Master/Slave relationship between CE-FE. • Logical separation by means of providing base protocol and service functions. • Service specific functions can be encoded using TLV, OID or XML. • Transport/Interconnect independence • Supports latest ForCES Requirements draft.

  3. CE-SET ACTIVE CE-1 INACTIVE CE-2 associations ACTIVE FE-1 ACTIVE FE-2 INACTIVE FE-3 FACT – NE model

  4. Version Message Class Message Type P Length CE-Tag FE-ID Transaction Sequence Number (TSN) Payload Message Structure

  5. Message Class and Messages (1) • Association Establishment • To establish logical connection between CE and FE • Join, Leave message etc • Capabilities Exchange & Configuration • To exchange FE’s capabilities and to configure FE’s functions. • Capability request, Configure FE Blocks, Topology request etc • State Maintenance • To track element states and report state changes. • Heart-beat, PE UP, PE Down, PE Active and Inactive etc

  6. Message Class and Messages (2) • Traffic Maintenance • To control data and control traffic between CE and FE. • Packet Redirection, Control packet forwarding etc. • Event Notification • Asynchronous status change notification by FE to CE. • Event Register, Deregister, Notification message,etc.. • Vendor Specific • To extend the protocol beyond its current capabilities.

  7. Association Phase FE CE Join Request 1 Validation of FE endpoint Join Response 2 Capability Request 3 FE Block addressing, handles and relationship Capability Response 4 Topology Request 5 Topology Response 6 Configure FE Block 7 FE Block configuration Configuration Acknowledgement 8 PE UP 9 PE UP acknowledgement 10 State Maintenance (Element State) PE (FE) ACTIVE 11 PE ACTIVE acknowledgement 12

  8. Element State ACTIVE Alternate CE/FE active CE/FE active CE/FE inactive INACTIVE CE/FE down CE-FE communication failure CE/FE down CE-FE communication failure CE/FE UP DOWN

  9. Normal Operation FE CE Heart beat request 1 Heart beat response 2 Query Request 3 Query Response 4 Port Event Notification 5 Port Event Notification Ack 6 Configure Logical Components (Modify) 7 Configure Logical Components ACK 8 Control packet redirect 9 Control packet redirect ACK 10

  10. Other features • Two-phase transaction support • Command bundling • High availability support • Security • Configured as part of FE-Manager and CE-Manager • Re-keying leveraged to Security protocols. • Security for shared network similar to OSPFv3

  11. Questions

More Related