Re: So where have all these new 6man WG people come from?

"Henderickx, Wim (Nokia - BE/Antwerp)" <wim.henderickx@nokia.com> Fri, 29 May 2020 07:32 UTC

Return-Path: <wim.henderickx@nokia.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04B963A0C5E for <ipv6@ietfa.amsl.com>; Fri, 29 May 2020 00:32:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-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=nokia.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 jR7_hs-oybtI for <ipv6@ietfa.amsl.com>; Fri, 29 May 2020 00:32:02 -0700 (PDT)
Received: from EUR04-VI1-obe.outbound.protection.outlook.com (mail-eopbgr80135.outbound.protection.outlook.com [40.107.8.135]) (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 7EE5A3A0C5A for <6man@ietf.org>; Fri, 29 May 2020 00:32:01 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=jq955LAz33zqxPR28j/UkH4QJgHW6AQp0nypihIwMlhWin/0dY2hGyYcJkxSSCbqMYV++UB18thRx8TPeLAdfZxwQW8vj3V5FNoot+2H4zFhPpkV0RFfbsHJiJAiyD/ax5y/7XG4JRlwMlpxSxEmuWAKcW09X5YUuOpxiZsrkEwZ0iiXEceTF8gILveFe7lQwpAq0wDag5HdKBHACalkeIgTJ4okkWhZ5lCsnVYgKg4Cg5UzwwtwIE/KlzD8G52olzTvjSl33QCJb8aEHUR9quz/hlV5nNMuPwvbUeiMOj0cQxDCxFFqMBA+tM330WeOlnROPVdAwiTG48ZsEJT/dg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=L3sXiPr9j9bn0onA+WEN5Dxs8bSVWEml4kzXHz8BGas=; b=hQfa5xFNMeGeDtt5/bB7eSsDngc/Iw9DSkF73bs20jGYnLzchoEzJ7h4R3Y4EfVJeQjYC7SiW5AXt9BaoOWclBDG2YzY4valOnZu7zSlGbtgCcHXERFvFQIMHKZ8tmpUFYeTna4JIpIWZ1LGoC+LPfmD0OnLYrBrWDQd12vgHAyKqt7/2jWYQZHBF8UhRnaLJcSy8uPnLHCgOD2wFWjIK5rfgL+tfeexRI3FX26E/zQbBTCV4TjB2CGKTeCC7Ab7Tvly8iNzJamUvyIaygmL8bdchiEObdRzMx6WGB4DSkigmwB4EowaIucsNkT+7oNyzuAalLerDN3X/8G9dgPoFA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=nokia.com; dmarc=pass action=none header.from=nokia.com; dkim=pass header.d=nokia.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com; s=selector1-nokia-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=L3sXiPr9j9bn0onA+WEN5Dxs8bSVWEml4kzXHz8BGas=; b=MBxhGmAQqhCUe9H8awXtIwHvr+4GfJcAZVPgxuYvIH3OObopPGCUFis/FSiZZrRg5dzGKb8VPsNEYagq2kvuVd5AZilQ0xSY5YKvQdt+mEJAT+CUPXhEQj+oog1plsvMOC+yBT7cftJZbElXMIyLOth9abv+qktwNEWmxqi7NQg=
Received: from AM0PR07MB4497.eurprd07.prod.outlook.com (2603:10a6:208:7a::20) by AM0PR07MB4786.eurprd07.prod.outlook.com (2603:10a6:208:72::16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3066.7; Fri, 29 May 2020 07:31:58 +0000
Received: from AM0PR07MB4497.eurprd07.prod.outlook.com ([fe80::75d9:62a8:8868:5119]) by AM0PR07MB4497.eurprd07.prod.outlook.com ([fe80::75d9:62a8:8868:5119%7]) with mapi id 15.20.3066.007; Fri, 29 May 2020 07:31:58 +0000
From: "Henderickx, Wim (Nokia - BE/Antwerp)" <wim.henderickx@nokia.com>
To: Andrew Alston <Andrew.Alston@liquidtelecom.com>, "Templin (US), Fred L" <Fred.L.Templin@boeing.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, 6MAN <6man@ietf.org>
Subject: Re: So where have all these new 6man WG people come from?
Thread-Topic: So where have all these new 6man WG people come from?
Thread-Index: AQHWNOJ5z4Jwz+ZBqUSskBNC6QRmfKi99nwAgAAGDACAAD1TAIAAYn6A///yAYCAAD/fgA==
Date: Fri, 29 May 2020 07:31:58 +0000
Message-ID: <8FD2A346-A31C-4A48-8E79-0478259058AB@nokia.com>
References: <CAO42Z2xDygUXTGwVunGSTMkZGMF8VePrPaXLSAJg14vAJdca5A@mail.gmail.com> <44595462-bef1-c1e9-5aed-f7a296bcac9e@gmail.com> <40f65b9fe1ee47168c59336b4415718b@boeing.com> <BCE8ACD8-4811-4CB6-A802-08DD8A9563B1@liquidtelecom.com> <A19E5E27-EC4A-4B9C-BF05-4C62952CDAFF@nokia.com> <VI1PR03MB5056C86FB130197145F119E6EE8F0@VI1PR03MB5056.eurprd03.prod.outlook.com>
In-Reply-To: <VI1PR03MB5056C86FB130197145F119E6EE8F0@VI1PR03MB5056.eurprd03.prod.outlook.com>
Accept-Language: nl-BE, en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.37.20051002
authentication-results: liquidtelecom.com; dkim=none (message not signed) header.d=none;liquidtelecom.com; dmarc=none action=none header.from=nokia.com;
x-originating-ip: [2a02:1810:350a:9600:d989:6581:572e:2205]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: cb179cff-4def-4a2f-01e9-08d803a25ef8
x-ms-traffictypediagnostic: AM0PR07MB4786:
x-microsoft-antispam-prvs: <AM0PR07MB4786EA3373D6A30B1D11EAC3838F0@AM0PR07MB4786.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:2399;
x-forefront-prvs: 04180B6720
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: UjMXJWbyNyeT59/wD/9hRi91CF/gLZ/1gTO6I98yApUGomwZ50SxYycprCX4iPcmBqLawKhNEXNHfLuvO+j/DIj8zFMpQPoDJBVL5cJYYYcpdz+p9zVusA39dEdjdjNQz1T0+zAwpGT9lHBVFdEcRvMcxO+3QPzxaRhpzbT8zn8lqlBBhaHGJLgkd2MWy9bHeRdICXPijwiSvges24aupcV5qp/TxxO7yOLZxcovglZUyeCIOunsaQHhdyJO326cvUCrqUeHHf6P289EtuXNdIQ3UyvSUrHkkd57tcoitslWN8cpAtVAgF4YqCDHCKC3blV2hXM9DHEqjBG8kqCGY9TLQXxp6QJbAg/leZ64xMqxOjULCOriXzV4s18s6pyicOAJM2VLhMBKA+bD1rHw7w==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:AM0PR07MB4497.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(4636009)(376002)(346002)(39860400002)(136003)(366004)(396003)(966005)(110136005)(71200400001)(2906002)(86362001)(6512007)(6486002)(66946007)(53546011)(6506007)(2616005)(76116006)(8676002)(36756003)(66556008)(64756008)(316002)(83380400001)(166002)(8936002)(33656002)(5660300002)(66574014)(186003)(478600001)(66476007)(66446008); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: MPFLPM7M4GicOY7PeRmfDYi854MzrmULCjLbDYw74HhGXcdRMkE8V+bXbzZnLEhkwW9apnBa8zINIxACS7QVlXzdM06Bif+eOOwLGH+8hO9Wkxpjz13YdVcx877nYkmX2edxy2T2HHSMJty/HJdEU+WfhBol4GBBxMP+40evA5rubcr7k+6wB0TDiVmROIMdoed2ft9COcETVlJwqpnQ9VCX0ZtQVZLVw9aeL3wgw8PagFKHEme/0YPH1/2CPQiRybZTxItHElNI8H5TR62bZFBe+HcMuXsJZ1km21jW5FLhtecfy3a3FLBfIWEGUySw7Pk6Z1lrn5Et+NK86DYARt0hfJGf9HJhEKrilszHRbIUs36POSqIliloBwguydq+XN765uET4tIQQorslw9VZ7uTPS99l4Flxa9RtiAyWqRYK2uaUiTcUGHpWIONRuPvk4+lBEeqRlE+mexfkvM94lvErFt1I5VlhFBORBtTx9lHq9o4nNatR/OvsuJz9dNYblHT/Mn1atpub1fJvBz9eKTU7nBliIwzdUmUhpPQks47lPhiokxADe/CI3fPGIE5
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_8FD2A346A31C4A488E790478259058ABnokiacom_"
MIME-Version: 1.0
X-OriginatorOrg: nokia.com
X-MS-Exchange-CrossTenant-Network-Message-Id: cb179cff-4def-4a2f-01e9-08d803a25ef8
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 May 2020 07:31:58.4922 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: svX5K7a6WBVpaZjrOXP7i6nv3kT0yW4whWSChVH0QtyUA8lylYI+L1/YP5JQF3xjJ0osG5xIGarjBBpJpdZDEF81iZL6P7ktAtQMZGD8ok8=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR07MB4786
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Aj_O5QV_ewgbU1bReh-LyTrSgMQ>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 May 2020 07:32:05 -0000

Andrew, RFC8663 is doing exactly the same, you route based on destination IP to the other end. Balancing will work the same way as you use the outer ipv6 header.
The tag defines the destination IP to put in the outer header and you get what you want.

It is the same with CRH, you determine the next destination IP based on the lookup of the tag. The operations are the same.

From: Andrew Alston <Andrew.Alston@liquidtelecom.com>
Date: Friday, 29 May 2020 at 07:43
To: "Henderickx, Wim (Nokia - BE/Antwerp)" <wim.henderickx@nokia.com>om>, "Templin (US), Fred L" <Fred.L.Templin@boeing.com>om>, Brian E Carpenter <brian.e.carpenter@gmail.com>om>, 6MAN <6man@ietf.org>
Subject: RE: So where have all these new 6man WG people come from?

Actually – I was expecting this reply.

And no – RFC8663 does NOT accomplish what I want.

With 8663 – tunnels have to be built – normally manually.  With CRH – I have to do precisely nothing, because the routing is done on the DA over the non-MPLS supporting nodes and its stock standard destination routing.
That means – balancing works – no need to build tunnels – no need to construct anything – its simpler, its easier and it saves me one hell of a lot of hassle.

I also point out that – we aren’t talking about one or two rings here – we can be talking about 20 -  30 -  40 rings.  So which one do I build my tunnels over?  With CRH – I don’t have to care.

Thanks

Andrew


From: Henderickx, Wim (Nokia - BE/Antwerp) <wim.henderickx@nokia.com>
Sent: Friday, 29 May 2020 07:33
To: Andrew Alston <Andrew.Alston@liquidtelecom.com>om>; Templin (US), Fred L <Fred.L.Templin@boeing.com>om>; Brian E Carpenter <brian.e.carpenter@gmail.com>om>; 6MAN <6man@ietf.org>
Subject: Re: So where have all these new 6man WG people come from?

Andrew, RFC8663 would do the job in the same way. On top you also will need to interwork with MPLS, so you have to do all kinds of mapping and encap with CRH to interwork with CRH. RFC8663 is a much better alternative for such environment

From: ipv6 <ipv6-bounces@ietf.org<mailto:ipv6-bounces@ietf.org>> on behalf of Andrew Alston <Andrew.Alston@liquidtelecom.com<mailto:Andrew.Alston@liquidtelecom.com>>
Date: Friday, 29 May 2020 at 02:41
To: "Templin (US), Fred L" <Fred.L.Templin@boeing.com<mailto:Fred.L.Templin@boeing.com>>, Brian E Carpenter <brian.e.carpenter@gmail.com<mailto:brian.e.carpenter@gmail.com>>, 6MAN <6man@ietf.org<mailto:6man@ietf.org>>
Subject: Re: So where have all these new 6man WG people come from?

I want to add another use case to this, and it’s pretty critical to some of my thinking

Imagine this scenario –

P -> PE <ASBR> -> Metro

In the metro – you have a bunch of metro aggregation nodes – imagine them connected something like:

A <----> B <----> C<----> D
|           |           |          |
E <----> F <----> G <---->H

(I’ve included a png in case the formatting of this gets messed up)

Now – say hypothetically there are rings of building handoffs that start and stop at separate metro nodes – so a ring that goes from D through H – say 10 devicse deep.   Those devices are:


a.)     Relatively low end devices – but have sufficient forwarding capacity to carry traffic between the metro nodes

b.)    Support MPLS on V4 – do not support it on V6 (and never will, since there is on LDPv6 on those devices, and well, LDPv6 was pretty much still born anyway imho)

