Middlebox Signaling in a NSIS framework
draft-brunner-nsis-mbox-fmwk-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Marcus Brunner , Martin Stiemerling | ||
Last updated | 2002-06-27 | ||
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
The Next Steps in Signaling (NSIS) working group has started looking into signaling for QoS in various cases. In this draft, we show the similarities and differences of signaling for QoS versus signaling for NAT and firewall traversal. It seams that there are quite a number of similarities, which might make sense to use a potential NSIS protocol for NAT and firewall traversal as well.
Authors
Marcus Brunner
Martin Stiemerling
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)