Problems Analysis of NSIS Aggregation Teardown Signaling in Mobility Scenarios
draft-marwaha-nsis-aggregation-teardown-signaling-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Shivanajay Marwaha | ||
| Last updated | 2006-10-18 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
If a Mobile Node communicates with different Corresponding Nodes and there exists a common path for these sessions, NSIS allows these reservations to be aggregated. However, change of aggregation path caused by mobility event creates problems related to the prompt removal of the old aggregation state in case Correspondent Nodes are NSIS Initiators, i.e. multiple Correspondent Nodes will send multiple teardown messages for tearing down the same unused aggregated section and may cause problems of extra signaling overhead, delay in tearing down, reliability, redundancy and extra processing overhead. This draft presents the analysis of these problems.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)