Re: [Softwires] More changes to revision 03. - Sent again in text
Leaf yeh <leaf.y.yeh@huawei.com> Wed, 01 February 2012 01:36 UTC
Return-Path: <leaf.y.yeh@huawei.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6582911E80B5 for <softwires@ietfa.amsl.com>; Tue, 31 Jan 2012 17:36:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.549
X-Spam-Level:
X-Spam-Status: No, score=-6.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 13WUa21R3Q3e for <softwires@ietfa.amsl.com>; Tue, 31 Jan 2012 17:36:30 -0800 (PST)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id 486DE11E809D for <softwires@ietf.org>; Tue, 31 Jan 2012 17:36:30 -0800 (PST)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LYO002NGXSRZK@szxga05-in.huawei.com> for softwires@ietf.org; Wed, 01 Feb 2012 09:36:27 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LYO00F71XSI00@szxga05-in.huawei.com> for softwires@ietf.org; Wed, 01 Feb 2012 09:36:27 +0800 (CST)
Received: from szxeml212-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA) with ESMTP id AGR28546; Wed, 01 Feb 2012 09:36:18 +0800
Received: from SZXEML403-HUB.china.huawei.com (10.82.67.35) by szxeml212-edg.china.huawei.com (172.24.2.181) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 01 Feb 2012 09:35:56 +0800
Received: from SZXEML510-MBS.china.huawei.com ([169.254.8.45]) by szxeml403-hub.china.huawei.com ([::1]) with mapi id 14.01.0323.003; Wed, 01 Feb 2012 09:36:08 +0800
Date: Wed, 01 Feb 2012 01:36:06 +0000
From: Leaf yeh <leaf.y.yeh@huawei.com>
X-Originating-IP: [10.70.39.113]
To: softwires WG <softwires@ietf.org>
Message-id: <E1CE3E6E6D4E1C438B0ADC9FFFA345EA1FCACC06@SZXEML510-MBS.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset="utf-8"
Content-language: zh-CN
Content-transfer-encoding: base64
Accept-Language: zh-CN, en-US
Thread-topic: [Softwires] More changes to revision 03. - Sent again in text
Thread-index: AQHM4IHpkImcNDpvvUqUUEK4En+SDA==
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
X-CFilter-Loop: Reflected
References: <067E6CE33034954AAC05C9EC85E2577C073C63F7@XMB-RCD-111.cisco.com>
Subject: Re: [Softwires] More changes to revision 03. - Sent again in text
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Wed, 01 Feb 2012 01:36:31 -0000
Rajiv - I would very much favor having a sharing ratio as a 'given' variable. Though Rajiv prefers 'sharing ratio' to 'EA-bit length', which is a little different from the text of section 5, I'd also like the draft could define an explicit format for the expression of the MAP rules including BMR, FMR & DMR. BTW, more questions on the example of DMR in section 5.4, <Quote> - {2001:db8:0001:0000:<interface-id>:/128 (Rule IPv6 prefix), 0.0.0.0/0 (Rule IPv4 prefix), 192.0.2.1 (BR IPv4 address)} Q1. What does ‘<’ mean here? Q2. Does ‘interface-id>:/128’ sound a prefix here? Q3. Is the BR IPv4 address (192.0.2.1) necessary here? There seems no IPv4 address in the BMR & FMR, but they also work well for the MAP forwarding function. Best Regards, Leaf -----Original Message----- From: Rajiv Asati (rajiva) [mailto:rajiva@cisco.com] Sent: Tuesday, January 31, 2012 6:26 AM To: Leaf yeh; Ole Trøan Cc: softwires WG; map-dt@external.cisco.com; fine_sz@huawei.com Subject: RE: [Softwires] More changes to revision 03. > C2. The sharing ratio sounds a calculated result, not a ‘given’ condition; I would very much favor having a sharing ratio as a 'given' variable, instead of a calculated result (and instead of EA-bit length, if needed be) since it is easier to understand, explain and work it out. In fact, most of the examples included in the document show the sharing-ratio being used as a given variable, so we just need to update the rules. Cheers, Rajiv > -----Original Message----- > From: softwires-bounces@ietf.org [mailto:softwires-bounces@ietf.org] On > Behalf Of Leaf yeh > Sent: Monday, January 30, 2012 6:38 AM > To: Ole Trøan > Cc: softwires WG; map-dt@external.cisco.com team; fine_sz@huawei.com > Subject: Re: [Softwires] More changes to revision 03. > > Ole - what's the difference? > > > > I suggested the following text for the readable . > > > > Given: > > End-user IPv6 prefix: 2001:db8:0012:34::/56 > > Basic Mapping Rule: {2001:db8:00::/40 (Rule IPv6 prefix), > > 192.0.2.0/24 (Rule IPv4 prefix), > > 16 (Rule EA-bits length)} > > PSID offset: 4 (default value as per section 5.1.3) > > > > We get the IPv4 address, its sharing ratio and port-set: > > > > EA bits offset: 40 > > IPv4 suffix bits (p): Length of IPv4 address (32) - IPv4 prefix length (24) = 8 > > IPv4 address: 192.0.2.18 (0x12) > > > > Sharing ratio: 256 (16 - (32 - 24) = 8. 2^8 = 256) > > > > > > Cheers, > > Leaf > > > > > > -----Original Message----- > > From: Ole Trøan [mailto:ot@cisco.com] > > Sent: Monday, January 30, 2012 6:16 PM > > To: Leaf yeh > > Cc: fine_sz@huawei.com; map-dt@external.cisco.com team > > Subject: Re: More changes to revision 03. > > > > Leaf, > > > > > Again C&Qs on the examples in the newly updated candidate of MAP-03: > > > > > > A. Section 5.2 - Given: > > > End-user IPv6 prefix: 2001:db8:0012:34::/56 > > > Basic Mapping Rule: {2001:db8:00::/40 (Rule IPv6 prefix), > > > 192.0.2.0/24 (Rule IPv4 prefix), > > > 16 (Rule EA-bits length)} > > > Sharing ratio: 256 (16 - (32 - 24) = 8. 2^8 = 256) > > > PSID offset: 4 > > > > > > We get IPv4 address and port-set: > > > EA bits offset: 40 > > > IPv4 suffix bits (p): Length of IPv4 address (32) - > > > IPv4 prefix length (24) = 8 > > > …. > > > > > > C1. The ‘End-user IPv6 prefix’ shall be express as ‘2001:db8:0012:3400::/56’ > as per the section 2.3 of RFC4291; > > > > fixed. > > > > > C2. The sharing ratio sounds a calculated result, not a ‘given’ condition; > > > > what's the difference? > > > > > > > > > > B. Section 5.3 - Given: > > > IPv4 destination address: 192.0.2.18 > > > IPv4 destination port: 9030 > > > Forwarding Mapping Rule: {2001:db8:00::/40 (Rule IPv6 prefix), > > > 192.0.2.0/24 (Rule IPv4 prefix), > > > 16 (Rule EA-bits length)} > > > > > > We get IPv6 address: > > > IPv4 suffix bits (p): 32 - 24 = 8 (18 (0x12)) > > > PSID length: 8 > > > PSID: 0x34 (9030 (0x2346)) > > > EA bits: 0x1234 > > > MAP IPv6 address: 2001:db8:0012:3400:00c0:0002:1200:3400 > > > > > > C3. I suppose the default ‘PSID offset: 4’ seems need to express in the ‘given’ > conditions; > > > > OK > > > > > Q1. Have the draft stated the ‘u’ bits in the Interface-ID should be 0x00? > > > > it states that it is based on 6052. I think that should be sufficient. > > > > cheers, > > Ole > > > >
- Re: [Softwires] More changes to revision 03. Ole Trøan
- Re: [Softwires] More changes to revision 03. Leaf yeh
- Re: [Softwires] More changes to revision 03. Rajiv Asati (rajiva)
- Re: [Softwires] More changes to revision 03. - Se… Leaf yeh
- Re: [Softwires] More changes to revision 03. - Se… Ole Trøan