Re: [v6ops] I-D Action: draft-ietf-v6ops-transition-comparison-04.txt

Gábor LENCSE <lencse@hit.bme.hu> Tue, 24 May 2022 07:32 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 93E64C157B49 for <v6ops@ietfa.amsl.com>; Tue, 24 May 2022 00:32:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.756
X-Spam-Level:
X-Spam-Status: No, score=-3.756 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-1.857, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3hDfCbvpLbUZ for <v6ops@ietfa.amsl.com>; Tue, 24 May 2022 00:32:21 -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 55323C14EB1E for <v6ops@ietf.org>; Tue, 24 May 2022 00:32:20 -0700 (PDT)
Received: from [192.168.1.145] (host-79-121-40-187.kabelnet.hu [79.121.40.187]) (authenticated bits=0) by frogstar.hit.bme.hu (8.15.2/8.15.2) with ESMTPSA id 24O7W5AF004375 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <v6ops@ietf.org>; Tue, 24 May 2022 09:32:11 +0200 (CEST) (envelope-from lencse@hit.bme.hu)
X-Authentication-Warning: frogstar.hit.bme.hu: Host host-79-121-40-187.kabelnet.hu [79.121.40.187] claimed to be [192.168.1.145]
Message-ID: <84c06175-6d4d-1fbf-7e88-6dfc6c8b401b@hit.bme.hu>
Date: Tue, 24 May 2022 09:32:01 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.9.0
Content-Language: en-US
To: v6ops@ietf.org
References: <02E70CC0-74F2-4F03-ACD2-408B4186A949@consulintel.es> <30656_1653376924_628C879B_30656_404_1_17f7358da478412a98c03ab31eb13786@orange.com>
From: Gábor LENCSE <lencse@hit.bme.hu>
In-Reply-To: <30656_1653376924_628C879B_30656_404_1_17f7358da478412a98c03ab31eb13786@orange.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: clamav-milter 0.103.2 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.40.187; helo=[192.168.1.145]; envelope-from=lencse@hit.bme.hu; x-software=spfmilter 2.001 http://www.acme.com/software/spfmilter/ with libspf2-1.2.10;
X-DCC--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/W_c087b_RSgDqj55eucXHuouZ0w>
Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-transition-comparison-04.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.34
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, 24 May 2022 07:32:25 -0000

Dear Med,

Will you be satisfied if we cite a few cases for each technology, when 
the implementations do support direct communication?

I mean doing it just here, on this list. I think we should not include 
the vendor specific information into the draft. It would be unfair 
against those, about whom we do not know it.

However, showing examples justifies that the statements are objective.

Best regards,

Gábor



