Re: [Teas] New term for the underlay construct used for slice realization

Tarek Saad <tsaad.net@gmail.com> Tue, 17 August 2021 15:37 UTC

Return-Path: <tsaad.net@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 CE5D53A1FFA for <teas@ietfa.amsl.com>; Tue, 17 Aug 2021 08:37:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.996
X-Spam-Level:
X-Spam-Status: No, score=-1.996 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, HTTPS_HTTP_MISMATCH=0.1, MIME_QP_LONG_LINE=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 RVQ4hm92r3NF for <teas@ietfa.amsl.com>; Tue, 17 Aug 2021 08:37:23 -0700 (PDT)
Received: from mail-qv1-xf2d.google.com (mail-qv1-xf2d.google.com [IPv6:2607:f8b0:4864:20::f2d]) (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 5EDDA3A1FF7 for <teas@ietf.org>; Tue, 17 Aug 2021 08:37:23 -0700 (PDT)
Received: by mail-qv1-xf2d.google.com with SMTP id eh1so3722099qvb.11 for <teas@ietf.org>; Tue, 17 Aug 2021 08:37:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=iweMUOj+zRV2/yx/jriOJm5rpiU6n+XBbwkNUYFlO6s=; b=WiO5pWqgH2LvuFwWHFgO7RfreCndmZkz8CaOlfvyYNtRfthp7hED87aFkKPeuDJQjr vh1DVIoH2opjZISr5uJ6j3mgDu0ptpVphVtGYba9YBq2aEuSbC/b1JONhVHhYR/MmH+n B6KaKOGixRud641nuvbTmXB4KNkyqxdqsBDVK3igcNKmso0HHhd+yyEDDm4pFZPVvm6c yrViITiGoiavFFuWVPYjT7wV7lG6qqVGwszKokL+kl1VBuZUHFdC8/hb0ML7M+8E205b YRDWoXNSsasJ0q45Y8q1LBhAeC4tWQle2wWly/X6/cGMRmY/AgNvzEzC5d1vtMe/Fjrw +gBQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=iweMUOj+zRV2/yx/jriOJm5rpiU6n+XBbwkNUYFlO6s=; b=IOItZMcdhfExw450hroYwGhZFgNEbRWXGUOPP5vD8MTTirixKmud2ORWc+IHFSOfWZ ILkK5KqiC+HoRWnWgoO5qYD4tUrdylcxB2RXwttSRW95aFJFt721VtVeZI8kU78dPpbg ZTBgrf8353MwrRC7R5zwQ9MeJ0s2BG68raCOs1W+6Wdg18pkoU2J0sv6MUzqvhNHrn4n 3JystSBhy1R0I+lQcUGotwdFvHDEmj+Q+mCvGYLPpIZzY1ZTzFmdNiWGEPSLvvQVDlUC qnBswm3mDzvoZLQWtaoa+UGjmy1+GVZDMA6rRhsyZwLs+dgvh6nEVu37jYMRQHMLIH1C EOHw==
X-Gm-Message-State: AOAM532hVQZ4BEfP1KNue8JS9dblh0uvSlwQAiRl7IxGs1h02M0kBHeT nqbKIeC61N/DWQ+znJKf8WE=
X-Google-Smtp-Source: ABdhPJx7z5HiM+KwuCJzqVr5WNr08kYS4qYjevQiPf5h3z/nJT9RJOYYt5gS9YAkr6TJ46i8+lx5gA==
X-Received: by 2002:a05:6214:f0c:: with SMTP id gw12mr4048218qvb.2.1629214641215; Tue, 17 Aug 2021 08:37:21 -0700 (PDT)
Received: from smtpclient.apple ([2607:fea8:e31c:c300:1412:d4a5:4331:1480]) by smtp.gmail.com with ESMTPSA id bm7sm1540442qkb.79.2021.08.17.08.37.19 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 17 Aug 2021 08:37:20 -0700 (PDT)
Content-Type: multipart/alternative; boundary=Apple-Mail-DCA0CF09-FA4B-4D45-8262-8B30E1F71E48
Content-Transfer-Encoding: 7bit
From: Tarek Saad <tsaad.net@gmail.com>
Mime-Version: 1.0 (1.0)
Date: Tue, 17 Aug 2021 11:37:18 -0400
Message-Id: <94297D6F-7DCE-4A7E-B03C-58F78CE8AE25@gmail.com>
References: <BY3PR05MB808158BBA685253C2D1A387FC7FD9@BY3PR05MB8081.namprd05.prod.outlook.com>
Cc: "Dongjie (Jimmy)" <jie.dong@huawei.com>, vishnupavan@gmail.com, Adrian Farrel <adrian@olddog.co.uk>, TEAS WG <teas@ietf.org>
In-Reply-To: <BY3PR05MB808158BBA685253C2D1A387FC7FD9@BY3PR05MB8081.namprd05.prod.outlook.com>
To: John E Drake <jdrake@juniper.net>
X-Mailer: iPhone Mail (18G82)
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/JfMChD-ySQuFHYKEprSVa5ErTMc>
Subject: Re: [Teas] New term for the underlay construct used for slice realization
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: Tue, 17 Aug 2021 15:37:30 -0000

Hi all,

Indeed, this is inline to my previous email (and definition of slice aggregate in bestbar draft). The aggregate is for the collection of network streams (e.g. network slice connection streams) that can use the network resources allotted for this aggregate. In this sense there are two things:

1) the group of streams of similar SLA requirements that are grouped together (aggregate)
2) the network resources that are allotted to be used by aggregates

