A New Internet-Draft is available from the on-line Internet-Drafts directories.
Title : NSIS Flow ID and packet classification issues
Author(s) : H. Cheng, et al.
Filename : draft-cheng-nsis-flowid-issues-00.txt
Pages : 16
Date : 2005-5-13
In NSIS signaling the Flow ID is used for identifying the traffic
flows of an application session. Usually, it is derived from the
communication addresses information used in traffic classification
and filtering. Since the Flow ID is used for both signaling message
routing and signaling state management, its dependency on the address
information creates advert effects in certain scenarios. It also
limits the applicability of the NSIS signaling for handover
optimization in certain environment because of the lack of address
information. Therefore, Flow ID derivation and the packet
classification information should be separated in the NSIS design.
This document presented some detailed analysis of the problems faced
by the current Flow ID generation practice.
A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-cheng-nsis-flowid-issues-00.txt
To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.
Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
"get draft-cheng-nsis-flowid-issues-00.txt".
A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
Internet-Drafts can also be obtained by e-mail.
Send a message to:
mailserv@ietf.org.
In the body type:
"FILE /internet-drafts/draft-cheng-nsis-flowid-issues-00.txt".
NOTE: The mail server at ietf.org can return the document in
MIME-encoded form by using the "mpack" utility. To use this
feature, insert the command "ENCODING mime" before the "FILE"
command. To decode the response(s), you will need "munpack" or
a MIME-compliant mail reader. Different MIME-compliant mail readers
exhibit different behavior, especially when dealing with
"multipart" MIME messages (i.e. documents which have been split
up into multiple messages), so check your local documentation on
how to manipulate these messages.
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
- <ftp://ftp.ietf.org/internet-drafts/draft-cheng-nsis-flowid-issues-00.txt>
-
_______________________________________________
I-D-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/i-d-announce
