90 likes | 260 Views
NEMO RO Problem Space. Prepared for 55 th IETF By Pascal Thubert (Cisco), Ng Chan Wah & Takeshi Tanaka (Panasonic) 20021120. CN. CR. HA1. HA2. Internet. HA-VMN. MR1. MR2. VMN. HA1: HA of MR1 HA2: HA of MR2 HA-VMN: HA of VMN CR: Correspondent Router. Routes in NEMO.
E N D
NEMO RO Problem Space Prepared for 55th IETF By Pascal Thubert (Cisco), Ng Chan Wah & Takeshi Tanaka (Panasonic) 20021120 55th IETF NEMO WG
CN CR HA1 HA2 Internet HA-VMN MR1 MR2 VMN HA1: HA of MR1 HA2: HA of MR2 HA-VMN: HA of VMN CR: Correspondent Router Routes in NEMO • Nesting Basic support of Nemo leads to: • Processing overhead at MR and HA • Packets delivery latency • Packet fragmentation • … 55th IETF NEMO WG
Types of RO for NEMO • The Route Optimization problem space can be split into 4 possible types: • RO for nested mobile network • RO with visiting mobile host • RO with correspondent node • RO within routing infrastructure 55th IETF NEMO WG
CN CR HA1 HA2 Internet HA-VMN MR1 MR2 VMN HA1: HA of MR1 HA2: HA of MR2 HA-VMN: HA of VMN CR: Correspondent Router RO for nested mobile network • Reduce the number of tunnels • Should impact only operations of MR and HA • Packets still experience ‘dog-leg’ routing 55th IETF NEMO WG
CN CR HA1 HA2 Internet HA-VMN MR1 MR2 VMN HA1: HA of MR1 HA2: HA of MR2 HA-VMN: HA of VMN CR: Correspondent Router RO with VMH • Visiting mobile hosts participates in NEMO RO • May further reduce the number of tunnels required • Impact the operations of VMH, MR, and HA 55th IETF NEMO WG
CN CR HA1 HA2 Internet HA-VMN MR1 MR2 VMN HA1: HA of MR1 HA2: HA of MR2 HA-VMN: HA of VMN CR: Correspondent Router RO with CN • Route Optimized between CN and MR/VMH • MIPv6 RR test between MR and CN is broken • May impact the operations of CN, in addition to VMH, MR and HA. 55th IETF NEMO WG
CN CR HA1 HA2 Internet HA-VMN MR1 MR2 VMN HA1: HA of MR1 HA2: HA of MR2 HA-VMN: HA of VMN CR: Correspondent Router RO within routing infrastructure • Route Optimized between Correspondent Router and MR/VMH • May impact the operations of VMH, MR and HA • Correspondent Node can be a plain IPv6 host 55th IETF NEMO WG
Conclusion • Basic is sufficient for limited applications • RO is wanted for nested configurations • RO is critical for large deployments 55th IETF NEMO WG
Nemo RO Drafts so far • Informational • draft-thubert-nemo-ro-taxonomy-00.txt • Solutions • draft-ng-nemo-access-router-option-00.txt • draft-thubert-nemo-reverse-routing-header-01.txt 55th IETF NEMO WG