IETF Logo Mail Archive

Re: [Idr] Using BGP to advertise SD-WAN tunnels end point's private IPv6 addresses. (was registering tunnel types

Linda Dunbar <linda.dunbar@huawei.com> Mon, 05 November 2018 16:23 UTC

Return-Path: <linda.dunbar@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 EF890130F1F; Mon, 5 Nov 2018 08:23:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 7rXEYueq6ezQ; Mon, 5 Nov 2018 08:23:22 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2881A130E7D; Mon, 5 Nov 2018 08:23:22 -0800 (PST)
Received: from lhreml701-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 99F799B2EA70A; Mon, 5 Nov 2018 16:23:18 +0000 (GMT)
Received: from SJCEML702-CHM.china.huawei.com (10.208.112.38) by lhreml701-cah.china.huawei.com (10.201.108.42) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 5 Nov 2018 16:23:20 +0000
Received: from SJCEML521-MBS.china.huawei.com ([169.254.2.103]) by SJCEML702-CHM.china.huawei.com ([169.254.4.237]) with mapi id 14.03.0415.000; Mon, 5 Nov 2018 08:23:16 -0800
From: Linda Dunbar <linda.dunbar@huawei.com>
To: "Henderickx, Wim (Nokia - BE/Antwerp)" <wim.henderickx@nokia.com>, Fred Baker <fredbaker.ietf@gmail.com>
CC: "idr@ietf.org" <idr@ietf.org>, "int-area@ietf.org" <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Thread-Topic: [Idr] Using BGP to advertise SD-WAN tunnels end point's private IPv6 addresses. (was registering tunnel types
Thread-Index: AQHUdP39JxtZsSK87kCi+BjaMuwg9KVBUglA
Date: Mon, 05 Nov 2018 16:23:16 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F66B182E67@sjceml521-mbs.china.huawei.com>
References: <4A95BA014132FF49AE685FAB4B9F17F66B18249E@sjceml521-mbs.china.huawei.com> <6E397847-407E-4F69-AD31-E87D0001F603@gmail.com> <4A95BA014132FF49AE685FAB4B9F17F66B182B93@sjceml521-mbs.china.huawei.com> <A55564ED-B913-437C-8442-DA5962F2BEC3@gmail.com> <DA03CDE7-539B-4DAB-A68D-07C2ABD3A066@nokia.com>
In-Reply-To: <DA03CDE7-539B-4DAB-A68D-07C2ABD3A066@nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.126.173.228]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/Gt0vtr3GBu3rW4K4bcUNB_4HEww>
Subject: Re: [Idr] Using BGP to advertise SD-WAN tunnels end point's private IPv6 addresses. (was registering tunnel types
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 05 Nov 2018 16:23:30 -0000

So we need to add another type to the subTLV: Mapping (for the scenario of CPE using IPv6, being translated to IPv4 to connect to its peer that uses IPv4, correct?

Linda

-----Original Message-----
From: Henderickx, Wim (Nokia - BE/Antwerp) [mailto:wim.henderickx@nokia.com] 
Sent: Monday, November 05, 2018 6:52 PM
To: Fred Baker <fredbaker.ietf@gmail.com>; Linda Dunbar <linda.dunbar@huawei.com>
Cc: idr@ietf.org; int-area@ietf.org; ipv6@ietf.org
Subject: Re: [Idr] Using BGP to advertise SD-WAN tunnels end point's private IPv6 addresses. (was registering tunnel types

In SD-WAN ctxt, to let a site which has IPv4 on the WAN talk to another site which has  IPv6 on the WAN, we will need to send the packets to a device who can map the v4 address to a v6 address (no NAT, but mapped I call it). The mapping table has nothing to do with NAT and is setup by a controller in most solutions.

Now this is working irrespective if the v4 site is NATed  (one way or another) or not.

On 05/11/2018, 17:42, "Idr on behalf of Fred Baker" <idr-bounces@ietf.org on behalf of fredbaker.ietf@gmail.com> wrote:

    
    
    > On Nov 5, 2018, at 5:40 PM, Linda Dunbar <linda.dunbar@huawei.com> wrote:
    > 
    > If a CPE-1 has private IPv6 addresses for its ports behind NAT, and CPE-2 has IPv4 address, can CPE-1 communicate with CPE-2 by the NAT's IPv4 address?
    
    There is no such thing as an IPv6 private address. I'm not sure how to respond to the question.
    --------------------------------------------------------------------------------
    Victorious warriors win first and then go to war,
    Defeated warriors go to war first and then seek to win.
         Sun Tzu

v2.23.0 | Report a Bug | By Email