Re: [Coin] Final minutes

<> Fri, 09 August 2019 15:13 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id BC0BA12021D for <>; Fri, 9 Aug 2019 08:13:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id eXofuwKLZwkt for <>; Fri, 9 Aug 2019 08:13:49 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 2B6731201F3 for <>; Fri, 9 Aug 2019 08:13:49 -0700 (PDT)
Received: from ([]:65004 helo=hemantPC) by with esmtpsa (TLSv1.2:AES128-SHA256:128) (Exim 4.92) (envelope-from <>) id 1hw6aI-00DHoS-V3; Fri, 09 Aug 2019 10:13:45 -0500
Reply-To: <>
From: <>
To: "'Marie-Jose Montpetit'" <>, <>
References: <> <013001d54ebf$d7f07dc0$87d17940$> <>
In-Reply-To: <>
Date: Fri, 9 Aug 2019 11:14:15 -0400
Organization: MNK Consulting
Message-ID: <018301d54ec5$1c42a070$54c7e150$>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0184_01D54EA3.95351F20"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQKHVC85qkFXNpP9gIpZvB66rYdpogItd/vtAtE2l1alZupHgA==
Content-Language: en-us
X-OutGoing-Spam-Status: No, score=-0.2
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname -
X-AntiAbuse: Original Domain -
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain -
X-Get-Message-Sender-Via: authenticated_id:
X-From-Rewrite: unmodified, already matched
Archived-At: <>
Subject: Re: [Coin] Final minutes
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "COIN: Computing in the Network" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 09 Aug 2019 15:13:52 -0000

Merging P4 programs has several issues to deal with.  We have documented the issues at our P4-Ansible link below.     




From: Marie-Jose Montpetit <>; 
Sent: Friday, August 09, 2019 10:45 AM
Subject: RE: [Coin] Final minutes


Thanks! The audio is on the datatracker for coinrg:


Marie-José Montpetit, Ph.D.

Research Affiliate, MIT Media Laboratory <> <> 


On August 9, 2019 at 10:36:06 AM, <>  ( <> ) wrote:

I didn’t attend the IETF nor did I listen to any meeting minutes, if any audio exists.  Going by the pdf Marie-Jose sent out, item 6 is interesting to me.  


Dave Oran asked merging two P4 programs.  A uses case is being discussed in the P4 community.  An operator is using a P4 switch from Cisco/Arista.   However, the operator has some new service in mind.  The operator writes his/her P4 program.  How does the operator (customer) merge the customer with vendor P4 program?  Cisco was first with an incremental P4 merging tool called daPIPE.  My company also developed a tool called P4-Ansible (  Cisco only supports p4-14 programs.  Our tool supports p4-16 programs and much more.  Such merging of P4 programs changes firmware of the switch asic.  Thus, the switch data plane has to reset to run the new merged P4 programs.  The switch cpu operates control-plane and continue to run.  The whole switch doesn’t need a reset. 


Regarding, changing P4 program without resetting switch data-plane, one can change tables and table actions of the MAU (Match-Action Unit) in data plane.  P4runtime ( is used for such changes. 




From: Coin < <> > On Behalf Of Marie-Jose Montpetit
Sent: Friday, August 09, 2019 8:03 AM
To: <> 
Subject: [Coin] Final minutes


The final meeting minutes are attached and uploaded in data tracker.


We will also request an interim meeting for Tuesday October 8 starting a 9am eastern time (US). Details to come.







Marie-José Montpetit, Ph.D.

Research Affiliate, MIT Media Laboratory <> <>