Re: [spring] WGLC - draft-ietf-spring-srv6-network-programming Mon, 02 March 2020 13:40 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 03D8B3A0BF8 for <>; Mon, 2 Mar 2020 05:40:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Status: No, score=-2.098 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_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 2bQF6Alm-4sg for <>; Mon, 2 Mar 2020 05:40:06 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E26AB3A0BF6 for <>; Mon, 2 Mar 2020 05:40:05 -0800 (PST)
Received: from (unknown [xx.xx.xx.66]) by (ESMTP service) with ESMTP id 48WLqS3cKpz5w3s; Mon, 2 Mar 2020 14:40:04 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=ORANGE001; t=1583156404; bh=08k+QJVcDpBj1ucz3kJGPLVcv8SE77MnJe87W681DWE=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=q/6kSVGtwyvUnjjb+ayFYSXmT9EMh30JCZz3JOwE6qzU69OonJ0pVBBhT7VJgT0U2 Tlnh2EIWMrC2y2YeWZbeo4FYF5tDy5yh9ozS52vJ22SlTmcKmVJsFo0GNZLeG/0VmT /51/ie9e3g0XVVA0/vBsYTZj5ipai6gMoSMmXhDiyuZs4mKpR8X4hLyfJuLU8NdbY6 mwFojYIRMVNlYOzAj11ubRnpxIWcaBRpXDncHyCSfgxxFj5+qwHvnkx6Q1D99/gRLl vU4n7gkNAq8xto39qr8x82ex4H6Eymo09WKM0dfknozWe5bjAfxdv+JGllwvXll5sv D5HeK7WBBbdEQ==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.86]) by (ESMTP service) with ESMTP id 48WLqS2Z8Fz8sZ2; Mon, 2 Mar 2020 14:40:04 +0100 (CET)
Received: from OPEXCAUBM43.corporate.adroot.infra.ftgroup ([fe80::b846:2467:1591:5d9d]) by OPEXCAUBMA4.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0487.000; Mon, 2 Mar 2020 14:40:04 +0100
From: <>
To: S Moonesamy <>, Martin Vigoureux <>, Suresh Krishnan <>
CC: "" <>
Thread-Topic: [spring] WGLC - draft-ietf-spring-srv6-network-programming
Thread-Index: AQHV7nBpq7uRDIrDzE6zxTCNbz5nDqgw+VaAgAAemQCABDlmoA==
Date: Mon, 2 Mar 2020 13:40:03 +0000
Message-ID: =?utf-8?q?=3C9924=5F1583156404=5F5E5D0CB4=5F9924=5F109=5F28=5F53?= =?utf-8?q?C29892C857584299CBF5D05346208A48DD5043=40OPEXCAUBM43=2Ecorporate?= =?utf-8?q?=2Eadroot=2Einfra=2Eftgroup=3E?=
References: =?utf-8?q?=3C17421=5F1575566127=5F5DE93B2F=5F17421=5F93=5F1=5F53?= =?utf-8?q?C29892C857584299CBF5D05346208A48D1A3DA=40OPEXCAUBM43=2Ecorporate?= =?utf-8?q?=2Eadroot=2Einfra=2Eftgroup=3E_=3C5518=5F1582908787=5F5E594573=5F?= =?utf-8?q?5518=5F436=5F1=5F53C29892C857584299CBF5D05346208A48DD1BCA=40OPEXC?= =?utf-8?q?AUBM43=2Ecorporate=2Eadroot=2Einfra=2Eftgroup=3E?= <> <> <>
In-Reply-To: <>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [spring] WGLC - draft-ietf-spring-srv6-network-programming
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 02 Mar 2020 13:40:08 -0000

Dear Mr  S. Moonesamy,

> -----Original Message-----
> From: spring [] On Behalf Of S Moonesamy
> Sent: Friday, February 28, 2020 11:03 PM
> To: Martin Vigoureux
> Cc:
> Subject: Re: [spring] WGLC - draft-ietf-spring-srv6-network-programming
> 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?

And as stated in Martin's and mine email, that's the reason for which the decision will be called by Martin (AD).
> 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.

To me, the email from Suresh was crystal clear.
That been said, Suresh has now updated the errata status. So what's your point exactly?

[under Suresh's control that I'm explicitly adding in copy]

> Regards,
> S. Moonesamy
> 1.
> 2.
> 3.
> _______________________________________________
> spring mailing list


Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.