IETF Logo Mail Archive

Re: Ombudsteam update

Suresh Krishnan <suresh.krishnan@gmail.com> Mon, 21 January 2019 15:02 UTC

Return-Path: <suresh.krishnan@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 60444130F32; Mon, 21 Jan 2019 07:02:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level:
X-Spam-Status: No, score=-0.999 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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 ec8uGTUFpBb4; Mon, 21 Jan 2019 07:02:05 -0800 (PST)
Received: from mail-yb1-xb2d.google.com (mail-yb1-xb2d.google.com [IPv6:2607:f8b0:4864:20::b2d]) (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 51364130EEF; Mon, 21 Jan 2019 07:02:03 -0800 (PST)
Received: by mail-yb1-xb2d.google.com with SMTP id 2so7271036ybw.4; Mon, 21 Jan 2019 07:02:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=o8ZRKcdFDMCmp56Au9PBMJc+o1zYzn3sRNavEuJKDh8=; b=hOacm0LAzKyBCJPLjZRf/wG8kxYW/NBZY+wuRFy9mYijbrySJpN5HKsVb+dJINDmp9 mKlCz5qE0JUYBOw3Bt3pndXWmBOI+NN/xPKaIv69lfsnZFoHG2a9kOWih1Lg0GZsP3CO bbET4nV5xzuMDpBaxMWMK7JeczLFoITWfCppkhxhMkTaM/m9yBQV2gNuTOnw6iQC9yCg tjBw3sj330pmABgQtbf4/jf7aluPIh/TwdhSB2SU/QRvXgoVk6Oe4yjwHyPkIdZpf+UC qSAzmCVIOROhfyT5fqc1vmXNa9z4fXgwuFIrXdir8qgbieIV2FV0f9rrp9OccbQClltC IlZw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=o8ZRKcdFDMCmp56Au9PBMJc+o1zYzn3sRNavEuJKDh8=; b=LBblbWZDU8GaOYufLlnMreRD6l0obgX5SAR4jEeWo4jabZz9k81Voskh8tqU69+1pl WSJiLLEj8jA0vOgw6f+fXy3A8p1fdihXTX90bA8AtBBf7lz6106/H4W8EAqgzs/gA6Wi pHjMO5+1+TLM6/xiSj/TWyyziQVyfUNTQL66nARTXcKPDpK0bOBRJ0J2lGX1Ma/L+/VE k8+ZMd004ZNVV4GZ37tt4usSWJDoO5+pZ1K/i4svZegYo53USf7WltfOefSqkdEOV0k+ tp/P5LdoR9kT0nsO7oHkfgFxcptPj7716JmXL7bsci+1nNoU2nr0WphXe6rfTpVyEhhz s7GQ==
X-Gm-Message-State: AJcUukemu+u6RtjRJsE4zxrxagd8WZQrtq23dzSOAvgv/yDi3b1+TdZy pSqK8ZflWU2FdRhchG3qD/3n71WT
X-Google-Smtp-Source: ALg8bN55tWu7ztSBMCBwDdm9xGxWU3TvCIcYFDGGyOCo6JgPFRTA1SENBrFOSltHtKI7n9JUYJxCXA==
X-Received: by 2002:a25:fc17:: with SMTP id v23mr17304887ybd.48.1548082922099; Mon, 21 Jan 2019 07:02:02 -0800 (PST)
Received: from [10.0.0.20] (45-19-110-76.lightspeed.tukrga.sbcglobal.net. [45.19.110.76]) by smtp.gmail.com with ESMTPSA id i7sm5183544ywd.7.2019.01.21.07.02.00 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 21 Jan 2019 07:02:01 -0800 (PST)
From: Suresh Krishnan <suresh.krishnan@gmail.com>
Message-Id: <AAE6C5D5-4272-4FE9-8F93-AE4B519C5C60@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_BFC51A93-564F-4FA2-B098-B43FFFCE6C8F"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Subject: Re: Ombudsteam update
Date: Mon, 21 Jan 2019 10:02:00 -0500
In-Reply-To: <CADnDZ8875inB-tdadtVajYBJiZC-Tu++j+GYPUz=pEiNvGqcTw@mail.gmail.com>
Cc: Allison Mankin <allison.mankin@gmail.com>, ietf <ietf@ietf.org>, Ombudsteam <ombudsteam@ietf.org>, IESG <iesg@ietf.org>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
References: <82BCE48D-9B20-4819-82A0-BD8378AFBED5@ietf.org> <CADnDZ8_6SbSe3QP2FkWjW_fkDehiVUt9HPPAFyF1itz8ZfyBBA@mail.gmail.com> <CAP8yD=vAk1+pkPY9LQktV6mHKYC=uWRreV513W2rPj6U=jgtzg@mail.gmail.com> <CADnDZ88m51dADnQLkOMcLVtJY=3kOwGzCRFPu9YZJ9THednAHA@mail.gmail.com> <CAP8yD=uhp-GKoTg9BmO7vYAErDA2jKWF8uFjUV=_gd1Jd28wog@mail.gmail.com> <CADnDZ8875inB-tdadtVajYBJiZC-Tu++j+GYPUz=pEiNvGqcTw@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BDihB4pGu2OxxYFyybNdfLH9HsI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 21 Jan 2019 15:02:08 -0000

Hi AB,

> On Jan 18, 2019, at 1:18 AM, Abdussalam Baryun <abdussalambaryun@gmail.com> wrote:
> 
> 
> 
> On Wed, Jan 16, 2019 at 8:09 PM Allison Mankin <allison.mankin@gmail.com <mailto:allison.mankin@gmail.com>> wrote:
> Hi, Abdussalam,
> 
> You are right, I misread the date on the mail when I was writing yesterday (I have a kind of calendar dyslexia).   I too have that mail, but what I wrote yesterday is still the case.  
> 
> Please let ombudteam know (adding back ombudsteam to this email) if you have a continuing issue, as my mail said yesterday.
> 
> Yes I have a continuing issues, and the ombudsteam will be informed in the coming days, however, the biggest problem/issue was the IPWAVE AD and chair MUST follow up to make discussions easy and productive.

For people who do not know the context, this was AB’s mail

https://mailarchive.ietf.org/arch/msg/its/8aH6ikp6mIJ5BMIJApx6PqqyzPg

This was Tony Li’s mail that AB was responding to

https://mailarchive.ietf.org/arch/msg/its/iGhHmoJy2Ien_iyoOgd6I5gXzWM

> My formal public message was ignored by IETF AD office

????. I did respond on list to your message with my view

https://mailarchive.ietf.org/arch/msg/its/Lb84WgER7edzsJhp5cyjhxoYaxk

> , then formal private message ignored by ombudsteam, so I was powerless. 

I am not privy to the workings of the ombudsteam. I will let them respond to this.

> It is strange that it is easy of IETF-members/selected-members to ignore/drop formal emails/messages/letters/requests in IETF/IESG.

Once you escalated the message to the ombudsteam, it is for the ombudsteam to judge. If there were specific actions for the ipwave chairs or the IESG I am assuming we would have heard from the ombudsteam.

Thanks
Suresh

v2.23.0 | Report a Bug | By Email