IETF Logo Mail Archive

Re: [Pidloc] Encoding Routing in FAST

Behcet Sarikaya <sarikaya2012@gmail.com> Mon, 15 October 2018 14:30 UTC

Return-Path: <sarikaya2012@gmail.com>
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 F3371130E08 for <pidloc@ietfa.amsl.com>; Mon, 15 Oct 2018 07:30:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.748
X-Spam-Level:
X-Spam-Status: No, score=-1.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=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 Ge1jgHNGbPqA for <pidloc@ietfa.amsl.com>; Mon, 15 Oct 2018 07:30:19 -0700 (PDT)
Received: from mail-wm1-x333.google.com (mail-wm1-x333.google.com [IPv6:2a00:1450:4864:20::333]) (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 74241130E81 for <pidloc@ietf.org>; Mon, 15 Oct 2018 07:30:18 -0700 (PDT)
Received: by mail-wm1-x333.google.com with SMTP id z204-v6so19944940wmc.5 for <pidloc@ietf.org>; Mon, 15 Oct 2018 07:30:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:reply-to:from:date:message-id :subject:to:cc; bh=WKhvHAfXZ7eKyeLuNjPGG3s/iJUMpuMKa8QR7ZVqE3k=; b=JZIFY7Ug9+CIatIQbqeufG4b+BGBFDu2hwrK25EI+i6kiKVuzBcWyxvMLqZ81gef6Z uJPUOU8bGxHCDO7wr/NHzyMjR6+uIf/+X8fn+ArKeJ7nxAxQRacIpIWrpLyv/Cctpw18 CciWWn1J79cKfbmUDPzR9lZntY1Ps2HAkDJejw0Sz0OPdMwPLe4QSI/iaIPI1DireOJz xNmbC78WiQ/Jiv1gAfN4djb4PlPpetjIyjmMs/Jc4ihuJuhj9RDYq5GRbm9sUZG7gJGk 5Z7A99E5ZZwuoICiUHhQ/G2XY42nMudgpQnVrmgkRHoastBwmFMtmk47MTVbXy0eKNIB Y7og==
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:reply-to :from:date:message-id:subject:to:cc; bh=WKhvHAfXZ7eKyeLuNjPGG3s/iJUMpuMKa8QR7ZVqE3k=; b=VFLbTEKTxj6sza2O12nXJSYENU2/+9jJHmKZ2xWHqwbGqhD16zOwXfYQ2c/5d+Dg0Z EyzmWrmXhFwyo2Z45GAu9Dn3ABirN+W4JKmqeVd+HFxEdPtCtBvM5oQyQMutG0lwFS4A 4bYm+oAdn3BRhkFgMAkSbX8qP0+31uEjWwIBEhlU0lUI4Ak0wxDQKwls1HdqMQrGXa30 gPu2/Prg8caRYWIk6tiMUnbz4xkuB3YKaaBiGsTh8XqpNwqmddHzmL0vYfYICCUkGIoE qxyiytXSBRRq9paDyguqk7NriMogyE8PAWpHOt5OAgCaIhIPahgKJ7KW3w4Uxp37URkz zwdw==
X-Gm-Message-State: ABuFfoiEFLWe6YMBTkkCgW6IOYbPtKx0Ur2b+EoF1pZGOvHlUnDCoegR Yj9tsO9Bq+pJZ83NV/D0ATzRypsyfYxfkERfcR8=
X-Google-Smtp-Source: ACcGV615FZHWrJfMHM3KJgHZpsgrDy1CNUXQl3LVk52dckyN23K1VIlEBanaT4l+7Xzb7AAwA+bxW/EU6rTNccuZs0o=
X-Received: by 2002:a1c:5702:: with SMTP id l2-v6mr12383143wmb.83.1539613816835; Mon, 15 Oct 2018 07:30:16 -0700 (PDT)
MIME-Version: 1.0
References: <CAC8QAceeuSkmtmXqXaROA+L3SFXeJs1oQTO+Hp1bh-rXM9YziQ@mail.gmail.com> <CAPDqMeqVq5-dHY_yT=sJo_p1Hsayx0b1Ez6JmYLsDDcZKMJLfg@mail.gmail.com>
In-Reply-To: <CAPDqMeqVq5-dHY_yT=sJo_p1Hsayx0b1Ez6JmYLsDDcZKMJLfg@mail.gmail.com>
Reply-To: sarikaya@ieee.org
From: Behcet Sarikaya <sarikaya2012@gmail.com>
Date: Mon, 15 Oct 2018 09:30:05 -0500
Message-ID: <CAC8QAcc-vARqw9sYurjFZVKc08_pEUFzxoMR5tXMUK9T7PodGw@mail.gmail.com>
To: Tom Herbert <tom@quantonium.net>
Cc: sarikaya@ieee.org, pidloc@ietf.org, dirk.von-hugo@telekom.de
Content-Type: multipart/alternative; boundary="000000000000a4d3580578454654"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pidloc/iOh0OTeGmRHuGOCfhPClr1A1J-g>
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 14:30:21 -0000

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?

Is this somehow related to SRv6?



> 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?

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