[MEXT] Comments to draft-tsirtsis-mext-binary-filters-00.txt

Yungui Wang <w52006@huawei.com> Thu, 18 June 2009 02:41 UTC

Return-Path: <w52006@huawei.com>
X-Original-To: mext@core3.amsl.com
Delivered-To: mext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 97F553A6BFC for <mext@core3.amsl.com>; Wed, 17 Jun 2009 19:41:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.092
X-Spam-Level:
X-Spam-Status: No, score=-0.092 tagged_above=-999 required=5 tests=[AWL=-1.282, BAYES_05=-1.11, MANGLED_SIDE=2.3]
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 yCjpC0tpD2bd for <mext@core3.amsl.com>; Wed, 17 Jun 2009 19:41:57 -0700 (PDT)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id B8B0A3A6820 for <mext@ietf.org>; Wed, 17 Jun 2009 19:41:57 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KLE0097KY67LP@szxga04-in.huawei.com> for mext@ietf.org; Thu, 18 Jun 2009 10:42:08 +0800 (CST)
Received: from huawei.com ([172.24.1.33]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KLE008C3Y673V@szxga04-in.huawei.com> for mext@ietf.org; Thu, 18 Jun 2009 10:42:07 +0800 (CST)
Received: from w52006d ([10.164.12.17]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KLE001AFY64AC@szxml06-in.huawei.com> for mext@ietf.org; Thu, 18 Jun 2009 10:42:07 +0800 (CST)
Date: Thu, 18 Jun 2009 10:42:04 +0800
From: Yungui Wang <w52006@huawei.com>
In-reply-to: <4A106574.8040107@it.uc3m.es>
To: 'mext' <mext@ietf.org>
Message-id: <000001c9efbe$5d43f810$110ca40a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset="us-ascii"
Content-transfer-encoding: 7bit
Thread-index: AcnXJcXbG7LY0xerTje1j/btjd0iGwA/92Tg
Subject: [MEXT] Comments to draft-tsirtsis-mext-binary-filters-00.txt
X-BeenThere: mext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: w52006@huawei.com
List-Id: Mobile IPv6 EXTensions WG <mext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mext>
List-Post: <mailto:mext@ietf.org>
List-Help: <mailto:mext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Jun 2009 02:41:58 -0000

Hello

1, Could the TLV/TV (type, length, value) format be used to encode
the paramters in the IPv4/IPv6 Flow Description sub-option?
Consideration: It may be not necessary to describe a flow which
includes all the parameters in the Flow Description sub-options.
At the same time, one parameter may appear multiple times in the
sub-option for a flow. For example, a flow may be presented as TCP
port 5000 and 5001.

2,  Could the Ethernet service flow description sub-option be also
introduced in this document? 
Consideration: The Ethernet service flow description sub-option is
senseful when Ethernet service is supported by MIP (referring to
http://www.ietf.org/internet-drafts/draft-wu-mip4-ether-02.txt ).
The format of the Ethernet serice flow description sub-option is:

- Ethernet serice flow description sub-option (TV format)
0x01   48bit,source MAC address
0x02   48bit,destination MAC address
0x03   16bit,ethernet type
0x04   16bit,vlan tag

- Ethernet serice flow description sub-option (proto header
format)

 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|S|D|E|V|       Reservered      |   (S) Source MAC Address      |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                    (S) Source MAC Address                     |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                 (D)Destination MAC Address                    |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|(D)Destination MAC Address     |   (E) Ethernet Type           |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|        (V) VLAN tag           |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


B.R.  
Yungui