Requirements of a Quality of Service (QoS) Solution for Mobile IP
draft-ietf-nsis-qos-requirements-01

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3583.
Author Hemant Chaskar
Last updated 2013-03-02 (Latest revision 2003-06-18)
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Informational
Formats
txt htmlized bibtex bibxml
Additional resources Mailing list discussion
Stream WG state (None)
Document shepherd (None)
IESG IESG state Became RFC 3583 (Informational)
Action Holders
(None)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Allison J. Mankin
IESG note
Send notices to <john.loughney@nokia.com>
Email authors Email WG IPR References Referenced by Nits Search email archive
draft-ietf-nsis-qos-requirements-01 
A new Request for Comments is now available in online RFC libraries.

        RFC 3583

        Title:      Requirements of a Quality of Service (QoS)
                    Solution for Mobile IP
        Author(s):  H. Chaskar, Ed.
        Status:     Informational
        Date:       September 2003
        Mailbox:    hemant.chaskar@nokia.com
        Pages:      10
        Characters: 22541
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-nsis-qos-requirements-01.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3583.txt

Mobile IP ensures correct routing of packets to a mobile node as the
mobile node changes its point of attachment to the
Internet.  However, it is also required to provide proper Quality of
Service (QoS) forwarding treatment to the mobile node's packet stream
at the intermediate nodes in the network, so that QoS-sensitive IP
services can be supported over Mobile IP.  This document describes
requirements for an IP QoS mechanism for its satisfactory operation
with Mobile IP.

This document is a product of the Next Steps in Signaling Working
Group of the IETF.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.