Re: [Raw] Alissa Cooper's Block on charter-ietf-raw-00-02: (with BLOCK)

"BRUNGARD, DEBORAH A" <db3546@att.com> Wed, 05 February 2020 17:07 UTC

Return-Path: <db3546@att.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 E67DA1200BA; Wed, 5 Feb 2020 09:07:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-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 6fXeUFu7aLKA; Wed, 5 Feb 2020 09:07:41 -0800 (PST)
Received: from mx0a-00191d01.pphosted.com (mx0a-00191d01.pphosted.com [67.231.149.140]) (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 03B9C120145; Wed, 5 Feb 2020 09:07:40 -0800 (PST)
Received: from pps.filterd (m0048589.ppops.net [127.0.0.1]) by m0048589.ppops.net-00191d01. (8.16.0.42/8.16.0.42) with SMTP id 015H5hw5026716; Wed, 5 Feb 2020 12:07:37 -0500
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by m0048589.ppops.net-00191d01. with ESMTP id 2xyhq8j7d9-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 05 Feb 2020 12:07:37 -0500
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id 015H7YNo004126; Wed, 5 Feb 2020 12:07:35 -0500
Received: from zlp27128.vci.att.com (zlp27128.vci.att.com [135.66.87.50]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id 015H7WE3004079 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 5 Feb 2020 12:07:32 -0500
Received: from zlp27128.vci.att.com (zlp27128.vci.att.com [127.0.0.1]) by zlp27128.vci.att.com (Service) with ESMTP id B48F5400A0A8; Wed, 5 Feb 2020 17:07:32 +0000 (GMT)
Received: from MISOUT7MSGHUBAA.ITServices.sbc.com (unknown [130.9.129.145]) by zlp27128.vci.att.com (Service) with ESMTPS id 9B3C9400A0A3; Wed, 5 Feb 2020 17:07:32 +0000 (GMT)
Received: from MISOUT7MSGUSRDE.ITServices.sbc.com ([169.254.5.116]) by MISOUT7MSGHUBAA.ITServices.sbc.com ([130.9.129.145]) with mapi id 14.03.0468.000; Wed, 5 Feb 2020 12:07:32 -0500
From: "BRUNGARD, DEBORAH A" <db3546@att.com>
To: "Venkatesan, Ganesh" <ganesh.venkatesan@intel.com>
CC: Alissa Cooper <alissa@cooperw.in>, "raw-chairs@ietf.org" <raw-chairs@ietf.org>, "raw@ietf.org" <raw@ietf.org>, The IESG <iesg@ietf.org>
Thread-Topic: [Raw] Alissa Cooper's Block on charter-ietf-raw-00-02: (with BLOCK)
Thread-Index: AQHV26Or66VPlAvo+ESqEke1TyIa56gM0S8+gABWwYD//65KDA==
Date: Wed, 5 Feb 2020 17:07:31 +0000
Message-ID: <5688ECF0-1C83-40DE-942E-2C5BB300536B@att.com>
References: <158085239614.15693.12020911716179839628.idtracker@ietfa.amsl.com> <E9F0EC1A-E38F-4F3E-B2F1-088404964782@att.com>, <311BE885E0DA8D4BB369A037CF5B64A7A067147E@ORSMSX107.amr.corp.intel.com>
In-Reply-To: <311BE885E0DA8D4BB369A037CF5B64A7A067147E@ORSMSX107.amr.corp.intel.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.138, 18.0.572 definitions=2020-02-05_05:2020-02-04, 2020-02-05 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 mlxscore=0 adultscore=0 clxscore=1011 impostorscore=0 priorityscore=1501 lowpriorityscore=0 mlxlogscore=999 spamscore=0 bulkscore=0 suspectscore=0 phishscore=0 malwarescore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2001150001 definitions=main-2002050130
Archived-At: <https://mailarchive.ietf.org/arch/msg/raw/EmUUM45CMbdM6s5GnbC8ZoEqVok>
Subject: Re: [Raw] Alissa Cooper's Block on charter-ietf-raw-00-02: (with BLOCK)
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: Wed, 05 Feb 2020 17:07:44 -0000

Exactly- we need to provide timely standard solutions for these applications-

Deborah

Sent from my iPhone

> On Feb 5, 2020, at 12:00 PM, Venkatesan, Ganesh <ganesh.venkatesan@intel.com> wrote:
> 
> Hello All:
>>> Some of these applications already are existing with proprietary solutions.
> 
> Is this something that we want to encourage? I would think that standardized solutions are far better from the perspective of interoperability and enablement of new markets.
> 
> Cheers --
> ganesh
> “It is amazing what you can accomplish if you don’t care who gets the credit.” – Harry Truman
>  
> 
> -----Original Message-----
> From: Raw <raw-bounces@ietf.org> On Behalf Of BRUNGARD, DEBORAH A
> Sent: Wednesday, February 5, 2020 8:49 AM
> To: Alissa Cooper <alissa@cooperw.in>
> Cc: raw-chairs@ietf.org; raw@ietf.org; The IESG <iesg@ietf.org>
> Subject: Re: [Raw] Alissa Cooper's Block on charter-ietf-raw-00-02: (with BLOCK)
> 
> Hi Alissa,
> 
> Please refer to Pascal’s reply for background.
> 
> I didn’t intend to scope this to only aeronautical applications. I was only trying to point to it as one of the critical. As the use cases are under discussion, I didn’t want at this time to give “the answer”. The use case document has more information.
> 
> As you and Alvaro are looking for more detail, would this sentence added to the end of the second paragraph help?
> 
> “Other example wireless applications include Industrial, Pro Audio and Video, Gaming, and Edge Robotics.”
> 
> The intention of why this is not scoped specifically to aeronautical is because the hope is to find a common solution for multiple applications similar to the detnet, teas, and ccamp approach.
> 
> On your second part questioning which is first - applications or use cases- I’m not sure the confusion. Some of these applications already are existing with proprietary solutions. Others as Pascal noted are waiting for technology improvements. Can you provide suggested rewording to help us understand?
> 
> Thanks for your interest!
> Deborah 
> 
> 
>> On Feb 4, 2020, at 4:40 PM, Alissa Cooper via Datatracker <noreply@ietf.org> wrote:
>> 
>> Alissa Cooper has entered the following ballot position for
>> charter-ietf-raw-00-02: Block
>> 
>> When responding, please keep the subject line intact and reply to all 
>> email addresses included in the To and CC lines. (Feel free to cut 
>> this introductory paragraph, however.)
>> 
>> 
>> 
>> The document, along with other ballot positions, can be found here:
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.
>> org_doc_charter-2Dietf-2Draw_&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=6UhG
>> pW9lwi9dM7jYlxXD8w&m=502tSGOqoismvYiL8leAR3QQnD4BL_k8zLb-AfTcfEo&s=ugP
>> n41aRiN67TWEyT9eFhIzEILnyFFm_cKV5BmDYGBU&e=
>> 
>> 
>> 
>> ----------------------------------------------------------------------
>> BLOCK:
>> ----------------------------------------------------------------------
>> 
>> I still feel that the charter is unclear on the relationship between 
>> "Aeronautical Data Applications" and the work of this WG. The charter 
>> says this is "one" critical application, but then uses the term "these 
>> newly identified industry applications" and "these newer industry 
>> applications." Do those snippets of text refer to multiple different 
>> aeronautical applications? Or do they refer to applications in other 
>> domains? Since the aeronautical applications are called out multiple 
>> times, are they expected to take precedence over other applications 
>> when the use cases and requirements are defined?
>> 
>> Also, this is a little pedantic but since there has been a lot of 
>> confusion about this, I think it needs to be clarified: the charter 
>> says "RAW’s focus will be on identifying use cases and requirements for these new applications."
>> Wouldn't we expect applications to flow from use cases, not the other 
>> way around? That is, if the WG intends to invent use cases for 
>> applications that already exist, that seems backwards.
>> 
>> 
>> 
>> 
>> --
>> Raw mailing list
>> Raw@ietf.org
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mail
>> man_listinfo_raw&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=6UhGpW9lwi9dM7jYl
>> xXD8w&m=502tSGOqoismvYiL8leAR3QQnD4BL_k8zLb-AfTcfEo&s=5MVQbSJo0RLpCObZ
>> kYE9G-SwrJB44e4uVsdyMi-ZdWc&e=
> --
> Raw mailing list
> Raw@ietf.org
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_raw&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=6UhGpW9lwi9dM7jYlxXD8w&m=b8YaPgiIvQDkqWDZFQ7QSLq9n1W00Jgze0jOn4baBC4&s=5CQGOOyeRZT7cZI5GIjD4AlCemnW9o0-H80MQ1Zi1L8&e=