Subject: [forces] FW: New Version Notification for draft-haleplidis-forces-packet-parallelization-01.txt

From: "Haleplidis Evangelos" <[email-masked]>
Date: Fri, 19 Oct 2012 18:49:58 +0300

Greetings to the list,

We have submitted a new version for the parallelization draft.

A major change is that we removed the valid metadatum in order for the merging metadata to be opaque to LFBs inside a parallel path. This will allow backward compatibility with current defined LFBs. In order for the merger to know that an error has occurred in a parallel path, it will receive the packet/chunk from the InvalidIn port. This port will be connected to exception output ports from LFBs in the path. Along with the invalid packet/chunk it may be followed by a ExceptionID or ValidateErrorID (defined in lfb-lib).

Also we added some more counters for invalid packets/chunks. We now have also counters per error IDs and a counter that keeps track of in how many merges were all packet/chunks invalid.

Also we made the parallel type a component in the splitter LFB, per Jamal's comment. The parallel type will be sent forward to the merger LFB as metadata.

Regards,
Evangelos Haleplidis.

> -----Original Message-----
> From: [email-masked] [mailto:[email-masked]]
> Sent: Friday, October 19, 2012 6:43 PM
> To: [email-masked]
> Cc: [email-masked]
> Subject: New Version Notification for draft-haleplidis-forces-packet-
> parallelization-01.txt
> 
> 
> A new version of I-D, draft-haleplidis-forces-packet-parallelization-
> 01.txt
> has been successfully submitted by Evangelos Haleplidis and posted to
> the IETF repository.
> 
> Filename:	 draft-haleplidis-forces-packet-parallelization
> Revision:	 01
> Title:		 ForCES Packet Parallelization
> Creation date:	 2012-10-19
> WG ID:		 Individual Submission
> Number of pages: 28
> URL:             http://www.ietf.org/internet-drafts/draft-haleplidis-forces-packet-parallelization-01.txt
> Status:          http://datatracker.ietf.org/doc/draft-haleplidis-forces-packet-parallelization
> Htmlized:        http://tools.ietf.org/html/draft-haleplidis-forces-packet-parallelization-01
> Diff:            http://www.ietf.org/rfcdiff?url2=draft-haleplidis-forces-packet-parallelization-01
> 
> Abstract:
>    Forwarding and Control Element Separation (ForCES) defines an
>    architectural framework and associated protocols to standardize
>    information exchange between the control plane and the forwarding
>    plane in a ForCES Network Element (ForCES NE).  RFC5812 has defined
>    the ForCES Model provides a formal way to represent the
> capabilities,
>    state, and configuration of forwarding elements within the context
> of
>    the ForCES protocol, so that control elements (CEs) can control the
>    FEs accordingly.  More specifically, the model describes the logical
>    functions that are present in an FE, what capabilities these
>    functions support, and how these functions are or can be
>    interconnected.
> 
>    Many network devices support parallel packet processing.  This
>    document describes how ForCES can model a network device's
>    parallelization datapath.
> 
> 
> 
> 
> The IETF Secretariat