From nobody Fri Sep 5 09:27:08 2014 Return-Path: X-Original-To: forces@ietfa.amsl.com Delivered-To: forces@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D9401A0AEB; Fri, 5 Sep 2014 09:27:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VVdex5W3LGUc; Fri, 5 Sep 2014 09:27:04 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 021AD1A0AE2; Fri, 5 Sep 2014 09:27:04 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 5.6.2.p6 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140905162704.3532.46550.idtracker@ietfa.amsl.com> Date: Fri, 05 Sep 2014 09:27:04 -0700 Archived-At: http://mailarchive.ietf.org/arch/msg/forces/lEDKTavUIx3Fn8xsO1xBxLDcw48 Cc: forces@ietf.org Subject: [forces] I-D Action: draft-ietf-forces-packet-parallelization-02.txt X-BeenThere: forces@ietf.org X-Mailman-Version: 2.1.15 List-Id: ForCES WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Sep 2014 16:27:05 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Forwarding and Control Element Separation Working Group of the IETF. Title : ForCES Packet Parallelization Authors : Evangelos Haleplidis Joel Halpern Filename : draft-ietf-forces-packet-parallelization-02.txt Pages : 26 Date : 2014-09-05 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 (RFC 5810), 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 datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-forces-packet-parallelization/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-forces-packet-parallelization-02 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-forces-packet-parallelization-02 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. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Fri Sep 5 09:30:04 2014 Return-Path: X-Original-To: forces@ietfa.amsl.com Delivered-To: forces@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D3DC1A0745 for ; Fri, 5 Sep 2014 09:30:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0HIDa0cWuD4w for ; Fri, 5 Sep 2014 09:30:01 -0700 (PDT) Received: from mail-we0-x22f.google.com (mail-we0-x22f.google.com [IPv6:2a00:1450:400c:c03::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AAA701A096C for ; Fri, 5 Sep 2014 09:30:00 -0700 (PDT) Received: by mail-we0-f175.google.com with SMTP id k48so12024914wev.34 for ; Fri, 05 Sep 2014 09:29:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:thread-index :content-language; bh=kZFxpfRWuhkwAWDOASj4zG4gqE64TpDrcuua60GY06g=; b=vy1TzbjPwJ1sBJ6GV45G9QCIEorC5++mhXVZxwMMqzqPg0RkHJyALdL5Xut4BV+ki2 P+XIY7sENJBHY+oHrAlq+N8jhT15i4KpH7P7l9UE/9BPq/zKXKlJuePMTAH+EBvjmurA y8pRJF77g4VZhhFhid3Ukr8FbJtEApPUN6JkWvCk0GGo5xuwS8I+2o/VRIaamSxqCec4 lxoDz+0aTl8qF8dfbhvWdJT3HQ9b2+Bz9J+g+z4heWBANzHcmEoKBn8bdR+3yyBIphd5 1pMwkocpis6h3aJIcLCMRK6YiNqMw/RHex0D4J8rKQjmHuWvS1IJjq3ARKR3+otiCvhz ksVg== X-Received: by 10.194.221.74 with SMTP id qc10mr15896756wjc.39.1409934599252; Fri, 05 Sep 2014 09:29:59 -0700 (PDT) Received: from EhalepXPS (ppp141237188192.access.hol.gr. [141.237.188.192]) by mx.google.com with ESMTPSA id ka3sm1943195wjc.3.2014.09.05.09.29.57 for (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 05 Sep 2014 09:29:58 -0700 (PDT) From: "Haleplidis Evangelos" To: , References: <055001cfc0b4$3f3b2240$bdb166c0$@olddog.co.uk> In-Reply-To: <055001cfc0b4$3f3b2240$bdb166c0$@olddog.co.uk> Date: Fri, 5 Sep 2014 19:29:58 +0300 Message-ID: <00db01cfc926$a432da10$ec988e30$@com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ac/AtDtozAT+vPO+T8OhbRWTyCRa9wIcin+Q Content-Language: el Archived-At: http://mailarchive.ietf.org/arch/msg/forces/dJmkhuy8hnJyAyomMzgDV1z8FX4 Cc: forces@ietf.org Subject: Re: [forces] AD review of draft-ietf-forces-packet-parallelization X-BeenThere: forces@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ForCES WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Sep 2014 16:30:03 -0000 Greetings Adrian, We have just uploaded the new version of packet parallelization that tries to address all of your issues. Thanks again for the review. Regards, Evangelos. > -----Original Message----- > From: forces [mailto:forces-bounces@ietf.org] On Behalf Of Adrian > Farrel > Sent: Tuesday, August 26, 2014 1:31 AM > To: draft-ietf-forces-packet-parallelization.all@tools.ietf.org > Cc: forces@ietf.org > Subject: [forces] AD review of draft-ietf-forces-packet-parallelization > > Hi authors, > > I have done my usual AD review on receiving a publication request for > your draft. > > I have a question, a request, and a suggestion. > > I'll put the document into "Revised I-D" state until we have resolved > these issues. > > Thanks for the work, > Adrian > > --- > > Is this really standards track and not experimental? The reason I ask > is because it sounds (to me) that packet parallelization is quite an > advanced feature that may have some "interesting" behavioral > characteristics. If you tell me that, "this is stable, we know what we > are doing, the implementations that exist are really being deployed" > then I'll be happy. If you say "we have an implementation and are > seeing how it behaves" then perhaps you should consider whether this is > an experiment. > > This is a topic for discussion. You don't have to make a change until > we have covered the ground and understand what we are dealing with. > > --- > > The IANA Considerations section needs some work. Please: > - Name the registries where you are requesting code points. > - Please request allocations (i.e. don't write descriptive text) > - the values you are asking for appear to come from the Standards > Action space: why mention FCFS? > - Do you *need* the values you are asking for (18-20 and x10), are you > suggesting them, or do you not actually care? You need to make this > clear in your text. > > --- > > Some comments from the document shepherd are recorded in the write-up > and should get some attention from the authors. > > Additionally, there is some English that could benefit from a quick re- > read and some polish. > > _______________________________________________ > forces mailing list > forces@ietf.org > https://www.ietf.org/mailman/listinfo/forces From nobody Tue Sep 9 09:45:49 2014 Return-Path: X-Original-To: forces@ietfa.amsl.com Delivered-To: forces@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B4EF1A7008; Tue, 9 Sep 2014 09:45:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JqljhRjrcMPO; Tue, 9 Sep 2014 09:45:44 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 32D671A6FF0; Tue, 9 Sep 2014 09:45:44 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 5.6.2.p6 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140909164544.5203.62790.idtracker@ietfa.amsl.com> Date: Tue, 09 Sep 2014 09:45:44 -0700 Archived-At: http://mailarchive.ietf.org/arch/msg/forces/6Nv9L09gMfZkw65V4kEgAeH4Cak Cc: forces@ietf.org Subject: [forces] I-D Action: draft-ietf-forces-protoextension-06.txt X-BeenThere: forces@ietf.org X-Mailman-Version: 2.1.15 List-Id: ForCES WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Sep 2014 16:45:45 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Forwarding and Control Element Separation Working Group of the IETF. Title : ForCES Protocol Extensions Author : Jamal Hadi Salim Filename : draft-ietf-forces-protoextension-06.txt Pages : 24 Date : 2014-09-09 Abstract: Experience in implementing and deploying ForCES architecture has demonstrated need for a few small extensions both to ease programmability and to improve wire efficiency of some transactions. The ForCES protocol is extended with a table range operation and a new extension for error handling. This documents updates both RFC 5810 and RFC 7121 semantics to achieve that end goal. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-forces-protoextension/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-forces-protoextension-06 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-forces-protoextension-06 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. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Thu Sep 11 14:23:55 2014 Return-Path: X-Original-To: forces@ietfa.amsl.com Delivered-To: forces@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F55A1A02D0; Thu, 11 Sep 2014 14:23:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0tiopevuaYXc; Thu, 11 Sep 2014 14:23:50 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id ACC4B1A02D6; Thu, 11 Sep 2014 14:23:41 -0700 (PDT) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: IETF-Announce X-Test-IDTracker: no X-IETF-IDTracker: 5.6.2.p6 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140911212341.2309.11210.idtracker@ietfa.amsl.com> Date: Thu, 11 Sep 2014 14:23:41 -0700 Archived-At: http://mailarchive.ietf.org/arch/msg/forces/YHMS8NNaDb9b9ELwJdoTuQutgcA Cc: forces mailing list , forces chair , RFC Editor Subject: [forces] Protocol Action: 'ForCES Protocol Extensions' to Proposed Standard (draft-ietf-forces-protoextension-06.txt) X-BeenThere: forces@ietf.org X-Mailman-Version: 2.1.15 List-Id: ForCES WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Sep 2014 21:23:53 -0000 The IESG has approved the following document: - 'ForCES Protocol Extensions' (draft-ietf-forces-protoextension-06.txt) as Proposed Standard This document is the product of the Forwarding and Control Element Separation Working Group. The IESG contact persons are Adrian Farrel and Alia Atlas. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-forces-protoextension/ Technical Summary Experience in implementing and deploying ForCES architecture has demonstrated need for a few small extensions both to ease programmability and to improve wire efficiency of some transactions. This documents updates both RFC 5810 and RFC 7121 semantics to achieve that end goal. Working Group Summary The extensions are straightforward, and there was no difficulty in coming to consensus on all points described. There were suggested extensions for earlier versions of the document that were not included based on discussions in the WG for the sake of simplicity. We believe the working group is solidly behind this document. Document Quality At least one implementation has validated some of the features described in the document. Personnel Evangelos Haleplidis is the document shepherd Adrian Farrel is the Responsible Area Director From nobody Thu Sep 11 14:57:03 2014 Return-Path: X-Original-To: forces@ietfa.amsl.com Delivered-To: forces@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FEC31A02D6; Thu, 11 Sep 2014 14:56:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9EP7mcxwTCMe; Thu, 11 Sep 2014 14:56:58 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 23CE41A028A; Thu, 11 Sep 2014 14:56:58 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 5.6.2.p6 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140911215658.13058.32311.idtracker@ietfa.amsl.com> Date: Thu, 11 Sep 2014 14:56:58 -0700 Archived-At: http://mailarchive.ietf.org/arch/msg/forces/uCrd081P_Wqwf-F_NN4vdP6yznY Cc: forces@ietf.org Subject: [forces] I-D Action: draft-ietf-forces-model-extension-05.txt X-BeenThere: forces@ietf.org X-Mailman-Version: 2.1.15 List-Id: ForCES WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Sep 2014 21:56:59 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Forwarding and Control Element Separation Working Group of the IETF. Title : ForCES Model Extension Author : Evangelos Haleplidis Filename : draft-ietf-forces-model-extension-05.txt Pages : 30 Date : 2014-09-11 Abstract: This memo extends the Forwarding and Control Element Separation (ForCES) model defined in RFC 5812 and updates RFC5812 to allow complex datatypes for metadata, optional default values for datatypes, optional access types for structures. It fixes an issue with Logical Functional Block (LFB) inheritance. It also introduces two new features a new event condition BecomesEqualTo and LFB properties. The changes introduced in this memo do not alter the protocol and retain backward compatibility with older LFB models. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-forces-model-extension/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-forces-model-extension-05 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-forces-model-extension-05 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. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Fri Sep 12 15:36:06 2014 Return-Path: X-Original-To: forces@ietfa.amsl.com Delivered-To: forces@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FD831A0077 for ; Fri, 12 Sep 2014 15:36:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2FBYWkdUFCw1 for ; Fri, 12 Sep 2014 15:36:03 -0700 (PDT) Received: from mail-we0-x232.google.com (mail-we0-x232.google.com [IPv6:2a00:1450:400c:c03::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3181C1A004C for ; Fri, 12 Sep 2014 15:36:03 -0700 (PDT) Received: by mail-we0-f178.google.com with SMTP id q58so1444307wes.9 for ; Fri, 12 Sep 2014 15:36:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:message-id:mime-version:content-type :content-transfer-encoding:thread-index:content-language; bh=nyMrJ9nNxUuTY3Zmy5lP4HZiXInDfLC05OtjXwGZpRE=; b=iuThI1UwPpUis4BQeHkN81UCzQPfaaLZYfB+brJMSGNaWksv09hO304JoXjtSFwcxH nI+EN0NSttp/fUynwP8VybRBAQPKfsjLNWgjlHN+dFBlf4LqNi7wKdbsqd8+S2PoD27x eqpBkvdlVe7bQissusZdUdiH00n87Y4OeoVAp9/wuytw8uqMmuheXbvnIR5MQCehi1NQ clQrYL4m685NuTd8L/hEnT5KWyXd5bwWCfC9WBWL/7EZH7p8vpRsX1q0H/Z44T0WYW3m jlKM6UzVIGp6l0+fvMEhKo1Z1JtZWfoTbUjA7J9DApj+FHIm8sqy22q7RGWRAlCrqXC4 vcdw== X-Received: by 10.180.228.106 with SMTP id sh10mr5884963wic.65.1410561361803; Fri, 12 Sep 2014 15:36:01 -0700 (PDT) Received: from EhalepXPS (ppp079166104131.access.hol.gr. [79.166.104.131]) by mx.google.com with ESMTPSA id n5sm5903095wja.38.2014.09.12.15.36.00 for (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 12 Sep 2014 15:36:01 -0700 (PDT) From: "Haleplidis Evangelos" To: Date: Sat, 13 Sep 2014 01:36:05 +0300 Message-ID: <01fa01cfced9$f2810300$d7830900$@com> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ac/OC28L2HAiY428RfeToqS9SQeL7wAxupBQ Content-Language: el Archived-At: http://mailarchive.ietf.org/arch/msg/forces/Ed1HASHKyI0ccF7k9nCVWgrfVTc Subject: [forces] FW: New Version Notification for draft-ietf-forces-model-extension-05.txt X-BeenThere: forces@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ForCES WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Sep 2014 22:36:05 -0000 Greetings to the list, The model extension draft was updated yesterday. There was a small issue = with the default values for datatypes, but with the help and suggestions = by Joel this was resolved. The problem was that allowing typeRef and atomic values to have default = values directly could create confusion and didn't make sense, as you may = had multiple default value definitions in one place (e.g. if you created = an LFB component this is atomic and both could have default values).=20 So, the solution, suggested by Joel, was to move the default value from = typeRef and atomic to the dataTypeDefinition altogether, similar to the = component definition in LFBs. So in effect the goal of having default values in datatypes is achieved = in a simpler and cleaner way. Now, there is a small overhead penalty. In order to define, e.g. a = struct with 5 components with different default values, a developer = would have to create 5 new datatypes. However the simplicity and gains = are better that the alternative. In addition this scheme supports = hierarchical default values. E.g. Define an data type once (e.g. an IPv4 = address), and reuse it to define different default values as different = datatypes as needed (localhost, broadcast, etc.).=20 Examples are provided in the draft. On a final notice, the following formal restrictions on default values = were defined in order to remove ambiguity: 1. Default Values MUST be ignored if the data type is not an atomic or a base data type. 2. When a datatype X with default value A is referenced from a datatype Y with a default value B, the default value of the datatype that references overrides the referenced default value, e.g. in this case Y's default value will be B. 3. Default Values of LFB components overrides any default value specified from the dataTypeDef definition. 4. Default Values of datatypes reference in capabilities or metadata MUST be ignored. Regards, Evangelos Haleplidis. > -----Original Message----- > From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] > Sent: Friday, September 12, 2014 12:57 AM > To: Evangelos Haleplidis; Evangelos Haleplidis > Subject: New Version Notification for draft-ietf-forces-model- > extension-05.txt >=20 >=20 > A new version of I-D, draft-ietf-forces-model-extension-05.txt > has been successfully submitted by Evangelos Haleplidis and posted to > the IETF repository. >=20 > Name: draft-ietf-forces-model-extension > Revision: 05 > Title: ForCES Model Extension > Document date: 2014-09-11 > Group: forces > Pages: 30 > URL: http://www.ietf.org/internet-drafts/draft-ietf-forces- > model-extension-05.txt > Status: https://datatracker.ietf.org/doc/draft-ietf-forces- > model-extension/ > Htmlized: http://tools.ietf.org/html/draft-ietf-forces-model- > extension-05 > Diff: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-forces- > model-extension-05 >=20 > Abstract: > This memo extends the Forwarding and Control Element Separation > (ForCES) model defined in RFC 5812 and updates RFC5812 to allow > complex datatypes for metadata, optional default values for > datatypes, optional access types for structures. It fixes an issue > with Logical Functional Block (LFB) inheritance. It also = introduces > two new features a new event condition BecomesEqualTo and LFB > properties. The changes introduced in this memo do not alter the > protocol and retain backward compatibility with older LFB models. >=20 >=20 >=20 >=20 > 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. >=20 > The IETF Secretariat From nobody Mon Sep 15 10:09:34 2014 Return-Path: X-Original-To: forces@ietfa.amsl.com Delivered-To: forces@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA6101A8891; Mon, 15 Sep 2014 10:09:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PQV6JzIHzVVc; Mon, 15 Sep 2014 10:09:02 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 040461A89C6; Mon, 15 Sep 2014 09:34:28 -0700 (PDT) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: IETF-Announce X-Test-IDTracker: no X-IETF-IDTracker: 5.6.2.p6 Auto-Submitted: auto-generated Precedence: bulk Sender: Message-ID: <20140915163428.7818.17593.idtracker@ietfa.amsl.com> Date: Mon, 15 Sep 2014 09:34:28 -0700 Archived-At: http://mailarchive.ietf.org/arch/msg/forces/T1ISNtxf1fdUFkuDpMdOqRWoNps Cc: forces@ietf.org Subject: [forces] Last Call: (ForCES Packet Parallelization) to Proposed Standard X-BeenThere: forces@ietf.org X-Mailman-Version: 2.1.15 Reply-To: ietf@ietf.org List-Id: ForCES WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2014 17:09:09 -0000 The IESG has received a request from the Forwarding and Control Element Separation WG (forces) to consider the following document: - 'ForCES Packet Parallelization' as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2014-09-29. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. 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 (RFC 5810), 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 file can be obtained via http://datatracker.ietf.org/doc/draft-ietf-forces-packet-parallelization/ IESG discussion can be tracked via http://datatracker.ietf.org/doc/draft-ietf-forces-packet-parallelization/ballot/ The following IPR Declarations may be related to this I-D: http://datatracker.ietf.org/ipr/2329/ From nobody Mon Sep 15 20:23:25 2014 Return-Path: X-Original-To: forces@ietfa.amsl.com Delivered-To: forces@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BA141A0264; Mon, 15 Sep 2014 20:23:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m7-HeY7VWlcv; Mon, 15 Sep 2014 20:23:17 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 01FFA1A0290; Mon, 15 Sep 2014 20:23:15 -0700 (PDT) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: IETF-Announce X-Test-IDTracker: no X-IETF-IDTracker: 5.6.2.p6 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140916032315.8332.8319.idtracker@ietfa.amsl.com> Date: Mon, 15 Sep 2014 20:23:15 -0700 Archived-At: http://mailarchive.ietf.org/arch/msg/forces/kUb1l1Dc8uL2cSbif9HZgwZYzts Cc: forces mailing list , forces chair , RFC Editor Subject: [forces] Protocol Action: 'ForCES Model Extension' to Proposed Standard (draft-ietf-forces-model-extension-05.txt) X-BeenThere: forces@ietf.org X-Mailman-Version: 2.1.15 List-Id: ForCES WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Sep 2014 03:23:19 -0000 The IESG has approved the following document: - 'ForCES Model Extension' (draft-ietf-forces-model-extension-05.txt) as Proposed Standard This document is the product of the Forwarding and Control Element Separation Working Group. The IESG contact persons are Adrian Farrel and Alia Atlas. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-forces-model-extension/ Technical Summary 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). This memo extends the Forwarding and Control Element Separation (ForCES) model defined in RFC 5812 and updates RFC5812 to allow complex datatypes for metadata, optional default values for datatypes, optional access types for structures. It fixes an issue with Logical Functional Block (LFB) inheritance. It also introduces two new features a new event condition BecomesEqualTo and LFB properties. The changes introduced in this memo do not alter the protocol and retain backward compatibility with older LFB models. Working Group Summary The extensions are straightforward, and there was no difficulty in coming to consensus on all points described. We believe the working group is solidly behind this document. Document Quality There were earlier extensions in earlier versions of the document that were removed based on discussions in the WG for the sake of simplicity. At least one implementation has validated some of the features described in the document. The shepherd validated the sanity of the new extensions to the XML schema in section 4. AD review led to a number of changes (largely for clarity) and a significant issue which resulted in the change of the model version number. Personnel The document shepherd is Jamal Hadi Salim The responsible Area Director is Adrian Farrel