Re: [Softwires] More changes to revision 03. - Sent again in text

Ole Trøan <otroan@employees.org> Wed, 01 February 2012 14:01 UTC

Return-Path: <ichiroumakino@gmail.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 E125711E857A for <softwires@ietfa.amsl.com>; Wed, 1 Feb 2012 06:01:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.399
X-Spam-Level:
X-Spam-Status: No, score=-3.399 tagged_above=-999 required=5 tests=[AWL=-0.100, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
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 remTRfehyhI7 for <softwires@ietfa.amsl.com>; Wed, 1 Feb 2012 06:01:06 -0800 (PST)
Received: from mail-ww0-f42.google.com (mail-ww0-f42.google.com [74.125.82.42]) by ietfa.amsl.com (Postfix) with ESMTP id 200BD11E8577 for <softwires@ietf.org>; Wed, 1 Feb 2012 06:01:05 -0800 (PST)
Received: by wgbgn7 with SMTP id gn7so6151495wgb.1 for <softwires@ietf.org>; Wed, 01 Feb 2012 06:01:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=C2Hpo1EhSvez6Ivrpra/NPwyRD4HzW9hXJbgKEBjM/E=; b=e8L59AyrXpnm9mi+vW1TjwNPS/7glzg+5f9sFKDwJDCmAUCJHzQits2Ig8VlkhUdMd HAX+7e9alX9n5kA5ooDe3N0Ehy3be0jqCiawuuhUEwdzwMutcJCRw7pjSHpNuBSRqV56 Kt+IZBnbWFjyizJ5Z9JLohj0puykDSTnbhpO4=
Received: by 10.180.77.228 with SMTP id v4mr18991298wiw.2.1328104865271; Wed, 01 Feb 2012 06:01:05 -0800 (PST)
Received: from [10.147.13.29] (64-103-25-233.cisco.com. [64.103.25.233]) by mx.google.com with ESMTPS id n5sm73970063wiw.7.2012.02.01.06.01.03 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 01 Feb 2012 06:01:03 -0800 (PST)
Sender: Ole Troan <ichiroumakino@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=windows-1252
From: =?iso-8859-1?Q?Ole_Tr=F8an?= <otroan@employees.org>
In-Reply-To: <E1CE3E6E6D4E1C438B0ADC9FFFA345EA1FCACC06@SZXEML510-MBS.china.huawei.com>
Date: Wed, 1 Feb 2012 15:01:02 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <8617EB83-AD23-4B65-BD76-A817153ACE33@employees.org>
References: <067E6CE33034954AAC05C9EC85E2577C073C63F7@XMB-RCD-111.cisco.com> <E1CE3E6E6D4E1C438B0ADC9FFFA345EA1FCACC06@SZXEML510-MBS.china.huawei.com>
To: Leaf yeh <leaf.y.yeh@huawei.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: softwires WG <softwires@ietf.org>
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 14:01:07 -0000

Leaf,

> 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.

the current document specifies which parameters make up the rule. the only time a rule would be passed on the wire is for provisioning, it is explicitly defined in the DHCP option draft.

> BTW, more questions on the example of DMR in section 5.4,
> 
> <Quote> - {2001:db8:0001:0000:&lt;interface-id>:/128 (Rule IPv6 prefix),
> 0.0.0.0/0 (Rule IPv4 prefix),
> 192.0.2.1 (BR IPv4 address)}
> 
> Q1.  What does ‘&lt’ mean here?

XML artifact. '&lt' => less than => '<'

> Q2.  Does ‘interface-id>:/128’ sound a prefix here?

yes. MAP-T forwards traffic towards a "default prefix", while MAP-E sends to an address.

> 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.

if the Rule IPv4 prefix is used to indicate default route 0/0, then there is nothing to give the IPv4 prefix part. so the complete address is given as a parameter. this is to help implementations requiring that the next-hop is of the same address family as the route in the RIB. it will never make it onto the wire, so strictly speaking it isn't needed. useful for troubleshooting though, so that you can IPv4 ping your default router.

cheers,
Ole