[Idr] Regarding encoding examples from draft-ietf-idr-flow-spec-v6-07

Zhuangshunwan <zhuangshunwan@huawei.com> Fri, 20 January 2017 09:16 UTC

Return-Path: <zhuangshunwan@huawei.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC444129ABF for <idr@ietfa.amsl.com>; Fri, 20 Jan 2017 01:16:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.419
X-Spam-Level:
X-Spam-Status: No, score=-7.419 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.199, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H8bgn8M_bJ5p for <idr@ietfa.amsl.com>; Fri, 20 Jan 2017 01:16:28 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6CBF3129408 for <idr@ietf.org>; Fri, 20 Jan 2017 01:16:27 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml706-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CZE21643; Fri, 20 Jan 2017 09:16:23 +0000 (GMT)
Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by lhreml706-cah.china.huawei.com (10.201.5.182) with Microsoft SMTP Server (TLS) id 14.3.301.0; Fri, 20 Jan 2017 09:16:22 +0000
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml411-hub.china.huawei.com ([10.98.56.70]) with mapi id 14.03.0235.001; Fri, 20 Jan 2017 17:16:11 +0800
From: Zhuangshunwan <zhuangshunwan@huawei.com>
To: "idr@ietf.org" <idr@ietf.org>
Thread-Topic: Regarding encoding examples from draft-ietf-idr-flow-spec-v6-07
Thread-Index: AdJy/dXJyloMBDxrS82oXMQyTXl0Hg==
Date: Fri, 20 Jan 2017 09:16:47 +0000
Message-ID: <19AB2A007F56DB4E8257F949A2FB9858C883017C@NKGEML515-MBX.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.86.254]
Content-Type: multipart/alternative; boundary="_000_19AB2A007F56DB4E8257F949A2FB9858C883017CNKGEML515MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020201.5881D567.02E2, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 8504ed7f750a29f93e540d494d6ce296
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/7zkDDlZOnvZp_NKixTSRSVFuTUY>
Subject: [Idr] Regarding encoding examples from draft-ietf-idr-flow-spec-v6-07
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jan 2017 09:16:30 -0000

Hi Authors and WG,

I have some confusion and hope to get your help.

The following examples come from draft-ietf-idr-flow-spec-v6-07:
"
   The following example demonstrates the new prefix encoding for: "all
   packets to ::1234:5678:9A00:0/64-104 from 192::/8 and port {range
   [137, 139] or 8080}".  In the destination prefix, "80-" represents
   the prefix offset of 80 bits.  In this exmaple, the 0 offset is
   omitted from the printed source prefix.

    +---------------------------+-------------+-------------------------+
    | destination               | source      | port                    |
    +---------------------------+-------------+-------------------------+
    | 0x01 68 50 12 34 56 78 9A | 02 00 08 c0 | 04 03 89 45 8b 91 1f 90 |
    +---------------------------+-------------+-------------------------+
"
I have two questions:

1)  For destination filter example, the given offset value is 0x50, should

it be 0x40 ?



2)  For source filter example, per my understanding, the prefix length value

is 0x08, the offset value is 0x00, so the source filter should be encoded

as 0x02 08 00 C0, not 0x02 00 08 c0 ?




Thanks,

Shunwan