Re: [spring] WGLC - draft-ietf-spring-srv6-network-programming

S Moonesamy <sm+ietf@elandsys.com> Fri, 28 February 2020 22:04 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15A233A1ED0 for <spring@ietfa.amsl.com>; Fri, 28 Feb 2020 14:04:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=elandsys.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 2PtyAGG7dbZ9 for <spring@ietfa.amsl.com>; Fri, 28 Feb 2020 14:04:09 -0800 (PST)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id 538CF3A1ECE for <spring@ietf.org>; Fri, 28 Feb 2020 14:04:05 -0800 (PST)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.116.105.122]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 01SM3ogM028168 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 28 Feb 2020 14:04:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1582927442; x=1583013842; i=@elandsys.com; bh=WabM5QV00GmkORJUewkEDwQp+DQuvyxx26I2yrKVPkY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=oEh6y/Bs+IqnXyB1R2sCpSktssCzk/ErT2KvBbPc63nWh5XztVGkC7SGees/WrQ1T 1h1GoPLDY5nYNH0ukYgoLLolqRoO3s5ZAtU2ekznTT8cAlM2ihW4p3+fWjzJJ0/ZHM VftcR1rah6EGW2DwIcs9cb4VYWCP9eQKypFupCYI=
Message-Id: <6.2.5.6.2.20200228132634.1060a610@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 28 Feb 2020 14:02:38 -0800
To: Martin Vigoureux <martin.vigoureux@nokia.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Cc: spring@ietf.org
In-Reply-To: <9b677b7c-fe52-dbae-7f83-2b5be5194325@gont.com.ar>
References: <17421_1575566127_5DE93B2F_17421_93_1_53C29892C857584299CBF5D05346208A48D1A3DA@OPEXCAUBM43.corporate.adroot.infra.ftgroup> <5518_1582908787_5E594573_5518_436_1_53C29892C857584299CBF5D05346208A48DD1BCA@OPEXCAUBM43.corporate.adroot.infra.ftgroup> <C8417F71-D61E-42AC-831E-B85269D5D4A5@steffann.nl> <9b677b7c-fe52-dbae-7f83-2b5be5194325@gont.com.ar>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/VK75j1TlsEA1zFcQ_IjC0_g86Og>
Subject: Re: [spring] WGLC - draft-ietf-spring-srv6-network-programming
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Feb 2020 22:04:13 -0000

Dear Mr Vigoureux,

I am contacting you as you are listed as the Responsible Area 
Director for the SPRING Working Group [1].  I would like to thank the 
Working Group for providing some information [2] about the status of 
the Working Group Last Call.

I was a bit surprised to see that one of the Working Group Chairs is 
listed as a contributor in 
draft-ietf-spring-srv6-network-programming-10.  It is quite unusual 
to have the contributor of a Working Group document handle the 
Working Group process for the document.  Would there be a potential 
conflict of interest?

The summary provides by the Working Group Chair states that the 
Responsible Area Director "has not accepted the related errata".  I 
took a quick look at erratum eid5933; it is listed as "Reported".  As 
the erratum has not been classified as per the relevant IESG 
Statement, describing it as "not accepted" is inaccurate.

Regards,
S. Moonesamy

1. https://datatracker.ietf.org/wg/spring/about/
2. https://mailarchive.ietf.org/arch/msg/spring/or8086G4iYfee5_Icw4PnhkPLBo/
3. https://www.rfc-editor.org/errata/eid5933