Re: [lisp] [Ila] LISP for ILA

Dino Farinacci <> Tue, 06 March 2018 01:00 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B985912D7F4; Mon, 5 Mar 2018 17:00:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Status: No, score=-2.7 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_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id RRGIn2007pLT; Mon, 5 Mar 2018 17:00:07 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4001:c0b::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 7D7F11241F5; Mon, 5 Mar 2018 17:00:07 -0800 (PST)
Received: by with SMTP id v194so12594021itb.0; Mon, 05 Mar 2018 17:00:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=AJpOXmKywdoM4FKDyRyDRAdfF3pOYhFMVEAcmQHwJ/c=; b=L0kHIVgW38Kho4LmEICmSq8pP4rSUuuWtI4rI8aE688Ig2dAmZh8CHRpAUBorptT+Q JzAZELZN/DHw49SPFmpRVY6qkILylZ3hll1DOApwxGLB8txSvOeAyKtS9qzW2/LxZCuX uUX0u7VKzr9I1bYzG80NAIgwNnJSA6XP28mPWheE76bS3scx3IV9HAzI1gTKKb2w4R/F 2EWISQOweyJwyM07do9LAbZouIHqYLpV6mhuEhWc+4SLoEqAOmpORBNYE6BGHVCyyjOl C7GnPzViJ0OkYDlxSiPS/9L5bn4rFmOWMcGJquq6dFyC92+05xaq6fyc0XB9xJSvd7dQ 66SA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=AJpOXmKywdoM4FKDyRyDRAdfF3pOYhFMVEAcmQHwJ/c=; b=uFRpnYEVXkHSsFvAoURXYHAd2uQSHD3UsMgdDyQEwih0xwD87n4RzIBl8Ljm27V7Ef zY8BIiTOVqQIV5zM4UOA1soX4PTHLHc+kz+duxflXAYFN9fn0TA7rsNCq9eA7I9EfNzo XdJWuYXFWMv702yAfdEe3tJ54FPOKk/huZ43R5ja3/nU5XP5AptQ4qpNpWnHnD+Vc9HD LPoxSwP/LTtyoxdqE3mTGAzyNxmEfLP05dnM36DDDOomX9uERNxVsZ8qM3SCt+REJCdW p9N1BYUubaXB4gg7euA6b05kBQfH1Xth7JKrJBr5t4Wheup+C10MFT+7fQhQ6PFZe5eI igHg==
X-Gm-Message-State: AElRT7FAGvTBPdEMev6OzZgUM6TMjk5tGchyHfQgT6HjPmOSbpcLk3mS 85XIwFqDGnTFFSGwYL8j1hQ=
X-Google-Smtp-Source: AG47ELvE9fCLNgEYEDxotwbS3Pr15yz4JsIW0iqRw6rCQytP4lsNdrxA5+8RA3UqcM8bip+yLAia/Q==
X-Received: by with SMTP id k62mr16465558ith.134.1520298006855; Mon, 05 Mar 2018 17:00:06 -0800 (PST)
Received: from ( []) by with ESMTPSA id p194sm5615031itp.34.2018. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 05 Mar 2018 17:00:06 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
From: Dino Farinacci <>
In-Reply-To: <>
Date: Mon, 05 Mar 2018 17:00:03 -0800
Cc: "Alberto Rodriguez Natal (natal)" <>, Fabio Maino <>, "" <>, "" <>, Albert Cabellos <>, "Vina Ermagan (vermagan)" <>
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <>
To: Tom Herbert <>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <>
Subject: Re: [lisp] [Ila] LISP for ILA
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: Tue, 06 Mar 2018 01:00:09 -0000

> Looking at the map-reply message format, I am concerned about its
> size. By my count, it's 40 bytes to provide one record with one
> locator where record and locator are 8 bytes. If we need to scale a
> system to billions of nodes this overhead could be an issue even if
> it's the control plane. Is there any plan to have a compressed version
> of this. For instance ,if there is only one RLOC returned wouldn't the
> priorities and weights be useless?

My comment about this spec is that you really don’t need a LCAF format to format the addresses. You can use AFI=2 and use IPv6 format. That will reduce the size.

But if you start compressing out fields, reality will set in and new features will be added and you’ll be back where we started. You want to multi-home, don’t you?