Re: [v6ops] NAT64 in RA, draft-ietf-6man-ra-pref64

"Mudric, Dusan (Dusan)" <dmudric@avaya.com> Wed, 03 July 2019 19:02 UTC

Return-Path: <dmudric@avaya.com>
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 5407D120654; Wed, 3 Jul 2019 12:02:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-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=avaya365.onmicrosoft.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 cD0uoFPLW5nq; Wed, 3 Jul 2019 12:02:00 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) (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 DF8E7120670; Wed, 3 Jul 2019 12:01:56 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A2E0AACo+hxd/yYyC4dlHQEBBQEHBQGBUwgBCwGBQ1CBYgQzCodZA4RSX4kVgluJTY15gS6BJAMYPAkBAQENAS0CAQEChDoCAgKCRjQJDgEDAQEBBAEBAQEEAQICaYo3DINFOTIBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEFAjg4AQECAgESKAYBATgEDQEIFQMeMREmAQQBEggahGsDDg8BAgKaIAKBCDCIXwEBgiIagl8BAQWFDg0LghIJCQGBKgGLdYFBPoERRoJMPoIagioCgzqCJql/QAkCghaQDIQOgiuHHIN5A4oujTCJL44EAgICAgQFAg4BAQWBUDmBWHAVO4JsgkGDcYpTcoEpi1QBgSABAQ
X-IPAS-Result: A2E0AACo+hxd/yYyC4dlHQEBBQEHBQGBUwgBCwGBQ1CBYgQzCodZA4RSX4kVgluJTY15gS6BJAMYPAkBAQENAS0CAQEChDoCAgKCRjQJDgEDAQEBBAEBAQEEAQICaYo3DINFOTIBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEFAjg4AQECAgESKAYBATgEDQEIFQMeMREmAQQBEggahGsDDg8BAgKaIAKBCDCIXwEBgiIagl8BAQWFDg0LghIJCQGBKgGLdYFBPoERRoJMPoIagioCgzqCJql/QAkCghaQDIQOgiuHHIN5A4oujTCJL44EAgICAgQFAg4BAQWBUDmBWHAVO4JsgkGDcYpTcoEpi1QBgSABAQ
Received: from mailauth.avaya.com (HELO p-us1-erheast-smtpauth.us1.avaya.com) ([135.11.50.38]) by co300216-co-outbound.net.avaya.com with ESMTP; 03 Jul 2019 15:01:55 -0400
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-US1EXHC03.global.avaya.com) ([135.11.85.14]) by p-us1-erheast-out.us1.avaya.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 Jul 2019 15:01:55 -0400
Received: from PWEXCVMAP01.global.avaya.com (135.11.85.80) by AZ-US1EXHC03.global.avaya.com (135.11.85.14) with Microsoft SMTP Server (TLS) id 14.3.439.0; Wed, 3 Jul 2019 15:01:55 -0400
Received: from PWEXCVMAP02.global.avaya.com (135.11.85.81) by PWEXCVMAP01.global.avaya.com (135.11.85.80) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1531.3; Wed, 3 Jul 2019 15:01:55 -0400
Received: from PW365VMAP02.avaya.com (135.8.98.110) by PWEXCVMAP02.global.avaya.com (135.11.85.81) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.1531.3 via Frontend Transport; Wed, 3 Jul 2019 15:01:55 -0400
Received: from NAM04-CO1-obe.outbound.protection.outlook.com (104.47.45.55) by PW365VMAP02.avaya.com (135.8.98.110) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1531.3; Wed, 3 Jul 2019 14:01:54 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Avaya365.onmicrosoft.com; s=selector1-Avaya365-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=4vQi1wLCHTFRgX6X3CeuPf7QB+MiJFHmvBTq1YIhZQ0=; b=nPHiu8iESSREdZ4dCtxfKqa9Elx8pWEjsiRmNCA8gBRZoMnLDj3xkQlpg91G8qa0ukjL/yMcY3jkV0mXl53bLTW0X97UOpeSHW29yyPec9vrtYm2+3B+4/4A2qhaL8ASMQt3PD35itq1scoltVhW7lWK1SPLjPFndbr7b2IKhK0=
Received: from DM6PR15MB2506.namprd15.prod.outlook.com (20.176.71.32) by DM6PR15MB2572.namprd15.prod.outlook.com (20.179.160.207) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2052.15; Wed, 3 Jul 2019 19:01:51 +0000
Received: from DM6PR15MB2506.namprd15.prod.outlook.com ([fe80::697d:5307:1f7a:79bc]) by DM6PR15MB2506.namprd15.prod.outlook.com ([fe80::697d:5307:1f7a:79bc%6]) with mapi id 15.20.2032.019; Wed, 3 Jul 2019 19:01:51 +0000
From: "Mudric, Dusan (Dusan)" <dmudric@avaya.com>
To: 6man <6man@ietf.org>, IPv6 Operations <v6ops@ietf.org>
Thread-Topic: NAT64 in RA, draft-ietf-6man-ra-pref64
Thread-Index: AdUx0cT0aqZJH36KQ+aPddD1wR/aYA==
Date: Wed, 03 Jul 2019 19:01:51 +0000
Message-ID: <DM6PR15MB2506C03D1D88F2785B5016C1BBFB0@DM6PR15MB2506.namprd15.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=dmudric@avaya.com;
x-originating-ip: [104.129.196.166]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: c020a28b-3da8-42aa-498d-08d6ffe8e84f
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(7168020)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:DM6PR15MB2572;
x-ms-traffictypediagnostic: DM6PR15MB2572:
x-microsoft-antispam-prvs: <DM6PR15MB2572E8CB756593499E191F82BBFB0@DM6PR15MB2572.namprd15.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:7691;
x-forefront-prvs: 00872B689F
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(366004)(376002)(39860400002)(346002)(396003)(189003)(199004)(478600001)(26005)(68736007)(3846002)(6116002)(52536014)(66476007)(186003)(73956011)(76116006)(99286004)(66946007)(450100002)(256004)(86362001)(8936002)(81156014)(81166006)(8676002)(102836004)(55236004)(66446008)(25786009)(66556008)(6506007)(53546011)(7696005)(64756008)(5660300002)(14454004)(74316002)(55016002)(110136005)(71190400001)(71200400001)(6246003)(66066001)(2906002)(53936002)(316002)(33656002)(6436002)(9686003)(486006)(476003)(7736002)(305945005)(229853002); DIR:OUT; SFP:1101; SCL:1; SRVR:DM6PR15MB2572; H:DM6PR15MB2506.namprd15.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: avaya.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: TCMjGpZgTEDkaYvbL344+cO7ebEb8cJGCFyL/HQlU5n5hO5LoU7T39INFwuQK2NSo+UJp6W6WClP5Eskm7/ARqCxVtX+onVGTsPl6ojVkQFheOQruEKrxCIv2qOfH0pLj2x3+oiwNqkcWEw8exKJEzE931GPrU1zLDTAqsJgFtG3FcCYnEwxkQHp3cCEVT0veJfCZ2KlaPYFYabXzbt3zTaQq9dnQQMN/yraXAKhB9m3vtChi69tTq8CB7C1VWOd5HV/oNtetG7i4xaE+7ekcyjVL58RT/Y3CIRaEkfCvRRWa60zVB6nWQiAwygz9AbMikqfydyut3a0p30d5oEKy55gzLUHc3kkcwLyOHzW3cTzpYxDG9/LN+0O52hJgpQ6c21ocXGuYAZMbFc9ITEPQmegsAfsmzBcu6yePRoR3D0=
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: c020a28b-3da8-42aa-498d-08d6ffe8e84f
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Jul 2019 19:01:51.3610 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 04a2636c-326d-48ff-93f8-709875bd3aa9
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: dmudric@avaya.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR15MB2572
X-OriginatorOrg: avaya.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/xSlsy2vkzCo9PdVtlGhD5W7x0Xk>
Subject: Re: [v6ops] NAT64 in RA, draft-ietf-6man-ra-pref64
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: Wed, 03 Jul 2019 19:02:10 -0000

> 
> On Tue, Jul 2, 2019 at 9:49 AM Jen Linkova <furry13@gmail.com> wrote:
> 
> > I've been told that an IPv6-only
> > host might want to exclude some addresses from synthesis and use IPv4
> > to reach them, so I'm trying to understand how *an IPv6-only* host
> > (which, IMHO, can only use IPv6) reach anything using IPv4.
> >
> 
> Right. That was the gist of my earlier comment. I believe we all agree that
> in the most common deployment scenario (i.e., an IPv6-only host with no
> IPv4), an exclusion list is not useful, because the host really can't reach
> anything that's not reachable via IPv6.
> 

> From: v6ops <v6ops-bounces@ietf.org> On Behalf Of JORDI PALET
> MARTINEZ
>     And, oh yes, someone using IPv4 (or X.25, or SNA) could go through a
> translator and communicate with an IPv6-only host in such a domain. It's
> IPv6-only up to that translator.

[Dusan] Please clarify how IPv4-only host can reach IPv6 only host, and vice versa. Also, how IPv6 only host can know IPv4 address of IPv4 only host, assuming IPv4 only host is in a public domain?