Re: [v6ops] Call for Discussion draft-palet-v6ops-ipv6-only
JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Tue, 09 June 2020 13:55 UTC
Return-Path: <prvs=1429d4c227=jordi.palet@consulintel.es>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4B933A0953 for <v6ops@ietfa.amsl.com>; Tue, 9 Jun 2020 06:55:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es
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 xzC9CHGUG8dz for <v6ops@ietfa.amsl.com>; Tue, 9 Jun 2020 06:55:36 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) by ietfa.amsl.com (Postfix) with ESMTP id 736123A094E for <v6ops@ietf.org>; Tue, 9 Jun 2020 06:55:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1591710934; x=1592315734; i=jordi.palet@consulintel.es; q=dns/txt; h=User-Agent:Date: Subject:From:To:Message-ID:Thread-Topic:References:In-Reply-To: Mime-version:Content-type:Content-transfer-encoding; bh=0klFH9ji IEaVcJYuSVfh+gAIEHaoG4cK6Ruw4tRVe5Q=; b=Hq6yHDCaQfpJgW3diYhti5HQ nTUrW/FRD9Fz2FR+P5ctpVAmP59k4U2v0AHAU34B3KAu5dNnd23OXh0WhlQvYK2z i11+L7NsHpg3fMH1xPhNnx7+oJiifBM9FWw3RSZu6gi9klOGPXDj/+pciDU3H/kJ b78eF085wo5dYc5i9vw=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Tue, 09 Jun 2020 15:55:34 +0200
X-Spam-Processed: mail.consulintel.es, Tue, 09 Jun 2020 15:55:34 +0200
Received: from [10.10.10.144] by mail.consulintel.es (MDaemon PRO v16.5.2) with ESMTPA id md50000206847.msg for <v6ops@ietf.org>; Tue, 09 Jun 2020 15:55:32 +0200
X-MDRemoteIP: 2001:470:1f09:495:793a:609c:a43c:9e74
X-MDHelo: [10.10.10.144]
X-MDArrival-Date: Tue, 09 Jun 2020 15:55:32 +0200
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=1429d4c227=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: v6ops@ietf.org
User-Agent: Microsoft-MacOutlook/16.37.20051002
Date: Tue, 09 Jun 2020 15:55:31 +0200
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: "v6ops@ietf.org" <v6ops@ietf.org>
Message-ID: <C46EB3D6-30F3-4EE4-94EB-B659D2612C6C@consulintel.es>
Thread-Topic: [v6ops] Call for Discussion draft-palet-v6ops-ipv6-only
References: <DM6PR05MB6348F5472AE8FE5937D18A23AE850@DM6PR05MB6348.namprd05.prod.outlook.com> <alpine.DEB.2.20.2006091451550.29463@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.20.2006091451550.29463@uplift.swm.pp.se>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Ym8QoyqrbHPErh558dcIxdiSy4Q>
Subject: Re: [v6ops] Call for Discussion draft-palet-v6ops-ipv6-only
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jun 2020 13:55:38 -0000
Hi Mikael, In my opinion, your example, has several parts. If we want to talk about "all", should be sufficient to say "this is a 464XLAT" case. I think this is out of the scope of the document, because 464XLAT itself is very well self-contained/described. The point is if you want to talk about the WAN link itself. In your example case it is clearly an IPv6-only WAN. If you want to talk about the UE, actually "today OSs" are native dual-stack, however, in this network it is being used as a transitional IPv6 host/router. The full point of the document is that if we talk about an specific transition mechanism, everything is very clear (unless the network is doing a "special" deployment different from the standard), however, in many occasions it is very relevant to make sure if the WAN links (for example) are *natively* transporting IPv6-only. That said, I'm of course happy to add a few examples. Not sure if that should be an annex or in the main text already. Regards, Jordi @jordipalet El 9/6/20 14:56, "v6ops en nombre de Mikael Abrahamsson" <v6ops-bounces@ietf.org en nombre de swmike=40swm.pp.se@dmarc.ietf.org> escribió: On Mon, 8 Jun 2020, Ron Bonica wrote: > Folks, > > > > Each week between now and IETF week, we will review and discuss one draft with an eye towards progressing it. > > > > This week, please review and comment on draft-palet-v6ops-ipv6-only. I think it would be good if we could come up with some terms that cause less confusion when discussing different solutions. So this draft has an embryo for that, but I think it would be good if there were some examples. So let's say I want to describe a mobile access with IPv6 only WAN that supports 464xlat? What is that then? "dual stack LAN with transitional 464xlat-enabled router with IPv6 only WAN and NAT64 function in the network"? That's still long and cumbersome...? -- Mikael Abrahamsson email: swmike@swm.pp.se _______________________________________________ v6ops mailing list v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.
- [v6ops] Call for Discussion draft-palet-v6ops-ipv… Ron Bonica
- Re: [v6ops] Call for Discussion draft-palet-v6ops… Philip Homburg
- Re: [v6ops] Call for Discussion draft-palet-v6ops… Mikael Abrahamsson
- Re: [v6ops] Call for Discussion draft-palet-v6ops… JORDI PALET MARTINEZ
- Re: [v6ops] Call for Discussion draft-palet-v6ops… Pengshuping (Peng Shuping)
- Re: [v6ops] Call for Discussion draft-palet-v6ops… Richard Patterson