RFC 3583 on Requirements of a Quality of Service (QoS) Solution for Mobile IP
rfc-editor@rfc-editor.org Wed, 03 September 2003 23:32 UTC
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16689 for <ietf-announce-web-archive@odin.ietf.org>; Wed, 3 Sep 2003 19:32:15 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14) id 19uh06-0002Vp-Fw for ietf-announce-list@asgard.ietf.org; Wed, 03 Sep 2003 19:25:22 -0400
Received: from ietf.org ([10.27.2.28]) by asgard.ietf.org with esmtp (Exim 4.14) id 19ugz9-0002SY-C1 for all-ietf@asgard.ietf.org; Wed, 03 Sep 2003 19:24:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16239; Wed, 3 Sep 2003 19:24:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ugz7-000546-00; Wed, 03 Sep 2003 19:24:21 -0400
Received: from gamma.isi.edu ([128.9.144.145]) by ietf-mx with esmtp (Exim 4.12) id 19ugz6-000543-00; Wed, 03 Sep 2003 19:24:20 -0400
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6p2/8.11.2) with ESMTP id h83NOLN05960; Wed, 3 Sep 2003 16:24:21 -0700 (PDT)
Message-Id: <200309032324.h83NOLN05960@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3583 on Requirements of a Quality of Service (QoS) Solution for Mobile IP
Cc: rfc-editor@rfc-editor.org, nsis@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 03 Sep 2003 16:24:20 -0700
Sender: owner-ietf-announce@ietf.org
Precedence: bulk
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. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.