IETF Logo Mail Archive

Re: [lisp] [spring] IPv6-compressed-routing-header-crh

Dino Farinacci <farinacci@gmail.com> Thu, 18 April 2019 22:05 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 2067E1203E1; Thu, 18 Apr 2019 15:05:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.452
X-Spam-Level:
X-Spam-Status: No, score=-0.452 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, HTML_IMAGE_ONLY_20=1.546, HTML_IMAGE_RATIO_06=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 2AzPl6j8H96r; Thu, 18 Apr 2019 15:04:59 -0700 (PDT)
Received: from mail-ot1-x32c.google.com (mail-ot1-x32c.google.com [IPv6:2607:f8b0:4864:20::32c]) (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 4AEA91203CD; Thu, 18 Apr 2019 15:04:59 -0700 (PDT)
Received: by mail-ot1-x32c.google.com with SMTP id o74so2980489ota.3; Thu, 18 Apr 2019 15:04:59 -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=auDnx5WsaM6HQ5DxX70RMyjBF1c9f177iERrw+bfPbM=; b=jPAtfhNQwJQ7cooUtL2NUfp4tW9F3neYRlDnnd2HZN5SXGX/sAUEVW9oJ3kadggXRd qttbCv0A85EsfiKmDbwiiZrvIk9ZN7rFfKsMlJaKrl5y3LR1bsVWOQavz9xx8bNw2VtS v2s6v6QnQoq02aEWKZhHZFlVmWjcuBCa4T6PJuBkvS3t/4YAudTkLxkEimzR7+xud1Ej 6QfDwN2VRoPDJh8jeu6otN3TZO477CePbWLXKHF2BHJx8sSdtJlMmG3CnxHogWYAq+PM hW0O0V2kfp48/LOnZxszcqueMVvgD2MxAhikrYeEEYhJYgfktk5Oq4C2MtWn3z2+p69j 14mg==
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=auDnx5WsaM6HQ5DxX70RMyjBF1c9f177iERrw+bfPbM=; b=ono81K2jPzGOt9+Jl6L3HyUyRiclyqxPqWjF+s2shW1aLClcpt5FAdSJ8YaSaYMN0j gdU/QF0UlZ5uvpbCd4btYIA7jAMO7fZsNRxw/29/C2vKF7N7CSwr/bQHrwglscqLMv/p 9QngqHlsNwz0aho6VtoKfyCfWOeEiQTRaFc7Q7t3ed5jzg79YBG9iChexzt0YPehJgmU pwaUhvNUFaMNMBYJr3n+EiSoctOeHC3I9HGWMccMzpttvd73lzwcnL0Q4JYba0pskk9m zXXQ2TgV/7VpFYKgN9Oy7mPOBC1iSmVPRKeHrDC+SlvSJ9FXh8xdfpyOSjY5A9sRAFgA Hocw==
X-Gm-Message-State: APjAAAX1mTGMSNem0aWLc5JnjmyAkjfkQJhYSn0iWwYIE9Zku8A/9TW0 FgUKJp9rgDyn9MOOV0GCWtA=
X-Google-Smtp-Source: APXvYqyq0k7ipPb7MUDQQwroFTz27J9wYmQNynWIhrb6gKbrX5ERWcDGwl9TRjIMYKhfqL+V++tYdQ==
X-Received: by 2002:a9d:5b7:: with SMTP id 52mr100558otd.279.1555625098554; Thu, 18 Apr 2019 15:04:58 -0700 (PDT)
Received: from dino-macbook.attlocal.net (adsl-108-94-1-135.dsl.pltn13.sbcglobal.net. [108.94.1.135]) by smtp.gmail.com with ESMTPSA id l49sm1206288otc.19.2019.04.18.15.04.30 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 18 Apr 2019 15:04:57 -0700 (PDT)
From: Dino Farinacci <farinacci@gmail.com>
Message-Id: <1A4DFA66-D01C-4704-B81E-B1F02FC1A146@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_5684746F-2B66-4DD5-B766-141F89F3E8DA"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Thu, 18 Apr 2019 15:04:26 -0700
In-Reply-To: <CAOj+MMHTYWEhsRE9P8AO-1OQHX7VyUUoV=VEzHSuv5f-MBPFRA@mail.gmail.com>
Cc: Tom Herbert <tom@herbertland.com>, Ron Bonica <rbonica@juniper.net>, Gyan Mishra <hayabusagsm@gmail.com>, SPRING WG <spring@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "lisp@ietf.org list" <lisp@ietf.org>
To: Robert Raszuk <robert@raszuk.net>
References: <A881B89B-5E72-40CD-81F3-50396958A554@cisco.com> <BYAPR05MB4245D3F821D84847549FB6DAAE5A0@BYAPR05MB4245.namprd05.prod.outlook.com> <CA+b+ERmo9cPgCtnDgvkqNkFiLXdOJikWRLOKXM9NQfbNtJ__Zg@mail.gmail.com> <CAO42Z2yKmWub+maw4oVzaEY4HoHVszwOo4FQNCHT0uVkKFNwRw@mail.gmail.com> <CA+b+ERk+UiXg5Vtv-2kshkJ9VQMpMF22deFpKfGeMmqbBE9QtA@mail.gmail.com> <CAO42Z2yPi6wb85jh5es3feboJ5fOhr+iS8OraPjLD-rKTkNSQg@mail.gmail.com> <CAOj+MMHXWsXbBmByy8TWNfAWm0fKuiN6BDdGLzBgN7GRHkz+1A@mail.gmail.com> <CALx6S34FPPq9R=RAxhnPJRHT8z07htnC8banLkL2gU94Bz61hQ@mail.gmail.com> <CAO42Z2z+4JhObAktyd0KrULdwcrSkiFOD4cOVPt0QeVdHVES9A@mail.gmail.com> <CALx6S35Xnymc3oSKOX68bmtuWTH_6_Cd10FwjOd0db9TXVGp8Q@mail.gmail.com> <CAOj+MMG79BeMy2HgeS0WFs8+ZZzpNG77M8E7A4zbDjjKs7wG3Q@mail.gmail.com> <BYAPR05MB4245D2964D8F90A3A76356C0AE2A0@BYAPR05MB4245.namprd05.prod.outlook.com> <46DF565F-9A1A-4247-9A05-DE04396C8F5A@gmail.com> <BYAPR05MB4245A7C3E215FF0028FE9B06AE260@BYAPR05MB4245.namprd05.prod.outlook.com> <CAOj+MMGhU3bJtfQ4QjCeFiFpj+XkEhjnvU0MgO9bhNEvERN7Ew@mail.gmail.com> <BN7PR05MB424378EE1287B03467E2B4CAAE260@BN7PR05MB4243.namprd05.prod.outlook.com> <CAOj+MMFHTUMrmcNuHirnvO100pgtV1n+3HBCASSmx5=f_1ApWQ@mail.gmail.com> <CALx6S378oLyMnTns7VX8J9S4PfD4Lcwr_0__4ctEA=wptYsRuQ@mail.gmail.com> <CAOj+MMHTYWEhsRE9P8AO-1OQHX7VyUUoV=VEzHSuv5f-MBPFRA@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/ZHHWwHnjvILcUbnPDGqpwMXa8kQ>
Subject: Re: [lisp] [spring] IPv6-compressed-routing-header-crh
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, 18 Apr 2019 22:05:01 -0000

> Yes this is true - any mapping can be used to express much more then topological information. See LISP as example :) 

With respect to the data-plane, the ELP (Explicit Locator Path, defined in RFC8060 and use-cases in draft-ietf-lisp-te) RLOC-record:



The L-bit, when set, means that Reencap Hop is routable by the underlay (an RLOC). When 0, a mapping system lookup can be performed to get the RLOC. Hence, doing what Tom commented on.

Note this format above is in the *control-plane* and each node along the segment-route(LOL)/reencapsulation path has the ELP stored apriori.

My demo of SR using the LISP mapping system, these ELP formatted records are used and registered in the mapping system. They are registered with L-bit set to 1 and the AFI=2 (an IPv6 RLOC).

But note, if you used this in the control-plane, there would be no packet overhead because the destination address used to find these ELP paths. The authors of SR already know this.

FYI,
Dino

v2.23.0 | Report a Bug | By Email