Re: [Teas] I-D Action: draft-nsdt-teas-transport-slice-definition-03.txt

Joel Halpern Direct <jmh.direct@joelhalpern.com> Thu, 06 August 2020 15:17 UTC

Return-Path: <jmh.direct@joelhalpern.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 60D2B3A0AD3 for <teas@ietfa.amsl.com>; Thu, 6 Aug 2020 08:17:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.047
X-Spam-Level:
X-Spam-Status: No, score=-3.047 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, NICE_REPLY_A=-0.949, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 y8PXnmBPPgmF for <teas@ietfa.amsl.com>; Thu, 6 Aug 2020 08:17:03 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B0E93A0ACF for <teas@ietf.org>; Thu, 6 Aug 2020 08:17:03 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4BMsXv3Tf9z1ntYj; Thu, 6 Aug 2020 08:17:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1596727023; bh=SLf5pPulggc9wTKr2D/rFntxU1Ajo4Q+dWt3MrcWe8M=; h=Subject:To:References:From:Date:In-Reply-To:From; b=e+l6tXm6GfYQKiaoPXVUeLdmAvl1wZ0OtBigPW6NxKFIOSrefGdNPUQvW8Z5B5eeb hOZlNlPsEwHE05JrpYZKCikey9hqzGOS6FnpfRzPmhME9thEWadyFN4MsqOWCsK9q/ WCmUwkSt0pM2coMqjXwMbI9jxan9T+96j2P9Kq40=
X-Quarantine-ID: <wmbE5Na2DEWc>
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.128.43] (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 4BMsXt6CHNz1ntYY; Thu, 6 Aug 2020 08:17:02 -0700 (PDT)
To: "Rokui, Reza (Nokia - CA/Ottawa)" <reza.rokui@nokia.com>, "teas@ietf.org" <teas@ietf.org>
References: <159460858327.31249.6774312592426516405@ietfa.amsl.com> <a671ad62-65ea-134f-7855-ee3008539e0b@joelhalpern.com> <8757A5BE-BD59-4B9C-A5E9-0DC4A4D74D87@nokia.com>
From: Joel Halpern Direct <jmh.direct@joelhalpern.com>
Message-ID: <a4254b80-81de-25cb-d0b2-f3863024fa23@joelhalpern.com>
Date: Thu, 6 Aug 2020 11:17:01 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <8757A5BE-BD59-4B9C-A5E9-0DC4A4D74D87@nokia.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/bEwNBtzKKrqa6XdPbRjqK6HSH0A>
Subject: Re: [Teas] I-D Action: draft-nsdt-teas-transport-slice-definition-03.txt
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, 06 Aug 2020 15:17:05 -0000

Thank you for commenting the the TSRE question.
Let me reprase my question, given the comments...

Given that TSRE is strictly technology and infrastructure specific, why 
is it defined in this document?  Whether we need it or not it seems to 
be outside the scope of this document.

Yours,
Joel

On 8/6/2020 11:12 AM, Rokui, Reza (Nokia - CA/Ottawa) wrote:
> Thanks Joel for your comments.
> 
> Please see inline for TSRE.
> 
> Reza
> 
> On 2020-07-12, 11:59 PM, "Teas on behalf of Joel Halpern" 
> <teas-bounces@ietf.org on behalf of jmh@joelhalpern.com> wrote:
> 
>      My thanks to the design team for the update to this document.  It is
> 
>      much improved.
> 
>      I a  unable to understand the third paragraph of section 4.1.2.  I do
> 
>      not know what maximum occupancy refers to.  It seems to be talking 
> about
> 
>      some kind of notion of objectives applying to subsets of traffic 
> within
> 
>      a slice.  But I can't tell.
> 
>      Appendix A.1 is labeled as discussion, and as such appears to be 
> trying
> 
>      to be informative rather than normative.  However, the last 
> paragraph of
> 
>      introduces things a customer may ask for (i.e. SLOs) that are not
> 
>      described in the rest of the document, and do not actually seem to 
> me to
> 
>      be appropriate.  I wowuld ask that the last paragraph of section 
> A.1 be
> 
>      stricken.
> 
>      Some minor comments:
> 
>      At one point the SLA is defined (I believe reasonably)as the contract
> 
>      5that describes the SLOs with the consequences for missing them.  Then
> 
>      in section 4.1 it says "all SLOs combine to form the SLA".  Believe 
> you
> 
>      mean "form the objective portion of the SLA"  or "contribute to the 
> SLA"
> 
>      or something, since the contractual and consequence aspects of the SLA
> 
>      are outside of the SLOs?
> 
>      Given that availability is defined in terms of the other SLOs (quite
> 
>      reasonable) and that some of those may not be directly measurable), it
> 
>      seems that availability should itself be considered indirectly 
> measurable?
> 
>      nit - Given that the earlier text says that this is only an initial
> 
>      list, there is no need to include a bullet in the aspects that says
> 
>      "Other objectives could be specified".  It is true.  But has already
> 
>      been stated above.
> 
>      In section 4.2 on transport service endpoints, the text seems to say
> 
>      that an endpoint has a specific kind of connectivity (P2P, P2MP, ...).
> 
>      It seems perfectly valid for a single TSE to be using both P2P and 
> P2MP
> 
>      communication.  It seems rather odd to have to consider it to be two
> 
>      TSEs.  From later text, it is the slice, not the endpoint, which as a
> 
>      particular connectivity type.
> 
>      I wonder if the "Transport Slice Realization endpoint" is useful?  
> Given
> 
>      that many things are in both the sample TSE list and the sample TSRE
> 
>      list, it is going to be hard to tell them apart.  And as far as I can
> 
>      tell, the TSRE is internal to the transport, and therefore outside the
> 
>      scope of this document?  The differentiation in the diagram that 
> follows
> 
>      the description does not seem to line up with the description, and
> 
>      leaves me more confused.
> 
> [Reza]
> 
> As mentioned in draft, Transport slice realization endpoints (TSRE) are 
> allocated and
> 
> assigned by the network controller during the realization of a 
>   transport slice and are technology-specific, i.e. they depend on the
> 
> network technology used during the transport slice realization.
> 
> Depends on the definition of the transport slice, Transport Slice 
> endpoints (TSE) and TSRE might be very similar but their object models 
> are different.
> 
> Please also see the following draft which addresses the modeling of the 
> transport slice realization:
> 
>   * draft-liu-teas-transport-network-slice-yang-01
> 
> In summary, TRSE are assigned during the transport slice realization and 
> will be communicated from TSC NBI to higher system “Transport slice 
> Customer” and identifies how a transport slice is realized in the network.
> 
> We will add more clarification to the draft.
> 
>      Yours,
> 
>      Joel
> 
>      On 7/12/2020 10:49 PM, internet-drafts@ietf.org wrote:
> 
>      >
> 
>      > A New Internet-Draft is available from the on-line 
> Internet-Drafts directories.
> 
>      >
> 
>      >
> 
>      >          Title           : IETF Definition of Transport Slice
> 
>      >          Authors         : Reza Rokui
> 
>      >                            Shunsuke Homma
> 
>      >                            Kiran Makhijani
> 
>      >                            Luis M. Contreras
> 
>      >                            Jeff Tantsura
> 
>      >         Filename        : 
> draft-nsdt-teas-transport-slice-definition-03.txt
> 
>      >         Pages           : 21
> 
>      >         Date            : 2020-07-12
> 
>      >
> 
>      > Abstract:
> 
>      >     This document describes the definition of a slice in the 
> transport
> 
>      >     networks and its characteristics.  The purpose here is to bring
> 
>      >     clarity and a common understanding of the transport slice 
> concept and
> 
>      >     describe related terms and their meaning.  It explains how 
> transport
> 
>      >     slices can be used in combination with end to end network 
> slices, or
> 
>      >     independently.
> 
>      >
> 
>      >
> 
>      > The IETF datatracker status page for this draft is:
> 
>      > 
> https://datatracker.ietf.org/doc/draft-nsdt-teas-transport-slice-definition/
> 
>      >
> 
>      > There are also htmlized versions available at:
> 
>      > 
> https://tools.ietf.org/html/draft-nsdt-teas-transport-slice-definition-03
> 
>      > 
> https://datatracker.ietf.org/doc/html/draft-nsdt-teas-transport-slice-definition-03
> 
>      >
> 
>      > A diff from the previous version is available at:
> 
>      > 
> https://www.ietf.org/rfcdiff?url2=draft-nsdt-teas-transport-slice-definition-03
> 
>      >
> 
>      >
> 
>      > 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.
> 
>      >
> 
>      > Internet-Drafts are also available by anonymous FTP at:
> 
>      > ftp://ftp.ietf.org/internet-drafts/
> 
>      >
> 
>      >
> 
>      > _______________________________________________
> 
>      > I-D-Announce mailing list
> 
>      > I-D-Announce@ietf.org
> 
>      > https://www.ietf.org/mailman/listinfo/i-d-announce
> 
>      > Internet-Draft directories: http://www.ietf.org/shadow.html
> 
>      > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 
>      >
> 
>      _______________________________________________
> 
>      Teas mailing list
> 
>      Teas@ietf.org
> 
>      https://www.ietf.org/mailman/listinfo/teas
>