NSIS Flow ID and packet classification issues

1
NSIS Flow ID andpacket classification issues
ltdraft-cheng-nsis-flowid-issues-01.txtgt
Hong Cheng, Qijie Huang, Takako Sanda, Toyoki
Ue IETF63 August, 2005
2
Motivation Goal

• Motivation
• Generating packet classifier from MRI may not
  be able to function properly
• Off path case
• Multiple address case (including aggregation,
  tunneling)
• Address variation case
• Goal
• Have separate Filter info element (Filter List)
  and Routing info element (MRI), in order to
• Support off path signaling
• Support sharing QoS resources among multiple
  flows
• Optimize NSIS signaling
• Reduce signaling overhead
• Filter List A list of Filter Spec

3
Off Path Signaling

• In off-path case, packet classifier needs to be
  different from MRI.
• Signaling route is different from data route
• NI/NR may be different from sender/receiver of
  the data packets
• Filter List supports
• Carrying packet classification information
  separately
• MRI is for routing/managing signaling messages

4
Sharing QoS resources among multiple flows

• QoS resource sometimes needs to be shared between
  multiple flows
• When predictive path is installed (such as
  mobility case), sharing QoS resource is
  necessary at overlapped section between current
  path and predictive path
• In aggregation or tunnel cases, QoS resources
  also need to be shared among different flows
• Filter List supports
• ADD a new packet classification information
  (like Filter Spec) into the list
• Share QoS resources

5
Optimize NSIS Signaling

• In Multiple Address case (e.g. multiple ports are
  used for one session) and in address variation
  case (e.g. ports changing during session),
  sending signaling for multiple times is required
• Signaling routes are the same -gt sending multiple
  signaling will be overhead
• To support signaling aggregation -gt different
  bindings are needed (Session binding or Flow
  binding), it is overhead
• Filter List supports
• Carrying multiple address information (i.e.
  Packet Classifier)
• For MRI, one of multiple address can be employed

Filter List filter1 (Port1), filter2 (Port2)
Port 1Port 2
Session 1
Server
MRI Flow ID 1 (Port1)
Terminal
6
Considerations

• NAT traversal
• In NAT, Filter List as well as MRI has to be
  changed according to the policy rule
• Where the Filter List should be placed?
• GIMPS Layer?
• Common NSLP Layer?