idnits 2.17.1 draft-ietf-nsis-qos-requirements-01.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3583 5 Title: Requirements of a Quality of Service (QoS) 6 Solution for Mobile IP 7 Author(s): H. Chaskar, Ed. 8 Status: Informational 9 Date: September 2003 10 Mailbox: hemant.chaskar@nokia.com 11 Pages: 10 12 Characters: 22541 13 Updates/Obsoletes/SeeAlso: None 15 I-D Tag: draft-ietf-nsis-qos-requirements-01.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3583.txt 19 Mobile IP ensures correct routing of packets to a mobile node as the 20 mobile node changes its point of attachment to the 21 Internet. However, it is also required to provide proper Quality of 22 Service (QoS) forwarding treatment to the mobile node's packet stream 23 at the intermediate nodes in the network, so that QoS-sensitive IP 24 services can be supported over Mobile IP. This document describes 25 requirements for an IP QoS mechanism for its satisfactory operation 26 with Mobile IP. 28 This document is a product of the Next Steps in Signaling Working 29 Group of the IETF. 31 This memo provides information for the Internet community. It does 32 not specify an Internet standard of any kind. Distribution of this 33 memo is unlimited. 35 This announcement is sent to the IETF list and the RFC-DIST list. 36 Requests to be added to or deleted from the IETF distribution list 37 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 38 added to or deleted from the RFC-DIST distribution list should 39 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 41 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 42 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 43 help: ways_to_get_rfcs. For example: 45 To: rfc-info@RFC-EDITOR.ORG 46 Subject: getting rfcs 48 help: ways_to_get_rfcs 50 Requests for special distribution should be addressed to either the 51 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 52 specifically noted otherwise on the RFC itself, all RFCs are for 53 unlimited distribution.echo 54 Submissions for Requests for Comments should be sent to 55 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 56 Authors, for further information.