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

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C9F7B3A041A for <>; Mon, 2 Mar 2020 06:16:23 -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 lG_VGLZ_iDgK for <>; Mon, 2 Mar 2020 06:16:21 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 6E4863A0410 for <>; Mon, 2 Mar 2020 06:16:21 -0800 (PST)
Received: from (unknown [xx.xx.xx.11]) by (ESMTP service) with ESMTP id 48WMdH51tCz8smT; Mon, 2 Mar 2020 15:16:19 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=ORANGE001; t=1583158579; bh=FKiKw/NWMzgmPI237ZS024GB3KWq/YaL471gYdPgK+Q=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=Ii2p1FY/IFKrZR9FakkU8bjKqXWG7poqUxfTFcMKj3kqwq4LetGCjhCu9/i1vWCgy O3JvRQntZyEgEbvmt8IN//yfkFh2SOzEXVQIGiF9eTbYZzzZVHVsoB+UsdBNz+34Sh yaErlGhaNIPWd+7WsxDHc/HzrrnsJHgjWq4nL7KphGxwLnYEOUCmSfIBH0BqE/HR8c NxK80hFsRirEBfq16lTuEBVraEZgmRwQByJSdpGn5v+uGMbzCzYr5ZeU6M6hA20qjz W3NZmwPsnT9gDTVFFSU7JTmVCR0RskdV8SjndWPHebEsyf00XUoUyPQelfLWMnO1oZ QxWUxpOZtCfqg==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.51]) by (ESMTP service) with ESMTP id 48WMdH3g6jzCqjy; Mon, 2 Mar 2020 15:16:19 +0100 (CET)
Received: from OPEXCAUBM43.corporate.adroot.infra.ftgroup ([fe80::b846:2467:1591:5d9d]) by OPEXCAUBM22.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0487.000; Mon, 2 Mar 2020 15:16:19 +0100
From: <>
To: S Moonesamy <>, Martin Vigoureux <>, Suresh Krishnan <>
CC: "" <>
Thread-Topic: [spring] WGLC - draft-ietf-spring-srv6-network-programming
Thread-Index: AQHV7nBpq7uRDIrDzE6zxTCNbz5nDqgw+VaAgAAemQCABEFrAA==
Date: Mon, 2 Mar 2020 14:16:18 +0000
Message-ID: =?utf-8?q?=3C23625=5F1583158579=5F5E5D1533=5F23625=5F379=5F8=5F5?= =?utf-8?q?3C29892C857584299CBF5D05346208A48DD5266=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 14:16:24 -0000

Dear S. Moonesamy,

Please see and read inline  
> 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?

As stated twice on the list, by both by Martin and myself, the decision will be taken by Martin, not me:

> From: Martin Vigoureux
> Bruno being involved in the draft currently in WG LC, I will handle closing it.

> From:
> I've discussed this with our AD (Martin) and he agreed to make the formal decision to send the document to the next level. Thank you Martin.

> 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.

The email from Suresh that I had cited in support of my statement, seemed and still seems clear to me.

What was not clear to you in Suresh's email?

>  I will process this and move it to the "Hold for Document Update" state

> > Just to be clear, I believe that your stated decision of processing this errata as "Hold for document update" is not only incorrect, but also doesn't represent the consensus this working group got during the rfc2460bis effort -- now RFC8200.
>  > As such, I will formally Appeal your decision.
> Please do go ahead. I stand by my assessment that this is a misuse of the Errata process and it is not a simple clarification as you claim."

Please take another look now. Suresh has updated the status of the errata. I guess that your point is now moot.

[+ Suresh]


> 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.