Re: [Teas] Network slicing framework : Issue #4: Describing the network slice service
Xufeng Liu <xufeng.liu.ietf@gmail.com> Thu, 07 October 2021 16:24 UTC
Return-Path: <xufeng.liu.ietf@gmail.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D8F73A0B4F for <teas@ietfa.amsl.com>; Thu, 7 Oct 2021 09:24:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 Cocea2-v1Qyt for <teas@ietfa.amsl.com>; Thu, 7 Oct 2021 09:24:47 -0700 (PDT)
Received: from mail-ed1-x534.google.com (mail-ed1-x534.google.com [IPv6:2a00:1450:4864:20::534]) (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 3DAB33A0B42 for <teas@ietf.org>; Thu, 7 Oct 2021 09:24:47 -0700 (PDT)
Received: by mail-ed1-x534.google.com with SMTP id g10so24541798edj.1 for <teas@ietf.org>; Thu, 07 Oct 2021 09:24:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=QPJ0DwXQrUOr4GdLrKfJPcw373t3s9wTjPVQPYAcOcA=; b=fr1av5zQEChxwL5XySkdlqnBPLLinXI1JI4uioAx2BZht71NzTZ/jDnV9sXYqMb136 4gCryTUEgfzeHgWl7B+4e6HBZr7aH0jS/niWtca5RBRxj4/UtmlsIG18RqLh5LhOh5r7 1yFFjSW//w3nRGORXdMa9wk2oxqsv5IKoPFsqKEN7gj99h69G9x20fvoIS/FH+weI5aS O0aishgUtJbWKHnt7lZk/M7isPimIfBlk2zuDTB0kno1E0wFZ/ghWjx2hOehy/dfHiGk SQc818jn/lkE/QVeYRtnm3waDlXFa7iH+OaSiF1U9MuVu4MzMNqjrGSdHooI03n9RmKS IqwQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=QPJ0DwXQrUOr4GdLrKfJPcw373t3s9wTjPVQPYAcOcA=; b=uvjceXxU89ibXXKKTMH7GR+PgQdF02lvvMunjp85fkyfkGWxq7+f1QWt520bNAMdu4 O8eQXp2SGxDbYZa8gOL1w7db3VYRNUMjgaUueWGWghQsZiqlUICw/vQPRL0Eoz7BNI/S c298ZJ1O7tCF3tuZ/fgwSZs0O/bGirqos5xbxvPdqA7ZLJY/r/CqJLE7ZXxsMwPlyLcf pkY34fB4TkyWwOffCs374rhXv127HiDrMKxXs/z2hEc3bm9tFqLQKFI2TNpHSqyxQnyw mQuID9MFjaFQGUqvuubmwml0XLh9WSJizaONweR88MMV4S0ENF+m1Bcz6WeHA7Il6bvJ p5ww==
X-Gm-Message-State: AOAM533LKLZarZOHOnHjJ4Sy72FhFN82+Gi0o7n7ax9qBHNJv/I51n04 ho0ODunPguuaE0htOIpSFTs3la6IfU+yWKTBWmE=
X-Google-Smtp-Source: ABdhPJyLTSBYm8sIveZlEDmE+vKXDtjLyC74I16JQJHJ8ofbGpJ9ZfCzxGunHqgH102D24gR8QQPCNGgT7jEOVkRnTs=
X-Received: by 2002:a17:907:784f:: with SMTP id lb15mr6550209ejc.260.1633623877642; Thu, 07 Oct 2021 09:24:37 -0700 (PDT)
MIME-Version: 1.0
References: <051101d7b3bf$986f5ec0$c94e1c40$@olddog.co.uk> <11690_1632912777_61544589_11690_440_1_787AE7BB302AE849A7480A190F8B93303540EE47@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
In-Reply-To: <11690_1632912777_61544589_11690_440_1_787AE7BB302AE849A7480A190F8B93303540EE47@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
From: Xufeng Liu <xufeng.liu.ietf@gmail.com>
Date: Thu, 07 Oct 2021 12:24:26 -0400
Message-ID: <CAEz6PPQbF_U9NFHwm+CQkxJPKniWjoNJq-X5Wihb1qzCaajEVw@mail.gmail.com>
To: Med Boucadair <mohamed.boucadair@orange.com>
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, TEAS WG <teas@ietf.org>, Vishnu Pavan Beeram <vbeeram@juniper.net>
Content-Type: multipart/alternative; boundary="000000000000ec6db605cdc5b214"
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/pGe6Q5gq_JwI-y7lu_e2SHqvfwA>
Subject: Re: [Teas] Network slicing framework : Issue #4: Describing the network slice service
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Oct 2021 16:24:52 -0000
I would hope the service could support topology-as-a-server, beyond connectivity-as-a-service, or provide the capability to specify an explicit path for connectivity. Thanks, - Xufeng On Wed, Sep 29, 2021 at 6:53 AM <mohamed.boucadair@orange.com> wrote: > Hi Adrian, all, > > That minimal scope is a good starting point. > > I had a proposal to get us out of SLO/SLE taxonomy, though. > > Cheers, > Med > > > -----Message d'origine----- > > De : Teas <teas-bounces@ietf.org> De la part de Adrian Farrel > > Envoyé : lundi 27 septembre 2021 18:49 > > À : 'TEAS WG' <teas@ietf.org>; 'Vishnu Pavan Beeram' < > vbeeram@juniper.net> > > Objet : [Teas] Network slicing framework : Issue #4: Describing the > > network slice service > > > > Hi, > > > > The current document describes the service in terms of: > > - endpoints > > - connectivity matrices > > - SLOs/SLE > > > > I believe that today's meeting had no objection to keeping this minimal > > definition, and specifically that it would not be appropriate to put an > > Information Model into the document. > > > > Opinions are wanted to confirm this view (silence is consent!). > > > > Pavan suggested that "a little more text may be needed" and I took this > as > > him volunteering to draft that text. > > > > Thanks, > > Adrian > > > > _______________________________________________ > > Teas mailing list > > Teas@ietf.org > > https://www.ietf.org/mailman/listinfo/teas > > > _________________________________________________________________________________________________________________________ > > Ce message et ses pieces jointes peuvent contenir des informations > confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez > recu ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages > electroniques etant susceptibles d'alteration, > Orange decline toute responsabilite si ce message a ete altere, deforme ou > falsifie. Merci. > > This message and its attachments may contain confidential or privileged > information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and > delete this message and its attachments. > As emails may be altered, Orange is not liable for messages that have been > modified, changed or falsified. > Thank you. > > _______________________________________________ > Teas mailing list > Teas@ietf.org > https://www.ietf.org/mailman/listinfo/teas >
- [Teas] Network slicing framework : Issue #4: Desc… Adrian Farrel
- Re: [Teas] Network slicing framework : Issue #4: … Vishnu Pavan Beeram
- Re: [Teas] Network slicing framework : Issue #4: … mohamed.boucadair
- Re: [Teas] Network slicing framework : Issue #4: … Xufeng Liu
- Re: [Teas] Network slicing framework : Issue #4: … mohamed.boucadair