Re: [alto] New Version Notification for draft-lachos-multi-domain-sfc-alto-00.txt

Danny Alex Lachos Perez <dlachosper@gmail.com> Mon, 02 July 2018 23:35 UTC

Return-Path: <dlachosper@gmail.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78199131411; Mon, 2 Jul 2018 16:35:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 hRlsYF8E2IY4; Mon, 2 Jul 2018 16:35:49 -0700 (PDT)
Received: from mail-pg0-x236.google.com (mail-pg0-x236.google.com [IPv6:2607:f8b0:400e:c05::236]) (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 A85B7131473; Mon, 2 Jul 2018 16:35:31 -0700 (PDT)
Received: by mail-pg0-x236.google.com with SMTP id x5-v6so53778pgp.7; Mon, 02 Jul 2018 16:35:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=GiaYaQt2HIwbwroBsuZOZdse8DWKGMCILMMnyGgimFk=; b=MeBUZnoir4vPEwNkDxSc0g2yYng8D/s3+26VCZmSeXLkvjF8x8E5dNYj1yShvsFOa+ e+wIwBBkzaC/qb77zLMyb54WIsQdByHxn7jf54wuhSEmrATh7GoQp/9bqcAKyzX5B3lu 8RCACrKzdWkZiWTyeLUi9QacPCQfyG0u+XDiNjc8wAqgc1q6sYWivwOdgi2C1HN8x3Ds /12Mi1HJd9wDfPymepI91LnuObQMwVaUHpVi11p/Pi6KQ+j53Z1JelsCnK/MX3wJ4F8J VlXqRrOoCrA+fSGQ6sJe5AnqcWoU3MHV1DJsYc8ni4+DfEB5IeWgLC+75xvCzKAcUa7j NcmQ==
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=GiaYaQt2HIwbwroBsuZOZdse8DWKGMCILMMnyGgimFk=; b=ihgkYq4HjoV5e+JDQmS1BEZPHZxhbbUYq/k5VYJmszafIG8ByM5lQgAsaMBn2Q/Ar2 Tq+/TdWylhHflHw62Zf7EjkM1+6gM4xj1cc3wekwq6jUIoSs12C7NbTBwky0fYlQRtnd VLq4qjIgyVepxCs7vKl8qUaHMwufedRbRjW7jz6fPEvPshCSRBE8B5aShezIyTzkL5Ln e9depREvTYihFRJmCqrwSpWvtkeTyqXC4Lh1n6CzAiMxjOBxKULqJkqa2oCAl45SBnFl 9KLD9zy9WjZ0I2YEzoIDLMa90FRCOb3tivc1UtbyGf5MZtuIt5nEbRmM6g4KqvmAtjxo 9WOA==
X-Gm-Message-State: APt69E1oDrfztZ2b7FXruMO3MsOawWxAzyJrpz5QTwT4+WpJeLcazwzZ O7IntRIHLTufQPsXCrMBFZFJfGl6jd5HHQCucqDYEg==
X-Google-Smtp-Source: AAOMgpdZcMRfFbYbkYUGvafeqzy2nGbOravoC38NCHakpctnvTl7gaH1BoD6Dg5k8arlN6O1UWwo4sDjmsHcJcgYUlM=
X-Received: by 2002:a62:3101:: with SMTP id x1-v6mr26874387pfx.246.1530574530970; Mon, 02 Jul 2018 16:35:30 -0700 (PDT)
MIME-Version: 1.0
References: <153056233927.16122.5390536777785176859.idtracker@ietfa.amsl.com>
In-Reply-To: <153056233927.16122.5390536777785176859.idtracker@ietfa.amsl.com>
From: Danny Alex Lachos Perez <dlachosper@gmail.com>
Date: Mon, 2 Jul 2018 20:35:19 -0300
Message-ID: <CAEDarX+JT2J=uMFcskoKhZNOu7XvESDYSNxjEwaV0EapQ+tnQg@mail.gmail.com>
To: internet-drafts@ietf.org, IETF ALTO <alto@ietf.org>, sfc@ietf.org, nfvrg@irtf.org
Cc: "Y. Richard Yang" <yang.r.yang@gmail.com>, qiao.xiang@cs.yale.edu, "Christian Rodolfo E. Rothenberg" <chesteve@dca.fee.unicamp.br>
Content-Type: multipart/alternative; boundary="000000000000388a0305700ca7d1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/thFCuJpzzjPAJXG_MslLGBDIg1s>
Subject: Re: [alto] New Version Notification for draft-lachos-multi-domain-sfc-alto-00.txt
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/alto/>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Jul 2018 23:35:58 -0000

Dear WG members.

The main idea behalf this draft is to start a discussion (SFC, ALTO as well
as other WGs) regarding if, how, and under what conditions ALTO can be
useful to improve the multi-domain SFC process.

This version provides arguments why ALTO is a meaningful protocol in the
context of SFC traversing different domains, and it presents use case
examples about the how ALTO can be used to advertise and discover
(abstract) topology, resource and service information from different
domains, and then compute inter-domain service function paths.

Any comment, question, and suggestion from the WGs would be greatly
appreciated.

Ss

Danny Lachos

On Mon, Jul 2, 2018 at 5:12 PM <internet-drafts@ietf.org> wrote:

>
> A new version of I-D, draft-lachos-multi-domain-sfc-alto-00.txt
> has been successfully submitted by Danny Alex Lachos Perez and posted to
> the
> IETF repository.
>
> Name:           draft-lachos-multi-domain-sfc-alto
> Revision:       00
> Title:          Multi-domain Service Function Chaining with ALTO
> Document date:  2018-07-02
> Group:          Individual Submission
> Pages:          14
> URL:
> https://www.ietf.org/internet-drafts/draft-lachos-multi-domain-sfc-alto-00.txt
> Status:
> https://datatracker.ietf.org/doc/draft-lachos-multi-domain-sfc-alto/
> Htmlized:
> https://tools.ietf.org/html/draft-lachos-multi-domain-sfc-alto-00
> Htmlized:
> https://datatracker.ietf.org/doc/html/draft-lachos-multi-domain-sfc-alto
>
>
> Abstract:
>    Currently, Service Function Chaining (SFC) that span domains with
>    different technology, administration or ownership are being defined
>    by the SFC WG.  This document focuses on how the Application Layer
>    Traffic Optimization (ALTO) protocol can be used to advertise and
>    discover abstract topology, resource and service information from
>    different domains, and then compute inter-domain service function
>    paths.  Another important concern of this draft is to initiate a
>    discussion (ALTO, SFC as well as other WGs) regarding if, how, and
>    under what conditions ALTO can be useful to improve the multi-domain
>    SFC process.
>
>
>
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>
>