Re: Long-standing practice of due-diligence is expected - Re: [spring] CRH is not needed - Re: How CRH support SFC/Segment Endpoint option?

Andrew Alston <> Wed, 27 May 2020 20:19 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B8D233A0B38 for <>; Wed, 27 May 2020 13:19:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.795
X-Spam-Status: No, score=-1.795 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, WEIRD_PORT=0.001] autolearn=no autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id KKv7v6SOae8V for <>; Wed, 27 May 2020 13:19:08 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id D7F9E3A0B3C for <>; Wed, 27 May 2020 13:19:07 -0700 (PDT)
Received: from ( []) (Using TLS) by with ESMTP id uk-mta-240-RMuWXDQDOVOTV-XEzRZtZw-1; Wed, 27 May 2020 21:19:01 +0100
Received: from (2603:10a6:803:bf::31) by (2603:10a6:803:6a::27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3021.26; Wed, 27 May 2020 20:18:59 +0000
Received: from ([fe80::e433:d25a:4afe:ae67]) by ([fe80::e433:d25a:4afe:ae67%7]) with mapi id 15.20.3045.018; Wed, 27 May 2020 20:18:59 +0000
From: Andrew Alston <>
To: Ron Bonica <>, "Zafar Ali (zali)" <>, "Henderickx, Wim (Nokia - BE/Antwerp)" <>, Sander Steffann <>
CC: 6man <>, "" <>
Subject: Re: Long-standing practice of due-diligence is expected - Re: [spring] CRH is not needed - Re: How CRH support SFC/Segment Endpoint option?
Thread-Topic: Long-standing practice of due-diligence is expected - Re: [spring] CRH is not needed - Re: How CRH support SFC/Segment Endpoint option?
Thread-Index: AQHWNFukLM0xAvUWK0W7ISBmqA7+6qi8UGJQgABBSoA=
Date: Wed, 27 May 2020 20:18:58 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-GB
msip_labels: MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Enabled=true; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_SetDate=2020-05-27T20:07:25Z; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Method=Standard; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Name=0633b888-ae0d-4341-a75f-06e04137d755; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_SiteId=bea78b3c-4cdb-4130-854a-1d193232e5f4; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_ActionId=0a514ecf-4f95-4973-b8dc-9c9018c05d82; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_ContentBits=2
user-agent: Microsoft-MacOutlook/16.36.20041300
x-originating-ip: [2c0f:fe40:3:3:a0a9:cf99:d78c:dff0]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: a551b8d0-d997-45f0-975a-08d8027b30be
x-ms-traffictypediagnostic: VI1PR03MB3984:
x-microsoft-antispam-prvs: <>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 04163EF38A
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: V3iwNlOUOh+XyGpINya8BABWZ1zmChEotk7Jnmd2L4VZUem2HcEsGgrf0syYG23i/43t7rS2bjg4EzuwxUDtcPz418bGl/1mYxr2OALEOoMWh8OEJcS0egcectt058XOn7HpPgANQT/Q3+ipjk9LMdY1m51z4f1SCFBpbPhVd7b7tYJw+52+GAnYrUI0rAyF2JMpgWP1rMDdne1KaTQkFkvPSvKgJKQR1Pp64x+9u3qyxv3+pH7ZVGpGSoOoprMZsKBb5SoPRf9yfcbAmhumbvQvBkjROqaOY7ZRkgALZSmR9GJdARADRkaaI2WGyYWiPOyVob7vqdnsjt0LkKDcdaJi95YubrazJIgDFHvdbLi40W+n7sKevNOs+XsMnbH9gG6Vnj2Nu+NC7OMJm/tj4Q==
x-forefront-antispam-report: CIP:; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM;; PTR:; CAT:NONE; SFTY:; SFS:(4636009)(346002)(376002)(366004)(136003)(396003)(39860400002)(966005)(6486002)(33656002)(6512007)(5660300002)(110136005)(54906003)(4326008)(8936002)(36756003)(86362001)(8676002)(53546011)(6506007)(316002)(186003)(2906002)(71200400001)(478600001)(2616005)(64756008)(66446008)(166002)(83380400001)(91956017)(66476007)(66946007)(76116006)(66556008); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: GwoB6GtWS1ZIOjnEWpe1XHf5ZhOEZ7L0cZal3DHtJQV5pMVvXSK+uPPTvcOZ6hTQ+YOzoFYuFrOZtuMqt6s+ZabQ4MR5Hs+KcQW/9wuvlqeoo+2Hsz623xjk3RHWlqWoRweszwwENaFJYfOeoHuEyCCs8E8RtLCTq7xKFq5Cs5k/NosOFkvQCuuqtihur+3euTpf0RtrDt76WA0xRFi9EkSEOJ2GkrX1y5gTXrVFqCmf2CQAMHvbwqvBaQDKZDVZuvDOkxhXRajwEGz9U8iea/ohE3Y7PxbeLfhATNphEFc1KMaYTV24/moSdPeV1qvwBBgeX79kLwCvim4KPvT24S7FZOV29x3AGwIVS/sMkILb51AuttakkgV29UXAs7okIONrr+Ctrc0HcLMMO9OWBb6rINrtQa8jVSnulipdK+AjSZH7PMYeFPxnvVyO/sGLDFzD9+NLOtXvzhVGTqWxUVumPwBJBqIe7AROgso1hMGRpiCPE6FEK/iOcAB8m3cdIWsGJMMnNWbLgNXZbsA+f1Uy6Xau3Jsmfjf62ZhyD9U=
x-ms-exchange-transport-forked: True
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: a551b8d0-d997-45f0-975a-08d8027b30be
X-MS-Exchange-CrossTenant-originalarrivaltime: 27 May 2020 20:18:59.0557 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 68792612-0f0e-46cb-b16a-fcb82fd80cb1
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: rln2HQqJ7wNTgdDtFpA9DqBGjFI9tRhRpedfy1/ZmEa+R6yNdXlcdwHLftUY4xm/ig+N9EFVq3EeGPRNxoXUQX5fSPQbcRV8Cz38AcIV6JQ=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR03MB3984
X-Mimecast-Spam-Score: 0
Content-Type: multipart/alternative; boundary="_000_30C37AC0B03A45B1BE0F7E185361BBBCliquidtelecomcom_"
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 27 May 2020 20:19:11 -0000

What I find so bizarre is –

You have an multiple operators – who have clearly said – we want this – we see advantage of this.  Yet still the obstructionism and denialism continues.  The “not invented here” syndrome seems to run deep – and email after email is patently ignored from the very people who have to buy the hardware.  Reference is made to Montreal – yet the emails that stated the use cases after it went by with no response.  No technical objections ever show up – other than – we don’t want this and you haven’t given us this mythical architecture document – which was yet another non-technical response that seems so clearly designed to stall any innovation that doesn’t come from one source.

All I see from the operator perspective here is obstructionism and stalling in a desperate attempt to block anything that could be a threat to what was dreamed up by someone else.  It is almost as if there is fear that the market may choose something other than what was designed – and that fear is driving this stance of throw everything we hav against the wall and hope that something sticks – because the technical arguments have failed time and again.

This pitbull approach certainly doesn’t garner any respect for me, does not help to promote srv6 which seems to be what you want and in fact convinces me more every day that CRH is the right move – where I can built on top of it without the obstructionism of a vendor that seems to have zero interest in what mysef and other operators are clearly stating over and over again.

Yet again – I support crh – I’ve deployed CRH – CRH works for us – and we still continue to support it.  And irrespective of if it is adopted – the development of it will continue – and it will exist – the only question is – do we end up with something that the market wants outside of the auspices of the IETF – or do we end up with something that is properly standardized, because this level of obstructionism will not prevent the development.

Can we actually get back to proper technical reasoning?



From: ipv6 <> on behalf of Ron Bonica <>
Date: Wednesday, 27 May 2020 at 23:07
To: "Zafar Ali (zali)" <>om>, "Henderickx, Wim (Nokia - BE/Antwerp)" <>om>, Sander Steffann <>
Cc: 6man <>rg>, "" <>
Subject: RE: Long-standing practice of due-diligence is expected - Re: [spring] CRH is not needed - Re: How CRH support SFC/Segment Endpoint option?


Why all the passion about stopping the CRH? Does it break any existing standard? Does it consume any scarce resource?

You might argue that there is a scarcity of Routing header type numbers. But that would be a very short argument. You might argue that WG resources are scarce, and that it would take too much time to review this fourteen page document. But that argument might take more time than the document review.

In your email, below, you mention “the hardware and software investment from vendors”. Is that the scarce resource?

Vendors are not obliged to implement every draft that is adopted as a WG item. Generally, the marketplace drives product roadmaps.

If the only resource we are protecting is vendor investment, the long-standing practice of due diligence should be tempered by operator demand. The IETF should not pretend to understand operator requirements better than the operators themselves.

Why not let the marketplace decide whether it needs a CRH?


Juniper Business Use Only
From: Zafar Ali (zali) <>
Sent: Wednesday, May 27, 2020 3:19 PM
To: Henderickx, Wim (Nokia - BE/Antwerp) <>om>; Sander Steffann <>
Cc: Mach Chen <>om>; Ron Bonica <>et>; Chengli (Cheng Li) <>om>; 6man <>rg>;; Zafar Ali (zali) <>
Subject: Long-standing practice of due-diligence is expected - Re: [spring] CRH is not needed - Re: How CRH support SFC/Segment Endpoint option?

[External Email. Be cautious of content]

WH> My position remains that RFC8663 is a valid alternative and is available; I am against WG adoption of CRH.

The industry widely supports RFC8663.

Instead of denying the evidence, could the CRH authors and proponents finally understand that people are not opposed to new ideas?

People are reminding a long-standing practice of the IETF process. Before tackling a new piece of work, a working group must perform a due diligence on

  1.  whether this new work is redundant with respect to existing IETF protocols,
  2.  whether this new work would deliver genuine benefits and use-cases.

It is factually and logically clear to the working-group that the currently submitted CRH documents.

  1.  fail to position CRH with respect to existing standard widely supported by the industry (e.g., RFC8663)
  2.  fail to isolate new benefit or use-case [1]

This positive collaborative feedback was already given in SPRING.

The CRH authors may change this analysis. They need to document 1 and 2.

Why did the CRH authors not leverage this guidance in SPRING WG?

This was also the chair's guidance in Montreal [2] and Singapore [3]

All the lengthy discussions and debates on the mailing list could be avoided if only the CRH authors would tackle 1 and 2.

The CRH authors must tackle 1 and 2.

  *   This is the best way to justify a/the work from the IETF community and b/ the hardware and software investment from vendors.
  *   True benefits must be present to justify such a significant engineering investment (new data-pane, new control-plane).


Regards … Zafar