The limitation in current NEMO scenario -Problem Statement

1
The limitation in current NEMO scenario -Problem
Statement

• draft-zhao-nemo-limitations-ps-00.txt
• John.zhao(Huawei technology shanghai RD)
• Ke lin (Shanghai jiao tong university)
• Wen tao zhong (Shanghai jiao tong university)
• 2007-12-01

2
Index

• Problems and solutions
• MR loop
• Entry point selection
• PMIP related
• Conclusions and suggestion
• Future plan
• Next step
• References

3
Problem 1 ---- MR loop
Problem The MR may establish the route loop each
other. Suggestion We need to distinguish the MR.
4
Problem 2 ---- entry point selection
Problem The mobile entities(MR or MN) need to
select a more stable entry point as the selection
to visit the internet. Suggestion Let the mobile
learn some more information about the upper level
router.
5
Scenarios of PMIP related
?
LMA/HA needs the binding info for the LFNs
prefix as the following MRID??MRs HoA??MRs
CoA??LFNs Prefix

• The network is PMIPv6 enabled. (MIPv4 is similar)
• MR bootstrapping in this PMIPv6 network.
• MR didnt run the NEMO protocol(RFC3963) and
  network use PMIP to management its mobility.
• We use the root MR as the example, and others is
  similar.But if nested MR occurred, RO is
  suggested to promote the efficiency.

6
Problems and requirements of PMIP related

• 1)How to forward the packets destinated to the
  nodes under the MR?
• MAG send the PBU included with the LFNs prefix
  to LMA/HA.
• 2)Where to find the LFNs prefix of that MR?
• Policy server
• Getting it/them from that MR
• 3)When does the MAG send the PBU?
• When the MR enter into the PMIPv6 domain.
• 4)How does the MAG know this is a MR but not a
  MN?
• Policy server
• Getting it/them from that MR

7
solution
PBU(with LFNs prefix)
MR ID CoA HoA LFNs prefix
Really? I need help you binding your LFNs prefix
in LMA/HA.
This is a MR (Optional includeing with the LFNs
prefix)
8
Conclusions and suggestion

• Conclusions
• Mobile router is difference to mobile node in
  pmip scenario and need to be learnt by pmip
  domain
• If can mobile router know each other and the
  distinguish with those fixed routers, it maybe
  useful for the best route path selection and the
  access to the internet.
• Suggestion
• We suggest that we can extend current router
  discovery messages to achieve these goals.

9
Next step

• Agree to these problems?
• Agree to these solutions?
• We need to provide this details as above?
• If true, if this draft can be accepted in mext?
• Other suggestions?