A Framework for Network Slices in Networks Built from IETF Technologies
draft-ietf-teas-ietf-network-slices-25

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, draft-ietf-teas-ietf-network-slices@ietf.org, jgs@juniper.net, rfc-editor@rfc-editor.org, teas-chairs@ietf.org, teas@ietf.org, vbeeram@juniper.net
Subject: Document Action: 'A Framework for Network Slices in Networks Built from IETF Technologies' to Informational RFC (draft-ietf-teas-ietf-network-slices-25.txt)

The IESG has approved the following document:
- 'A Framework for Network Slices in Networks Built from IETF
   Technologies'
  (draft-ietf-teas-ietf-network-slices-25.txt) as Informational RFC

This document is the product of the Traffic Engineering Architecture and
Signaling Working Group.

The IESG contact persons are Jim Guichard, Andrew Alston and John Scudder.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-teas-ietf-network-slices/

Ballot Text

Technical Summary

   This document describes network slicing in the context of networks
   built from IETF technologies.  It defines the term "IETF Network
   Slice" and establishes the general principles of network slicing in
   the IETF context.

   The document discusses the general framework for requesting and
   operating IETF Network Slices, the characteristics of an IETF Network
   Slice, the necessary system components and interfaces, and how
   abstract requests can be mapped to more specific technologies.  The
   document also discusses related considerations with monitoring and
   security.

   This document also provides definitions of related terms to enable
   consistent usage in other IETF documents that describe or use aspects
   of IETF Network Slices.

Working Group Summary

   The shepherd sez:

   "There was broad agreement in the WG to progress this document" and 
   "There was no controversy. However, there were rough consensus calls 
   made on a few items after considerable amount of healthy debate and 
   discussion in the WG." 

   It may be worth noting that "The document is a result of merging two 
   documents that were put together by a large design team (appointed by 
   WG chairs)", I imagine that may relate to the "rough consensus calls". 

Document Quality

   The shepherd sez:

   "This document does not propose any protocol extensions. It is an informational
   document that discusses the framework for requesting and operating IETF Network 
   Slices. There are no existing implementations of this framework reported in the
   document. There are some solution documents (which are being discussed in the 
   WG) that adhere to the framework discussed in this document -- these solutions 
   are being driven by several vendors/operators and are expected to eventually get 
   implemented in some form."

Personnel

   The Document Shepherd for this document is Vishnu Pavan Beeram. The
   Responsible Area Director is John Scudder.

RFC Editor Note

RFC Editor Note

  Please update John Drake’s information as je_drake@yahoo.com, affiliation 'individual'.