Re: [v6ops] dhcpv6-pd on cellular, IoT router
Alexandre Petrescu <alexandre.petrescu@gmail.com> Fri, 26 March 2021 16:25 UTC
Return-Path: <alexandre.petrescu@gmail.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 3A0913A225F for <v6ops@ietfa.amsl.com>; Fri, 26 Mar 2021 09:25:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.632
X-Spam-Level:
X-Spam-Status: No, score=-1.632 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no 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 a3c7i3WunUOG for <v6ops@ietfa.amsl.com>; Fri, 26 Mar 2021 09:25:33 -0700 (PDT)
Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (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 A40B03A2262 for <v6ops@ietf.org>; Fri, 26 Mar 2021 09:25:33 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 12QGPUo4040354 for <v6ops@ietf.org>; Fri, 26 Mar 2021 17:25:30 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 9D665204EE5 for <v6ops@ietf.org>; Fri, 26 Mar 2021 17:25:30 +0100 (CET)
Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 93C90204805 for <v6ops@ietf.org>; Fri, 26 Mar 2021 17:25:30 +0100 (CET)
Received: from [10.8.35.150] (is154594.intra.cea.fr [10.8.35.150]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 12QGPUtP020698 for <v6ops@ietf.org>; Fri, 26 Mar 2021 17:25:30 +0100
To: v6ops@ietf.org
References: <BL0PR05MB5316425C5650B5D2FE43DE4DAE6C9@BL0PR05MB5316.namprd05.prod.outlook.com> <35c4cf4f-0128-dff6-27a3-4cc868539f7f@gmail.com> <9614BF99-431D-4046-9762-0F111AFBB27D@consulintel.es> <a498117e-4834-41f8-5c90-ad7734d07220@hit.bme.hu> <e770fec1-2189-f683-6c74-36e32541c53d@gmail.com> <abe65114-d9c9-10ee-2c78-449051acbb61@hit.bme.hu> <3c50c72b-b606-a6cf-3095-f08ad48eecf5@gmail.com> <2A0C2B40-2DA4-4941-A09F-5BD31EDA3301@consulintel.es> <2e64b426-3a0a-b5f8-0306-005e9f1023d0@gmail.com> <72754d29-8b57-66fa-2b3a-fc6680c339f2@hit.bme.hu> <bdeec6da-3b2a-8cd4-e2d4-feb62c282c7d@gmail.com> <5E67F1F7-4065-4500-B722-D1E8E9458242@consulintel.es> <0db72084-5952-d8b0-c3ab-cc30d7325111@gmail.com> <DA520004-3768-4CA0-9A8F-9FDC76572AB5@consulintel.es> <1f1052d5-d89e-0c10-06f5-aa0c71405942@gmail.com> <80A5F547-DD89-482E-B479-A525D1551FB6@consulintel.es> <198cdcdd-177b-0461-5b75-ae13640ae652@gmail.com> <4A828E48-8089-4130-B01E-4D83639A006F@consulintel.es>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <3dfcf650-5bc2-f64a-e904-826626f5a7da@gmail.com>
Date: Fri, 26 Mar 2021 17:25:29 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.9.0
MIME-Version: 1.0
In-Reply-To: <4A828E48-8089-4130-B01E-4D83639A006F@consulintel.es>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/KIzFxwfrt1w9pD7DQwOMzC-tDmM>
Subject: Re: [v6ops] dhcpv6-pd on cellular, IoT router
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: Fri, 26 Mar 2021 16:25:38 -0000
Le 26/03/2021 à 17:14, JORDI PALET MARTINEZ a écrit : > > > -> They are broken then - complain to the vendor, > > How can I complain to a vendor of not implementing '64hare' which is an > INFORMATIONAL RFC? > > Either make the RFC Stds Track or not try to put it on the list of > absolute requirements for a device... > > -> Vendors don't really care so much about if an RFC is class "a" or "b" or "c". Money talks. Don't buy them. I was _offered_ these devices and then bulk price for more. One cant beat that. That should be compared to the gratuitous 64share software but on a 1000Eur hardware smartphone package. Compare it too to the price I'd have to may out of my own pocket to submit our own DHCPv6-PD client compiled from open source in order to get it a place in the store. And even if I paid that, I think it would be refused by the store owner because of other non technical reasons against DHCP. This situation is far from desirable. If there were a cheap IoT router on the market with root ssh and not block DHCPv6 on 4G then I am all ears :-) But there isnt :-( So it's staled. Alex > > > > It is not blocked by "hardware" but may be by > > > baseband modem firmware. > > > > 'is not' on one hand and 'may' on the other hand - I can only agree with > > you, but there is something missing. > > > > That is the situation right now. > > > > -> IETF is not the place to resolve buggy implementations, only complaining to vendors will resolve it, and ultimately, finding alternative suppliers. > > We will not resolve buggy implementations here. > > We will continue to stale. > > > > > >> One example of this was, a few years ago, the contract awarded to > > >> Telefónica for 53 millions of gas and electricity meters in UK, > > >> worth 1.5 billion pounds in 15 years, using cellular and 6LOWPAN. > > >> If they have done it with IPv4, they will have needed 34 million > > >> NATs, according to their own calculations. > > > > > > The IoT devices that I acquire on the market dont do 6lowpan. There > > > are indeed many 6lowpan devices but there are also many other IoT > > > devices that connect on 4G, have Bluetooth/WiFi/Ethernet/Galileo and > > > yet dont do 6lowpan. > > > > > > -> Those devices don't deserve the right to be called IoT then. A > > > real IoT devices must have IPv6 support. > > > > Ah? DO you mean that an IoT device on the market that does not do > > 6lowpan or does not do IPv6 can not be called IoT? > > > > This might go very far, but should be considered. > > > > -> From the perspective of IETF, technically we could document it. However, the problem is more a marketing advise. Most of the companies selling all kind of cheap sensors, just don't care, they will keep calling "IoT" to any crap hardware, even if is not IP enabled at all (I've seen RF-only sensors being called IoT sensors ...). > > Might be to say IoT sensors are just the RF-only devices. > > But how about 'IoT Routers'? > > We propose the definition of an 'IoT Router' to be this: > > IoT Router - a device of class IoT. It has several wired and > > wireless interfaces. One wireless interface is of type cellular, > > like 4G or 5G. This cellular interface is egress. The other > > interfaces are ingress. There are at least two ingress interfaces. > > There is at least one set of two interfaces that can not be bridged > > together, for example 802.11b and Bluetooth. If all ingress > > interfaces in the IoT Router can be bridged, for example 802.11b and > > Ethernet, then there is at least one other router in the same local > > network as the IoT Router, that can not be bridged to this IoT > > Router. The IoT Router needs more than one /64 prefix. An example > > of IoT Router is Sierra Wirelss mangOH Red, or Maestro Wireless E220. > > -> I think and IoT router definition don't need to enforce any specific interface, because it depends on the scenario. However, it needs to enforce IPv6 support. > > > > > >> https://www.google.com/search?q=telefonica+awarded+uk+meters > > >> > > >> Now, if you want to make it more complex, and you really need to > > >> keep IPv4 incoming connections, you can still configure the NAT64 > > >> for that, either for specific ports or addresses. However, as said, > > >> it doesn't make sense to use IPv4 for new deployments of > > >> "anything". > > > > > > If I _have_ to do NAT, then NAT44 is largely sufficient. There is > > > no need for v4-v6 transition mechanisms (I mean not in these trials > > > I consider). > > > > > > -> It is utopic to believe that NAT44 will keep scaling ... > > > > I can agree that in the long term NAT44 might not scale, but I can also > > agree that NAT64 wouldnt scale either. > > > > -> NAT64 scales if we continue "real" IPv6 deployment *because* it means that you use less and less NAT64 translations, so less IPv4 addresses required on the NAT64 Internet-facing interfaces. The nice think about 464XLAT is that you "drop" IPv4 in a natural way, just passing the time, nothing to be done. When you do IPv6-only deployments (with IPv4aaS) in ISPs, you suddenly see (at least in residential networks) 75%-85% of the traffic being IPv6-only end-to-end. > > Hmmm, thinking abou tit. > > Alex > > > > > Yes, let us do IPv6, unless one calls IPv6 the IPv4+translation :-) > > > > Alex > > > > > > > > > > > > > > > > > > > > ********************************************** 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 > > > > > > > _______________________________________________ > > 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 > > > > _______________________________________________ > 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 >
- [v6ops] draft-vf-v6ops-ipv6-deployment Ron Bonica
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Fred Baker
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Paolo Volpato
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Dhruv Dhody
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Paolo Volpato
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Brian E Carpenter
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Dhruv Dhody
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment hsyu
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment nalini.elkins@insidethestack.com
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Paolo Volpato
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Paolo Volpato
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Paolo Volpato
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Alexandre Petrescu
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Alexandre Petrescu
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment hsyu
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Alexandre Petrescu
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment JORDI PALET MARTINEZ
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Gabor LENCSE
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Alexandre Petrescu
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Gabor LENCSE
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Alexandre Petrescu
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Gert Doering
- Re: [v6ops] address representations, and addresse… Alexandre Petrescu
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment JORDI PALET MARTINEZ
- Re: [v6ops] address representations, and addresse… Gert Doering
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Vasilenko Eduard
- Re: [v6ops] address representations, and addresse… Alexandre Petrescu
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Alexandre Petrescu
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment JORDI PALET MARTINEZ
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment JORDI PALET MARTINEZ
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Gabor LENCSE
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Alexandre Petrescu
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Alexandre Petrescu
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Alexandre Petrescu
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Martin Hunek
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Alexandre Petrescu
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Alexandre Petrescu
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment hsyu
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment JORDI PALET MARTINEZ
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Alexandre Petrescu
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Alexandre Petrescu
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Vasilenko Eduard
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Gert Doering
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Alexandre Petrescu
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Gert Doering
- Re: [v6ops] draft-lmhp-v6ops-transition-compariso… Alexandre Petrescu
- Re: [v6ops] draft-lmhp-v6ops-transition-compariso… JORDI PALET MARTINEZ
- Re: [v6ops] draft-lmhp-v6ops-transition-compariso… Alexandre Petrescu
- Re: [v6ops] draft-lmhp-v6ops-transition-compariso… JORDI PALET MARTINEZ
- Re: [v6ops] draft-lmhp-v6ops-transition-compariso… Alexandre Petrescu
- Re: [v6ops] draft-lmhp-v6ops-transition-compariso… Alexandre Petrescu
- Re: [v6ops] draft-lmhp-v6ops-transition-compariso… JORDI PALET MARTINEZ
- Re: [v6ops] draft-lmhp-v6ops-transition-compariso… JORDI PALET MARTINEZ
- Re: [v6ops] draft-lmhp-v6ops-transition-compariso… Alexandre Petrescu
- Re: [v6ops] draft-lmhp-v6ops-transition-compariso… JORDI PALET MARTINEZ
- Re: [v6ops] dhcpv6-pd on cellular, IoT router Alexandre Petrescu
- Re: [v6ops] dhcpv6-pd on cellular, IoT router JORDI PALET MARTINEZ
- Re: [v6ops] draft-lmhp-v6ops-transition-compariso… Gert Doering
- Re: [v6ops] dhcpv6-pd on cellular, IoT router Alexandre Petrescu
- Re: [v6ops] dhcpv6-pd on cellular, IoT router Ted Lemon
- Re: [v6ops] draft-lmhp-v6ops-transition-compariso… Alexandre Petrescu
- Re: [v6ops] dhcpv6-pd on cellular, IoT router JORDI PALET MARTINEZ
- Re: [v6ops] dhcpv6-pd on cellular, IoT router Alexandre Petrescu
- Re: [v6ops] dhcpv6-pd on cellular, IoT router JORDI PALET MARTINEZ
- [v6ops] draft-vf-v6ops-ipv6-deployment and draft-… Fred Baker
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment and dr… Xipengxiao
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment and dr… Gabor LENCSE
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment xiechf@chinatelecom.cn
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment JORDI PALET MARTINEZ
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Brian E Carpenter
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Lencse Gábor
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment JORDI PALET MARTINEZ
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment JORDI PALET MARTINEZ
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Vasilenko Eduard
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Vasilenko Eduard
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Giuseppe Fioccola
- [v6ops] How can one check the presence of IPv4aaS… Lencse Gábor
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Brian E Carpenter
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Vasilenko Eduard
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment JORDI PALET MARTINEZ
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment JORDI PALET MARTINEZ
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment JORDI PALET MARTINEZ
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment JORDI PALET MARTINEZ
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Lencse Gábor
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Vasilenko Eduard
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Olivier MJ Crépin-Leblond
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment JORDI PALET MARTINEZ
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Giuseppe Fioccola
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Alexandre Petrescu
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Olaf.Bonness
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment JORDI PALET MARTINEZ
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Alexandre Petrescu
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Alexandre Petrescu
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment JORDI PALET MARTINEZ
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment JORDI PALET MARTINEZ
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Alexandre Petrescu
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment and dr… Giuseppe Fioccola
- Re: [v6ops] How can one check the presence of IPv… otroan
- Re: [v6ops] complains about '64::' addresses draf… Alexandre Petrescu
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment and dr… xiechf@chinatelecom.cn
- Re: [v6ops] How can one check the presence of IPv… Alexandre Petrescu
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment and dr… STARK, BARBARA H
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment and dr… Giuseppe Fioccola
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment and dr… STARK, BARBARA H
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment and dr… Giuseppe Fioccola
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment and dr… Alexandre Petrescu
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment and dr… Alexandre Petrescu
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment and dr… JORDI PALET MARTINEZ
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment and dr… JORDI PALET MARTINEZ
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment and dr… STARK, BARBARA H
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Brian E Carpenter
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Vasilenko Eduard
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Brian E Carpenter
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment STARK, BARBARA H
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment JORDI PALET MARTINEZ
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Gyan Mishra
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Gyan Mishra
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment and dr… Ackermann, Michael
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment and dr… Giuseppe Fioccola
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment and dr… Giuseppe Fioccola
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment and dr… Pengshuping (Peng Shuping)
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Giuseppe Fioccola
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment and dr… Giuseppe Fioccola
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment and dr… Alexandre Petrescu
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment and dr… Dhruv Dhody
- Re: [v6ops] How can one check the presence of IPv… xiechf@chinatelecom.cn
- Re: [v6ops] How can one check the presence of IPv… Alexandre Petrescu
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment STARK, BARBARA H
- [v6ops] Buying and selling IPv4 addresses and the… Lencse Gábor
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Yannis Nikolopoulos
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Yannis Nikolopoulos
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Brian E Carpenter
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment JORDI PALET MARTINEZ
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Gyan Mishra
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment JORDI PALET MARTINEZ
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Gyan Mishra
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Vasilenko Eduard
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Yannis Nikolopoulos
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Yannis Nikolopoulos
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment otroan
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment JORDI PALET MARTINEZ
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment JORDI PALET MARTINEZ
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Vasilenko Eduard
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment JORDI PALET MARTINEZ
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Vasilenko Eduard
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Yannis Nikolopoulos
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment N.Leymann
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment JORDI PALET MARTINEZ
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment JORDI PALET MARTINEZ
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment JORDI PALET MARTINEZ
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Alexandre Petrescu
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Vasilenko Eduard
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Brian E Carpenter
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment JORDI PALET MARTINEZ
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment JORDI PALET MARTINEZ
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Yannis Nikolopoulos
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment JORDI PALET MARTINEZ
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Gert Doering
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Yannis Nikolopoulos
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Brian E Carpenter
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Gert Doering
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment JORDI PALET MARTINEZ
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment JORDI PALET MARTINEZ
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Yannis Nikolopoulos
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Fred Baker
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment and dr… Fred Baker
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment hsyu
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment JORDI PALET MARTINEZ
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Gabor LENCSE
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment hsyu
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment JORDI PALET MARTINEZ
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Alexandre Petrescu
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Alexandre Petrescu
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Alexandre Petrescu
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Gert Doering
- Re: [v6ops] draft-vf-v6ops-ipv6-deployment Fred Baker