Now lets say I get a dual break – C to D and D to H – the only communication path left – as the path of last resort is one of the metro rings D through H – and yes – that’s a last resort – you don’t wanna be routing through those rings unless you truly have to – but – it is a path of last resort.

In an MPLS world – V4 MPLS traffic will keep flowing – via the rings – using the last resort path. In a V6 world – I have a problem.  In an V4 MPLS world – despite the fact that I do not have support SR-MPLS – I have SRMS which will allow me to actually run effective SR through the ring.  There is no SRMS that I know of for V6 – or if there is – it’s certainly never been implemented by any vendor I have ever seen.  I could static backup tunnels over the metro rings and shove my v6 traffic over those – except – that means retaining V4 on the rings.  Alternatively – I could go either SRv6 (and I’ve stated many times why that doesn’t work for me in any way shape or form) or – I can use CRH – because the intermediary devices do not have to know anything about it.

Bottom line – for those who wish to say “Qu'ils mangent de la MPLS” – guess what – this doesn’t work for us in this scenario.  CRH does.  I point out that replacing the thousands upon thousands of devices in the metro rings – also makes no logical sense whatsoever.

So basically – there are cases where – I need to be able to run functionality over islands – I need to be able to do it without V6 MPLS support – and I need those devices to be able to pass the stuff transparently.  I do not wish to be creating static tunnels – I do not to break loose based steering because it has to flow through the path of last resort – and I have zero interest in running SRv6.  CRH – works in this scenario – it’s been tested – extensively.

