Re: [ieee-ietf-coord] comment on IEEE 802 position statement

Roger Marks <r.b.marks@ieee.org> Sun, 26 July 2020 17:46 UTC

Return-Path: <r.b.marks@ieee.org>
X-Original-To: ieee-ietf-coord@ietfa.amsl.com
Delivered-To: ieee-ietf-coord@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33C8B3A104E for <ieee-ietf-coord@ietfa.amsl.com>; Sun, 26 Jul 2020 10:46:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.838
X-Spam-Level:
X-Spam-Status: No, score=-1.838 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=0.26, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ieee.org
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 Yg6IuplDChFN for <ieee-ietf-coord@ietfa.amsl.com>; Sun, 26 Jul 2020 10:46:15 -0700 (PDT)
Received: from mail-ot1-x32e.google.com (mail-ot1-x32e.google.com [IPv6:2607:f8b0:4864:20::32e]) (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 314333A104D for <ieee-ietf-coord@ietf.org>; Sun, 26 Jul 2020 10:46:15 -0700 (PDT)
Received: by mail-ot1-x32e.google.com with SMTP id w17so10682421otl.4 for <ieee-ietf-coord@ietf.org>; Sun, 26 Jul 2020 10:46:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ieee.org; s=google; h=date:from:to:message-id:in-reply-to:references:subject:mime-version; bh=ZYpfCgBtJjbjEGf9WpPluksza14O6Fq33mxx6QpXkbY=; b=fQ7wcTUxwKB0PmvPw8LXUCDYzVimnC+RQ55LcT47lFDFsjQU6ZdND82a1UKXMGN2nd USfrpEpilVCgrZOHeyYGcU0L2M7ZG+CBAPhiOkNKXbF2aUD0sCHZHKqlG9lVImipr9we B3g2rKBqPwGtc0bJqaYzCEP6ZkbSI50O/1Ix4=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:message-id:in-reply-to:references :subject:mime-version; bh=ZYpfCgBtJjbjEGf9WpPluksza14O6Fq33mxx6QpXkbY=; b=VGRyt0N/3zMQTx7KZZPBU8zbuqG3q/YUWvhdnj6aJ2ZN0vAbgjpMAROsa8iGmQZtJH mZdifFbcAfs0fWEvNC1FZo3Je3eN4YM6Mv0eq77WcKetZw7KoZnUqIpecAvJA5xerCLK Ws2fzud/OO8jTEoWOCTjeYCzQaH2eG76SIsIK3bqisigauHDprs6lHJGhdshYFfmfHc6 53uG4cI7OvAkjSWbp3vg545RYVfNut2GqPBSr/dTtgh0lxsMkZ56cT/9+3rFvtJHi5n3 jGQFttVK/dz08yqHhSAPB7kqMb8ZiUeFUK7cBLcq6+yHc7ujohbQGX4HvQ3yP026LieU FQIA==
X-Gm-Message-State: AOAM532QvBawDubkDdQeZ9p0Z53GpMyPruiZM4D6GsCrh4xvWcaffIMq j1UF6dL2hK6o/GHRl829cQgsxegq9nc=
X-Google-Smtp-Source: ABdhPJwxzdgrLBYXVcH2nKLvBSp3Vmft3HJXe8W2cM2VedKH4a1gyvJwGQGCFvCfDpHme2e+lsAjyQ==
X-Received: by 2002:a05:6830:1e42:: with SMTP id e2mr16959738otj.46.1595785573830; Sun, 26 Jul 2020 10:46:13 -0700 (PDT)
Received: from [192.168.1.200] (c-73-14-166-156.hsd1.co.comcast.net. [73.14.166.156]) by smtp.gmail.com with ESMTPSA id i9sm2366833oos.33.2020.07.26.10.46.08 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 26 Jul 2020 10:46:13 -0700 (PDT)
Date: Sun, 26 Jul 2020 11:45:50 -0600
From: Roger Marks <r.b.marks@ieee.org>
To: "ieee-ietf-coord@ietf.org" <ieee-ietf-coord@ietf.org>, Glenn Parsons <glenn.parsons=40ericsson.com@dmarc.ietf.org>
Message-ID: <a5ae5873-1c22-4365-8589-a2b714968a90@Spark>
In-Reply-To: <CY4PR15MB1270F53F059AA51898B861588B770@CY4PR15MB1270.namprd15.prod.outlook.com>
References: <CY4PR15MB1270F53F059AA51898B861588B770@CY4PR15MB1270.namprd15.prod.outlook.com>
X-Readdle-Message-ID: a5ae5873-1c22-4365-8589-a2b714968a90@Spark
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="5f1dc157_49c0e823_2a1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ieee-ietf-coord/ddWPZJEGFLFbWm6KMJtCMk5Vk2k>
Subject: Re: [ieee-ietf-coord] comment on IEEE 802 position statement
X-BeenThere: ieee-ietf-coord@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Management-level discussions between IEEE and IETF on topics of interest to both SDOs <ieee-ietf-coord.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ieee-ietf-coord>, <mailto:ieee-ietf-coord-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ieee-ietf-coord/>
List-Post: <mailto:ieee-ietf-coord@ietf.org>
List-Help: <mailto:ieee-ietf-coord-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ieee-ietf-coord>, <mailto:ieee-ietf-coord-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Jul 2020 17:46:18 -0000

Glenn,

What is the anticipated use of this statement?

I have some general comments:
(a) If 802 has a concern, I would prefer that it make a request or advocate a position.
(b) You said that "IETF has already sent a liaison on this," but I don't know if a reader would know that the 802 paragraph is even on the same subject. The subject of the IETF statement is specific, but the subject of the proposed 802 statement is generic.
(c) Since IEEE is a member of ITU/T, it's in a position to advance its views. Is 802 asking for an additional role in ITU-T, beyond that provided to an ITU-T member?

Here are some specific comments:

The  IEEE 802 LAN/MAN Standards Committee (LMSC) develops and maintains networking standards and recommended practices for local, metropolitan, and other area networks, using an open and accredited process, and advocates them on a global basis.  In order to ensure consistent global impact of standardization and increase awareness of the ecosystem related to network implementation and operation, IEEE 802 maintains liaison relationships with other groups.  Communication is key to a healthy working relationship, fostering an understanding of the working methods of the different groups which aids and thereby aiding efficient and non-duplicative standards development.  IEEE 802 is engaged in standardization efforts that are integral building blocks of the Internet and pPrivate Nnetworks.  Any standardization efforts that are investigating the evolution or a revolution related to the Internet, Internet Protocol, or how the Internet or Internet Protocols leverage the published IEEE 802 standards or ongoing development is of interest to the IEEE 802 LMSC and we request coordination.

Cheers,

Roger
On Jul 24, 2020, 2:51 PM -0600, Glenn Parsons <glenn.parsons=40ericsson.com@dmarc.ietf.org>, wrote:
> Colleagues,
>
> Regarding ITU-T and proposals made in the context of their next study period, there are topics of interest/concern for IEEE 802..  As a result, the following position is being proposed for approval by the IEEE 802 LMSC on Aug 4th.  Given IETF has already sent a liaison on this (https://datatracker.ietf.org/liaison/1677/), and in the spirit of cooperation, IEEE 802 would like to solicit feedback from IETF to ensure that our statement is complementary.
>
>
> The  IEEE 802 LAN/MAN Standards Committee (LMSC) develops and maintains networking standards and recommended practices for local, metropolitan, and other area networks, using an open and accredited process, and advocates them on a global basis.  In order to ensure consistent global impact of standardization and increase awareness of the ecosystem related to network implementation and operation, IEEE 802 maintains liaison relationships with other groups.  Communication is key to a healthy working relationship fostering an understanding of the working methods of the different groups which aids efficient and non-duplicative standards development.  IEEE 802 is engaged in standardization efforts that are integral building blocks of the Internet and Private Networks.  Any standardization efforts that are investigating the evolution or a revolution related to the Internet, Internet Protocol, or how the Internet or Internet Protocols leverage the published IEEE 802 standards is of interest to the IEEE 802 LMSC.
>
>
> Cheers,
> Glenn.
> --
> Glenn Parsons
> Chair, IEEE 802.1 WG
> glenn.parsons@ericsson.com
> +1-613-963-8141
>
> _______________________________________________
> ieee-ietf-coord mailing list
> ieee-ietf-coord@ietf.org
> https://www.ietf.org/mailman/listinfo/ieee-ietf-coord