[lisp] Constructing Map-Replies with overlapping prefixes

Eric Rescorla <ekr@rtfm.com> Thu, 07 February 2019 02:12 UTC

Return-Path: <ekr@rtfm.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 E659D130FB8 for <lisp@ietfa.amsl.com>; Wed, 6 Feb 2019 18:12:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.041
X-Spam-Level:
X-Spam-Status: No, score=-2.041 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.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 CyvzDfCXhgfX for <lisp@ietfa.amsl.com>; Wed, 6 Feb 2019 18:12:01 -0800 (PST)
Received: from mail-lf1-x12c.google.com (mail-lf1-x12c.google.com [IPv6:2a00:1450:4864:20::12c]) (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 268DB130FB4 for <lisp@ietf.org>; Wed, 6 Feb 2019 18:12:01 -0800 (PST)
Received: by mail-lf1-x12c.google.com with SMTP id l142so7003270lfe.2 for <lisp@ietf.org>; Wed, 06 Feb 2019 18:12:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=S1QrGOgrxTM+2JjvHPt5THlnHzuLfwXRH3mtzXUQ/D0=; b=GlZnQN7uqcFXojgLYPBDhOFr7kOfCb2IkIRChDIYUr2+2DeJaLSsFHqHVIdFL1poOT wWaC6aUTJBPVEpBckhAMDXIy58XIwD37renBSRoS/mNp5EjKCJveiRsGlz4RFVuSM3u/ A8+b2fG9UdvLq+qOzi0B0N5NqQqie/sx7pg7IIzGyTn55kBY1E6L9YEFmbCmRUM5t3Jp xNlUaFtmQVWpFxOE84EnQpqe9+as787WSvLijaB+GTY8WbI8RfiYXPSdHZbATmHTcbhQ Q/gPvjVeZvuWtjefcTSvHZpf1SydVAdLrJSrgF0t1q/2xnuAe2mm2P0yRtIwDr9F+7ve Z+aA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=S1QrGOgrxTM+2JjvHPt5THlnHzuLfwXRH3mtzXUQ/D0=; b=Ujz4ojzgMnpv/xxLVEQ6j9SfLoNXJYkavHU+GGMjTtRLynFhp7rNOMo4kJm/4SUsMy KqGRYPPBol13OKEognVEEBvKHqGh28ZXkC+/BA0nlBeXLBp3i8n+MYAREDasJ/3CL5MP KGtTMHbaKSEYKSyvcGB+meLlBnX2k78yZXRbigX3jDTpuOZnYs4/++2jRplmPNqoMA0o JQbaHfvWfbt0c3GS7alkKKAbUDzIXodiV3uvR1jYoVqO6guvJp/1udr6mhALvu7iHumR 1rVL3CDG5hqKIk5VVF6uU3Kqdq1cnzU1o8f6/13HdJaF/5ElJXbT9MzAJBV6TjepqkwS 92JA==
X-Gm-Message-State: AHQUAubOUntQhD3bAa0pPNFOH42Kx3xj9xtYZyqsdAZqFecBSomTW90j 6wTV+IeBkKvbk8Ryrrw2nm8vA1VJwX7MuIyf8730yA==
X-Google-Smtp-Source: AHgI3IZacwX1UqmYgl7rtqnWVSPKSqWzY0aTpnXyjuW3LUqHf1y2HFbX2UTiGz++nrNgX57UV9emal7YSNsGCN9S+5U=
X-Received: by 2002:a19:1d87:: with SMTP id d129mr7614592lfd.106.1549505519204; Wed, 06 Feb 2019 18:11:59 -0800 (PST)
MIME-Version: 1.0
From: Eric Rescorla <ekr@rtfm.com>
Date: Wed, 06 Feb 2019 18:11:19 -0800
Message-ID: <CABcZeBOW=Vam7jxe14gFvu2+8BkQGkJH4eocxhF17ngcYv37rA@mail.gmail.com>
To: IESG <iesg@ietf.org>, draft-ietf-lisp-rfc6833bis@ietf.org, "lisp@ietf.org list" <lisp@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000ccf6a0581445e0e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/fh0MbZnqhbRoR6l2XZt5Ne7AOzc>
Subject: [lisp] Constructing Map-Replies with overlapping prefixes
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, 07 Feb 2019 02:12:03 -0000

I'm trying to piece together the algorithm in 6833-bis S 5.5
for Map-Replies. The text says:

   A Map-Reply returns an EID-Prefix with a mask-length that is less
   than or equal to the EID being requested.

So, consider the case where an MS has two mappings:

   10/8 -> ETR1
   11/8 -> ETR2

If the Map-Request is for 10.0.0.1, then I would return

   10/8 -> ETR1

Now consider what happens when I have three mappings:

   10/16   -> ETR1
   10.0.2/24 -> ETR3 // New
   11/16   -> ETR2

Now we turn to the remainder of this section:

   When an EID moves out of a LISP site [I-D.ietf-lisp-eid-mobility],
   the database mapping system may have overlapping EID-prefixes.  Or
   when a LISP site is configured with multiple sets of ETRs that
   support different EID-prefix mask-lengths, the database mapping
   system may have overlapping EID-prefixes.  When overlapping EID-
   prefixes exist, a Map-Request with an EID that best matches any EID-
   Prefix MUST be returned in a single Map-Reply message.  For instance,
   if an ETR had database mapping entries for EID-Prefixes:

I'm having trouble parsing this, but what I get out of the example
is that the Map-Response is supposed to contain the EID-prefix that
best matches the request, plus whatever exceptions would be required
to create a correct routing table. So, that would mean in the case
where the Map-Request contains 10.0.0.1, the MS would have to reply
with:

   10/16   -> ETR1
   10.0.2/24 -> ETR3 // New

The first of these is necessary to provide correct routing information
for the requested prefix and the second to avoid providing incorrect
routing information for 10.0.2.1.

Do I have this correct? It seems like the alternative is that the MS
or ETR synthesize a new, more specific prefix. Is that what's intended
instead? The example in S 5.5 suggests otehrwise, but perhaps I am
misunderstanding.

Thanks,
-Ekr