IETF Logo Mail Archive

Re: [Pidloc] Encoding Routing in FAST

Tom Herbert <tom@quantonium.net> Mon, 15 October 2018 15:14 UTC

Return-Path: <tom@quantonium.net>
X-Original-To: pidloc@ietfa.amsl.com
Delivered-To: pidloc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C97F130EC2 for <pidloc@ietfa.amsl.com>; Mon, 15 Oct 2018 08:14:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=quantonium-net.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 hMXSEqJXB0Vl for <pidloc@ietfa.amsl.com>; Mon, 15 Oct 2018 08:14:19 -0700 (PDT)
Received: from mail-io1-xd33.google.com (mail-io1-xd33.google.com [IPv6:2607:f8b0:4864:20::d33]) (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 8D531130EB0 for <pidloc@ietf.org>; Mon, 15 Oct 2018 08:14:19 -0700 (PDT)
Received: by mail-io1-xd33.google.com with SMTP id l25-v6so14494331ioj.0 for <pidloc@ietf.org>; Mon, 15 Oct 2018 08:14:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quantonium-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=p0rhChWworyaPMLQhvXbAbUx7Z4g8eo8kx7QdcwXZSo=; b=OqO4pRXlUAcVWppIvIOVZLLAWKN0aYwidP6szGJ8lot8Dip3mr3rhZKO5Q3pRUa3Wh Nb6X0Gv5uIK4A96Jxq3s2Cj2kLwYyz35w42eo7iGFKe2J8terOpZnXUNJ+P1mC/98IH2 hsskMDQIBwwH3t/RzhUcizir+OYBTZHJoUoLwpPWkO9nBXZAiibQwsJQp1X4zlgoKRvN mXU8qmZNJbXqu+CXb7FaumrxgsCUn4JZ+acKjWzGK1b6qh+YrktBoXnazQoxGRm4OtvZ Dm2yhQvcedw8Wq3Jl43RIeTTyzBhoSGEDan0Q5MFfXt5gm5oVVOXLrmhx4Qz/17Pohpl poMw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=p0rhChWworyaPMLQhvXbAbUx7Z4g8eo8kx7QdcwXZSo=; b=dliI8p0hIYT38tFbR7QvBuwXoH0MrMFxpCI6h86TJyXKeRxrLSfmJU+znWkkNTisPc +kkH9BFtyg0HIJjn5Zsn9qILEj802p5ycoAhkxCGIfnrOUpgRIgqO4DQ9v5khi3n/ZrD KKK1C2JKIbskJFBhRC4HyrWAOeawK7m1fhTWf/Yj8cyzz1Ozh5bmO1X/KLtg+TTGqgGS oDc61kDTwVFB+RcLZpr/sJOkYVUbO6g46za3n4F06VWmI5mKHinz7MuCwX05WZpUA5k0 +hqQVX6nUegDHwzrf+ug6FAse+08Oe6pe3Rf0nRx/BYEIkXeBKA3e4yA0bLGHHpmRpO4 uJ4g==
X-Gm-Message-State: ABuFfoiyN4exZEIm86PxRySNG5XQRbIyY/ioF0degTXV/slnC5cdjNqI OTeKvuQfWPMqI2QxD/y4ZwvG9/VTx3JEyNxH6cZlZg==
X-Google-Smtp-Source: ACcGV61xhUcjwyMkyDB0LmSamFwjkkqKikd2lFvEFWwgGirh/lcSjCKn0GYRAe0fesAkenuV2OItdaE3tvQWb/waGcg=
X-Received: by 2002:a5e:8d02:: with SMTP id m2-v6mr13197212ioj.122.1539616458671; Mon, 15 Oct 2018 08:14:18 -0700 (PDT)
MIME-Version: 1.0
References: <CAC8QAceeuSkmtmXqXaROA+L3SFXeJs1oQTO+Hp1bh-rXM9YziQ@mail.gmail.com> <CAPDqMeqVq5-dHY_yT=sJo_p1Hsayx0b1Ez6JmYLsDDcZKMJLfg@mail.gmail.com> <CAC8QAcc-vARqw9sYurjFZVKc08_pEUFzxoMR5tXMUK9T7PodGw@mail.gmail.com>
In-Reply-To: <CAC8QAcc-vARqw9sYurjFZVKc08_pEUFzxoMR5tXMUK9T7PodGw@mail.gmail.com>
From: Tom Herbert <tom@quantonium.net>
Date: Mon, 15 Oct 2018 08:14:07 -0700
Message-ID: <CAPDqMepuxDuOXi04s5HaVk_TZ_TEP4szM4iQc7ydwrFL9JMOFg@mail.gmail.com>
To: Behcet Sarikaya <sarikaya@ieee.org>
Cc: pidloc@ietf.org, dirk.von-hugo@telekom.de
Content-Type: multipart/alternative; boundary="0000000000001c21ae057845e485"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pidloc/JVM9n5tdqWQ4IL4UNLhYmkXVKbs>
Subject: Re: [Pidloc] Encoding Routing in FAST
X-BeenThere: pidloc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <pidloc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pidloc>, <mailto:pidloc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pidloc/>
List-Post: <mailto:pidloc@ietf.org>
List-Help: <mailto:pidloc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pidloc>, <mailto:pidloc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Oct 2018 15:14:24 -0000

On Mon, Oct 15, 2018, 7:30 AM Behcet Sarikaya <sarikaya2012@gmail.com>
wrote:

> Hi Tom,
>
>
>
> On Fri, Oct 12, 2018 at 12:20 PM Tom Herbert <tom@quantonium.net> wrote:
>
>>
>>
>> On Fri, Oct 12, 2018, 7:56 AM Behcet Sarikaya <sarikaya2012@gmail.com>
>> wrote:
>>
>>> Hi all,
>>>
>>> Tom Herbert published a draft
>>>
>>> https://tools.ietf.org/html/draft-herbert-route-fast-00
>>>
>>> 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
>> information.
>>
>>>
>>> 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.
>>
>
> You mean source routing?
>

It can be used as type of source routing, but it's more generic. The
ability to specify routing and services in return path is critical.


> Is this somehow related to SRv6?
>

Not really. SRv6 SIDs could be encoded in a ticket in a compressed form is
possible.

>
>
>
>> 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.
>>
>>
> I don't quite understand these things well, I need to dig more into it.
> What I understood from you draft is that it is a UDP application, i.e. it
> is application layer solution, is this correct?
>

No, it uses IPv6 Hop-by-Hop options. No encapsulation required.

Tom


> Behcet
>
>> Tom
>>
>>
>>
>>
>>> Any comments?
>>>
>>> Behcet
>>> --
>>> Pidloc mailing list
>>> Pidloc@ietf.org
>>> https://www.ietf.org/mailman/listinfo/pidloc
>>>
>>

v2.8.7 | Report a Bug | By Email