IETF Logo Mail Archive

Re: [lisp] Mirja Kühlewind's Discuss on draft-ietf-lisp-rfc6833bis-13: (with DISCUSS and COMMENT)

Dino Farinacci <farinacci@gmail.com> Thu, 13 September 2018 15:17 UTC

Return-Path: <farinacci@gmail.com>
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 C1810130DD3; Thu, 13 Sep 2018 08:17:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 dTYXYwFVEk2r; Thu, 13 Sep 2018 08:17:06 -0700 (PDT)
Received: from mail-pf1-x443.google.com (mail-pf1-x443.google.com [IPv6:2607:f8b0:4864:20::443]) (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 F0D9F130DC8; Thu, 13 Sep 2018 08:17:05 -0700 (PDT)
Received: by mail-pf1-x443.google.com with SMTP id d4-v6so2831214pfn.0; Thu, 13 Sep 2018 08:17:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=j7bXDjvc92YlBuAnw6Fcty2e6Z8f3400/9Vyro/L9Fo=; b=BwufuBKOvAw4YoE8QEt2dr4Vr72asJM+ENKczO1mJHofOFZqqI4RqoBI0dCsEe97TT a5ekTBNoHRpfbqm8BwexnZ+SPDJHM1FCO/niw76SWrUuzLdRxXFkWSXUy/WnsqnLEVFR 717wX4MtaLK/RabV+sEEI5SUZCLWlrtGZxgxhSQZoYTUUFMORWFCFp7Hx6fINNOkEVBW vEjcXRkzRCTBXwsiSI3ZWv/Sed5WswgHVSSQ8bBOYefs7iByxeTVcpieh1DCznDyae0C L2MSpl/LMllPpXcwgOdjwCqH/tqThCVAjiq6NAgNwbOrMKEyUy5+CokrKnd0jblJa8jw 6otQ==
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=j7bXDjvc92YlBuAnw6Fcty2e6Z8f3400/9Vyro/L9Fo=; b=i0Mb/Ac6oo83AXe8ptrNzLjqx6NoWGVSXDDlHl80OfQc9kqa4wI+8IQuVKMIX0gDkd ZeJgjlGwAsdEwxFNqpFBlX4ZVvlXK1C5iNFtstpJUgytqwKkHXg6JUkPfdpGxiNCJFZs rQjpw2b6TnOu7RhUeFOGt4ydPQ4u1acI771AcNeSN0ESqPuctZOYST7vs0enEN0w5IBH K+l4B0T5dYwhgN6H9cEtNv39a5KptXMgEpFRo6KGPSAWROsDAUHGQMDwAjOpsg2ocH4B PQtmaPPDQbBB9yjQr1/0h3eYosieqE3c9LI80sIo0n8gO1kUrmmjCES5R8QOkAxGyd2l JHqg==
X-Gm-Message-State: APzg51AFKT5ai94B1J2w9tmNTJlDDQIWLXJ6n6mOMPKDxa+r0tiG/zbs djtOygNm/l+VaVUdAoS0T9pfsq87
X-Google-Smtp-Source: ANB0VdYQZT0CNBwhFZ4epouj5312JMsGM3coxVhl22064x1u6EDy4rlEQ7NzT7JzWADciHat+vFUCA==
X-Received: by 2002:a62:8a4f:: with SMTP id y76-v6mr7894736pfd.233.1536851825521; Thu, 13 Sep 2018 08:17:05 -0700 (PDT)
Received: from [10.31.79.252] ([96.72.181.209]) by smtp.gmail.com with ESMTPSA id o10-v6sm8142741pfk.76.2018.09.13.08.17.03 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 13 Sep 2018 08:17:04 -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 <farinacci@gmail.com>
In-Reply-To: <18BB371C-58BB-48ED-B7D2-568412A7890F@gigix.net>
Date: Thu, 13 Sep 2018 08:17:02 -0700
Cc: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>, The IESG <iesg@ietf.org>, draft-ietf-lisp-rfc6833bis@ietf.org, lisp-chairs@ietf.org, "lisp@ietf.org list" <lisp@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <C0C3BCBC-BAAB-46BD-980A-284C9FD394C6@gmail.com>
References: <153667812809.16741.10796738054406466412.idtracker@ietfa.amsl.com> <9D08CA59-8AC4-4866-944E-98553C37E547@gmail.com> <00DCC7FC-096E-4822-A702-2EE4C70327EB@gigix.net> <0F740BE5-63AF-4D18-BD79-D7D6A352B40A@kuehlewind.net> <2A356E01-FD24-4F6E-9800-4718BCA907F8@gmail.com> <18BB371C-58BB-48ED-B7D2-568412A7890F@gigix.net>
To: Luigi Iannone <ggx@gigix.net>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/kZeTe9lGmWm-EGS3F2luBbsJk1k>
Subject: Re: [lisp] Mirja Kühlewind's Discuss on draft-ietf-lisp-rfc6833bis-13: (with DISCUSS and COMMENT)
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 13 Sep 2018 15:17:08 -0000


> On Sep 13, 2018, at 12:58 AM, Luigi Iannone <ggx@gigix.net> wrote:
> 
> Hi Dino,
> 
>> On 13 Sep 2018, at 00:03, Dino Farinacci <farinacci@gmail.com> wrote:
>> 
>>> 
>>> Actually I brought this up because there were more cases where I found that ALT knowledge is needed. If you don’t want this to be a normative reference and remove the sentence above (which I’m not sure is helpful), please also double-check all other occurrences of ALT and make sure the discussed case is also understandable without ALT knowledge.
>> 
> 
> I disagree on the approach. IMO it makes more sense to me that this document describes just the Map-Server/Map-Resolver front end. 
> How the front-end works with the actual mapping system is a matter of the specific mapping system.
> In other words, how Map-Server/Map-Resolver works with LISP-DDT should be in the LISP-DDT document. Ditto for LISP+ALT.

I can go along with this. I have wordsmithed that paragraph to not mention LISP-ALT.

> 
>> I think it should left in and we should add LISP-DDT to the paragraph. Since the two mapping transport systems that have moved forward to RFC are ALT and DDT. And I believe they should both be Normative References.
>> 
> 
> This  means two downrefs. We will need to move them to PS.
> I really do not see the need for this but YMMV.

I will keep then as Informative references. And to address Mirja’s comment about believing that a reader would need to know more about ALT and DDT, I would respond to say, that the documentation is saying that a map-server and map-resolver are last-hops/first-hops to ANY mapping database transport system. So you can treat it as a black box. The operation of these nodes are discussed in the approprorate mapping database transport systems (such as LISP-ALT and LISP-DDT).

There are also refernces to LISP-ALT (and LISP-DDT) when we have the option for xTRs to be directlry part of the mapping system. This may be a choice for LISP deployers when they want a less centralized mapping system. Again, there are just references that in this case, the xTRs are “first-hop/last-hop” nodes of these mapping database systems.

How does that sound Mirja?

Dino

> 
> Ciao
> 
> L.
>

v2.23.0 | Report a Bug | By Email