On Wed, Jan 16, 2019 at 8:09 PM Allison Mankin <allison.mankin@xxxxxxxxx> 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. My formal public message was ignored by IETF AD office, then formal private message ignored by ombudsteam, so I was powerless. It is strange that it is easy of IETF-members/selected-members to ignore/drop formal emails/messages/letters/requests in IETF/IESG.
IETF should update such procedure that gives that opportunity/error, so that IETF becomes fair and treats all world communities equal.
I will send you another message that is between you and me and my colleagues in ombudsteam, because of the confidentiality rules in our BCP (RFC 7776).
ok, this will be my last public message related to the subject, the purpose was to help make procedures/RFCs fair/updated/working-right. However, making things private/confidential without management can help issues to grow with no fair solutions.
AB
IETF Participant from Africa,
On Wed, 16 Jan 2019 at 12:22, Abdussalam Baryun <abdussalambaryun@xxxxxxxxx> wrote:Hi Allison,Yes I have the email which was sent on Monday 9th October 2017 at 6:06 AM to ombudsteam@xxxxxxxx, and allison.mankin@xxxxxxxxx. I only sent once to those addresses and my email was not sent in 2018.
Abdussalam,IETF Participant from Africa,On Tue, Jan 15, 2019 at 8:37 PM Allison Mankin <allison.mankin@xxxxxxxxx> wrote:Hi, Absussalam,my name is Abdussalam, meaning serving God the peace,I can't find the 2017 issue, but I did find the one in 2018, and not my reply. I recall sending you a reply. I'm going to send you another one now, with apologies since you did not receive it. Also you should inform me if you find a request from 2017.AllisonOn Sat, 12 Jan 2019 at 04:04, Abdussalam Baryun <abdussalambaryun@xxxxxxxxx> wrote:Hi Alissa,I hope this ombudsteam procedure is working well with no issues. How does the procedure monitor the time/delay of respond/action? I remember in 2017, I send an email to its email and cc to one person's name mentioned in your email. I did not get any reply (that email sent was ignored by both emails, and is still waiting for reply with very long delay), I noticed then that this ombudsteam is not working well as needed. Maybe there is a problem in implementation of rfc7776 or the procedure needs to be update for better practice. IETF is about implementing procedures for best practices and for the community needs.Best RegardsABOn Fri, Jan 11, 2019 at 7:36 PM IETF Chair <chair@xxxxxxxx> wrote:The IETF ombudsteam <https://www.ietf.org/contact/ombudsteam/> is a designated group of people who have been selected to handle reports of potential harassment in the IETF. The ombudspeople serve in support of maintaining an IETF environment in which people of many different backgrounds are treated with dignity, decency, and respect, per our Anti-Harassment Policy <https://www.ietf.org/blog/ietf-anti-harassment-policy/>.
Earlier this week, Linda Klieforth stepped down from the ombudsteam. I would like to thank Linda for her foundational contributions to the team and for all she has done to help create a welcoming environment in the IETF.
Melinda Shore has graciously agreed to join the ombudsteam. Many thanks to Melinda for her willingness to take on this role in addition to her existing duties. Allison Mankin and Pete Resnick continue to serve on the team.
As always, the ombudsteam can be reached at ombudsteam@xxxxxxxx or at their individual addresses listed on the web page above. The IETF Anti-Harassment Procedures (RFC 7776) that govern the ombudsteam's operations can be found at <https://tools.ietf.org/html/rfc7776>.
Regards,
Alissa Cooper
IETF Chair
