From 547f490bd2767da84b12c09033cdbad4acff122e Mon Sep 17 00:00:00 2001 From: lkcl Date: Fri, 14 Jun 2019 14:47:53 +0100 Subject: [PATCH] --- isa_conflict_resolution/isamux_isans.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/isa_conflict_resolution/isamux_isans.mdwn b/isa_conflict_resolution/isamux_isans.mdwn index 776ef5743..759439374 100644 --- a/isa_conflict_resolution/isamux_isans.mdwn +++ b/isa_conflict_resolution/isamux_isans.mdwn @@ -210,7 +210,7 @@ Second answer: conflicts can still occur in the (unregulated, custom) 48-bit space, which *could* be resolved by ISAMUX/ISANS as applied to the *48* bit space in exactly the same way. And the 64-bit space. -# Why not leave this to individual custom vendors to solve on a case by case basis? +# Why not leave this to individual custom vendors to solve on a case by case basis? The suggestion was raised that a custom extension vendor could create their own CSR that selects between conflicting namespaces that resolve -- 2.30.2