Re: [v6ops] Thoughts about wider operational input
Joe Maimon <jmaimon@jmaimon.com> Wed, 30 March 2022 15:56 UTC
Return-Path: <jmaimon@jmaimon.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 6A9BE3A1011; Wed, 30 Mar 2022 08:56:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 6Jhi2-Lfgdiu; Wed, 30 Mar 2022 08:55:59 -0700 (PDT)
Received: from smtp.chl.com (smtp.ttec.chl.com [216.222.148.102]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0EC2C3A101D; Wed, 30 Mar 2022 08:55:56 -0700 (PDT)
Received: from [216.222.150.100] (joe.jmaimon.com [216.222.150.100]) by smtp.chl.com (8.13.6/8.13.6) with ESMTP id 22UFtrKK014634; Wed, 30 Mar 2022 10:55:54 -0500
To: "Ackermann, Michael" <MAckermann=40bcbsm.com@dmarc.ietf.org>, JORDI PALET MARTINEZ <jordi.palet=40consulintel.es@dmarc.ietf.org>, v6ops list <v6ops@ietf.org>
References: <52661a3d-75dc-111a-3f23-09b10d7cb8d4@gmail.com> <A72CDDDB-CDCE-4EAF-B95E-997C764DB2C4@gmail.com> <9175dc32-45c1-e948-c20a-3bcc958b77b9@gmail.com> <YjmJQMNgnJoSInUw@Space.Net> <D75EF08F-6A41-41B2-AFB2-649CBCC1D83E@consulintel.es> <CAPt1N1nRnYUFA=yyJHx6t52yqWbmcd2Tf1H8gQuCZBd3Q3VqJw@mail.gmail.com> <7F4AEB43-4B24-4A21-AE9D-3EB512B98C46@consulintel.es> <8fac4314b8244ba6b33eea68694296d0@huawei.com> <9A13E47B-75D0-443F-9EE9-D2917ACB2D0F@consulintel.es> <CAO42Z2xUG+BXj+VQpajed9aGjH+q-HR7RX7C-T4DsTbouz7xWQ@mail.gmail.com> <F6A90BBF-7F44-403E-960A-8F756353B562@chinatelecom.cn> <B49417F7-3EFB-4A4D-9D1A-0D21574EA4F2@consulintel.es> <DM6PR14MB31782C88A190259EE4B8C6B0D71F9@DM6PR14MB3178.namprd14.prod.outlook.com>
From: Joe Maimon <jmaimon@jmaimon.com>
Message-ID: <62447D91.2060001@jmaimon.com>
Date: Wed, 30 Mar 2022 11:56:01 -0400
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40
MIME-Version: 1.0
In-Reply-To: <DM6PR14MB31782C88A190259EE4B8C6B0D71F9@DM6PR14MB3178.namprd14.prod.outlook.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/w5AtGnQu_3prJm-3G1oLOAOXwPs>
Subject: Re: [v6ops] Thoughts about wider operational input
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, 30 Mar 2022 15:56:05 -0000
Ackermann, Michael wrote: > This message was sent securely using Zix® > <http://www.zixcorp.com/get-started/> > > > Great points Jordi! > > IMHO, the biggest problem is #2 (appropriately designated 😊) > > This is very old thinking and Security professionals will say this is > no longer a good idea for any security reason. But yet this > thinking persists. To the extent that we can educate these thoughts > away, and make enterprises realize that NATs are not desirable, I > believe that would be effective. > > Thanks > > Mike > I dont see any mention that Enterprises like abstraction of addressing that places them in control of it, not any vendor or even some external standards body that may or may not have their interests in mind and that they may or may not have any interest in participating. NAT is indeed a security layer, because it fails closed and requires explicit permission to allow traffic. Enterprises like that. You will not succeed in educating Enterprises why NAT's are undesirable until your understand the reasons they desire them. Joe > *From:* v6ops <v6ops-bounces@ietf.org> *On Behalf Of * JORDI PALET > MARTINEZ > *Sent:* Wednesday, March 30, 2022 3:25 AM > *To:* v6ops list <v6ops@ietf.org> > *Subject:* Re: [v6ops] Thoughts about wider operational input > > [External email] > > I bet that in the majority of the cases for enterprises willing to > continue using NAT with IPv6, the reasons are: > > 1. We are using to it in IPv4, why changing it in IPv6 (mental change > when adopting IPv6 = lack of proper training). > 2. Wrong perception that NAT (and hiding addresses) = security. > 3. Vendors of equipment continue to lie and say “yes” to customers > when they ask for NAT66, even if they are supporting an > experimental protocol (NPT) and they don’t tell customers “yes we > have it, but note that it is an experimental protocol, so not > proven interoperability and you’re exposed to consequences than we > don’t know yet with apps or services, and same problems as in NAT44”. > > Regards, > > Jordi > > @jordipalet > > El 30/3/22, 8:32, "v6ops en nombre de Chongfeng Xie" > <v6ops-bounces@ietf.org <mailto:v6ops-bounces@ietf.org> en nombre de > xiechf@chinatelecom.cn <mailto:xiechf@chinatelecom.cn>> escribió: > > Hi,Mark, > > Some enterprises do not want to expose their real address in the > network to the outside, so they will use NAT, whether nat44 or nat64 > or even nat66 in the future. Therefore, NAT may always exist with the > needs of customers. > > The technology itself is not right or wrong. It is inappropriate to > directly state whether a technology is good or bad, but whether the > technology is appropriate for specific scenarios. You said there was a > lot of issues with IPv6+NAT,under what scenario? What's are the > issues ? Is it a stateless IPv6+NAT or a stateful IPv6+NAT? > > Thanks > > Chongfeng > > 2022年3月30日 上午11:22,Mark Smith <markzzzsmith@gmail.com > <mailto:markzzzsmith@gmail.com>> 写 道: > > On Wed, 23 Mar 2022, 01:55 JORDI PALET MARTINEZ, > <jordi.palet=40consulintel.es@dmarc.ietf.org > <mailto:40consulintel.es@dmarc.ietf.org>> wrote: > > Hi Eduard, > > What I meant is that I will like to avoid the issues that NAT > creates for apps. We must aim for something better. > > This. > > IPv6+NAT creates a lot of the issues that IPv4+NAT does, so why > bother deploying IPv6 when you've already got the equivalent via > IPv4 today? > > People need to understand why enterprises go to the expense of > deploying technologies. > > Technology is a means to an end, not the end itself. Technology in > business either saves money or makes money for the business. > > Enterprises in the 1990s didn't really deploy IPv4, they deployed > global email and WWW access. Deploying IPv4 was the means to > reaching those ends, because IPv4 underpinned them. > > So the questions to think about in the context of businesses and > enterprises and IPv6 are: > > - What business problem does or can IPv6 solve better than > existing IPv4? > > - IPv6 is the technology means to an end, so what is or are the > ends that are of value to a business, where IPv6 is the better > underpinning technology than IPv4 to reach those ends? > > - How can deploying IPv6 save or make money for a business? > > Regards, > > Mark. > > On the other side, using an experimental protocol for > production networks, in my opinion is a big “NO”. > > Regards, > > Jordi > > @jordipalet > > El 22/3/22, 13:04, "v6ops en nombre de Vasilenko Eduard" > <v6ops-bounces@ietf.org <mailto:v6ops-bounces@ietf.org> en > nombre de vasilenko.eduard=40huawei.com@dmarc.ietf.org > <mailto:40huawei.com@dmarc.ietf.org>> escribió: > > Hi Jordi, > > I understand the desire to fix broken things. (I doubt it is > possible) > > But why NPT+ULA is not enough for MHMP now? > > It is very similar to what Enterprises and small businesses > have now. > > They would be happy. > > Eduard > > *From:* v6ops [mailto:v6ops-bounces@ietf.org > <mailto:v6ops-bounces@ietf.org>] *On Behalf Of *JORDI PALET > MARTINEZ > *Sent:* Tuesday, March 22, 2022 12:34 PM > *To:* v6ops@ietf.org <mailto:v6ops@ietf.org> > *Subject:* Re: [v6ops] Thoughts about wider operational input > > You’re right. Let’s say it in a different way, as may be my > first email was not clear on this. > > 1.I don’t think we want again to repeat the NAT problems, so > NPT is not a valid solution for me. > > 2.I think in the future almost every site could want to be > multihomed, in some cases “n” links active, many other cases > just as a backup. > > 3.This means that renumbering is not (probably) a valid choice > in any cases. > > 4.Can we make PI work in such “huge scale” scenario? > > 5.Can source-address forwarding work and solve all that, or we > need that and/or something else. > > Only if we solve this, organizations could learn that NAT with > IPv6 is not the solution, but something better that provides > the same results, and no need to have “private” addresses, > because the way NAT is offering a “different” addressing > inside and outside is not NAT per-se, but statefull firewalling. > > Regards, > > Jordi > > @jordipalet > > El 22/3/22, 10:27, "v6ops en nombre de Ted Lemon" > <v6ops-bounces@ietf.org <mailto:v6ops-bounces@ietf.org> en > nombre de mellon@fugue.com <mailto:mellon@fugue.com>> escribió: > > Is it really hncp that we needed here? I think the key tech > we need is source-address-based forwarding, and babel i think > has delivered that. Granted, getting that into soho routers is > a problem. > > On Tue, Mar 22, 2022 at 10:11 JORDI PALET MARTINEZ > <jordi.palet=40consulintel.es@dmarc.ietf.org > <mailto:40consulintel.es@dmarc.ietf.org>> wrote: > > Maybe the terminology is not the most appropriate and we > should talk about "organizations", because there are many > types of networks that have the same problem and those are > not enterprises (such as government sites, NGOs, etc.). > > The problem is the same regardless of the "size" of the > organization. The difference is that "today" most SMEs > don't have that problem because they don't have PI, but it > may turn the same when they realize that not being PI have > renumbering issues if changing the ISP. Of course, again, > if we talk about a "small" SME, then may not be an issue, > they only have 40 or 50 devices to renumber (your mileage > will vary), not easy but not "terrible". > > On the rest of Gert comments, definitively I agree, and > specially on our big mistake not working further on HNCP. > > Regards, > Jordi > @jordipalet > > > > El 22/3/22, 9:31, "v6ops en nombre de Gert Doering" > <v6ops-bounces@ietf.org <mailto:v6ops-bounces@ietf.org> en > nombre de gert@space.net <mailto:gert@space.net>> escribió: > > Hi, > > On Tue, Mar 22, 2022 at 11:42:12AM +1300, Brian E > Carpenter wrote: > > I agree with Jordi that multihoming is a genuine > impediment. What isn't generally realised is that it's a > problem of scale when considering at least 10,000,000 > enterprises, much more than it's a problem of IPv6 itself. > > What is "an enterprise"? > > My stance on this is that for "largely unmanaged SoHo > networks" - which > could be called "small enterprise" - dual-enduser-ISP > with dual-/48 or > NPT66 gets the job done in an easy and scalable way > (HNCP would have > been great, but IETF politics killed it). > > "Enterprise that truly need their own independent > fully managed network > with multiple ISP uplinks and fully routed independent > address space" > are probably way less than 10 million... > > Half of them do not want Internet access anyway, just > access to their > ALGs that will do the filtering and TLS inspection and > everything, and > then out to the Internet as a new TCP session (= could > be done with > DMZ islands of upstream-provider-allocated space just > fine). > > > We need to work on our marketing regarding > multihoming. "What is it that > you get, what is the cost, which of the variants do > you want, and why...?" > > Gert Doering > -- NetMaster > -- > have you enabled IPv6 on something today...? > > SpaceNet AG Vorstand: Sebastian v. Bomhard, > Michael Emmer > Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. > Grundner-Culemann > D-80807 Muenchen HRB: 136055 (AG Muenchen) > Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 > > _______________________________________________ > v6ops mailing list > v6ops@ietf.org <mailto:v6ops@ietf.org> > https://www.ietf.org/mailman/listinfo/v6ops > > > > ********************************************** > IPv4 is over > Are you ready for the new Internet ? > http://www.theipv6company.com <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 <mailto:v6ops@ietf.org> > https://www.ietf.org/mailman/listinfo/v6ops > > _______________________________________________ v6ops mailing > list v6ops@ietf.org <mailto:v6ops@ietf.org> > https://www.ietf.org/mailman/listinfo/v6ops > > > ********************************************** > IPv4 is over > Are you ready for the new Internet ? > http://www.theipv6company.com <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 <mailto:v6ops@ietf.org> > https://www.ietf.org/mailman/listinfo/v6ops > > > ********************************************** > IPv4 is over > Are you ready for the new Internet ? > http://www.theipv6company.com <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 <mailto:v6ops@ietf.org> > https://www.ietf.org/mailman/listinfo/v6ops > > _______________________________________________ > v6ops mailing list > v6ops@ietf.org <mailto:v6ops@ietf.org> > https://www.ietf.org/mailman/listinfo/v6ops > > _______________________________________________ v6ops mailing list > v6ops@ietf.org <mailto:v6ops@ietf.org> > https://www.ietf.org/mailman/listinfo/v6ops > <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. > > > The information contained in this communication is highly confidential > and is intended solely for the use of the individual(s) to whom this > communication is directed. If you are not the intended recipient, you > are hereby notified that any viewing, copying, disclosure or > distribution of this information is prohibited. Please notify the > sender, by electronic mail or telephone, of any unintended receipt and > delete the original message without making any copies. > > Blue Cross Blue Shield of Michigan and Blue Care Network of Michigan > are nonprofit corporations and independent licensees of the Blue Cross > and Blue Shield Association. > > > > This message was secured by *Zix <http://www.zixcorp.com>^® *. > > > _______________________________________________ > v6ops mailing list > v6ops@ietf.org > https://www.ietf.org/mailman/listinfo/v6ops
- [v6ops] Thoughts about wider operational input Fred Baker
- Re: [v6ops] Thoughts about wider operational input JORDI PALET MARTINEZ
- Re: [v6ops] Thoughts about wider operational input Brian E Carpenter
- Re: [v6ops] Thoughts about wider operational input Nick Buraglio
- Re: [v6ops] Thoughts about wider operational input Nick Buraglio
- Re: [v6ops] Thoughts about wider operational input Fred Baker
- Re: [v6ops] Thoughts about wider operational input Fred Baker
- Re: [v6ops] Thoughts about wider operational input Brian E Carpenter
- Re: [v6ops] Thoughts about wider operational input Bob Hinden
- Re: [v6ops] Thoughts about wider operational input Bjoern A. Zeeb
- Re: [v6ops] Thoughts about wider operational input Gert Doering
- Re: [v6ops] Thoughts about wider operational input Vasilenko Eduard
- Re: [v6ops] Thoughts about wider operational input Gert Doering
- Re: [v6ops] Thoughts about wider operational input JORDI PALET MARTINEZ
- Re: [v6ops] Thoughts about wider operational input JORDI PALET MARTINEZ
- Re: [v6ops] Thoughts about wider operational input Ted Lemon
- Re: [v6ops] Thoughts about wider operational input JORDI PALET MARTINEZ
- Re: [v6ops] Thoughts about wider operational input Toerless Eckert
- Re: [v6ops] Thoughts about wider operational input Gert Doering
- Re: [v6ops] Thoughts about wider operational input Gert Doering
- Re: [v6ops] Thoughts about wider operational input Xipengxiao
- Re: [v6ops] Thoughts about wider operational input Toerless Eckert
- Re: [v6ops] Thoughts about wider operational input JORDI PALET MARTINEZ
- Re: [v6ops] Thoughts about wider operational input Philip Homburg
- Re: [v6ops] Thoughts about wider operational input Ted Lemon
- Re: [v6ops] Thoughts about wider operational input Vasilenko Eduard
- Re: [v6ops] Thoughts about wider operational input Vasilenko Eduard
- Re: [v6ops] Thoughts about wider operational input Vasilenko Eduard
- Re: [v6ops] Thoughts about wider operational input Toerless Eckert
- Re: [v6ops] Thoughts about wider operational input Ackermann, Michael
- Re: [v6ops] Thoughts about wider operational input JORDI PALET MARTINEZ
- Re: [v6ops] Thoughts about wider operational input JORDI PALET MARTINEZ
- Re: [v6ops] Thoughts about wider operational input Gert Doering
- Re: [v6ops] Thoughts about wider operational input Gert Doering
- Re: [v6ops] Thoughts about wider operational input Gert Doering
- Re: [v6ops] Thoughts about wider operational input Vasilenko Eduard
- Re: [v6ops] Thoughts about wider operational input Vasilenko Eduard
- Re: [v6ops] Thoughts about wider operational input Vasilenko Eduard
- Re: [v6ops] Thoughts about wider operational input Gert Doering
- Re: [v6ops] Thoughts about wider operational input JORDI PALET MARTINEZ
- Re: [v6ops] Thoughts about wider operational input Vasilenko Eduard
- Re: [v6ops] Thoughts about wider operational input Nick Buraglio
- Re: [v6ops] Thoughts about wider operational input Vasilenko Eduard
- Re: [v6ops] Thoughts about wider operational input Gert Doering
- Re: [v6ops] Thoughts about wider operational input Gert Doering
- Re: [v6ops] Thoughts about wider operational input Vasilenko Eduard
- Re: [v6ops] Thoughts about wider operational input Vasilenko Eduard
- Re: [v6ops] Thoughts about wider operational input Gert Doering
- Re: [v6ops] Thoughts about wider operational input JORDI PALET MARTINEZ
- Re: [v6ops] Thoughts about wider operational input Simon
- Re: [v6ops] Thoughts about wider operational input Nick Buraglio
- Re: [v6ops] Thoughts about wider operational input Gert Doering
- Re: [v6ops] Thoughts about wider operational input Brian E Carpenter
- Re: [v6ops] Thoughts about wider operational input Nick Buraglio
- Re: [v6ops] Thoughts about wider operational input Ted Lemon
- Re: [v6ops] Thoughts about wider operational input Nick Buraglio
- Re: [v6ops] Thoughts about wider operational input Brian E Carpenter
- Re: [v6ops] Thoughts about wider operational input Brian E Carpenter
- Re: [v6ops] Thoughts about wider operational input Ted Lemon
- Re: [v6ops] Thoughts about wider operational input Nick Buraglio
- Re: [v6ops] Thoughts about wider operational input Ted Lemon
- Re: [v6ops] Thoughts about wider operational input Nick Buraglio
- Re: [v6ops] Thoughts about wider operational input Gert Doering
- Re: [v6ops] Thoughts about wider operational input Nick Buraglio
- Re: [v6ops] Thoughts about wider operational input Brian E Carpenter
- Re: [v6ops] Thoughts about wider operational input Chongfeng Xie
- Re: [v6ops] Thoughts about wider operational input Gyan Mishra
- Re: [v6ops] Thoughts about wider operational input Joe Maimon
- Re: [v6ops] Thoughts about wider operational input Gyan Mishra
- Re: [v6ops] Thoughts about wider operational input Gert Doering
- Re: [v6ops] Thoughts about wider operational input Gert Doering
- Re: [v6ops] Thoughts about wider operational input hsyu
- Re: [v6ops] Thoughts about wider operational input Vasilenko Eduard
- Re: [v6ops] Thoughts about wider operational input Scott Morizot
- Re: [v6ops] Thoughts about wider operational input Nick Buraglio
- Re: [v6ops] Thoughts about wider operational input Nick Buraglio
- Re: [v6ops] Thoughts about wider operational input Brian E Carpenter
- Re: [v6ops] Thoughts about wider operational input Joe Maimon
- Re: [v6ops] Thoughts about wider operational input Vasilenko Eduard
- Re: [v6ops] Thoughts about wider operational input Mark Andrews
- Re: [v6ops] Thoughts about wider operational input Nick Buraglio
- Re: [v6ops] Thoughts about wider operational input Mark Andrews
- Re: [v6ops] Thoughts about wider operational input Mark Andrews
- Re: [v6ops] Thoughts about wider operational input Brian E Carpenter
- Re: [v6ops] Thoughts about wider operational input Brian E Carpenter
- Re: [v6ops] Thoughts about wider operational input Daniel Woititz
- Re: [v6ops] Thoughts about wider operational input Owen DeLong
- Re: [v6ops] Thoughts about wider operational input Paolo Volpato
- Re: [v6ops] Thoughts about wider operational input Ted Lemon
- Re: [v6ops] Thoughts about wider operational input Ted Lemon
- Re: [v6ops] Thoughts about wider operational input Vasilenko Eduard
- Re: [v6ops] Thoughts about wider operational input Ackermann, Michael
- Re: [v6ops] Thoughts about wider operational input Philip Homburg
- Re: [v6ops] Thoughts about wider operational input Philipp S. Tiesel
- [v6ops] ULA precedence [Thoughts about wider oper… Brian E Carpenter
- Re: [v6ops] ULA precedence [Thoughts about wider … Nick Buraglio
- Re: [v6ops] ULA precedence [Thoughts about wider … Mark Andrews
- Re: [v6ops] ULA precedence [Thoughts about wider … Ackermann, Michael
- Re: [v6ops] Thoughts about wider operational input Paolo Volpato
- Re: [v6ops] ULA precedence [Thoughts about wider … Vasilenko Eduard
- Re: [v6ops] ULA precedence [Thoughts about wider … Vasilenko Eduard
- Re: [v6ops] ULA precedence [Thoughts about wider … Bob Hinden
- Re: [v6ops] ULA precedence [Thoughts about wider … Mark Smith
- Re: [v6ops] Thoughts about wider operational input Ackermann, Michael
- Re: [v6ops] ULA precedence [Thoughts about wider … Vasilenko Eduard
- Re: [v6ops] Thoughts about wider operational input Nick Buraglio
- Re: [v6ops] Thoughts about wider operational input Paolo Volpato
- Re: [v6ops] Thoughts about wider operational input Vasilenko Eduard
- Re: [v6ops] Thoughts about wider operational input Ackermann, Michael
- Re: [v6ops] Thoughts about wider operational input Nick Buraglio
- Re: [v6ops] Thoughts about wider operational input Ackermann, Michael
- Re: [v6ops] Thoughts about wider operational input Fred Baker
- Re: [v6ops] Thoughts about wider operational input Nalini J Elkins
- Re: [v6ops] Thoughts about wider operational input Xipengxiao
- Re: [v6ops] Thoughts about wider operational input E. Marie Brierley
- Re: [v6ops] Thoughts about wider operational input Ackermann, Michael
- Re: [v6ops] Thoughts about wider operational input Brian E Carpenter
- Re: [v6ops] Thoughts about wider operational input Ackermann, Michael
- Re: [v6ops] Thoughts about wider operational input Mark Smith
- Re: [v6ops] Thoughts about wider operational input E. Marie Brierley
- Re: [v6ops] Thoughts about wider operational input Brian E Carpenter
- Re: [v6ops] Thoughts about wider operational input E. Marie Brierley
- Re: [v6ops] Thoughts about wider operational input Chongfeng Xie
- Re: [v6ops] Thoughts about wider operational input Brian Carpenter
- Re: [v6ops] Thoughts about wider operational input JORDI PALET MARTINEZ
- Re: [v6ops] Thoughts about wider operational input nalini.elkins@insidethestack.com
- Re: [v6ops] Thoughts about wider operational input Philipp S. Tiesel
- Re: [v6ops] Thoughts about wider operational input Vasilenko Eduard
- Re: [v6ops] Thoughts about wider operational input Ackermann, Michael
- Re: [v6ops] Thoughts about wider operational input JORDI PALET MARTINEZ
- Re: [v6ops] Thoughts about wider operational input Joe Maimon
- Re: [v6ops] Thoughts about wider operational input Joe Maimon
- Re: [v6ops] Thoughts about wider operational input Fred Baker
- Re: [v6ops] Thoughts about wider operational input Ackermann, Michael
- Re: [v6ops] Thoughts about wider operational input JORDI PALET MARTINEZ
- Re: [v6ops] Thoughts about wider operational input Simon
- Re: [v6ops] Thoughts about wider operational input Joe Maimon
- Re: [v6ops] Thoughts about wider operational input Brian E Carpenter
- Re: [v6ops] Thoughts about wider operational input Brian E Carpenter
- Re: [v6ops] Thoughts about wider operational input Joe Maimon
- Re: [v6ops] Thoughts about wider operational input Joe Maimon
- Re: [v6ops] Thoughts about wider operational input Joe Maimon
- Re: [v6ops] Thoughts about wider operational input Mark Andrews
- Re: [v6ops] Thoughts about wider operational input Joe Maimon
- Re: [v6ops] Thoughts about wider operational input Simon
- Re: [v6ops] Thoughts about wider operational input Joe Maimon
- Re: [v6ops] Thoughts about wider operational input Nick Buraglio
- Re: [v6ops] Thoughts about wider operational input otroan
- Re: [v6ops] Thoughts about wider operational input Fred Baker
- Re: [v6ops] Thoughts about wider operational input Brian E Carpenter
- Re: [v6ops] Thoughts about wider operational input Vasilenko Eduard
- Re: [v6ops] Thoughts about wider operational input Joe Maimon
- Re: [v6ops] Thoughts about wider operational input Simon
- Re: [v6ops] Thoughts about wider operational input Joe Maimon
- Re: [v6ops] Thoughts about wider operational input Simon
- Re: [v6ops] Thoughts about wider operational input Ackermann, Michael
- Re: [v6ops] Thoughts about wider operational input Joe Maimon
- Re: [v6ops] Thoughts about wider operational input Mark Smith
- Re: [v6ops] Thoughts about wider operational input Mark Smith
- Re: [v6ops] Thoughts about wider operational input Simon
- Re: [v6ops] Thoughts about wider operational input Brian E Carpenter
- Re: [v6ops] Thoughts about wider operational input Xipengxiao
- Re: [v6ops] Thoughts about wider operational input Brian E Carpenter
- Re: [v6ops] Thoughts about wider operational input David Conrad
- Re: [v6ops] Thoughts about wider operational input David Conrad
- Re: [v6ops] Thoughts about wider operational input Brian E Carpenter
- Re: [v6ops] Thoughts about wider operational input Vasilenko Eduard
- Re: [v6ops] Thoughts about wider operational input JORDI PALET MARTINEZ
- Re: [v6ops] Thoughts about wider operational input JORDI PALET MARTINEZ
- Re: [v6ops] Thoughts about wider operational input Vasilenko Eduard
- Re: [v6ops] Thoughts about wider operational input Joe Maimon
- Re: [v6ops] Thoughts about wider operational input Brian E Carpenter
- Re: [v6ops] Thoughts about wider operational input Vasilenko Eduard
- Re: [v6ops] Thoughts about wider operational input Simon
- Re: [v6ops] Thoughts about wider operational input Mark Smith
- Re: [v6ops] Thoughts about wider operational input Greg Skinner
- Re: [v6ops] Thoughts about wider operational input Nick Buraglio
- Re: [v6ops] Thoughts about wider operational input Nick Buraglio
- Re: [v6ops] Thoughts about wider operational input Chris Cummings
- Re: [v6ops] Thoughts about wider operational input daveb
- Re: [v6ops] Thoughts about wider operational input Nick Buraglio
- Re: [v6ops] Thoughts about wider operational input Gert Doering
- Re: [v6ops] ULA precedence [Thoughts about wider … Nick Buraglio
- Re: [v6ops] ULA precedence [Thoughts about wider … Erik Auerswald
- Re: [v6ops] ULA precedence [Thoughts about wider … Vasilenko Eduard
- Re: [v6ops] ULA precedence [Thoughts about wider … Nick Buraglio
- Re: [v6ops] ULA precedence [Thoughts about wider … Lorenzo Colitti
- Re: [v6ops] ULA precedence [Thoughts about wider … Nick Buraglio
- Re: [v6ops] ULA precedence [Thoughts about wider … Lorenzo Colitti
- Re: [v6ops] ULA precedence [Thoughts about wider … Nick Buraglio
- Re: [v6ops] ULA precedence [Thoughts about wider … Brian E Carpenter
- Re: [v6ops] ULA precedence [Thoughts about wider … Kevin Myers
- Re: [v6ops] ULA precedence [Thoughts about wider … Lorenzo Colitti
- Re: [v6ops] ULA precedence [Thoughts about wider … Kevin Myers
- Re: [v6ops] ULA precedence [Thoughts about wider … Lorenzo Colitti
- Re: [v6ops] ULA precedence [Thoughts about wider … Vasilenko Eduard
- Re: [v6ops] ULA precedence [Thoughts about wider … Erik Auerswald
- Re: [v6ops] ULA precedence [Thoughts about wider … Erik Auerswald
- Re: [v6ops] ULA precedence [Thoughts about wider … Vasilenko Eduard
- Re: [v6ops] ULA precedence [Thoughts about wider … Mark Smith
- Re: [v6ops] ULA precedence [Thoughts about wider … Brian Carpenter
- Re: [v6ops] ULA precedence [Thoughts about wider … Erik Auerswald
- Re: [v6ops] ULA precedence [Thoughts about wider … Erik Auerswald
- Re: [v6ops] ULA precedence [Thoughts about wider … Erik Auerswald
- Re: [v6ops] ULA precedence [Thoughts about wider … Vasilenko Eduard
- Re: [v6ops] ULA precedence [Thoughts about wider … otroan
- Re: [v6ops] ULA precedence [Thoughts about wider … Vasilenko Eduard
- Re: [v6ops] ULA precedence [Thoughts about wider … Philip Homburg
- Re: [v6ops] ULA precedence [Thoughts about wider … Vasilenko Eduard
- Re: [v6ops] ULA precedence [Thoughts about wider … Philip Homburg
- Re: [v6ops] ULA precedence [Thoughts about wider … Vasilenko Eduard
- Re: [v6ops] ULA precedence [Thoughts about wider … Ted Lemon
- Re: [v6ops] ULA precedence [Thoughts about wider … Erik Auerswald
- Re: [v6ops] ULA precedence [Thoughts about wider … Erik Auerswald
- Re: [v6ops] ULA precedence [Thoughts about wider … otroan
- [v6ops] Vicious circle [ULA precedence [Thoughts … Brian E Carpenter
- Re: [v6ops] ULA precedence [Thoughts about wider … Mark Smith
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… David Farmer
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Brian Carpenter
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… David Farmer
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Ted Lemon
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Nick Buraglio
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Nick Buraglio
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… George Michaelson
- Re: [v6ops] ULA precedence [Thoughts about wider … Ted Lemon
- Re: [v6ops] ULA precedence [Thoughts about wider … Brian E Carpenter
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Brian E Carpenter
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Nick Buraglio
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Jen Linkova
- Re: [v6ops] ULA precedence [Thoughts about wider … Michael Richardson
- Re: [v6ops] ULA precedence [Thoughts about wider … Michael Richardson
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Kevin Myers
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… JORDI PALET MARTINEZ
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Kevin Myers
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Nick Buraglio
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… JORDI PALET MARTINEZ
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Nick Buraglio
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Michael Richardson
- Re: [v6ops] ULA precedence [Thoughts about wider … Mark Smith
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Kevin Myers
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Ted Lemon
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Nick Buraglio
- Re: [v6ops] ULA precedence [Thoughts about wider … Erik Auerswald
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Simon
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Simon
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Kevin Myers
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Jen Linkova
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Kevin Myers
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Xipengxiao
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Mark Smith
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Joe Maimon
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Nick Buraglio
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Mark Smith
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Gert Doering
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Gert Doering
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Vasilenko Eduard
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Havard Eidnes
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… David Farmer
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Ted Lemon
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Vasilenko Eduard
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Nick Buraglio
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Ed Horley
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Nick Buraglio
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Vasilenko Eduard
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Michael Sweet
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Kevin Myers
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Gert Doering
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Joe Maimon
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Gert Doering
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… David Farmer
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Brian E Carpenter
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Jen Linkova
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Vasilenko Eduard
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… David Farmer
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Philip Homburg
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Mark Smith
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… David Farmer
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Ed Horley
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Ackermann, Michael
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Kevin Myers
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Brian E Carpenter
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Michael Richardson
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Michael Richardson
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Philip Homburg
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Gert Doering
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Vasilenko Eduard
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Michael Richardson
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Kevin Myers
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Nick Buraglio
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Gert Doering
- Re: [v6ops] ULA precedence [Thoughts about wider … Fred Baker
- Re: [v6ops] ULA precedence [Thoughts about wider … Ed Horley
- Re: [v6ops] ULA precedence [Thoughts about wider … Brian E Carpenter
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… David Farmer
- Re: [v6ops] ULA precedence [Thoughts about wider … Erik Auerswald
- Re: [v6ops] ULA precedence [Thoughts about wider … Fred Baker
- Re: [v6ops] ULA precedence [Thoughts about wider … Ed Horley
- Re: [v6ops] ULA precedence [Thoughts about wider … Mark Andrews
- Re: [v6ops] ULA precedence [Thoughts about wider … Michael Richardson
- Re: [v6ops] ULA precedence [Thoughts about wider … Brian E Carpenter
- Re: [v6ops] ULA precedence [Thoughts about wider … Fred Baker
- Re: [v6ops] ULA precedence [Thoughts about wider … Michael Richardson
- Re: [v6ops] ULA precedence [Thoughts about wider … Brian E Carpenter
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Georgi Stoev
- Re: [v6ops] Vicious circle [ULA precedence [Thoug… Brian E Carpenter