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

<mohamed.boucadair@orange.com> Tue, 03 July 2018 12:03 UTC

Return-Path: <mohamed.boucadair@orange.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 1EB3E130E6A; Tue, 3 Jul 2018 05:03:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=unavailable autolearn_force=no
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 QlgLHv5CWS4s; Tue, 3 Jul 2018 05:03:33 -0700 (PDT)
Received: from orange.com (mta136.mail.business.static.orange.com [80.12.70.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E478130E72; Tue, 3 Jul 2018 05:03:30 -0700 (PDT)
Received: from opfednr06.francetelecom.fr (unknown [xx.xx.xx.70]) by opfednr26.francetelecom.fr (ESMTP service) with ESMTP id E0AB62092E; Tue, 3 Jul 2018 14:03:28 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.32]) by opfednr06.francetelecom.fr (ESMTP service) with ESMTP id BC3C71A0051; Tue, 3 Jul 2018 14:03:28 +0200 (CEST)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM32.corporate.adroot.infra.ftgroup ([fe80::8924:188:2124:a046%19]) with mapi id 14.03.0399.000; Tue, 3 Jul 2018 14:03:28 +0200
From: <mohamed.boucadair@orange.com>
To: "draft-lachos-multi-domain-sfc-alto@ietf.org" <draft-lachos-multi-domain-sfc-alto@ietf.org>, IETF ALTO <alto@ietf.org>, "sfc@ietf.org" <sfc@ietf.org>, "nfvrg@irtf.org" <nfvrg@irtf.org>
Thread-Topic: [sfc] New Version Notification for draft-lachos-multi-domain-sfc-alto-00.txt
Thread-Index: AQHUEl3EYXZTDhdqREmSJVhMkfQ3/KR9ZLkw
Date: Tue, 3 Jul 2018 12:03:27 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93302DF50C43@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <153056233927.16122.5390536777785176859.idtracker@ietfa.amsl.com> <CAEDarX+JT2J=uMFcskoKhZNOu7XvESDYSNxjEwaV0EapQ+tnQg@mail.gmail.com>
In-Reply-To: <CAEDarX+JT2J=uMFcskoKhZNOu7XvESDYSNxjEwaV0EapQ+tnQg@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.6]
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B93302DF50C43OPEXCLILMA3corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/KO2xrIhRKcnJxsyHfbjxaGuZM4g>
Subject: Re: [alto] [sfc] 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: Tue, 03 Jul 2018 12:03:35 -0000

Dear Danny,

Thank you for sharing this draft.

My main comments about this draft are as follows:

·         The SFC WG is currently scoped to one single administrative domain. Even for the work we have done about hierarchical SFC, the assumption is that sub-domains are managed by the same administrative entity.

·         Before getting into protocol details about how to realize inter-domain service chains, it would be really valuable to identify and describe concrete uses cases which require SFs from distinct administrative domains + justify why topology visibility is required + paths have to be computed end-to-end and so on.

FWIW, you may find some additional comments at:

·         .pdf: https://github.com/boucadair/IETF-Drafts-Reviews/blob/master/draft-lachos-multi-domain-sfc-alto-00-rev%20Med.pdf

·         .doc: https://github.com/boucadair/IETF-Drafts-Reviews/raw/master/draft-lachos-multi-domain-sfc-alto-00-rev%20Med.doc

Cheers,
Med

De : sfc [mailto:sfc-bounces@ietf.org] De la part de Danny Alex Lachos Perez
Envoyé : mardi 3 juillet 2018 01:35
À : internet-drafts@ietf.org; IETF ALTO; sfc@ietf.org; nfvrg@irtf.org
Cc : qiao.xiang@cs.yale.edu; Christian Rodolfo E. Rothenberg; Y. Richard Yang
Objet : Re: [sfc] New Version Notification for draft-lachos-multi-domain-sfc-alto-00.txt

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<mailto: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<http://tools.ietf.org>.

The IETF Secretariat