Re: Working with IEEE 802

Kalilou Dama <kaliloudama@yahoo.fr> Thu, 22 September 2016 10:47 UTC

Return-Path: <kaliloudama@yahoo.fr>
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 BF38112D73C for <ietf@ietfa.amsl.com>; Thu, 22 Sep 2016 03:47:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.fr
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 b7-6IoTlsiU0 for <ietf@ietfa.amsl.com>; Thu, 22 Sep 2016 03:47:22 -0700 (PDT)
Received: from nm20-vm7.bullet.mail.ir2.yahoo.com (nm20-vm7.bullet.mail.ir2.yahoo.com [212.82.96.249]) (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 3B32012D67D for <ietf@ietf.org>; Thu, 22 Sep 2016 03:47:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.fr; s=s2048; t=1474541239; bh=iPqawOZ0P4AzJ9HdE0FFJPt7LdHexG3ZdW8Id18KBDw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=Go5/I/jy66inaDfl1HDQOPSwt/xaakTBGUYOBC4jl5l1Btkq4zIxXTuo4ESEmuQ3ohh+d+O59I66KS9vWZ+mpDd9vOm79a5xdHi/3pb7aFfHlkxhyf6R8vLuhiDiod/W11k/h/zU1F5zB3lL/Bsg4ij7Su977T/DGgMx0UignofjXr0vLbK+ZzngcDaeNzuWh2uz98Y4cdVccMrJMQy+7w/UtTpd1cn2O5+ROCYxLykH1fVojhsArPlDWvuveyneZvm9Xikbo6fNJ11V91eAiJKw2+wNuI5oY+XfDs0wKWBgb6JUQ2efp4AYfvUVK+tjLoK9PCOkBdNrH5R8DzwfCA==
Received: from [212.82.98.52] by nm20.bullet.mail.ir2.yahoo.com with NNFMP; 22 Sep 2016 10:47:19 -0000
Received: from [212.82.98.96] by tm5.bullet.mail.ir2.yahoo.com with NNFMP; 22 Sep 2016 10:47:19 -0000
Received: from [127.0.0.1] by omp1033.mail.ir2.yahoo.com with NNFMP; 22 Sep 2016 10:47:19 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 274586.79045.bm@omp1033.mail.ir2.yahoo.com
X-YMail-OSG: bOTgmMQVM1nAS50_RN.N1FIRd_nJuAAwbPoAgcCwPHkSBw6iok.YXXBF4I4BrvX TLy21YXZ_uB19L_UgRPr3gfaKgfiiy4job2PCK18mplqzn5tIc9RjuwtWcXiSx2HafFEnfkJ_59i nY0NmJNtEwFBcSmW6uGsPvF8GwFG0YwhSjqsEMUpqnkPreqF.34MOTWbCASpsHE7oc6w9.M6.3IE zxiEDxLTIhQYCFlDBngYNVw8APkOG4vsqpQC9lO_VLU1N1b2AuwdXszHrUs6siOKoG69ntEjbVUm rfksWLU6Jmau4UBY_Vq84t_PHRVXN_tHLIBmKEa6Frh3gpuO4Kl6sv5Nm9sN9pgRk4ZFSd5hyqNP 4eDi9P0SwYtKBPG_gSEqpd0kcUDGBR80HF8hJ.qnFFW2QR3aV4FM7n2LsfLlcr4NEgcxAImrp8OM 9sqeNrA7LU4VVwPmohCti4apcrmUGUJ32WOYA72DHy9EvFmIqJ_lYTgF12wG5zOB_CmT10ytWXN_ ZkEXgPPVsoPS6G26T5ajk_fKh.DwtQ.h1B24Cq_go980xuEO.muYWx9vQWgX19w--
Received: from jws11196.mail.ir2.yahoo.com by sendmailws107.mail.ir2.yahoo.com; Thu, 22 Sep 2016 10:47:18 +0000; 1474541238.868
Date: Thu, 22 Sep 2016 10:47:18 +0000 (UTC)
From: Kalilou Dama <kaliloudama@yahoo.fr>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, Barry Leiba <barryleiba@computer.org>
Message-ID: <1668093647.5450130.1474541238492@mail.yahoo.com>
In-Reply-To: <CAKKJt-dmT5Guz_HLmbv5dphXsoctSBs+x6FP5H8kN2cncfZf2Q@mail.gmail.com>
References: <CADnDZ88y+GFa1qCctrS+KBgZ31KxWrKEq6Bpqd95zEkXy3tZXw@mail.gmail.com> <be89fc12-9ffa-1d69-c3ce-66141cf4ec80@bogus.com> <CAC4RtVBvphc02M4cVzmsLZKDaQn7cBJCk9K4uxS0yv3T2Yzd1w@mail.gmail.com> <CAKKJt-dmT5Guz_HLmbv5dphXsoctSBs+x6FP5H8kN2cncfZf2Q@mail.gmail.com>
Subject: Re: Working with IEEE 802
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_Part_5450129_974403647.1474541238491"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/IlV3-lhRPGCDtj519i2CZBI-OEg>
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
Reply-To: Kalilou Dama <kaliloudama@yahoo.fr>
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: Thu, 22 Sep 2016 10:47:24 -0000

Same thought. You are welcome
 kalilou DAMA
Consultant
Lawyer & Business Advisor


phone +223 66 74 88 07
03 BP 237 Bamako - MALI 

    Le Mercredi 21 septembre 2016 20h40, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> a écrit :
 

 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