Re: [v6ops] draft-vf-v6ops-ipv6-deployment

Gabor LENCSE <lencse@hit.bme.hu> Wed, 24 March 2021 08:39 UTC

Return-Path: <lencse@hit.bme.hu>
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 F20A73A2178 for <v6ops@ietfa.amsl.com>; Wed, 24 Mar 2021 01:39:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.645
X-Spam-Level:
X-Spam-Status: No, score=-0.645 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, IP_LINK_PLUS=0.012, NICE_REPLY_A=-0.001, NORMAL_HTTP_TO_IP=0.001, NUMERIC_HTTP_ADDR=1.242, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, WEIRD_PORT=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 OXgIqIYsL0u2 for <v6ops@ietfa.amsl.com>; Wed, 24 Mar 2021 01:39:23 -0700 (PDT)
Received: from frogstar.hit.bme.hu (frogstar.hit.bme.hu [IPv6:2001:738:2001:4020::2c]) (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 83C5D3A2174 for <v6ops@ietf.org>; Wed, 24 Mar 2021 01:39:23 -0700 (PDT)
Received: from [192.168.1.118] (host-79-121-42-153.kabelnet.hu [79.121.42.153]) (authenticated bits=0) by frogstar.hit.bme.hu (8.15.2/8.15.2) with ESMTPSA id 12O8dAuI093917 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <v6ops@ietf.org>; Wed, 24 Mar 2021 09:39:16 +0100 (CET) (envelope-from lencse@hit.bme.hu)
X-Authentication-Warning: frogstar.hit.bme.hu: Host host-79-121-42-153.kabelnet.hu [79.121.42.153] claimed to be [192.168.1.118]
To: v6ops@ietf.org
References: <BL0PR05MB5316425C5650B5D2FE43DE4DAE6C9@BL0PR05MB5316.namprd05.prod.outlook.com> <CAB75xn4ioyzQ5AvUrPKVyuybjZRV__Tv1OMs70Lm-z9bo1Eo6g@mail.gmail.com> <74d6dca7019f44aba09caf47ef703e2f@huawei.com> <CAB75xn7=swhtwqRuV6SoWoMO7jtCcPCc02XiVpAjE=VUx8CyaQ@mail.gmail.com> <6059897e.1c69fb81.ac270.d863SMTPIN_ADDED_BROKEN@mx.google.com> <749643a7-313f-4bd1-8bb8-7dc26d830070@gmail.com> <605aae8f.1c69fb81.8a8ed.04b7SMTPIN_ADDED_BROKEN@mx.google.com> <35c4cf4f-0128-dff6-27a3-4cc868539f7f@gmail.com> <9614BF99-431D-4046-9762-0F111AFBB27D@consulintel.es>
From: Gabor LENCSE <lencse@hit.bme.hu>
Message-ID: <a498117e-4834-41f8-5c90-ad7734d07220@hit.bme.hu>
Date: Wed, 24 Mar 2021 09:39:06 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1
MIME-Version: 1.0
In-Reply-To: <9614BF99-431D-4046-9762-0F111AFBB27D@consulintel.es>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-Virus-Scanned: clamav-milter 0.102.4 at frogstar.hit.bme.hu
X-Virus-Status: Clean
Received-SPF: pass (frogstar.hit.bme.hu: authenticated connection) receiver=frogstar.hit.bme.hu; client-ip=79.121.42.153; helo=[192.168.1.118]; envelope-from=lencse@hit.bme.hu; x-software=spfmilter 2.001 http://www.acme.com/software/spfmilter/ with libspf2-1.2.10;
X-DCC-wuwien-Metrics: frogstar.hit.bme.hu; whitelist
X-Scanned-By: MIMEDefang 2.79 on 152.66.248.44
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/fLbtV7ZEw3AYgPHlbDtSNyhvNPk>
Subject: Re: [v6ops] draft-vf-v6ops-ipv6-deployment
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, 24 Mar 2021 08:39:29 -0000

Of course, it is better to use DNS, but if you have only an IPv4 literal 
AND you know the NAT64 prefix used in your network, then you can 
synthesize the (RFC 6052) IPv4-embedded IPv6 address manually. :-)

The URL would look like:

https://[64:ff9b::218.2.231.237]:5001/cgi-bin/generate

Hopefully, your ISP uses a Network-Specific Prefix, and not the NAT64 
Well-Known Prefix.

Gábor