For grouping (2), the term identifies the resources on multiple network elements for use by this group. For this, I favour “network resource group” but can live with “network resource partition”. 

Regards,
Tarek

> On Aug 16, 2021, at 8:53 AM, John E Drake <jdrake@juniper.net> wrote:
> 
> 
> Hi,
>  
> It sounds like slice aggregates, or more generally overlay network service aggregates, are the things which use resource partitions.
>  
> Yours Irrespectively,
>  
> John
>  
>  
> Juniper Business Use Only
> From: Teas <teas-bounces@ietf.org> On Behalf Of Dongjie (Jimmy)
> Sent: Friday, August 13, 2021 9:20 AM
> To: EXT-vishnupavan@gmail.com <vishnupavan@gmail.com>om>; Adrian Farrel <adrian@olddog.co.uk>
> Cc: Tarek Saad <tsaad.net@gmail.com>om>; TEAS WG <teas@ietf.org>
> Subject: Re: [Teas] New term for the underlay construct used for slice realization
>  
> [External Email. Be cautious of content]
>  
> Hi Pavan,
>  
> Sorry for chiming in, please see some comments inline:
>  
> From: Teas [mailto:teas-bounces@ietf.org] On Behalf Of Vishnu Pavan Beeram
> Sent: Friday, August 13, 2021 1:32 AM
> To: Adrian Farrel <adrian@olddog.co.uk>
> Cc: Tarek Saad <tsaad.net@gmail.com>om>; TEAS WG <teas@ietf.org>
> Subject: Re: [Teas] New term for the underlay construct used for slice realization
>  
> ** As a WG participant.. **
> 
> Adrian, Hi!
> 
> Thanks for your earlier emails in this thread that have helped drill down the discussion to the specific item that needs a fresh term!
> Please see inline (prefixed VPB).
> 
> -Pavan (as a WG participant)
>  
> On Thu, Aug 12, 2021 at 10:05 AM Adrian Farrel <adrian@olddog.co.uk> wrote:
> Thanks for your useful opinion, Tarek.
>  
> I have no objection to the use of the word “aggregate”. It is generally used to express grouping together to treat as a single entity or to be treated in the same way.
>  
> But I do like “foo aggregate” to mean that a number of foo have been aggregated.
>  
> [VPB] But, that isn’t necessarily how IETF has been using the term “aggregate”.  “Behavior Aggregate” (as defined in IETF) doesn’t mean aggregating behaviors. The same goes for “Treatment Aggregate”. Behavior Aggregate (the way we read/interpret it) is an aggregate with a specific behavior. 
>  
> [Jie] I just checked the definition of the “aggregate” related terms in the RFCs:
>  
> Behavior Aggregate (defined in RFC 2474): a collection of packets with the same codepoint crossing a link in a particular direction.”
>  
> Traffic Aggregate (defined in RFC 3086): a collection of packets with a codepoint that maps to the same PHB, usually in a DS domain or some subset of a DS domain.
>  
> Treatment Aggregate (defined in RFC 5127): This term is defined as the aggregate of Diffserv service classes.  A treatment aggregate is concerned only with the forwarding treatment of the aggregated traffic,  which may be marked with multiple DSCPs.
>  
> My reading of these definitions is that “aggregate” here means either aggregated packets or aggregated service classes which are treated in the same way on a particular node or link.
>  
> While what we want to describe with the new term IMO is “a group of network resources allocated on a set of network nodes and links”. Such group of resources can be provisioned in different places of the network and are organized together to provide a specific network-level behavior.
>  
> Thus the key information to be delivered with the new term is “a group of organized resources in the network”, rather than “aggregated behavior at a particular point”.
>  
> Best regards,
> Jie
>  
> So “slice aggregate” would be an aggregation of slices. Your use in I-D.draft-bestbar-teas-ns-packet is, therefore, confusing. If the slices are *not* separated out into different flows (or traffic streams) then, yes, you are aggregating slices. But if the slices are separated out, as you describe, then what you have is “IETF network slice traffic stream aggregation”.
>  
>  
> [VPB] Yes. The definition of the slice aggregate (as defined in draft-bestbar-teas-ns-packet) does state that the slice aggregate comprises of one or more IETF network slice traffic streams.  We could have chosen a longer descriptive name, but opted to keep it short.
>  
>  
> “Network resource aggregate” would imply that resources have been collected together to be used as a single entity.
>  
> [VPB] Not necessarily. "Network Resource Aggregate" isn't meant to imply "aggregating network resources". The intent behind the proposal is to say that it is an aggregate that has specific network resources. 
>  
> You might do that, for example, with a set of parallel links that can be aggregated (or bundled) and treated as a single link.
>  
> I don’t think we are aggregating resources in this case. We are grouping, profiling, partitioning, collecting, or even filtering.
>  
> Adrian
>  
> From: Tarek Saad <tsaad.net@gmail.com> 
> Sent: 12 August 2021 15:41
> To: adrian@olddog.co.uk; 'Kiran Makhijani' <kiran.ietf@gmail.com>om>; 'John E Drake' <jdrake=40juniper.net@dmarc.ietf.org>rg>; 'Dongjie (Jimmy)' <jie.dong@huawei.com>om>; 'Lizhenbin' <lizhenbin@huawei.com>om>; teas@ietf.org
> Subject: Re: [Teas] New term for the underlay construct used for slice realization
>  
> Hi Adrian/all,
>  
> As described in I-D.ietf-teas-ietf-network-slice-definition, an IETF Network Slice service may include multiple connections that associate sets of endpoints - each having a set of SLOs/SLEs.
> In I-D.draft-bestbar-teas-ns-packet, we defined a Slice Aggregate as a construct that comprises of one or more IETF network slice traffic streams that share the same set of SLOs/SLEs.
> The Slice Aggregate construct allows aggregating streams from multiple IETF Network Slice connections that share common SLOs/SLEs so that the provider network can offer the same aggregate treatment to them. The Slice Aggregate resources are instantiated on specific network elements as dictated by the Slice Aggregate topology.
>  
> Since the scope of I-D.draft-bestbar-teas-ns-packet was the realization of IETF Network Slice service in a provider network, we had constrained the aggregate construct to slices.
>  
> We understand that the aggregate construct can be generalized to support other services. Let us offer another option to consider for representing the generic construct: “Network Resource Aggregate”. There are multiple IETF documents that use the term Aggregate whenever grouping multiple service classes (Behavior Aggregate, Treatment Aggregate, Traffic Aggregate, etc.) - refer to rfc5127 and rfc2474 for more examples.
>  
> Regards,
> Tarek
>  
>  
> From: Teas <teas-bounces@ietf.org> on behalf of Adrian Farrel <adrian@olddog.co.uk>
> Date: Wednesday, August 11, 2021 at 3:38 PM
> To: 'Kiran Makhijani' <kiran.ietf@gmail.com>om>, 'John E Drake' <jdrake=40juniper.net@dmarc.ietf.org>rg>, 'Dongjie (Jimmy)' <jie.dong@huawei.com>om>, 'Lizhenbin' <lizhenbin@huawei.com>om>, teas@ietf.org <teas@ietf.org>
> Subject: Re: [Teas] New term for the underlay construct used for slice realization
> 
> I wonder whether we can pick this apart and put it back together in a way
> that makes sense.
> 
> The customer's view of all this is an "IETF network slice service". I think
> (hope) we are all agreed on this. The customer may ask (in shorthand) for a
> "network slice", but:
> - they are talking about IETF technology, so they asking for an "IETF
> network slice"
> - they actually want behavioural characteristics and have no right to tell
> the operator
>   how to manage the network, so they are asking for an "IETF network slice
> service."
> 
> The operator has a bigger set of things to worry about. 
> 
> 1. At the top of the operator's view is the "IETF network slice service" as
>     requested by the customer. We have this defined already, so nothing more
>     to say.
> 
> 2. The operator maps the request for a slice service into the "IETF network
>     slice" which is the expression of the service in terms of network
> connectivity
>     in the context of the operator's network. The relationship here is like
> the
>     relationship between the L3SM and L3NM.
> 
> 3. At the bottom of their view is an underlying network. The technology of
> this
>    network depends, of course, on the operator's offering, but this is the
> network
>    technology being sliced. It may be an IP network, and MPLS network, an
> OTN,
>    or whatever. I would call this the "Underlay Network." This network may,
> in
>    turn, be built upon an underlay network of the same or a different
> technology,
>    and it may be facilitated through network slicing - but this need not
> concern
>    us here. 
> 
> 4. That leaves the glue in the middle: the bit that enables the scaling and
> maps
>    the network slice to the network. And I think it is this bit that is
> causing the
>    most debate about terminology. There are some points to consider:
> 
>    a. The term "network resources" applies to the bandwidth, queues,
> buffers,
>        etc. available on the links and nodes in the network. That may be 
>        extended to refer to whole links and nodes.
> 
>    b. The number of IETF network slice services is potentially large and the
>        operator needs a mechanism to scale the mapping of services to 
>        network resources.
> 
>    c. The IETF network slices may be grouped for identical treatment to
>        achieve scaling, where the grouping collects IETF network slices with
>        similar SLAs.
> 
>    d. It may be that different traffic flows within a single IETF network
> slice
>         have different characteristics. In this case, it may be beneficial
> to group
>         together some of the traffic flows from different slices.
> 
>    e. The grouped slices/flows are enabled in the network using network
>         resources assigned for that purpose. The assignment may be anything
>         from a fully-fledged virtual network (such as in ACTN or VPN+),
> through
>         network reserved resources (such as in MPLS-TE), and centrally
>         accounted resources (such as SDN or possible SR), to statistically
>         shared resources.
> 
> There seems to be various points for and against 4d. But, it would appear
> that this is an implementation or deployment issue that doesn't change what
> the protocols need to do. So we should probably allow it architecturally, or
> at least, not disallow it.
> 
> Of course, as Kiran points out, 4c/d/e may be a pass-through. That is, it is
> not necessary to implement such groupings either because there are only a
> few slices (which has been the view of some operators) or because the
> network systems can handle the number of slices. And it is in the nature of
> architectures of this sort that all functions can be nulled out without loss
> of generality, and we have to recall that the internals of provisioning
> systems may appear as functional blocks in our architectures, but we don't
> compel implementations to adhere to that type of architecture. So I don't
> think we have to worry on that account.
> 
> And that brings the question of how we name the resources that are gathered
> in 4e. 
> 
> I can't decide whether it is helpful to spend time saying why I don't like
> each of the proposed terms. I certainly have things I don't like about (for
> example) "slice aggregate" (because of 4d, which means it is really a "slice
> sub-flow aggregate"), and I am not a fan of "VTN" (because of "transport"
> and maybe it is not really a network). But maybe it is better for me to say
> what I think we should call things? I think we have...
> 
> -       IETF network slice service (customer view)
> -       IETF network slice (operator view)
> -       Resource partition (delivery mechanism)
> -       Underlay network (network used to support the slice)
> 
> Why "resource partition"? Well it is a collection of "nodes, links, and
> network resources that are marked within the network for use by a set of
> network slice traffic flows".
> It is possible that the word "partition" is too strong because it may imply
> to some people that resources in a partition cannot be shared, but I don't
> feel that.
> Softer words than "partition" would be "group", "bundle", "pool", and I
> could live with any of them.
> 
> Best,
> Adrian
> 
> 
> -----Original Message-----
> From: Teas <teas-bounces@ietf.org> On Behalf Of Kiran Makhijani
> Sent: 11 August 2021 16:00
> To: John E Drake <jdrake=40juniper.net@dmarc.ietf.org>rg>; Dongjie (Jimmy)
> <jie.dong@huawei.com>om>; Lizhenbin <lizhenbin@huawei.com>om>; teas@ietf.org
> Subject: Re: [Teas] New term for the underlay construct used for slice
> realization
> 
> Hi John, (and all),
> 
> Two very basic clarification questions:
> 1. How do we differentiate between  the slice-segments that are 
> resource-aware vs those that are not? I had assumed that since a slice 
> has an SLO, it will need network resource allocations in some form.
> 
> 2. Is it ok to assume that the customer view of slice is an 'IETF 
> network slice service' and the 'IETF slice realization' of that service 
> in a provider network is raises the question of underlay and overlay 
> constructs. Am I right?
> (a) if so, then we are acknowledging  the presence of another layer of 
> abstraction (for realization). It could be underlay/overlay or 
> aggregate/??. Then the term 'slice aggregate' is better and my 
> preference, it is easier to see that different slice-services are 
> aggregated into a single construct  in a provider network. Use of 
> underlay/overlay are confusing.
> (b) for a leaner provisioning, I would also prefer to see it documented 
> that the aggregate is optional and it should be possible to directly map 
> a slice-service to physical or real resources in the network. 
> specifically useful when a single domain is carving out slices for 
> different purposes.
> 
> Thanks
> Kiran
> 
> 
> ------ Original Message ------
> From: "John E Drake" <jdrake=40juniper.net@dmarc.ietf.org>
> To: "Dongjie (Jimmy)" <jie.dong@huawei.com>om>; "Lizhenbin" 
> <lizhenbin@huawei.com>om>; "teas@ietf.org" <teas@ietf.org>
> Sent: 8/11/2021 5:38:05 AM
> Subject: Re: [Teas] New term for the underlay construct used for slice 
> realization
> 
> >Jimmy,
> >
> >Snipped, comments inline.
> >
> >Yours Irrespectively,
> >
> >John
> >
> >
> >Juniper Business Use Only
> >
> >>  -----Original Message-----
> >>  From: Dongjie (Jimmy) <jie.dong@huawei.com>
> >>  Sent: Tuesday, August 10, 2021 11:03 PM
> >>  To: John E Drake <jdrake@juniper.net>et>; Lizhenbin <lizhenbin@huawei.com>om>;
> >>teas@ietf.org
> >>  Subject: RE: New term for the underlay construct used for slice
> realization
> >>
> >>  [External Email. Be cautious of content]
> >>
> >underlay construct for network slice realization bound to
> >>  > > network slice services? That is, is the underlay construct only for
> >>  > > use in network slicing, or should it be generalized for more
> possible uses?
> >>  >
> >>  > [JD] Absolutely yes
> >>
> >>  [Jie] I guess you mean "Yes" to the latter case, which is "it should be
> generalized
> >>  for more possible uses", is my understanding correct?
> >
> >[JD]  Yes to the latter
> >
> >>
> >>  >
> >>  > >
> >>  > > 2.      If the answer to question 1 is YES, should it reflect the
> following
> >>  > > characteristics?
> >>  > >
> >>  > > a.      It is about the underlay
> >>  > > b.      It is about the partitioned resources used to deliver the
> network slice
> >>  > > services
> >>  > > c.      It allows the 1:1, N:1, and 1:N mapping models between the
> network
> >>  > slice
> >>  > > services and the underlay construct. The 1:1 and N:1 mapping may be
> >>  > > straightforward. Does it also make sense to divide the elements or
> >>  > > traffic flows in a single network slice service to carry them in
> >>  > > different
> >>  > underlay constructs?
> >>  >
> >>  > [JD]  Yes to all of the above.  Please see:
> >>  > https://urldefense.com/v3/__https://datatracker.ietf.org/doc/html/draf
> >>  > t-drake-bess-enhanced-vpn-06__;!!NEt6yMaO-
> >>  gk!TCiJHCZCwFgwpuFoujxVlZ4r9
> >>  > F6mLpE4nJ-9zpqkY-kls-ROxL4C2_xNaR2ImI4$
> >>  > >
> >>  > > Lastly, here are some candidates of the "new term":
> >>  > >
> >>  > > Option 1: The network slice service is called "overlay slice", then
> >>  > > the underlay construct is called "underlay slice".
> >>  > >
> >>  > > Option 2: The network slice service is called "service slice", then
> >>  > > the underlay construct is called "resource slice".
> >>  >
> >>  > [JD]  I don't think we need another term for what we are already
> >>  > calling an 'IETF Network Slice Service'.  Adrian and I are considering
> >>  > the term 'resource partition' to describe the partitioning of underlay
> >>  > network resources in support of various overlay services such as IETF
> Network
> >>  Slice Services.
> >>  > This is congruent with the ideas expressed in:
> >>  > https://urldefense.com/v3/__https://datatracker.ietf.org/doc/html/draf
> >>  > t-ietf-spring-resource-aware-segmen__;!!NEt6yMaO-
> >>  gk!TCiJHCZCwFgwpuFouj
> >>  > xVlZ4r9F6mLpE4nJ-9zpqkY-kls-ROxL4C2_xNxEfwaXg$
> >>  > ts-03.  What this allows one to build is an 'partitioned underlay
> >>  > network topology'.
> >>
> >>  [Jie] Agree that here we are talking about the term for the underlay
> construct.
> >>  "Resource partition" captures one of its key characteristics, while IMO
> another
> >>  thing the term needs to reflect is that the resource partition is needed
> on a
> >>  subset of the links and nodes (rather than on a single node or link) in
> the physical
> >>  network, which together builds a logical network topology.
> >
> >[JD]  In my initial email, above, I was proposing 'partitioned underlay
> network topology'
> >
> >>
> >>  Best regards,
> >>  Jie
> >>
> >>  >
> >>  > >
> >>  > > Your opinion about these candidates are much appreciated. You may
> >>  > > also propose other new term if it complies with the above two
> points.
> >>  >
> >>  > [JD]  I think you have exceeded your remit.
> >>  >
> >>  > >
> >>  > >
> >>  > >
> >>  > > Best Regards,
> >>  > > Robin
> >>  > >
> >>  > > _______________________________________________
> >>  > > Teas mailing list
> >>  > > Teas@ietf.org
> >>  > > https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/te
> >>  > > as
> >>  > > __;!!N
> >>  > > Et6yMaO-gk!Q0ycOf0ELxT6mG1GbnO4LSL-Q99J4uu7jfdUtBECaI-
> >>  > > O08HqD31TGJciNjuxL2A$
> >>  >
> >>  > _______________________________________________
> >>  > Teas mailing list
> >>  > Teas@ietf.org
> >>  > https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/teas
> >>  > __;!!NEt6yMaO-gk!TCiJHCZCwFgwpuFoujxVlZ4r9F6mLpE4nJ-9zpqkY-kls-
> >>  ROxL4C2
> >>  > _xNDCrPaNQ$
> >
> >_______________________________________________
> >Teas mailing list
> >Teas@ietf.org
> >https://www.ietf.org/mailman/listinfo/teas
> 
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas
> 
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas