Re: [lisp] Comments to draft-boucadair-lisp-multiple-records-00

Dino Farinacci <farinacci@gmail.com> Tue, 10 October 2017 17:22 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 3B545133158 for <lisp@ietfa.amsl.com>; Tue, 10 Oct 2017 10:22:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DC_PNG_UNO_LARGO=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=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 UiEAhhzGVP8c for <lisp@ietfa.amsl.com>; Tue, 10 Oct 2017 10:22:11 -0700 (PDT)
Received: from mail-pf0-x22b.google.com (mail-pf0-x22b.google.com [IPv6:2607:f8b0:400e:c00::22b]) (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 E16561342E8 for <lisp@ietf.org>; Tue, 10 Oct 2017 10:22:10 -0700 (PDT)
Received: by mail-pf0-x22b.google.com with SMTP id b85so6754148pfj.13 for <lisp@ietf.org>; Tue, 10 Oct 2017 10:22:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=zFXX0hY8LyrXPQ7R7Ai2lgxKUVe8T6eUJy2K2lbcDtg=; b=lKt64BKncuE9kCcnn/pvt9wvX0jmahVyYZJ12oGCPX0+UARNQY/UXihVjQRjzc3jkS /jcTI1P99dAn4ICEA4Zf0su+osQT/869bOQhBqBJsPCpJP0x2sRsvVrYFOcb2EL1oeIs xGdhgW9yQBoVffxPp9lHwVpTMEFl2ELh3OWHIaiw23v7jvH6NeNoSUxPlsPIq8SijOCp hTwD12PI+cWb4IUsphD100bfWAG1DtCAvTn0QzhZrx/wxKRivPcZl7VHpFGAAIE5O9iO pCM/9r3USiDy2cJCuCwJaPnGiCKK2kQv5gKJwipd6fqcXwMQw2zBOHmvN1NRw/1NZlSd Psyg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=zFXX0hY8LyrXPQ7R7Ai2lgxKUVe8T6eUJy2K2lbcDtg=; b=ov3wTrPIAiUE65CUwvFeASMHxG9Zuwn98lgY711eJvhIdJ9IvpDoQiETMNhAKa4Xw3 PfTSlwgPWI42pC35zr3M9JPu1vcJk0yhWd5vHIp4Iyyjx5Hjouy1n1qhSqmKzghDbbyF s2LDC1i6J4EYTXstOWqAYtsSaBFKGPZXoF98alPYhIfnxjQzQwtb4at/o/IGzCbMlv68 DO165IzRUkhSRxzj0zmifKznZFWhns7gZOLM4tdh1BrRJYnYTmTRfcOJSd3SqSRokBNC 4jbkQwlxQvzQl8IiyUNokrKAp2Ma9Mc9R66RZnJn2ZPbz3CqhmupBv2GFXwUFpyRhcCu C5eQ==
X-Gm-Message-State: AMCzsaXcnbhCqBPaJ0K61R64bEt56YIppQrsXNgz6/iLXEvNtev+Eb+o bfs74sc/nLom8NmqfRKFLzo=
X-Google-Smtp-Source: AOwi7QBNFDiahSEMr5wJxveV14/MbV0Y+2TcjrzReezqvoCi1q9UsQkTX1MrZGC+Z/Rj85ePezkWkA==
X-Received: by 10.159.195.11 with SMTP id bd11mr8205518plb.58.1507656130477; Tue, 10 Oct 2017 10:22:10 -0700 (PDT)
Received: from [10.197.31.157] (173-11-119-245-SFBA.hfc.comcastbusiness.net. [173.11.119.245]) by smtp.gmail.com with ESMTPSA id r9sm25892655pfd.6.2017.10.10.10.22.08 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 10 Oct 2017 10:22:09 -0700 (PDT)
From: Dino Farinacci <farinacci@gmail.com>
Message-Id: <B225F6B3-B7FD-492C-9BD0-F5EB5FC1FEBD@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_F16BE124-119F-4749-964E-F591F52200E2"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Tue, 10 Oct 2017 10:22:10 -0700
In-Reply-To: <787AE7BB302AE849A7480A190F8B93300A051871@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
Cc: "lisp@ietf.org list" <lisp@ietf.org>
To: mohamed.boucadair@orange.com
References: <37C27B2F-AD76-4B5F-AFE6-E56D02180DD4@gmail.com> <787AE7BB302AE849A7480A190F8B93300A051871@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/BbkM8ckSo8mlXBYqtfutmZ63RGo>
Subject: Re: [lisp] Comments to draft-boucadair-lisp-multiple-records-00
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: Tue, 10 Oct 2017 17:22:13 -0000

> Hi Dino, 
> 
> Thank you for the comment. 
> 
> There is a provision in RFC6830 to support multiple RLCOs/EIDS but without specifying the behavior.

Right, I already said that.

> As you know, that RFC is crystal clear about that.

RFC6830 or your Internet Draft?

> Yes, I do think it is time to specify that behavior in the bis document.
> 
> Section 3 of draft-boucadair-lisp-multiple-records is an example of what can be considered in the bis document.

I’ll have a look at it. But what part of section 3? All the packet format descriptions are already in RFC6830. And you have this in section 3 which is semantically incorrect:



It is documented no where that a Map-Resolvers caching mappings. And if you are proposing that you need a lot more text to describe how mappings are kept up to date in the Map-Resolver. This is a major architectural change and really not sure you know the implications of it.

Map-Resolvers ONLY cache referral entries documented in the LISP-DDT RFC.

Also note, what if a Map-Request has both 10.1.1.1/32 and 10.1.0.0/16 encoded as EID records. And if the mapping system has registered 10.0.0.0/8, then does the Map-Reply contain two records to satisfy 10.1.1.1/32 AND 10.1.0.0/16, or just one EID record. And if so, how does the requestor know that the one reply record is associated with both request records or one doesn’t apply (or is not found in the mapping system).

As you can see there is a lot of text that would need to be written. Which I think is too late for RFC6833bis. That is why I asked you for text. I wanted to see how coarse versus detail your text would be and then have the WG judge if it should go in.

Then there is the practical aspect. What are you trying to accomplish with multiple EID-records in a Map-Request. Let’s start there.

Dino

> 
> Thank you.
> 
> Cheers,
> Med
> 
>> -----Message d'origine-----
>> De : lisp [mailto:lisp-bounces@ietf.org] De la part de Dino Farinacci
>> Envoyé : lundi 9 octobre 2017 18:56
>> À : lisp@ietf.org list
>> Objet : [lisp] Comments to draft-boucadair-lisp-multiple-records-00
>> 
>> Med/Christian, RFC6830 already supports multiple EID-records in both Map-
>> Requests and Map-Replies (as well as Map-Notify messages). If you think it
>> is not specified sufficiently, now is the time to add a better explanation
>> to RFC6833bis.
>> 
>> Dino
>> _______________________________________________
>> lisp mailing list
>> lisp@ietf.org
>> https://www.ietf.org/mailman/listinfo/lisp