Brian,

>It still isn't clear to me what the flow label adds to the semantics
>used by existing 5-tuple QOS classifiers.

First go look at RSVP.  Thats one.  In our RSVP implementation apps can
set the flowid and then get reserved resources along the path for audio
or video or even more mundane things like file transfer for mission
critical apps like downloading coordinates to a military operation.

Respond to Itojun's mail it says it all.  The bottom line is the
client or a server can set the flowlabel and with the address none of
those other tuples are needed and it can also be useful when IPsec is
being used to identify connections at a server that has a front end
router parsing connections for a large MP machine as another example and
get us away from monolithic TCP/IP processing.

Itojuns mail attached.  Also look at Itojuns draft.

regards,
/jim


Return-Path: [EMAIL PROTECTED]
Received: from oflume.zk3.dec.com by sigma.zk3.dec.com (8.8.8/1.1.20.3/24Apr98-0811AM)
        id RAA0000014230; Sat, 25 Nov 2000 17:00:41 -0500 (EST)
Received: from ztxmail01.ztx.compaq.com by oflume.zk3.dec.com 
(8.8.8/1.1.22.3/03Mar00-0551AM)
        id RAA0000028683; Sat, 25 Nov 2000 17:00:14 -0500 (EST)
Received: by ztxmail01.ztx.compaq.com (Postfix, from userid 12345)
        id 2521523C9; Sat, 25 Nov 2000 16:00:14 -0600 (CST)
Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97])
        by ztxmail01.ztx.compaq.com (Postfix) with ESMTP id 03A592091
        for <[EMAIL PROTECTED]>; Sat, 25 Nov 2000 16:00:12 -0600 (CST)
Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1])
        by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id HAA12506;
        Sun, 26 Nov 2000 07:00:05 +0900 (JST)
To: Brian E Carpenter <[EMAIL PROTECTED]>
Cc: Jim Bound <[EMAIL PROTECTED]>, "Ipng (E-Mail)" <[EMAIL PROTECTED]>
In-reply-to: brian's message of Sat, 25 Nov 2000 12:55:14 CST.
      <[EMAIL PROTECTED]>
X-Template-Reply-To: [EMAIL PROTECTED]
X-Template-Return-Receipt-To: [EMAIL PROTECTED]
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD  90 5F B4 60 79 54 16 E2
Subject: Re: Usage of IPv6 flow label
From: [EMAIL PROTECTED]
Date: Sun, 26 Nov 2000 07:00:05 +0900
Message-ID: <[EMAIL PROTECTED]>
Sender: [EMAIL PROTECTED]

>It still isn't clear to me what the flow label adds to the semantics
>used by existing 5-tuple QOS classifiers.

        just checking, here by "5-tuple" you meant:
        - IP address pair (src/dst)
        - layer 4 port number pair (src/dst)
        - protocol type
        is it correct?

        except for IP address, they may be embedded into ESP, or may be buried
        in IP header chain.  so for efficient router operation we need to
        use flow label, which will effectively give us the following 3 items
        (depending on the definition of "flow"):
        - layer 4 port number pair
        - protocol type
        see RFC2205 page 9.
        i believe this (availability of flow label field) is one of important
        value-adds of IPv6 against IPv4.

itojun
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page:                      http://playground.sun.com/ipng
FTP archive:                      ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------

Reply via email to