Re: [Teas] Disposition of draft-ietf-teas-ietf-network-slice-definition-00
Greg Mirsky <gregimirsky@gmail.com> Wed, 31 March 2021 19:53 UTC
Return-Path: <gregimirsky@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 16E483A3507 for <teas@ietfa.amsl.com>; Wed, 31 Mar 2021 12:53:39 -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, RCVD_IN_DNSWL_NONE=-0.0001, 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 snq_zICsud1X for <teas@ietfa.amsl.com>; Wed, 31 Mar 2021 12:53:34 -0700 (PDT)
Received: from mail-lf1-x12c.google.com (mail-lf1-x12c.google.com [IPv6:2a00:1450:4864:20::12c]) (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 416403A3505 for <teas@ietf.org>; Wed, 31 Mar 2021 12:53:34 -0700 (PDT)
Received: by mail-lf1-x12c.google.com with SMTP id o126so30910731lfa.0 for <teas@ietf.org>; Wed, 31 Mar 2021 12:53:34 -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=aNBMONykx4YOccT1O/bwaP7RJTjk/wf/BFoQPvbB0jU=; b=T6GD3grsOwx8cn3QGuz4wqSMWleOG0/0dTeig0B8BQa5HpPcqTwcDP9n2nElvXQQTa 7EXHZcL1fIEMcwQHhGmqlO4b6NPDGy8ZISig98tuPUN83pW+e6IPoYLrTN+k9AbRcjHf Lw2bERLNuBmFPBzVLNyQDa/Cn/tnK2pRj11/0uip7XxDHZ4mh+w7rXRoqiAwFnJ9W5ro yY2dnfyolIpBIpTXzDndWEB5nkV/W1p2iqNN6YtUMZ26hYxZFGCegdlDdeUXCkUiJIHl 9rhUSs5y0k5Z/A01Xzw9esLkWGHD3b337+Ajzhbuhvvf3sBdRyKcMTxlrC+mZwaSUZBZ qbVg==
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=aNBMONykx4YOccT1O/bwaP7RJTjk/wf/BFoQPvbB0jU=; b=t9IvPdC4ImWVP8EVb9cx7QFiXnJ+zJlyg/QAr2RRI1A0gUPV/9uYAXh74HP3TFRMOp yQdLN8619NTr4cxtFoEVw/Q/PCN1Qiu8K5WShsCZVPw8DExpZu4EjyuKH8PT8qBVz2dp RiRjWReyXXaAj+Qyg9JPYeAMq8S3xEQJkfjFposfA+Sb+w9LcCxdGfUMy07G3MBb03lM Fk8wqFj39/mrV46fWYQkrKRr8wpLapAo7F6D2ryVoskwpHVBCmtE74T+WlhxGqJj0bps J1OWvI5OUrL8xUMWBVj12osK4zW54Ipvk4YHxZWOc/WoHONQ8Pd0obamgVj1nTUVySig Aqdw==
X-Gm-Message-State: AOAM532VQj+yAaK3bglHT1oPXJlLKRJ4cK98CQdPTKpdBRHZuAqLcTxT dtKdPSrBC7B5s97R5CvmGiC/8YACdSBCwjxEycA2UVWH2lo=
X-Google-Smtp-Source: ABdhPJzsSZ7ppuSxhhMqwyPEEXoQ3xKW0WYvasBGQxXBLC8DeUKsssetT0udNSklaN1k5plfMMt53iKC8B9h+2JOTHU=
X-Received: by 2002:a19:5005:: with SMTP id e5mr3312222lfb.109.1617220411922; Wed, 31 Mar 2021 12:53:31 -0700 (PDT)
MIME-Version: 1.0
References: <MN2PR05MB66234D9E6C4F7792301731A8C77C9@MN2PR05MB6623.namprd05.prod.outlook.com>
In-Reply-To: <MN2PR05MB66234D9E6C4F7792301731A8C77C9@MN2PR05MB6623.namprd05.prod.outlook.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Wed, 31 Mar 2021 12:53:20 -0700
Message-ID: <CA+RyBmWVbewvLFt5jS1y_Uu-N=K41inBbTiL9RJq--pVL5OjTQ@mail.gmail.com>
To: John E Drake <jdrake=40juniper.net@dmarc.ietf.org>
Cc: "teas@ietf.org" <teas@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002d1b0505beda7842"
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/rryJFnPPOuIPE2XoRwZpUWE3OHg>
Subject: Re: [Teas] Disposition of draft-ietf-teas-ietf-network-slice-definition-00
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: Wed, 31 Mar 2021 19:53:39 -0000
Hi John, Eric, et al., I appreciate the proposal and believe that it correctly reflects the discussion of the draft-ietf-teas-network-slice-definition we had within the DT and as the WG. In fact, I support the proposed updates of the content of the draft-ietf-teas-network-slice-definition while maintaining it as a separate document. In my opinion, either way, works. Regards, Greg On Wed, Mar 31, 2021 at 8:44 AM John E Drake <jdrake= 40juniper.net@dmarc.ietf.org> wrote: > Hi, > > Eric and I have been asked by the teas working group chairs to merge the > subject draft into the framework > draft: > https://datatracker.ietf.org/doc/html/draft-ietf-teas-ietf-network-slice-framework-00. > Our proposal is detailed below. > > > Definition of IETF Network Slices > draft-ietf-teas-ietf-network-slice-definition-01 > > Table of Contents > > 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 > > *****JD The content of the two introductions will be merged > > 2. Terms and Abbreviations . . . . . . . . . . . . . . . . . . . 3 > > *****JD This will be a new section 2 in the Framework draft. The > current > section 2 of the Framework draft will be split between the new section 2 > and possibly sections 3 and 4. > > 3. Definition and Scope of IETF Network Slice . . . . . . . . . 4 > > *****JD This section will be moved to the new section 2. > > 4. IETF Network Slice System Characteristics . . . . . . . . . . 4 > > *****JD This section will be moved to the new section 2 > > 4.1. Objectives for IETF Network Slices . . . . . . . . . . . 5 > > *****JD This section will be split between the new section 2 and > possibly sections 3 and 4. > > 4.1.1. Service Level Objectives . . . . . . . . . . . . . . 5 > 4.1.2. Minimal Set of SLOs . . . . . . . . . . . . . . . . . 5 > 4.1.3. Other Objectives . . . . . . . . . . . . . . . . . . 7 > > *****JD These sections will be moved to the new section 2. > > 4.2. IETF Network Slice Endpoints . . . . . . . . . . . . . . 7 > > *****JD This section will be moved to the new section 2 and will be > updated to use the terminology agreed upon on the mailing list. A > reference to RFC 4364's section 9 "Carriers' Carriers" ( > https://datatracker.ietf.org/doc/html/rfc4364#section-9) > will be added. We will also note that the 'CE', 'attachment circuit', and > 'PE' can all be virtualized. > > 4.2.1. IETF Network Slice Connectivity Types . . . . . . . . 9 > > *****JD This section will be moved to the new section 2. > > 4.3. IETF Network Slice Composition . . . . . . . . . . . . . 9 > > *****JD This section will be moved to the new section 2. Note that the > non-definitional material in *all* of the preceding sections will be split > between sections 3 and 4. Section > 4 will become a generalized 'Applicability' section . > > 5. IETF Network Slice Structure . . . . . . . . . . . . . . . . 10 > > *****JD This section will be split between the new section 2 and > possibly sections 3 and 4. > > 6. IETF Network Slice Stakeholders . . . . . . . . . . . . . . . 11 > > *****JD This section will be moved to section 4. > > 7. IETF Network Slice Controller Interfaces . . . . . . . . . . 12 > > *****JD This is covered in section 3.3. > > 8. Realizing IETF Network Slice . . . . . . . . . . . . . . . . 12 > > *****JD This is covered in section 3.5. > > 9. Isolation in IETF Network Slices . . . . . . . . . . . . . . 13 > 9.1. Isolation as a Service Requirement . . . . . . . . . . . 13 > 9.2. Isolation in IETF Network Slice Realization . . . . . . . 13 > > *****JD These sections will be moved to the new section 2. They assume a > definition of the term 'isolation' which has never been explicitly > rendered, so we will propose a definition to the mailing list. > > 10. Security Considerations . . . . . . . . . . . . . . . . . . . 14 > > *****JD Relevant material will be moved to section 5.2. We will propose > what we consider to be relevant and irrelevant material to the mailing > list. > > 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 > > *****JD The Framework draft already has this section. > > 12. Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . 15 > > *****JD This section will be moved to section 6. > > 13. Informative References . . . . . . . . . . . . . . . . . . . 15 > > *****JD This section will be moved to section 7. > > Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17 > > *****JD This will need to be sorted out with the authors and contributors > to the Framework draft. > > > > *****JD For reference, below is the current table of contents for the > Framework draft: > > Framework for IETF Network Slices > draft-ietf-teas-ietf-network-slice-framework-00 > > Table of Contents > > 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 > 2. IETF Network Slice Objectives . . . . . . . . . . . . . . . . 4 > 3. Framework . . . . . . . . . . . . . . . . . . . . . . . . . . 5 > 3.1. Management systems or other applications . . . . . . . . 6 > 3.2. Expressing connectivity intents . . . . . . . . . . . . . 6 > 3.3. IETF Network Slice Controller (NSC) . . . . . . . . . . . 8 > 3.3.1. Northbound Interface (NBI) . . . . . . . . . . . . . 9 > 3.4. Mapping . . . . . . . . . . . . . . . . . . . . . . . . . 9 > 3.5. Underlying technology . . . . . . . . . . . . . . . . . . 9 > 4. Applicability of ACTN to IETF Network Slices . . . . . . . . 10 > 5. Considerations . . . . . . . . . . . . . . . . . . . . . . . 12 > 5.1. Monitoring . . . . . . . . . . . . . . . . . . . . . . . 12 > 5.2. Security Considerations . . . . . . . . . . . . . . . . . 13 > 5.3. Privacy Considerations . . . . . . . . . . . . . . . . . 13 > 5.4. IANA Considerations . . . . . . . . . . . . . . . . . . . 13 > 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 13 > 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 14 > 7.1. Normative References . . . . . . . . . . . . . . . . . . 14 > 7.2. Informative References . . . . . . . . . . . . . . . . . 14 > Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . 17 > Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18 > > Yours Irrespectively, > > John > > > Juniper Business Use Only > > _______________________________________________ > Teas mailing list > Teas@ietf.org > https://www.ietf.org/mailman/listinfo/teas >
- [Teas] Disposition of draft-ietf-teas-ietf-networ… John E Drake
- Re: [Teas] Disposition of draft-ietf-teas-ietf-ne… LUIS MIGUEL CONTRERAS MURILLO
- Re: [Teas] Disposition of draft-ietf-teas-ietf-ne… Greg Mirsky
- Re: [Teas] Disposition of draft-ietf-teas-ietf-ne… mohamed.boucadair