[Teas] Plan for progressing merger of network slicing drafts

Adrian Farrel <adrian@olddog.co.uk> Tue, 13 April 2021 10:03 UTC

Return-Path: <adrian@olddog.co.uk>
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 ED30B3A0FEA for <teas@ietfa.amsl.com>; Tue, 13 Apr 2021 03:03:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.782
X-Spam-Level:
X-Spam-Status: No, score=0.782 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAY_BE_FORGED=2.699, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no autolearn_force=no
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 cbqpabcYDC-F for <teas@ietfa.amsl.com>; Tue, 13 Apr 2021 03:03:13 -0700 (PDT)
Received: from mta6.iomartmail.com (mta6.iomartmail.com [62.128.193.156]) (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 AD9A03A0FE4 for <teas@ietf.org>; Tue, 13 Apr 2021 03:03:11 -0700 (PDT)
Received: from vs2.iomartmail.com (vs2.iomartmail.com [10.12.10.123]) by mta6.iomartmail.com (8.14.4/8.14.4) with ESMTP id 13DA39Ic012414 for <teas@ietf.org>; Tue, 13 Apr 2021 11:03:09 +0100
Received: from vs2.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id EF5452209F for <teas@ietf.org>; Tue, 13 Apr 2021 11:03:08 +0100 (BST)
Received: from asmtp1.iomartmail.com (unknown [10.12.10.248]) by vs2.iomartmail.com (Postfix) with ESMTPS id 12828220E4 for <teas@ietf.org>; Tue, 13 Apr 2021 10:47:44 +0100 (BST)
Received: from LAPTOPK7AS653V (74.197.bbplus.pte-ag1.dyn.plus.net [81.174.197.74] (may be forged)) (authenticated bits=0) by asmtp1.iomartmail.com (8.14.4/8.14.4) with ESMTP id 13D9lhdV023479 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <teas@ietf.org>; Tue, 13 Apr 2021 10:47:43 +0100
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'TEAS WG'" <teas@ietf.org>
Date: Tue, 13 Apr 2021 10:47:42 +0100
Organization: Old Dog Consulting
Message-ID: <0c3601d7304a$0ce8b750$26ba25f0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AdcwSgU6Se8/Nn9wQA+bWxKiWu5DSg==
Content-Language: en-gb
X-Originating-IP: 81.174.197.74
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-26088.006
X-TM-AS-Result: No--5.035-10.0-31-10
X-imss-scan-details: No--5.035-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-26088.006
X-TMASE-Result: 10--5.034600-10.000000
X-TMASE-MatchedRID: z9jZaPM/LM4af3p8Lo2lesmR5yDJkPg4lFGUu7DBzhjNXcHcbKfqs/WJ gt4kdjtvM2fTK2xDdkNrW/tgjC4+Afy8t1SC6KPcU3sFLicCFhV0XCktmVbm9Y728shq0PfIOWp ZLG7WA097V7HfSBmJS79TRqwLWOO9fpLn2LgPptwi/6vJpwCdxAGTUEvH1nWdB3Z6VWYr75wM6X BtKTGUp49icRgipC9nLpPDb/O22SWSoon1eth2f31xZa4kjJT3+LidURF+DB1LGr5hsjyfFbuJB aiamILR6ffqSxkRcQbkrEucXmMa6xCqCY95Uhhxw4LlAWtyEiWpB34ezti/uwg2kgWdt3qaeCNV 1mMi/45L+nDUy5QSWku9b6yxSsh3XlWOx86X2BNKbJsr2oxf7EhMUByBUHErRAqBEla9RS4QTKI swJr+pNyPap3TcMUpbZSw8NL5i2BR+Y5d0bm9QCP1O53jfNSIAveunI5PTNiYH2Fuz7U+NaPFjJ EFr+olfeZdJ1Xsorj72mXKge0hlwtuKBGekqUpIG4YlbCDECtruV6hT84yE4GINhWHqrPHhlwQy 6Kk8aTa20susze0yJpqlsem5Xoe9NH+Yk3ZnTGeqD9WtJkSIw==
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/4OmTcR0-UBVupCL6Nuc2jK9lDUw>
Subject: [Teas] Plan for progressing merger of network slicing drafts
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, 13 Apr 2021 10:03:15 -0000

Hi TEAS,

I wanted to let you know my plans for merging the network slicing drafts.

As you know, the chairs believe it would be best to have one document that
covers the terminology and architecture of IETF network slices. What I am
going to do is...

1. Start a fresh document called draft-ietf-teas-ietf-network-slice
- Authorship
   - I'll make everyone who was an author on the two foundation documents
     an author on the new document
   - Make everyone who was a contributor on the two foundation documents
     a contributor on the new document
   - You are all welcome to ask for a 'demotion' if you like
- Merge
   - The -00 version will be a very simple merge.
   - I will take all text from both documents and include it.
   - Note that the Table of Contents will not directly follow either
document
     since that would be impossible, but the flow should be relatively
simple.
   - I will use tags to show where the text came from.
   - If I don't include text (at the moment I see no reason to not include
any
     text) I will place it in an appendix so it is not lost.
- No new text and no changes
   - This version will not introduce new text or make any changes to text
- Post the document without asking for permission or review

2. Make an Editor's revision -01
- Merge
   - In this version I will attempt to merge the text by removing
duplication and
     by streamlining
- No new text
   - This version will not introduce new text, and changes made will only be
      editorial for the sake of merging. It will not be the intention to
make
      changes to the intention of the foundation documents.
- Post the document without asking for permission or review

3. Open the gates for discussion
- Normal WG discussion can follow

4. Strategic changes
- Sections and topics
   - We have already seen a couple of sections/topics raised on the list
   - This seems like a good way forward:
       - Pick a section or topic
       - Explain the issue you have with the current text
       - Suggest new text
       - WG debates to consensus
       - I update the section in the document and post it
- Teleconferences for debate
   - We should have meetings (interims? Interested parties?) to do work
   - Each meeting should be dedicated to one or more topics or sections
   - May do real-time edits based on previously proposed text

5. Revisions
- I like posting new versions of a document relatively frequently

6. Does the editor drive?
- I hope you will be suggesting text and ideas
- Failing that, I will be supplying suggestions and asking for agreement

Hope this will work for all of you.

Best,
Adrian