On 3/24/2021 9:02 AM, JORDI PALET MARTINEZ wrote:
> It will be much better to use DNS, not literals!
>
> You probably don't see that from an IPv6-only network because it is a literal (if you have NAT64+DNS64 it will work with DNS, if you have 464XLAT it will also work with a literal IPv4).
>   
>
> El 24/3/21 8:53, "v6ops en nombre de Alexandre Petrescu" <v6ops-bounces@ietf.org en nombre de alexandre.petrescu@gmail.com> escribió:
>
>
>
>      Le 24/03/2021 à 04:14, hsyu a écrit :
>      > Dear Paolo and  Alexandre,
>      >
>      > Thank you very much for your interest in this website.
>      >          This is a test website, and the current data still needs
>      > further confirmation. Therefore, I will post it after the data is corrected.
>
>      Hi,
>
>      Thank you for the reply.
>
>      The data on the website might be correct already.  I can see it on an
>      IPv4 connection.
>
>      But the access to that data should be on IPv6 too, not only on IPv4.
>
>      Ideally, one should add an IPv6 address to the computer's interface.
>      Then the URL would be something like
>      https://[2001:db8:1::1]:5001/cgi-bin/generate
>      (attention that is an IPv6 address for documentation, do not put that
>        particular address on the interface)
>
>      Alex
>
>      >
>      > 	
>      > Haisheng Yu(Johnson)
>      > hsyu@cfiec.net
>      >
>      > <https://maas.mail.163.com/dashi-web-extend/html/proSignature.html?ftlId=1&name=Haisheng+Yu%28Johnson%29&uid=hsyu%40cfiec.net&iconUrl=https%3A%2F%2Fmail-online.nosdn.127.net%2Fsm50a1433bca9fb284d4265d35e9ed54d3.jpg&items=%5B%22%22%2C%22hsyu%40cfiec.net%22%2C%22%22%2C%22%22%2C%22%22%5D>
>      >
>      > 签名由 网易邮箱大师 <https://mail.163.com/dashi/dlpro.html?from=mail81>
>      > 定制
>      > On 3/24/2021 02:14,Alexandre Petrescu<alexandre.petrescu@gmail.com>
>      > <mailto:alexandre.petrescu@gmail.com> wrote:
>      >
>      >     Hi,
>      >
>      >     Thank you for the link in China about IPv6 deployment.
>      >
>      >     But I can not see it :-(
>      >
>      >     When I copy paste that link (http://218.2.231.237:5001/cgi-bin/generate)
>      >     in my web browser  it responds that the connection has failed.  I use an
>      >     IPv6-only computer (Windows with IPv4 unchecked in the interface
>      >     Properties).
>      >
>      >     Ideally, one would put data about IPv6 on a server that is also capable
>      >     of doing IPv6.
>      >
>      >     Maybe one can put an IPv6 address on the server 218.2.231.237?
>      >
>      >     Alex
>      >
>      >
>      >     Le 23/03/2021 à 07:21, hsyu a écrit :
>      >
>      >         Hi Paolo, I can also provide some data on the deployment of IPv6 in
>      >         China. http://218.2.231.237:5001/cgi-bin/generate
>      >
>      >         Best regards.
>      >
>      >         Haisheng Yu(Johnson) hsyu@cfiec.net
>      >
>      >         <https://maas.mail.163.com/dashi-web-extend/html/proSignature.html?ftlId=1&name=Haisheng+Yu%28Johnson%29&uid=hsyu%40cfiec.net&iconUrl=https%3A%2F%2Fmail-online.nosdn.127.net%2Fsm50a1433bca9fb284d4265d35e9ed54d3.jpg&items=%5B%22%22%2C%22hsyu%40cfiec.net%22%2C%22%22%2C%22%22%2C%22%22%5D>
>      >
>      >
>      >         签名由 网易邮箱大师
>      >         <https://mail.163.com/dashi/dlpro.html?from=mail81> 定制 On
>      >         3/23/2021 12:40,Dhruv Dhody<dhruv.ietf@gmail.com>
>      >         <mailto:dhruv.ietf@gmail.com> wrote:
>      >
>      >         Hi Paolo,
>      >
>      >         I think we should highlight that we do not have visibility
>      >         inside the
>      >         enterprises beyond the external-facing website or email and thus it
>      >         is also difficult to gauge the IPv6 deployments inside enterprises.
>      >
>      >         [PV] Ok. Probably here you refer to small-medium enterprises. For
>      >         large enterprises public data on the usage of IPv6 can be retrieved
>      >         (Nalini, in copy, provided a good input on IPv6 in large
>      >         organizations). We will better specify this point in the next
>      >         version
>      >         of the draft.
>      >
>      >
>      >         I had this NIST data in mind -
>      >         https://fedv6-deployment.antd.nist.gov/cgi-bin/generate-com which
>      >         includes large enterprises and relies on DNS, mail, external
>      >         website. Also, see Eric's site -
>      >         https://www.vyncke.org/ipv6status/detailed.php?country=in
>      >
>      >         Thanks! Dhruv
>      >
>      >         _______________________________________________ v6ops mailing list
>      >         v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
>      >
>      >
>      >         _______________________________________________ v6ops mailing list
>      >         v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
>      >
>
>      _______________________________________________
>      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 mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>