Thanks

Andrew



From: ipv6 <ipv6-bounces@ietf.org<mailto:ipv6-bounces@ietf.org>> on behalf of "Templin (US), Fred L" <Fred.L.Templin@boeing.com<mailto:Fred.L.Templin@boeing.com>>
Date: Friday, 29 May 2020 at 00:03
To: Brian E Carpenter <brian.e.carpenter@gmail.com<mailto:brian.e.carpenter@gmail.com>>, 6MAN <6man@ietf.org<mailto:6man@ietf.org>>
Subject: RE: So where have all these new 6man WG people come from?

Brian, please don't delete the message about a concrete use for CRH in real-world
applications (planes, trains automobiles) with backing documentation:

https://mailarchive.ietf.org/arch/msg/ipv6/g43uTZFNVyLV3y-kvrDn8Qktk1Y/<https://mailarchive.ietf.org/arch/msg/ipv6/g43uTZFNVyLV3y-kvrDn8Qktk1Y>

Thanks - Fred

> -----Original Message-----
> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Brian E Carpenter
> Sent: Thursday, May 28, 2020 1:40 PM
> To: 6MAN <6man@ietf.org<mailto:6man@ietf.org>>
> Subject: Re: So where have all these new 6man WG people come from?
>
> I have concluded two things.
>
> 1. Most people have completely failed to understand the meaning of "adoption" in the IETF WG context. I and at least one co-author
> will be submitting a draft about that to the gendispatch WG soon.
>
> 2. When I hear a choir singing, it is the same as hearing one voice.
>
> My personal decision at this point is to delete all messages about CRH adoption unread, except for the message we will soon receive
> from the WG Chairs stating the rough consensus of the adoption call, which ends on 2020-05-29. I do feel sympathy for the Chairs who
> must read and evaluate everything.
>
> Regards
> Brian Carpenter
>
> On 28-May-20 23:23, Mark Smith wrote:
> > I've been an active participant in the ipng, 6man and v6ops IETF working groups since 2002.
> >
> > While I've only been to one IETF meeting in person since then (106, sponsored by the Internet Society), over that time I've come to
> recognise the names of many of the regular and active participants in these IPv6 working groups.
> >
> > I do not recognise many of the names of people who are objecting to the 6man working group adopting the CRH draft.
> >
> > Those who have been active 6man participants in recent years would know that even an ID adopted by 6man, written by Bob and
> Brian, that had a number of revisions, didn't survive WG last call, and that occurred while Bob was (as he still is) one of the 6man WG
> chairs.
> >
> >
> > Regards,
> > Mark.
> >
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org<mailto:ipv6@ietf.org>
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
> >
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org<mailto:ipv6@ietf.org>
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org<mailto:ipv6@ietf.org>
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------