Intra-NE Routing Mechanism
draft-guo-forces-routing-01.txt
Xiaoyi Guo([email protected])
64th IETF Meeting, Vancouver
Forwarding mechanism
Motivation
• One NE may include many CEs and FEs, one of
the forwarding path may cross many FEs ,not
cross only one FE.
• FEs should not know all the topology of the NE,
so the routing table in FEs should not include all
the NE routing information.
Forwarding mechanism
2 routing tables in CE --
Edge FE
CE
Intra-FE
FE1
RT
Edge FE
FE3
Intra-NE
RT
FE2
Forwarding mechanism
Data forwarding
• ----- Edge FE ----FE ---Edge FE --
• ( RT )
( Intra-NE RT ) ( RT )
• We focus on Intra-NE forwarding mechanism
Forwarding mechanism
Routing table construction:
• CE side:
SPF algorithm
Full topology --------- Intra-NE Routing Table
routing protocols
Routing information ----normal Routing table
• FE side :
CE send RT to each FE , not the full routing table
Next ..
•Consideration about the security?
•Could one hop forwarding use this mechanism ?
•Need the new LFBs construction?
•More details of this mechanism need to
considering and working out ….
Other questions?
Interested in this work?
Please send your comments to me and
ForCES mailing list.