IETF Logo Mail Archive

[Softwires] A General Question for Flow Label Usage

"Lee, Yiu" <Yiu_Lee@Cable.Comcast.com> Fri, 30 July 2010 20:07 UTC

Return-Path: <yiu_lee@cable.comcast.com>
X-Original-To: softwires@core3.amsl.com
Delivered-To: softwires@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4776E3A6B06 for <softwires@core3.amsl.com>; Fri, 30 Jul 2010 13:07:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.332
X-Spam-Level:
X-Spam-Status: No, score=0.332 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, RCVD_NUMERIC_HELO=2.067]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5nVDmJx19ZR6 for <softwires@core3.amsl.com>; Fri, 30 Jul 2010 13:07:50 -0700 (PDT)
Received: from cable.comcast.com (copdcimo01.potomac.co.ndcwest.comcast.net [76.96.32.251]) by core3.amsl.com (Postfix) with ESMTP id 4AE5E3A6B08 for <softwires@ietf.org>; Fri, 30 Jul 2010 13:07:50 -0700 (PDT)
Received: from ([147.191.124.13]) by copdcimo01.cable.comcast.com with ESMTP with TLS id 5503630.5310051; Fri, 30 Jul 2010 14:12:53 -0600
Received: from PAOAKEXCSMTP01.cable.comcast.com (10.52.116.30) by copdcexhub02.cable.comcast.com (147.191.124.13) with Microsoft SMTP Server id 14.0.702.0; Fri, 30 Jul 2010 14:08:12 -0600
Received: from PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) by PAOAKEXCSMTP01.cable.comcast.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 30 Jul 2010 16:08:08 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: from 87.213.214.66 ([87.213.214.66]) by PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) via Exchange Front-End Server legacywebmail.comcast.com ([24.40.8.153]) with Microsoft Exchange Server HTTP-DAV ; Fri, 30 Jul 2010 20:08:06 +0000
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="B_3363350885_3183605"; protocol="application/pkcs7-signature"; micalg="sha1"
Content-Class: urn:content-classes:message
Date: Fri, 30 Jul 2010 16:08:05 -0400
Message-ID: <C878A965.304BC%yiu_lee@cable.comcast.com>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
Thread-Topic: A General Question for Flow Label Usage
Thread-Index: AcswIuuawuYmAbp6fEaY3tg9LK6jTw==
From: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
To: softwires@ietf.org
X-OriginalArrivalTime: 30 Jul 2010 20:08:08.0009 (UTC) FILETIME=[ED65E390:01CB3022]
Subject: [Softwires] A General Question for Flow Label Usage
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jul 2010 20:07:51 -0000

Hi,

In RFC 3697, it says:

"A flow is a sequence of packets sent from a particular source to a
   particular unicast, anycast, or multicast destination that the source
   desires to label as a flow."

It later says the usage of a flow:

"The usage of the 3-tuple of the Flow Label and the Source and
   Destination Address fields enables efficient IPv6 flow
   classification, where only IPv6 main header fields in fixed positions
   are used."

I am confused why we can't use a flow label to effectively identify a flow
from a host behind a CPE in the AFTR. In what part this usage is against the
specification?

Thanks,
Yiu

v2.29.0 | Report a Bug | By Email | System Status