Re: [lisp] 6830bis Review (PLEASE COMMENTS)

Luigi Iannone <ggx@gigix.net> Wed, 10 January 2018 09:53 UTC

Return-Path: <ggx@gigix.net>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E3BD127077 for <lisp@ietfa.amsl.com>; Wed, 10 Jan 2018 01:53:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gigix-net.20150623.gappssmtp.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 eG7A5owujv4A for <lisp@ietfa.amsl.com>; Wed, 10 Jan 2018 01:53:14 -0800 (PST)
Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com [IPv6:2a00:1450:400c:c09::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D3C71241F8 for <lisp@ietf.org>; Wed, 10 Jan 2018 01:53:14 -0800 (PST)
Received: by mail-wm0-x231.google.com with SMTP id 141so8985110wme.3 for <lisp@ietf.org>; Wed, 10 Jan 2018 01:53:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gigix-net.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=4I4ZC2fGqWMDIcwDGzkHdY8QwIwsZUBKK7pPNLSF8wI=; b=cyXLuG9AJj7oS/UPA8cqslry8YUp83EZ298BSt3qENpExQvedljvGhUqaX/g/xyRaE IlklrgxN58M0OxRK/7lixZSp1OHDQp298KjuAveqaD8eVh2KhZVBz1AmdLVyBPAyY14n iOKH6JXDS2ExFz2/C4W7k63cTQ3+TSER4HneZqgpVTJEOiLDjLvVeSbgD8lSpfZY6FKb 6cq50WE1As9PGohLwFEdyXy9mjAIB3WkcSoIw4RwdM0dekrfEoPGm3u1IxaJ5ETKZQCR 9oa7hjo1gRE8DdMNfnNlflSdzwOzTBxsCbiIDmWbUsfqoj6qJtqX6Cg3IVK05W4YL1iM 0QUg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=4I4ZC2fGqWMDIcwDGzkHdY8QwIwsZUBKK7pPNLSF8wI=; b=PsRRx0bXDwwufwKBg8GbCQzCEN1+njsXqBV/zQG60bPh4uuPV5pz9rqz9Ro9ahWqmJ BuBVgD6wNwQtg4eim7KdhfLGLa8KyLDukPQGpM48FV20vWOH3qDN3/x00N7egtNcygXj iViTMgH8FzwYAWyECrug58NxT4/f6grWy08nTOThRY4to6clrBeWSu578X5up7JDrOTm 3bfFTgadyrAc9EjYV+gCs+fVNaDw6oo6Y3CUUckil9tM64x7DUrhSTpH+NIkscSsNfeF LbehT/0YxCGXFHjpNb8LicQB+s36B/SkjZNPY5DesESiQ4+/qBpTSfnjub2GRYTlLFgp mcQg==
X-Gm-Message-State: AKGB3mI6s2XocL+ygNGom6PDyEgy1LbDLF3wVaxFqbmaPw6wJ/0/y8Bw LzSofgyqvIRgJNa1PJ6YBn5PupqWNtY=
X-Google-Smtp-Source: ACJfBosvztxjfw3orEx4wFjiydJG0rD3e2DORQ/LDqm/yoZrqJaKdiiOcEmt7fgp/zqtYQfa00f1Mw==
X-Received: by 10.80.171.225 with SMTP id u88mr24714409edc.167.1515577992533; Wed, 10 Jan 2018 01:53:12 -0800 (PST)
Received: from ?IPv6:2001:660:330f:a4:6d04:1cfe:3b8d:cb39? ([2001:660:330f:a4:6d04:1cfe:3b8d:cb39]) by smtp.gmail.com with ESMTPSA id u21sm9165070edl.54.2018.01.10.01.53.10 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 10 Jan 2018 01:53:10 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
From: Luigi Iannone <ggx@gigix.net>
In-Reply-To: <131849F0-AA8F-440E-A75E-5E3407B182F3@gmail.com>
Date: Wed, 10 Jan 2018 10:53:07 +0100
Cc: "lisp@ietf.org list" <lisp@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <85F1B405-03CB-4DAC-9CC0-F55210FAACCA@gigix.net>
References: <599A8A3E-E291-4F8A-9461-CBE87C1A2C6F@gigix.net> <DD3BF978-9197-45FD-B448-0AFF45E31251@gigix.net> <E808D20D-368A-45E5-8672-5ED36A69E0EB@gigix.net> <131849F0-AA8F-440E-A75E-5E3407B182F3@gmail.com>
To: Dino Farinacci <farinacci@gmail.com>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/z6ZXzo_5i_yiXrvnd0hDPtuovhY>
Subject: Re: [lisp] 6830bis Review (PLEASE COMMENTS)
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: List for the discussion of the Locator/ID Separation Protocol <lisp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lisp>, <mailto:lisp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lisp/>
List-Post: <mailto:lisp@ietf.org>
List-Help: <mailto:lisp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lisp>, <mailto:lisp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jan 2018 09:53:16 -0000


> On 9 Jan 2018, at 19:00, Dino Farinacci <farinacci@gmail.com> wrote:
> 
> Brief reply.
> 
>>>>> 
>>>>> The OAM information is necessary for the data-plane. And if LISP-GPE, VXLAN, or any other data plane wants to use their own OAM or use the LISP control-plane differently, it needs to be documented in their data-planes. Hence, why this information is there.
>>>> 
>>>> Doesn’t make sense to me. That is not a reason. 
>>> 
>>> It is a reason, maybe one you don’t like, but it is a reason.
>>> 
>> 
>> The point is that in the current document there is a lot of OAM text that does not belong to the data-plane. 
> 
> The OAM mechanisms are only used for data-plane purposes and to manage the elements in the map-cache.

You just mixed up data-plane and control plane, hence, would be better move the OAM text


> It’s the only place it should go.
> 
>> 
>> 
>>>> That information can be available in another document and still be used by LISP-GPE, VxLAN, or any other data plane.
>>> 
>>> But we decided on only 2 documents. And if we put data-plane usage in a control-plane document, then we are making 6833bis like 6830.
>>> 
>> 
>> We are better organising the specifications so that they are clearer and easier to read.
> 
> 
>> 
>> 
>> [snip]
>>> 
>>>>>> You break the operational flow by opening a different point describing what is what. It makes the overall procedure unclear.
>>>>> 
>>>>> It was put there because someone commented on it. You have to tell me why you think it breaks flow. We discuss how end-systems send to EIDs. We say what EIDs are and how they are assigned to hosts. And then we move to RLOCs. It is pretty plan, simple, and straight-forward.
>>>>> 
>>>> 
>>>> Those two point would have more emphasis somewhere else. 
>>>> Where they are now they break the flow and do not provide details.
>>> 
>>> Unless you provide clear text where they should go, I’m not going to change it.
>>> 
>> 
>> Suggested to merge with previous bullet in the reply to Albert.
> 
> Sorry the references to references do not help. I want a comment to the -08 text.

Please read reply to Albert.


> 
>>> I made some minor comments but do not want to undo what David Black spent effort on and got approval for. And I certainly don’t want to repeat text as you suggested above.
>>> 
>> 
>> The text provided by Albert is very good, I will ask David to review the text again to make sure nothing has been lost.
> 
> Sorry the references to references do not help. I want a comment to the -08 text.

Please read reply to Albert.

> 
>> As I suggested in first mail: 
>> 
>> We need to keep: 1, 6, Echo-Nonce, 
>> 
>> We need to move: 2, 3, 4, 5,  RLOC-Probing
> 
> Sorry, I can’t follow these references.

Please read reply to Albert and my original review.

Thanks

L.



> 
> Dino
>