Re: Working with IEEE 802

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Wed, 21 September 2016 19:39 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 399B712B56A; Wed, 21 Sep 2016 12:39:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 9cVMB8W171WL; Wed, 21 Sep 2016 12:39:38 -0700 (PDT)
Received: from mail-yw0-x22c.google.com (mail-yw0-x22c.google.com [IPv6:2607:f8b0:4002:c05::22c]) (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 480DE12B4F2; Wed, 21 Sep 2016 12:39:38 -0700 (PDT)
Received: by mail-yw0-x22c.google.com with SMTP id u82so70635516ywc.2; Wed, 21 Sep 2016 12:39:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=tmMvciynSjDs/Kmo0cRPRog1BJLMTjWuNM+S7zfJnRo=; b=y1pl7Go2Pj3CCy0HEDxdDfdxj0qRodutTNdXETlD2oIEL0pNR5Xil4Y+6nUWDCJ9KL Qzn804JIwaj0fer3OgxXeTC4EeyrMdDhcSqfL96mDyw5RlElLi0jHIrCxfX3CWm9ftSp GTkRKzLo8QgXlmjHoyuYiwFDm8cSW1mlFFiFLgJbdFmxWqgLwvPaEDMdi6uKsTOXsqQp zaZvi4zCyyT7HdlXj1rVNsmIUo52zC+dl5Hoc2SU9iF7k7f8FsgxYcgo3EAi4X1obAIf PH2NgFf8/Bn6B03yfx4vriFeRTm7VpclXxBkKKQp/ksgayUayom0hmsM7lCvumPGrbZr DSdg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=tmMvciynSjDs/Kmo0cRPRog1BJLMTjWuNM+S7zfJnRo=; b=kf3rNZ+heiUAehXkKW195Rl3x30pXwbWhQB7WinfNovEJImyCxRG31nAymk8GGpbQE HR0EsMPhEZgqhsbEChCVago4MGVTNTzTU/kUkbPlMbcOLjwJpKDvEOEW2sbJCXNOxSw5 Dby+qSE5zBucxDR2YYKExq1J8UwLxHuCSeiscGWOBiQfMiejw7oVZ9PnABTPdnF5VtB6 Yd768EyipZeWaIyWGW/tOviqtIE9OzE5+BO36qSYbVoFAMM648njEBXoYoW41dtCk7sU YBWUVHE29875040shOCpwyV0E+6QsbT9DQNrHTfar6yJhOEU8AZz9Tqfn0bUjzKAUtWq UP1A==
X-Gm-Message-State: AE9vXwP9vwTLvMExaKGVaoDvm/sNck0tbyZ7NyVNr/pMQ7aGEanker+HdT6linpmW0QJA/OwHoZL7Gs/mLrDDQ==
X-Received: by 10.13.201.199 with SMTP id l190mr40662444ywd.181.1474486777629; Wed, 21 Sep 2016 12:39:37 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.24.86 with HTTP; Wed, 21 Sep 2016 12:39:37 -0700 (PDT)
In-Reply-To: <CAC4RtVBvphc02M4cVzmsLZKDaQn7cBJCk9K4uxS0yv3T2Yzd1w@mail.gmail.com>
References: <CADnDZ88y+GFa1qCctrS+KBgZ31KxWrKEq6Bpqd95zEkXy3tZXw@mail.gmail.com> <be89fc12-9ffa-1d69-c3ce-66141cf4ec80@bogus.com> <CAC4RtVBvphc02M4cVzmsLZKDaQn7cBJCk9K4uxS0yv3T2Yzd1w@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Wed, 21 Sep 2016 14:39:37 -0500
Message-ID: <CAKKJt-dmT5Guz_HLmbv5dphXsoctSBs+x6FP5H8kN2cncfZf2Q@mail.gmail.com>
Subject: Re: Working with IEEE 802
To: Barry Leiba <barryleiba@computer.org>
Content-Type: multipart/alternative; boundary=001a114e711c9b527f053d09b41a
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/EELgaQpKxKYt_8Q1ZcJsQgKAWCo>
Cc: IETF Chair <chair@ietf.org>, ietf <ietf@ietf.org>, Abdussalam Baryun <abdussalambaryun@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Sep 2016 19:39:40 -0000

I agree with Barry and Joel on their suggestions.

On Wed, Sep 21, 2016 at 2:22 AM, Barry Leiba <barryleiba@computer.org>
wrote:

> > On 9/19/16 7:48 PM, Abdussalam Baryun wrote:
> >> This coordination issue with other organisations related to standards
> >> is very important and affects pretty much our work, I suggest that the
> >> General Area opens a WG for this important coordination, many
> >> information are needed to be documented and focused on. IMHO, getting
> >> information about contacts will help each IETF WG separately, but what
> >> about the decisions for the whole IETF coordination with other SDOs
> >> especially when we get more deep in future. Having contacts between
> >> managers in SDOs is good start but usually in IETF our managers
> >> decisions reform after looking into the IETF WG ideas and decisions.
> >> Therefore, my suggestion is opening a discussion of why not future
> >> coordination through WG? or is it right time? or do we need a new
> >> work-process?
> >>
> >> I don't know the answers, does any one know?
> >
> > you should take a look at rfc 4052
>
> And for IEEE in particular, at RFC 7241.
>
> Barry
>

I'd note that the other SDOs that the IETF cooperated well with, while I
was still on the IAB and responsible for paying more attention to liaison
relationships in general, tended to be fairly open for individual
participation, and/or had participants who also participated in IETF.

If neither of those conditions holds, things get harder.

But this thread would be a good conversation to have with the IAB, who is
chartered with liaison oversight in RFC 2850, and have their own liaison
coordination program (details at
https://www.iab.org/activities/programs/iab-liaison-coordination-program/).
I'd start there, if I had ideas about IETF liaisons.

Spencer, speaking as a *former* IAB member