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

From: Jamal Hadi Salim <[email-masked]>
Date: Mon, 13 Jan 2014 08:35:18 -0500

As per discussion in Vancouver - the chairs believe there is
sufficient interest in
this  document for it to become a WG item. I did promise to do another review
but priorities havent bubbled up yet.
My gut feeling is to say please go ahead and resubmit as a WG item unless
there is objection to it.

cheers,
jamal

On Sat, Nov 16, 2013 at 6:28 PM, Haleplidis Evangelos <[email-masked]> wrote:
> Greetings to the list,
>
> We have just updated the parallelization draft after the decisions made in the Vancouver meeting.
>
> As we said in the meeting we believe this document is very stable and we would like to ask this document to be accepted as a wg item.
>
> Regards,
> Evangelos Haleplidis.
>
>> -----Original Message-----
>> From: [email-masked] [mailto:[email-masked]]
>> Sent: Sunday, November 17, 2013 1:25 AM
>> To: Joel Halpern; Evangelos Haleplidis
>> Subject: New Version Notification for draft-haleplidis-forces-packet-
>> parallelization-04.txt
>>
>>
>> A new version of I-D, draft-haleplidis-forces-packet-parallelization-
>> 04.txt
>> has been successfully submitted by Evangelos Haleplidis and posted to
>> the IETF repository.
>>
>> Filename:      draft-haleplidis-forces-packet-parallelization
>> Revision:      04
>> Title:                 ForCES Packet Parallelization
>> Creation date:         2013-11-16
>> Group:                 Individual Submission
>> Number of pages: 22
>> URL:             http://www.ietf.org/internet-drafts/draft-haleplidis-forces-packet-parallelization-04.txt
>> Status:          http://datatracker.ietf.org/doc/draft-haleplidis-forces-packet-parallelization
>> Htmlized:        http://tools.ietf.org/html/draft-haleplidis-forces-packet-parallelization-04
>> Diff:            http://www.ietf.org/rfcdiff?url2=draft-haleplidis-forces-packet-parallelization-04
>>
>> 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.
>>
>>
>>
>>
>> Please note that it may take a couple of minutes from the time of
>> submission until the htmlized version and diff are available at
>> tools.ietf.org.
>>
>> The IETF Secretariat
>
> _______________________________________________
> forces mailing list
> [email-masked]
> https://www.ietf.org/mailman/listinfo/forces