Re: [lisp] 6830bis Review

"Joel M. Halpern" <> Mon, 15 January 2018 18:10 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6FA5B12EAF7 for <>; Mon, 15 Jan 2018 10:10:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Status: No, score=-2.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 3g_0F7cmW3Rp for <>; Mon, 15 Jan 2018 10:10:53 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 21BE812EAF5 for <>; Mon, 15 Jan 2018 10:10:53 -0800 (PST)
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0A11E4A1A09; Mon, 15 Jan 2018 10:10:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=1.tigertech; t=1516039853; bh=c2qe/U+PPlDCvZPUzC780vUfW7MphGCdMgUUvqFLjDU=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=mL765WgxyjS4gE0rsLc/e1KdQroTiKiirVU+wivIjn7WyByXGNmJCAMgjzdcpqnxs /0d4jjOZDlq3XEUKPjZCdImS945M65x6aZvLz/ZsY4HNCVzUgSF3Db+4x+KOy8i/RD A6G/xd4vZbsCSNe1eMV3H6m0/WBIcpLVt+AmTJHk=
X-Virus-Scanned: Debian amavisd-new at
Received: from Joels-MacBook-Pro.local (unknown []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPSA id C5A101C02E5; Mon, 15 Jan 2018 10:10:51 -0800 (PST)
To: Dino Farinacci <>, Luigi Iannone <>
Cc: " list" <>, Alberto Rodriguez-Natal <>
References: <> <> <> <> <> <> <> <> <> <> <> <> <> <>
From: "Joel M. Halpern" <>
Message-ID: <>
Date: Mon, 15 Jan 2018 13:10:50 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <>
Subject: Re: [lisp] 6830bis Review
X-Mailman-Version: 2.1.22
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: Mon, 15 Jan 2018 18:10:54 -0000

<chair hat on> Let's try to separate things.

1) The fact that the messages are used only between xTRs does not tell 
us whether it is control or data.
2) The manipulation of map-cache may well be control (for example, if we 
were using a push-based control mechanism then map-cache control would 
be largely control.

</chair hat on>

<chair hat off>
Personally, it looks to me like SMR is a control mechanism.  It is 
information to control the operation of the xTR.  It is not data plane 
behavior.  It is driven from and drives control behavior.

One could argue that RLOC-probes are more borderline in tha tthey 
themselves behave more like data packets.  Still, my own thought process 
is to think of them as control operations.

The actual argument that can be made is that the capabilities these 
provide could be provided by another mechanism when another data plane 
is used.  But the capability needs to exist.  Putting these mechanisms 
in the control plane document makes it much easier to have the 
discussion about the fact that the control plane needs these functions 
to be robust.
After all, there is no goal that these are completely separate and 
independent entities.  Even if it may turn out that with sufficient care 
the control plane can be used for other things.
</chair hat off>

<chair hat on>  (Yes, my hats are bouncing.)
I would really like to hear from other WG members about this.  It is the 
WGs document.  The chairs would prefer not to simply use their own 
judgment.  So to repeat Luigi's plea: speak up.
</chair hat on>


On 1/15/18 12:55 PM, Dino Farinacci wrote:
>> SMRs and RLOC-probes are control-plane features used by xTRs to be able to run the data-plane.
> They are data-plane features that use control-plane messages. No other devices sends an RLOC-probe (or SMR) then an xTR. And the elements of operation are based on the map-cache. Any manipulation of the map-cache SHOULD NOT go in 6833bis.
> Dino
> _______________________________________________
> lisp mailing list