Hemant,
I see these are two possible areas that QOS needs to be addressed with respect to Reverse tunneling.
1. With reverse tunneling an end-to-end QOS Path setup is not applicable to the Mobile since its identity in the IP packet is lost (because of ip-in-ip encapsulation) in the foreign network. So QOS setup needs to be aware of the fact that the Mobile Node is using reverse tunneling.
2. Another scenario is Mobile Node is handing off from an FA(which is not supporting reverse tunneling and an end-to-end QOS path is setup for MN's packet stream) to an FA which supports the reverse tunneling. The QOS mechanism should be aware and support this scenario and vice-versa.
Rambabu Tummala
Nortel Networks
ESN 444-8970
External (972)684-8970
-----Original Message-----
From: Hemant.Chaskar@nokia.com [mailto:Hemant.Chaskar@nokia.com]
Sent: Wednesday, April 18, 2001 4:41 PM
To: mip-qos@research.nokia.com
Subject: RE: [MIP-QOS] MIP-QOS Requirements
Could you elaborate little more on what exactly is the issue with reverse
tunneling as regards QoS.
-----Original Message-----
From: ext Rambabu Tummala [mailto:tummala@nortelnetworks.com]
Sent: 18. April 2001 17:36
To: mip-qos@research.nokia.com
Subject: [MIP-QOS] MIP-QOS Requirements
I would like add this as a requirement.
* The scope of any solution should take RFC 3024 - Reverse Tunneling for
Mobile IP into consideration.
Regards,
Rambabu Tummala
Nortel Networks
ESN 444-8970
External (972)684-8970