Difference between revisions of "NSH SFC/Meeting"

From fd.io
Jump to: navigation, search
(Information From Past Meetings)
(Information From Past Meetings)
Line 40: Line 40:
 
4) NSH-aware VNFs in current proposal could be treated as NSH Proxy collocates with SF, there are two issues problems
 
4) NSH-aware VNFs in current proposal could be treated as NSH Proxy collocates with SF, there are two issues problems
 
raised by Joel need to address in the near future:
 
raised by Joel need to address in the near future:
     a. We need SFs to be natively NSH-aware, meaning they can manipulate metadata inside the NSH. Current implementation
+
     a. We need SFs to be natively NSH-aware, meaning they can manipulate metadata inside the NSH.  
       looks like NSH Proxy co-locate with SFs but SFs can only see the original frames.
+
       Current implementation looks like NSH Proxy co-locate with SFs but SFs can only see the original frames.
     b. How to handle NAT like or TCP Proxy like SFs after they change the headers of the inner headers which are typically
+
     b. How to handle NAT like or TCP Proxy like SFs after they change the headers of the inner  
      used as key to determine which next graph node is? The initial thought is to add some information to per-packet metadata
+
      headers which are typically used as key to determine which next graph node is?  
      before packets go into the SF, and the metadata can be used to determine if it needs to be re-encapsulated by NSH_SFC graph node.
+
      The initial thought is to add some information to per-packet metadata before packets go into  
      Hongjun is going to investigate it.
+
      the SF, and the metadata can be used to determine if it needs to be re-encapsulated by NSH_SFC  
 
+
      graph node.  
  
 +
AR: Hongjun to investigate how to support NAT and TCP Proxy sort of SFs
 
</div>
 
</div>
 
</div>
 
</div>

Revision as of 01:23, 6 December 2016

Meeting Details

Weekly on Monday, 60min, from 16:00 - 17:00 PDT.

Join Skype Meeting

Join by phone +1(916)356-2663 (or your local bridge access #) Choose bridge 5. (Global) English (United States)

Conference ID: 133570463

Find a local number

Agenda

The next NSH_SFC meeting is scheduled for Monday 4th Dec

  • Blocking issues (before VPP/HC code freeze) for NSH Proxy and Classifier in 1701 release
  • Proposal review: NSH-aware VNFs

Information From Past Meetings

 [Expand

2016-12-05


 [Expand

2016-11-28

 [Expand

2016-08-29

 [Expand

2016-06-20

 [Expand

2016-06-06