Re: [Pidloc] Encoding Routing in FAST

Tom Herbert <> Fri, 12 October 2018 17:20 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E26F7130E5A for <>; Fri, 12 Oct 2018 10:20:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, 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: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id imXYGFUPJu1e for <>; Fri, 12 Oct 2018 10:20:17 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::131]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id C460E130E51 for <>; Fri, 12 Oct 2018 10:20:17 -0700 (PDT)
Received: by with SMTP id l191-v6so19832254ita.4 for <>; Fri, 12 Oct 2018 10:20:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=4g+ySNdgHy/sBPIWu4eGa9wtjxmtqNrtrfJ6KY68QAs=; b=uNKzLq1ouvqmf1lvsrnGs5vBplKm4D0k6E/q5BlTwAmwmKu3/ThTYglyUyg5Zh6iy9 OYYM7GFQZM2xmZzfXlXhwLbJB5GOSYEQhVw1uAT8PFB+LYLEtH8x3JjhT4v87r9aBg6M V3xZOMXGNpMDExnEgk0yfPHdhGqizMwE+gNmdsOzkUwc0RvPUW56SZfWq9gGsqdGcG71 OxYhh2/++L++aBVB2n6uEWIATmhWASYu1mDXFyIIa4xitmIEZx1mqmiFAFlFd9k/yoU3 xc/KDld6Pw2j4LarbizYfn6A1SvjUFi0ebMzoiwU1tOzUhNGpslsSHjyYX2qL/McTzw2 fe+A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=4g+ySNdgHy/sBPIWu4eGa9wtjxmtqNrtrfJ6KY68QAs=; b=L3rhKx/z7y/0vWIvUtm5QK5VkW/YVc+Q2L9giIqwQaqAPFti5VPrwS1rp84bFnOMaM +/+j7pTEyTAKXKzrelOUp7NPg0OLvxgwNYU0q+trPDNXQS9G77UYFKKubB9gfAyrQ2Q1 YEf9c2UkIMOuKFn47Af1shAZF4McnFJhxqNqhP3xof89FebzWsLgnDnxJNysOqk52c64 o4pxLdMshoTvG4nwBKRF9unnoZFDXj+tdtnALEEummlku326P14iGO2kN0YVg5+hsgfk fK6Ug97y12XP7NBnTbcrjJN2Nf6j7XjS9q3FHBC7nYmmHgo5Ng0kipEjwBMBzbiClc9q JnFw==
X-Gm-Message-State: ABuFfoicEn61JV78Rg/M2Q7+Xbmn8a3vFktPaTGQIyntIr5ruV6A08/t 8T1lB58dZXO9b0m5Bg5y9ATZEXGzibhnTNlLaWy96qd9
X-Google-Smtp-Source: ACcGV63sMz0poWGzwtnxPlOaLc3IDI4CdufK2tukHCYYbKelfdhwFPvlFMx2gymHmXmxIxya9uxgE9QUpT+TFHZ+CXU=
X-Received: by 2002:a24:3c0a:: with SMTP id m10-v6mr5380894ita.15.1539364816692; Fri, 12 Oct 2018 10:20:16 -0700 (PDT)
MIME-Version: 1.0
References: <>
In-Reply-To: <>
From: Tom Herbert <>
Date: Fri, 12 Oct 2018 10:20:05 -0700
Message-ID: <>
To: Behcet Sarikaya <>
Content-Type: multipart/alternative; boundary="0000000000001441fa05780b4dae"
Archived-At: <>
Subject: Re: [Pidloc] Encoding Routing in FAST
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 12 Oct 2018 17:20:22 -0000

On Fri, Oct 12, 2018, 7:56 AM Behcet Sarikaya <>

> Hi all,
> Tom Herbert published a draft
> which describes a solution by which the client (mobile node) can send its
> locator to the sender.
> Tom defined the locator encoding for ILA and the network seems to be
> specific to ILA.
> However I believe this design can be generalized to other IdLoc protocols
> or at least the locator encoding could be reused..

Hi Behcet,

Thanks for posting and making connection.

Yes, ILA is an example. Tickets can contain other types of locators or

> Basically this draft represents a solution (ILA based) for the locator
> sharing cases mentioned in Erik's draft.

It might be a little different in that regard. FAST could encode locator
for return path in a ticket. Peer just reflects ticket and doesn't know
about locator, it's used to route packets in destination provider network.
So locators aren't actually being shared, they're transparently carried by
third parties.

Actual sharing could be done, for instance a locator as the ingress point
in a network might ambiguous enough to avoid privacy concerns. A ticket
might just contain locator (and network overlay method). In this case peers
would need to parse tickets, so the might go down path of a standardized
ticket format.


> Any comments?
> Behcet
> --
> Pidloc mailing list