Re: [Raw] Charter alignment of WG documents

Rick Taylor <rick@tropicalstormsoftware.com> Tue, 14 July 2020 16:09 UTC

Return-Path: <rick@tropicalstormsoftware.com>
X-Original-To: raw@ietfa.amsl.com
Delivered-To: raw@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61DB43A0932 for <raw@ietfa.amsl.com>; Tue, 14 Jul 2020 09:09:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 lkinqHOR_4tp for <raw@ietfa.amsl.com>; Tue, 14 Jul 2020 09:09:36 -0700 (PDT)
Received: from mail.tropicalstormsoftware.com (mail.tropicalstormsoftware.com [188.94.42.120]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CD7583A096B for <raw@ietf.org>; Tue, 14 Jul 2020 09:09:28 -0700 (PDT)
Received: from tss-server1.home.tropicalstormsoftware.com ([fe80::48e4:acbb:6065:8168]) by tss-server1.home.tropicalstormsoftware.com ([fe80::48e4:acbb:6065:8168%16]) with mapi id 14.03.0487.000; Tue, 14 Jul 2020 17:09:26 +0100
From: Rick Taylor <rick@tropicalstormsoftware.com>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
CC: "raw@ietf.org" <raw@ietf.org>
Thread-Topic: [Raw] Charter alignment of WG documents
Thread-Index: AdZZvlz0a553Fns+T3KAKQpnHYm6rQAFdRblAAj5VEA=
Date: Tue, 14 Jul 2020 16:09:24 +0000
Message-ID: <38A5475DE83986499AEACD2CFAFC3F9801F585CC58@tss-server1.home.tropicalstormsoftware.com>
References: <38A5475DE83986499AEACD2CFAFC3F9801F585CA14@tss-server1.home.tropicalstormsoftware.com> <7AE107A2-D4AC-4FEC-967F-E6838BD7E690@cisco.com>
In-Reply-To: <7AE107A2-D4AC-4FEC-967F-E6838BD7E690@cisco.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [2a02:1648:4000:120:849b:b085:a1a8:1136]
Content-Type: multipart/alternative; boundary="_000_38A5475DE83986499AEACD2CFAFC3F9801F585CC58tssserver1hom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/raw/UFcsKuMPtA5Azoi_yfRfvGP4enk>
Subject: Re: [Raw] Charter alignment of WG documents
X-BeenThere: raw@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: reliable and available wireless <raw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/raw>, <mailto:raw-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/raw/>
List-Post: <mailto:raw@ietf.org>
List-Help: <mailto:raw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/raw>, <mailto:raw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jul 2020 16:09:38 -0000

Hi Pascal,

(sorry for the top-post)

*Not* speaking as a co-chair.

I am in agreement with you, I do not feel a re-charter is appropriate, and would prefer to ‘massage’ our existing set of documents to capture the spirit of the charter and the needs to the WG.  However, as I am not an author of any of these documents and understand the amount of work that goes into a draft, so I am cautious about asking authors to start reorganising documents without a compelling reason.

I don’t believe we are far off at all.  Eve and my question to the WG group was based on this assumption.  Before too long I feel we will have many documents adopted, reviewed and ready for the IESG, so we just wanted to ensure that there is consensus in the WG about the relationship between the content of the documents, the charter and associated WGs such as DetNet before we get too far along this process.

Cheers,

Rick


From: Pascal Thubert (pthubert) [mailto:pthubert@cisco.com]
Sent: 14 July 2020 12:45
To: Rick Taylor
Cc: raw@ietf.org
Subject: Re: [Raw] Charter alignment of WG documents

Hello Rick

The problem statement draft was not listed in the final charter and slowly evolved into a combination of requirements, framework and architecture to march the charter. We also have a use case draft. For those we are mostly in line.

The gap analysis can only be done when the above are well agreed upon.

We do not have a charter item for the technologies we want to cover. That went away during the IESG negotiations and though the term “technologies” was conserved, the goal has completely derived. Even without a charter item the work is plainly in scope considering the first paragraph that lists the core technologies. How can the WG work on them without providing an informational description of what they are?

Up to the AD but I trust we can adopt without a recharter.
So we are not that far off are we?


Pascal


Le 14 juil. 2020 à 11:11, Rick Taylor <rick@tropicalstormsoftware.com> a écrit :

Hi All,

The chairs are currently putting together that agenda for IETF-108, and one of the topics we would like to discuss on-list and during the meeting is the alignment of the current selection of WG drafts and the WG charter.

As it currently stands, we have a number of drafts that describe the architecture, use-cases, details of various RAW technologies, and OAM.  However, the charter discusses documents describing technical evaluation, requirements, etc.

We are interested in the opinion of the various draft authors and the WG as a whole to the idea of either reorganising the content of documents to match those described by the charter, or updating the charter to match our mental model of the RAW drafts needed.  At the same time, we wonder if it is important for the RAW WG documents to mimic the structure of the DetNet foundational docs (Problem Statement, Use Cases, Architecture) more closely.

We understand that there would be pain and delay involved in reworking these documents and/or the charter, and we would like the WG to balance the pain against any perceived benefit.  We also do not want to discourage the current author teams – we greatly value all their current input, and want to maintain that momentum.

We hope this starts a productive conversation, and we are looking to reach some consensus shortly after IETF-108.

Cheers,

Rick & Eve


--
RAW mailing list
RAW@ietf.org
https://www.ietf.org/mailman/listinfo/raw