5/24/2022 9:22 AM keltezéssel, mohamed.boucadair@orange.com írta:
> Re-,
>
> I'm afraid this is not appropriate in an RFC.
>
> This document is not about certifying implems. Relying on some web search and then extrapolate to draw generic conclusion for a given technology is really weird.
>
> I hope that subjective text can be removed.
>
> Cheers,
> Med
>
>> -----Message d'origine-----
>> De : v6ops <v6ops-bounces@ietf.org> De la part de JORDI PALET
>> MARTINEZ
>> Envoyé : mardi 24 mai 2022 09:08
>> À : v6ops@ietf.org
>> Objet : Re: [v6ops] I-D Action: draft-ietf-v6ops-transition-
>> comparison-04.txt
>>
>> Hi Med,
>>
>> As previously explained, we drafted that text, considering the
>> docuemnts that we have been able to find from different vendors.
>>
>> We believe this text ensures that the reader of the document will
>> double-check with the possible vendors/products, what is the
>> support for hair-pinning they offer, so to be able to make a
>> better decision.
>>
>> Regards,
>> Jordi
>> @jordipalet
>>
>>
>>
>> El 24/5/22, 8:06, "v6ops-bounces@ietf.org en nombre de
>> mohamed.boucadair@orange.com" <v6ops-bounces@ietf.org en nombre de
>> mohamed.boucadair@orange.com> escribió:
>>
>>      Hi Jordi, Gabor, all,
>>
>>      Thank you for taking into account the various comments.
>>
>>      However, I see that the wording:
>>
>>      "Often NAT64 vendors support direct communication .."
>>
>>      and
>>
>>      "Some AFTR vendors support direct .."
>>
>>      made it to the public version while there is no evidence to
>> back these claims.
>>
>>      I'm uncomfortable to include such claims in the draft and,
>> thus, reiterate the suggestion to be factual: include what a
>> technology is designed to provide no what some specific implems
>> are doing.
>>
>>      Thank you.
>>
>>      Cheers,
>>      Med
>>
>>      > -----Message d'origine-----
>>      > De : I-D-Announce <i-d-announce-bounces@ietf.org> De la part
>> de
>>      > internet-drafts@ietf.org
>>      > Envoyé : lundi 23 mai 2022 21:51
>>      > À : i-d-announce@ietf.org
>>      > Cc : v6ops@ietf.org
>>      > Objet : I-D Action: draft-ietf-v6ops-transition-comparison-
>> 04.txt
>>      >
>>      >
>>      > A New Internet-Draft is available from the on-line Internet-
>> Drafts
>>      > directories.
>>      > This draft is a work item of the IPv6 Operations WG of the
>> IETF.
>>      >
>>      >         Title           : Pros and Cons of IPv6 Transition
>>      > Technologies for IPv4aaS
>>      >         Authors         : Gabor Lencse
>>      >                           Jordi Palet Martinez
>>      >                           Lee Howard
>>      >                           Richard Patterson
>>      >                           Ian Farrer
>>      > 	Filename        : draft-ietf-v6ops-transition-
>> comparison-
>>      > 04.txt
>>      > 	Pages           : 35
>>      > 	Date            : 2022-05-23
>>      >
>>      > Abstract:
>>      >    Several IPv6 transition technologies have been developed
>> to
>>      > provide
>>      >    customers with IPv4-as-a-Service (IPv4aaS) for ISPs with
>> an
>>      > IPv6-only
>>      >    access and/or core network.  All these technologies have
>> their
>>      >    advantages and disadvantages, and depending on existing
>>      > topology,
>>      >    skills, strategy and other preferences, one of these
>>      > technologies may
>>      >    be the most appropriate solution for a network operator.
>>      >
>>      >    This document examines the five most prominent IPv4aaS
>>      > technologies
>>      >    considering a number of different aspects to provide
>> network
>>      >    operators with an easy-to-use reference to assist in
>> selecting
>>      > the
>>      >    technology that best suits their needs.
>>      >
>>      >
>>      > The IETF datatracker status page for this draft is:
>>      > https://datatracker.ietf.org/doc/draft-ietf-v6ops-
>> transition-
>>      > comparison/
>>      >
>>      > There is also an htmlized version available at:
>>      > https://datatracker.ietf.org/doc/html/draft-ietf-v6ops-
>> transition-
>>      > comparison-04
>>      >
>>      > A diff from the previous version is available at:
>>      > https://www.ietf.org/rfcdiff?url2=draft-ietf-v6ops-
>> transition-
>>      > comparison-04
>>      >
>>      >
>>      > Internet-Drafts are also available by rsync at
>>      > rsync.ietf.org::internet-drafts
>>      >
>>      >
>>      > _______________________________________________
>>      > I-D-Announce mailing list
>>      > I-D-Announce@ietf.org
>>      > https://www.ietf.org/mailman/listinfo/i-d-announce
>>      > Internet-Draft directories: http://www.ietf.org/shadow.html
>> or
>>      > ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>
>>
>> __________________________________________________________________
>> _______________________________________________________
>>
>>      Ce message et ses pieces jointes peuvent contenir des
>> informations confidentielles ou privilegiees et ne doivent donc
>>      pas etre diffuses, exploites ou copies sans autorisation. Si
>> vous avez recu ce message par erreur, veuillez le signaler
>>      a l'expediteur et le detruire ainsi que les pieces jointes.
>> Les messages electroniques etant susceptibles d'alteration,
>>      Orange decline toute responsabilite si ce message a ete
>> altere, deforme ou falsifie. Merci.
>>
>>      This message and its attachments may contain confidential or
>> privileged information that may be protected by law;
>>      they should not be distributed, used or copied without
>> authorisation.
>>      If you have received this email in error, please notify the
>> sender and delete this message and its attachments.
>>      As emails may be altered, Orange is not liable for messages
>> that have been modified, changed or falsified.
>>      Thank you.
>>
>>      _______________________________________________
>>      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
> _________________________________________________________________________________________________________________________
>
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>