IETF Logo Mail Archive

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

Fred Baker <fredbaker.ietf@gmail.com> Mon, 05 November 2018 10:41 UTC

Return-Path: <fredbaker.ietf@gmail.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 460C7130EC9; Mon, 5 Nov 2018 02:41:52 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 WoCMIPUJMPqU; Mon, 5 Nov 2018 02:41:49 -0800 (PST)
Received: from mail-pl1-x62b.google.com (mail-pl1-x62b.google.com [IPv6:2607:f8b0:4864:20::62b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B61E0130F52; Mon, 5 Nov 2018 02:41:49 -0800 (PST)
Received: by mail-pl1-x62b.google.com with SMTP id g59-v6so4265138plb.10; Mon, 05 Nov 2018 02:41:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=GAGHHHfxftLrorNtL5OvXrKs8BXlR583FqdRfaYJC0M=; b=BOj0EVeyTfmjOYrfwO5cNtGrz7yxPgEChJUtNAlZGZ/UfVo7uKg21t3F85Bn7xB8s1 scWbPU0pSDa0lhZq2pyVEGTiVBgZrb6l/5J3fd3iiijlwVAIG8e4CZrmTvkiy3har2Oo dcEOSp0CfbydE3S4n045+itxZyF6UhMzUs87bptbjAF+0cJuhw82pqY8GXxGNbDSs+er 3Ms15J6zaoYo2XYa8bJc8HMv8ppx+PDYciQiH5u0/E5ZfqvIZo4kPemmLwy+Y3UEiWdQ +L0oKFrnHLL+qKCB8z0ALv02jii6Vw+8PbprSCfhkxauoaWh8EUjlXX9ieaCljuRXWyW 7oMA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=GAGHHHfxftLrorNtL5OvXrKs8BXlR583FqdRfaYJC0M=; b=M88/WwrX0eIFNr2v44HK0KVrHoyzjPUVi93yo4wUeCgw5L4moKWdJIzxKHbfsL5vT/ A2nbXoFWXm1IvbuKvDSxIhljj+AeuvHk88VPUrhiWjUsVRP9w9WlXzFAWxVcjrHjidmZ I1bqScYMn7vK4bJ5JA31iAfPd+9eo8Emzu1XKuLa+QJ31uDobnIOeaGslc9QK+OuEOyT Nx9O3V7g7hgb69NS2mRTkwHipqlhBkhXse4IHuwUK0ZJjAha2bOf/k39LSF1Nd3S8HD1 CDIEbcoXrMeCNWqIoe80npFbnZyVhNyCBn1uThx31T3o/nNKWwyXbIN0X9p2PnvcQ4vl AkOA==
X-Gm-Message-State: AGRZ1gJjd/w+f01+VUrC2rR4uiJ1IQilJauMsVS8sdU7KLMuV9vvC5iA bcLo7+yanJY5pB9Km0yjeDo=
X-Google-Smtp-Source: AJdET5ce4QO7V73KkW0Ine5TnDOXHl1vRXDGylo79fRZUuvOBDvQS1KbvjhxONegPwSfotK88REscQ==
X-Received: by 2002:a17:902:8b8a:: with SMTP id ay10-v6mr21537019plb.130.1541414509320; Mon, 05 Nov 2018 02:41:49 -0800 (PST)
Received: from dhcp-94bc.meeting.ietf.org (dhcp-94bc.meeting.ietf.org. [31.133.148.188]) by smtp.gmail.com with ESMTPSA id i189-v6sm33505603pfg.156.2018.11.05.02.41.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 05 Nov 2018 02:41:48 -0800 (PST)
From: Fred Baker <fredbaker.ietf@gmail.com>
Message-Id: <A55564ED-B913-437C-8442-DA5962F2BEC3@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_5B6B8F97-23B3-4304-8444-FCA742B0B33D"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Mon, 05 Nov 2018 17:41:41 +0700
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F66B182B93@sjceml521-mbs.china.huawei.com>
Cc: tom petch <ietfc@btconnect.com>, Joel Jaeggli <joelja@bogus.com>, "idr@ietf.org" <idr@ietf.org>, "int-area@ietf.org" <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
To: Linda Dunbar <linda.dunbar@huawei.com>
References: <4A95BA014132FF49AE685FAB4B9F17F66B18249E@sjceml521-mbs.china.huawei.com> <6E397847-407E-4F69-AD31-E87D0001F603@gmail.com> <4A95BA014132FF49AE685FAB4B9F17F66B182B93@sjceml521-mbs.china.huawei.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/jLGGBWT4nOaIz_qhcc3nCjf9d-8>
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 10:41:58 -0000


> 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