Re: [lisp] Alexey Melnikov's No Objection on draft-ietf-lisp-rfc6830bis-20: (with COMMENT)

Dino Farinacci <> Thu, 27 September 2018 17:31 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E2EBD130F04; Thu, 27 Sep 2018 10:31:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 9h1hEWlJzElj; Thu, 27 Sep 2018 10:31:13 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::534]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 2C995130FA5; Thu, 27 Sep 2018 10:31:13 -0700 (PDT)
Received: by with SMTP id d19-v6so2475605pgv.1; Thu, 27 Sep 2018 10:31:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=SA3V7TKVm95jMQQzvmdxleVrFwdfZoghnlseXp8EhSM=; b=j3ybr41Td2wT7CdHO1fUBadYcKi65jJJYsdET22xmWfhTBKlkBI6Oz2ZrPWpMozDPG dnq2pq0hsxbTzR0xCKAVJHDjJujGXzu3FkOEsJGVTV4rhYsegHR9UkACuc1QDWR1T8Pk sOdZIsJBeA9UANXwvqhdU+ejkrgzCGPl+XcOAjiNI59K8oLXtW++lm3tpsFrPbIRVAea USS2CDKKHVA6II7f9vOydRJ749dVr0qFlltHgeWpmN8b3heKJcSuajgxRXo1jNVfqWaK r934U1lTsCFfMUE4MzXX/HHCMp7LsWQDIZkuXYlhW//ENZrH7JUflaMCfugyx5lort4L OCbg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=SA3V7TKVm95jMQQzvmdxleVrFwdfZoghnlseXp8EhSM=; b=e7S9f2Ic/n9ag0zvMDlbH7mfACaPwEaRniOw8WWSzefjIuypGgrs0RKxa2EgkM8rPT A6+lQR2uiJ8gUShaIR9GRQLQ7beiR91QYXIlC06LfuCKIgPvgNgXHQkTIr8tRZFUwzWl 1IKAxbwh0dmhfWdw6CxQXHIG9E+x7s4uXYeELDKstnOPyDu+bXiJWsaIA3edUTBKG4PX B77ta9nyT9+xbeOsY9/4CQ7qnReIhlz8a9Ekck4+mr2uxUWWizPQeCPUxjS42i5Xe5Xn tzOzF2wLkiPvMZIRFPxYil9nHCDeokr6AMWicE0kFJ3oq0jVdjk1KX4zazS0pZGM7pJO M4GQ==
X-Gm-Message-State: ABuFfoidpmP1BtaNaLrzKphZu9mCLnMxQ5dEjK87I6vm5DdeWym3i+Cf QCeW9IP6MdhzZUKd3Y8Nkyg=
X-Google-Smtp-Source: ACcGV61/gdhte91rxYdOwDZAfmuPMh8MydCkQdJmOi2PhfJZ1QgdbFhoo8kS1CwEnQGaYjcss4xXDA==
X-Received: by 2002:a62:4494:: with SMTP id m20-v6mr12672973pfi.205.1538069472783; Thu, 27 Sep 2018 10:31:12 -0700 (PDT)
Received: from [] ([]) by with ESMTPSA id l79-v6sm4616333pfi.172.2018. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 27 Sep 2018 10:31:12 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Dino Farinacci <>
In-Reply-To: <>
Date: Thu, 27 Sep 2018 10:31:11 -0700
Cc: The IESG <>,, Luigi Iannone <>,,
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <>
To: Alexey Melnikov <>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <>
Subject: Re: [lisp] Alexey Melnikov's No Objection on draft-ietf-lisp-rfc6830bis-20: (with COMMENT)
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: List for the discussion of the Locator/ID Separation Protocol <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 27 Sep 2018 17:31:15 -0000

> Ok, maybe this is just me, but you don't actually define how to hash these
> things, you are only talking about what needs to be covered by the hash. I
> appreciate that picking a specific hashing algorithm is probably not relevant
> for interoperability, but I feel adding a specific algorithm (as an example or
> via a pointer) would improve the document.

We decided to leave this to the implementation and is a local matter ot the encapsulator. Most implementations use a “folded XOR”. Which means XOR the set of 32-bit fields from the 5-tuple hash, then XOR the 2 16-bit quantities, then XOR the 2 bytes. Mod the number of best priority RLOCs, to give you an index to choose one.