Re: [lisp] [Ila] LISP for ILA

Dino Farinacci <> Tue, 13 March 2018 19:56 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7300D1241F8; Tue, 13 Mar 2018 12:56:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Status: No, score=-2 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] 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 8XckfexS-eUW; Tue, 13 Mar 2018 12:56:46 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4003:c0f::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 18B03120047; Tue, 13 Mar 2018 12:56:46 -0700 (PDT)
Received: by with SMTP id t2-v6so905616otj.4; Tue, 13 Mar 2018 12:56:46 -0700 (PDT)
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=DiXnFXs2W7XVbupb3S+3aa9WmWDU0KtdbJthRWErrmA=; b=bvTmY2VSdGMQTLB4nPR9Esws5P0uOrW7ClSmlK169Vpjf3+DblTZI21i6ONrf6FrQP xxk+6ynL2k0b0NWCdQ9oco0zNZDqO+nFXcLJxqw/sFdtfRjC+Hl3V8gzMMBBJAuAVD+A YOtrl40+ajnnVk/wrCSy4Cy2cieM+Btkn1o65nSXmKnW+wJgZyCNHWOmF3HpYnS3I+J8 E8Aoohm1xMpWDy8UHhg919ldj57mIuQ89DVjLO+3Nf2rZcJ5rNIhc3lErXSbRFQFF5M4 pROSV/PoqiRogxPXf8Y6qGd6aD/LR9fsk1LaqooXavtPb1xfiF3XS/z12aSXveb65Zrs MZpQ==
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=DiXnFXs2W7XVbupb3S+3aa9WmWDU0KtdbJthRWErrmA=; b=TfSmkIxVmlN0PgX0t+/zHyxx7Jwdsnqc28qHB879heD0uZg0Jqp1Vnv2H6NtWLYpre fX+I5MmNhzryC/d+icjmFEf68NrE3suhnGPye0UFPFwbKUCf3H4tvDaOPR612jePkNqA 2nJAl/wAExWjd3JCVFP8KB+8Xy6O0zxi2NIWEu1UAWXcCk9sDYXU0a5XqKHTRBwhhbJK K3JCdhgKQPuE+oumGrDRRHHrgmWtu6IsrnJV0pz9nWCEw1IEt/a2LElzIKXQSoadBGBT 1VlIF3XIz3Ad3k7Pu3c3uEhheyb4Jwr5P06ZGf9VX5aoo9X/SRcusYZ5eNfPapMeJdBB SnOw==
X-Gm-Message-State: AElRT7HqaNQNYTR0vBQZ6OvU4pVZRPDIbmE6nSrajpXSkv1Xh+ChlicA bHuyjKIHFcfldhr2aaZ0y9E=
X-Google-Smtp-Source: AG47ELs9WTVlYpOmc4hxpacKLDJy/Lx+Gvj2mYK9vLF6nzEY5nm69ihu/8RBb0DPFFbJl9Td35EWNA==
X-Received: by with SMTP id p4mr1214470oth.397.1520971005424; Tue, 13 Mar 2018 12:56:45 -0700 (PDT)
Received: from ( []) by with ESMTPSA id c31sm539440otj.32.2018. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 13 Mar 2018 12:56:44 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
From: Dino Farinacci <>
In-Reply-To: <>
Date: Tue, 13 Mar 2018 12:56:43 -0700
Cc: Tom Herbert <>, Fabio Maino <>, "" <>, "" <>, Albert Cabellos <>, "Vina Ermagan (vermagan)" <>
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <> <>
To: "Alberto Rodriguez Natal (natal)" <>
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, 13 Mar 2018 19:56:47 -0000

> Using IPv6 format is something we considered while writing the draft. We went the LCAF route to have an explicit way to (1) distinguish ILA Identifiers/Locators from other addresses in the Mapping System, (2) specify the Identifier/Locator length and (3) include metadata bits. However, for simple scenarios (only ILA domain, no overlapping with non-local addresses, no multiple SIR prefixes, fixed Identifier length, no need for metadata bits, etc) things could work with AFI=2 format. If the rough consensus from the WG(s) is that a plain AFI=2 format is sufficient, we can certainly update the draft. I would like to know the opinion of others on this. 

Well identifiers can be encoded as ::<64-bits> and locators can be encoded as a regular prefix (leading bits and mask-length).

I have been running with some ILA addresses in my mapping system for a while now. I wanted to show Tom that it could be done easily. What I did was register a 128-bit EID which was the SIR-prefix plus identifier which mapped to a 128-bit RLOC that contained high-order bits as the routable locator and low-order bits as the identifier. I realize this is a bit redundant, but it could be done with no protocol or implementation changes.