Re: [Softwires] I-D Action: draft-ietf-softwire-lw4over6-06.txt

"Yuchi Chen" <chenycmx@gmail.com> Thu, 06 March 2014 08:00 UTC

Return-Path: <chenycmx@gmail.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4A4E1A012F for <softwires@ietfa.amsl.com>; Thu, 6 Mar 2014 00:00:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 oTUw0Mr5QSpW for <softwires@ietfa.amsl.com>; Thu, 6 Mar 2014 00:00:16 -0800 (PST)
Received: from mail-pd0-x232.google.com (mail-pd0-x232.google.com [IPv6:2607:f8b0:400e:c02::232]) by ietfa.amsl.com (Postfix) with ESMTP id 9818E1A0121 for <softwires@ietf.org>; Thu, 6 Mar 2014 00:00:16 -0800 (PST)
Received: by mail-pd0-f178.google.com with SMTP id x10so2219463pdj.9 for <softwires@ietf.org>; Thu, 06 Mar 2014 00:00:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:reply-to:subject:references:mime-version:message-id :content-type:content-transfer-encoding; bh=+m/v+QPa0kvnDtlwyMBf+rkox9SH6jhOYuzC/I51DhY=; b=MEzs+j+Hg1/1P+N98zW6D/TJLkWJDm1MaWqP/5DBQAASpxtxziEIdqK5CXgwiO6Ysp r+R26W1w0qPaJTpm3YZG9AfHPgDo1qaIHczw3kDwI59AWT5ixb7e85dJf9YCjAnpT35K YXXN8ynp6SIH4pzH02Miiyu6U1McF8GXE6jIRugjepB7HKTSw2cw5wOP/K/igy95AeM1 2SuaGy5k0Hz6MCcs48w2wcytp0dyrLv6TzHPE/F7zwijfbGq79kK48pprbYH2Zc6sDw2 Xzgo0iM6eAmfLArJibnmxaDBX5G/G+OHN4O6bNbSOJC2HgxzSypJ/m+/7kTHB5jDPDXR YQcA==
X-Received: by 10.69.25.69 with SMTP id io5mr12830250pbd.22.1394092812917; Thu, 06 Mar 2014 00:00:12 -0800 (PST)
Received: from netlab-PC ([59.64.255.198]) by mx.google.com with ESMTPSA id pp5sm16734769pbb.33.2014.03.06.00.00.03 for <multiple recipients> (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 06 Mar 2014 00:00:11 -0800 (PST)
Date: Thu, 06 Mar 2014 16:00:04 +0800
From: Yuchi Chen <chenycmx@gmail.com>
To: Ole Troan <otroan@employees.org>, Ian Farrer <ianfarrer@gmx.com>
References: <20140211075445.17615.61208.idtracker@ietfa.amsl.com> <FD878467-904B-4441-95B4-11D4461A612E@employees.org> <CF237FDE.AACEB%ian.farrer@telekom.de> <CAFFjW4jOBfvnqCV4UH8qt0HA5zZ-35f+q5ZepzjnwGX5_Oj9Gg@mail.gmail.com> <8A1B81989BCFAE44A22B2B86BF2B76318A2CDB8ED2@HE111643.EMEA1.CDS.T-INTERNAL.COM> <CAFFjW4iP2KqNJFtJPr5rp0tzRwM5TPjaqiSP5r13JqbX46ao7w@mail.gmail.com> <CD1D4FF6-9509-43B4-AFC4-4F1AF99D0C4D@gmx.com> <CAFFjW4ibkj_xpTuXrbYjxkdxD=+qNzapCGPHJwXsZ-k0ZvGg-g@mail.gmail.com> <CF335888.AE89D%ian.farrer@telekom.de> <CAFFjW4hv5WBiqyw9jM+ZoLMGR5k49pjKXG0epnhrsOGoBBKMYA@mail.gmail.com> <78CE37BA-11FB-4AE4-9D49-A3053616A31A@gmx.com> <53173611.5070208@viagenie.ca> <4255E91E-B1F0-4FE0-9A86-171922C7BC43@gmx.com> <6BE4C1C1-17D6-44B6-A9FC-F270D29AA0B0@employees.org> <F946C230-B91C-4463-823B-C3FB3B0577F2@gmx.com>, <98DA6B17-C07E-40B8-AABE-8A4D0D5F687A@employees.org>
X-Priority: 3
X-GUID: 3A3E63C7-C0CB-4661-AEC3-476C16FB6F78
X-Has-Attach: no
X-Mailer: Foxmail 7.0.1.92[cn]
Mime-Version: 1.0
Message-ID: <2014030615595650398421@gmail.com>
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/tIuAKSbAs3lxNJKkt7hZ3Z6q1Ek
Cc: softwires WG <softwires@ietf.org>
Subject: Re: [Softwires] I-D Action: draft-ietf-softwire-lw4over6-06.txt
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: chenycmx <chenycmx@gmail.com>
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: Thu, 06 Mar 2014 08:00:18 -0000

Hi Ole,

IMHO doing LPM with the lwAFTR's address is more straightforward than with a "Domain v6 prefix".

In addition, I don't see why Ian's proposal cannot cover the case you mentioned, the case in which an address out of the prefix domain can be chosen as the tunnel endpoint address. If lwB4 has been provisioned with such an address, and if this address does have a LPM with lwAFTR's address, lwB4 can still use it as the tunnel endpoint address. Please correct me if I'm missing anything.

Regards,
--------------
Yuchi

On 2014-03-06, 01:51, "Ole Troan" <otroan@employees.org> wrote:
>Ian,
>
>>>> No. As long as you know what particular mechanism you B4 vendor has implemented, you can provision accordingly.
>>>> 
>>>> The lwAFTR never has to do the LPM. It’s just got a tunnel endpoint address configured by the operator.
>>> 
>>> I'm not comfortable with that.
>> 
>> [ian] Why aren’t you comfortable with it?
>
>I thought that was obvious.
>- it reinvents the wheel
>- and it reinvents a wheel that is less round than the one already invented.
>
>is there any reason why you cannot use the existing wheel?
>or feel free to invent a better one, and we can adopt that for MAP.
>
>cheers,
>Ole
>
>
>> 
>>> 
>>> is there any reason why you couldn't do it as MAP does?
>>> 
>>> - include a "Domain IPv6 prefix" in the set of provisioning parameters.
>>> - the client does a longest match between the Domain IPv6 prefix and the End-user IPv6 prefixes
>>> and uses that to create the tunnel end point address.
>>> 
>>> that also allows the operator to use either the WAN side /64 or an address out of the PD as the tunnel endpoint address.
>>> 
>>> cheers,
>>> Ole
>
>