
From adrian@olddog.co.uk  Wed Oct  2 08:59:05 2013
Return-Path: <adrian@olddog.co.uk>
X-Original-To: forces@ietfa.amsl.com
Delivered-To: forces@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB9C621F9C90 for <forces@ietfa.amsl.com>; Wed,  2 Oct 2013 08:59:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.066
X-Spam-Level: 
X-Spam-Status: No, score=-2.066 tagged_above=-999 required=5 tests=[AWL=0.533,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xkwaxmd0tn4w for <forces@ietfa.amsl.com>; Wed,  2 Oct 2013 08:58:53 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id 8767A21F9D12 for <forces@ietf.org>; Wed,  2 Oct 2013 08:57:44 -0700 (PDT)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r92FvdD7022936;  Wed, 2 Oct 2013 16:57:40 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r92FvZl7022884 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 2 Oct 2013 16:57:39 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <draft-ietf-forces-ceha.all@tools.ietf.org>
References: <02b001ce884a$a1585040$e408f0c0$@olddog.co.uk> <CAAFAkD-iZ7nPmt=LPuP_fepgR5iGh0gGu9ex1Q5M11L37bhrmg@mail.gmail.com> <000001ce896e$719cc370$54d64a50$@olddog.co.uk> <CAAFAkD_Qc9upLbip7isVjWxap1JDWsoiy=b5x9yERbFTb3Jcjg@mail.gmail.com> <005401ce91d8$cebba310$6c32e930$@com> <043d01ce9c38$d4470990$7cd51cb0$@olddog.co.uk>, <CAAFAkD9ArGhtR4yjqi=-QijvOC306JmSvei6WmSTGi+L+F-c4A@mail.gmail.com> <47c336e0b91d46afa25e7e8224cbd520@BLUPR05MB151.namprd05.prod.outlook.com>
In-Reply-To: <47c336e0b91d46afa25e7e8224cbd520@BLUPR05MB151.namprd05.prod.outlook.com>
Date: Wed, 2 Oct 2013 16:57:33 +0100
Message-ID: <01e501cebf88$1dd8fba0$598af2e0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQI6Q07702xNavMLAOpMwrNoOkw4/QDZ/dJYAYs+HZYBvSIYHwIFW19dAdMPOjgCI0uW4gJAyZjAmKeQuoA=
Content-Language: en-gb
Cc: forces@ietf.org, forces-chairs@tools.ietf.org
Subject: Re: [forces] AD Review of draft-ietf-forces-ceha
X-BeenThere: forces@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: ForCES WG mailing list <forces.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/forces>, <mailto:forces-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/forces>
List-Post: <mailto:forces@ietf.org>
List-Help: <mailto:forces-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/forces>, <mailto:forces-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Oct 2013 15:59:06 -0000

Authors,

Why don't you do what Jamal suggested, post a new revision with this change and
the others already discussed, and then we can move the document forward?

Adrian

> Cc: Haleplidis Evangelos; forces@ietf.org;
draft-ietf-forces-ceha.all@tools.ietf.org
> Subject: Re: [forces] AD Review of draft-ietf-forces-ceha
> 
> Hi,
> 
> I am sorry I missed this - Evangelos reminded me while i was trying
> to figure out where the publication path is.
> 
> My take on this is we should use new rows for each version.
> But we also need a new column to identify the version. IMO, that
> would be the best way to scale in the future if we keep adding new versions.
> So if folks agree we would need to ask IANA for the new version column.
> 
> The reference column will continue to be identifying which RFC/docs are
> utilized and which are obsoleted.
> 
> cheers,
> jamal
> 
> On Sun, Aug 18, 2013 at 1:31 PM, Adrian Farrel <adrian@olddog.co.uk> wrote:
> > Hello,
> >
> >> > Section 5 needs to give clear and unambiguous instructions to the IANA.
> >> > It seems that the text in Section 5 is currently a placeholder for the
> >> > correct text.
> >>
> >> Looking on the IANA considerations I am not exactly sure how to address the
> >> issue.
> >>
> >> In my mind there are two possibilities.
> >>
> >> 1. Update the "Logical Functional Block (LFB) Class Names and Class
> >> Identifiers" https://www.iana.org/assignments/forces/forces.xml by adding
> >> one more column "LFB Version" after (or before) the LFB Class Name. Value
of
> >> 1.0 for all existing LFBs and then add a new row for Version 1.1 after the
> >> FE Protocol Object for version 1.1.
> >>
> >> 2. Update the FEPO reference with [RFC5810] v1.0, [CEHA RFC] v.1.1.
> >>
> >> I'm more inclined to go for the first one but that would require
> >> restructuring of the IANA page.
> >> What should be the proper way forward?
> >
> > I was hoping that Jamal would know what needed to be done here.
> > I think you are saying that the LFB class identifier in the registry points
to
> > XML present in the referenced document.
> > Thus, previously, when you saw LFB Class Identifier 2, you knew to look in
RFC
> > 5810 for the XML for the LFB.
> >
> > Now you have confusion. Does LFB Class Identifier 2 refer to the FEPO LFB
v1.0
> > in RFC 5810, the FEPO LFB v1.1 in this I-D, or both?
> >
> > I can't answer that question for you!
> >
> > However, since I see the version number embedded in the XML, I am relatively
> > sure that this document:
> > - updates RFC 5810 by replacing the XML
> > - should be referenced alongside RFC 5810 in the registry
> >
> > Note that updating 5810 requires a little work to:
> > - mention it in the meta-data
> > - note it in the Introduction "This document updates foo by doing bah."
> > - explain it in a short paragraph in the introduction.
> >
> >> > Section 3.1.1
> >> >
> >> > "CEID" is used without expansion. Although sometimes I find "CE ID" for
> >> example in 3.1.2.
> >>
> >> The CEID refers to a component in the FE Protocol Object. The CE ID refers
> >> to the ID of the CE. There were a few discrepancies but have been fixed.
The
> >> CEID is now followed by the word "component" while the CE ID is not. Will
> >> that be sufficient to remove the confusion?
> >
> > It would be nice if the first usage of each expanded it into English.
> >
> > Cheers,
> > Adrian
> >
> 



From internet-drafts@ietf.org  Mon Oct 14 14:13:10 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: forces@ietfa.amsl.com
Delivered-To: forces@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA53E21E8117; Mon, 14 Oct 2013 14:13:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 75weqfW-aosI; Mon, 14 Oct 2013 14:13:10 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0732321E8163; Mon, 14 Oct 2013 14:13:06 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131014211305.11455.40925.idtracker@ietfa.amsl.com>
Date: Mon, 14 Oct 2013 14:13:05 -0700
Cc: forces@ietf.org
Subject: [forces] I-D Action: draft-ietf-forces-ceha-08.txt
X-BeenThere: forces@ietf.org
X-Mailman-Version: 2.1.12
List-Id: ForCES WG mailing list <forces.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/forces>, <mailto:forces-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/forces>
List-Post: <mailto:forces@ietf.org>
List-Help: <mailto:forces-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/forces>, <mailto:forces-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Oct 2013 21:13:10 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Forwarding and Control Element Separation=
 Working Group of the IETF.

	Title           : ForCES Intra-NE High Availability
	Author(s)       : Kentaro Ogawa
                          Weiming Wang
                          Evangelos Haleplidis
                          Jamal Hadi Salim
	Filename        : draft-ietf-forces-ceha-08.txt
	Pages           : 27
	Date            : 2013-10-14

Abstract:
   This document discusses Control Element High Availability within a
   ForCES Network Element.  Additionally this document updates [RFC5810]
   by providing new normative text for the Cold-Standby High
   availability mechanism.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-forces-ceha

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-forces-ceha-08

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-forces-ceha-08


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 iesg-secretary@ietf.org  Wed Oct 16 12:35:00 2013
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: forces@ietfa.amsl.com
Delivered-To: forces@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49F9B11E82D7; Wed, 16 Oct 2013 12:35:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.442
X-Spam-Level: 
X-Spam-Status: No, score=-102.442 tagged_above=-999 required=5 tests=[AWL=0.158, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NicArEMW96JO; Wed, 16 Oct 2013 12:34:59 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 45B2611E8260; Wed, 16 Oct 2013 12:34:49 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p2
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <iesg-secretary@ietf.org>
Message-ID: <20131016193449.16458.81174.idtracker@ietfa.amsl.com>
Date: Wed, 16 Oct 2013 12:34:49 -0700
Cc: forces@ietf.org
Subject: [forces] Last Call: <draft-ietf-forces-ceha-08.txt> (ForCES Intra-NE High	Availability) to Proposed Standard
X-BeenThere: forces@ietf.org
X-Mailman-Version: 2.1.12
Reply-To: ietf@ietf.org
List-Id: ForCES WG mailing list <forces.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/forces>, <mailto:forces-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/forces>
List-Post: <mailto:forces@ietf.org>
List-Help: <mailto:forces-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/forces>, <mailto:forces-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Oct 2013 19:35:00 -0000

The IESG has received a request from the Forwarding and Control Element
Separation WG (forces) to consider the following document:
- 'ForCES Intra-NE High Availability'
  <draft-ietf-forces-ceha-08.txt> 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 2013-11-06 (the last call period has been
extended by one week to allow additional time as people prepare for
IETF-88). 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

   This document discusses Control Element High Availability within a
   ForCES Network Element.  Additionally this document updates [RFC5810]
   by providing new normative text for the Cold-Standby High
   availability mechanism.


The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-forces-ceha/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-forces-ceha/ballot/


No IPR declarations have been submitted directly on this I-D.

From hadi@mojatatu.com  Thu Oct 17 10:48:56 2013
Return-Path: <hadi@mojatatu.com>
X-Original-To: forces@ietfa.amsl.com
Delivered-To: forces@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E016811E81B8 for <forces@ietfa.amsl.com>; Thu, 17 Oct 2013 10:48:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.977
X-Spam-Level: 
X-Spam-Status: No, score=-102.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YFm646UtOf4R for <forces@ietfa.amsl.com>; Thu, 17 Oct 2013 10:48:51 -0700 (PDT)
Received: from mail-ee0-f41.google.com (mail-ee0-f41.google.com [74.125.83.41]) by ietfa.amsl.com (Postfix) with ESMTP id 3E35011E8169 for <forces@ietf.org>; Thu, 17 Oct 2013 10:48:50 -0700 (PDT)
Received: by mail-ee0-f41.google.com with SMTP id b15so1024626eek.28 for <forces@ietf.org>; Thu, 17 Oct 2013 10:48:50 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc :content-type; bh=+YM8ELcHljTHhNxSFQXUyUDiwxv0HUXa55nPkDI1IVI=; b=MwN1afyc0CroDX7m+zG2fBSSqfP2CxSNGogEJdRfYC2Ur7ZBWq7a9Evjro6OYafWN/ TnCtAUw0ZOHAET/tk3HJfuSjsP70HFak3PanAP1SLoEwlQPKjfRMOAGE3kvKUEDPOasR KMtkW1/1UblAKRoZp8kqny2I4GjbJV95ou0C7sCZOBTU+2NBmNkz3zsX4Tl7Yn1maw0l WKd8usb4t0gfDRDr8QW+sxTO4umr45YnrRX6b4Fz+R6dpbX+QQTN5S+4zUbtVCE2TDCb 6FP9ivLUCzqmsDF6crcJMcy8Kjm+wPoUMUN29GKx+xSnVPWJpcxjnpTPMFxiS/nnlDf3 vP9A==
X-Gm-Message-State: ALoCoQkH7+9FuFYudtJ6pJJBYD4RlgOw51FFTa309aSBO7mo4qtzhtg6PFfeEdSuPIEq97uXHJio
X-Received: by 10.204.121.201 with SMTP id i9mr7924419bkr.13.1382032130270; Thu, 17 Oct 2013 10:48:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.205.40.197 with HTTP; Thu, 17 Oct 2013 10:48:30 -0700 (PDT)
From: Jamal Hadi Salim <hadi@mojatatu.com>
Date: Thu, 17 Oct 2013 13:48:30 -0400
Message-ID: <CAAFAkD_iBXg9D1Sr_Y70f7Z+j5Knf5WcsgHoeb2kMeKUppknAQ@mail.gmail.com>
To: "forces@ietf.org" <forces@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: [forces] Agenda items
X-BeenThere: forces@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: ForCES WG mailing list <forces.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/forces>, <mailto:forces-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/forces>
List-Post: <mailto:forces@ietf.org>
List-Help: <mailto:forces-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/forces>, <mailto:forces-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Oct 2013 17:48:57 -0000

Folks,
If you have an item related to the WG that you would
like to present on - please send DJ and myself an email.

All chartered wg items that are in progress get automatic consideration.

cheers,
jamal

From ehalep@gmail.com  Thu Oct 17 12:26:51 2013
Return-Path: <ehalep@gmail.com>
X-Original-To: forces@ietfa.amsl.com
Delivered-To: forces@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A17A711E812A for <forces@ietfa.amsl.com>; Thu, 17 Oct 2013 12:26:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cNb-xvnRc9In for <forces@ietfa.amsl.com>; Thu, 17 Oct 2013 12:26:51 -0700 (PDT)
Received: from mail-ee0-x22b.google.com (mail-ee0-x22b.google.com [IPv6:2a00:1450:4013:c00::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 4ACDF11E817B for <forces@ietf.org>; Thu, 17 Oct 2013 12:26:41 -0700 (PDT)
Received: by mail-ee0-f43.google.com with SMTP id e52so1351693eek.16 for <forces@ietf.org>; Thu, 17 Oct 2013 12:26:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-type:content-transfer-encoding:thread-index :content-language; bh=w1ONOggCdny7yRU4Pme2gr2/RVNn4RUHWbod+z91LKk=; b=LUfh+1GgItAc8aD7fcPhknBHh9K/0jbWiT2NbotT+W1X/AjgK9xPWg9TM6R0nUZuP6 ymp/CbyusqrVKWigSeUqK2C28RxomcraNubGFD6x2Y/jsfOvP7kSgqyt6PJQexF0EMt9 aDSMjohU79RIwJXhAEL6v5ID6CmV7eBNqpOX7Z6A18fWR/Y+jSzkJWlkJ5uBcI7oC9Yx FNm1nSqTRfIyDlwCOOQRH4tNijzEfkCKSXBVUCE4U6qC9UNkVehxJY/GF1KJmv8W6KiR cr+XEYle9rThxIjDBUyIQcxHKnNbN5BvwcYElIlIbrPwaEr1lVVpJ8uRoNsNXrCqN5nw QFTw==
X-Received: by 10.15.67.131 with SMTP id u3mr14885850eex.34.1382038000934; Thu, 17 Oct 2013 12:26:40 -0700 (PDT)
Received: from EhalepXPS (ppp141237182120.access.hol.gr. [141.237.182.120]) by mx.google.com with ESMTPSA id l49sm112610824eeo.12.1969.12.31.16.00.00 (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 17 Oct 2013 12:26:40 -0700 (PDT)
From: "Haleplidis Evangelos" <ehalep@gmail.com>
To: <forces@ietf.org>
References: <CAAFAkD_iBXg9D1Sr_Y70f7Z+j5Knf5WcsgHoeb2kMeKUppknAQ@mail.gmail.com>
In-Reply-To: <CAAFAkD_iBXg9D1Sr_Y70f7Z+j5Knf5WcsgHoeb2kMeKUppknAQ@mail.gmail.com>
Date: Thu, 17 Oct 2013 22:26:35 +0300
Message-ID: <019601cecb6e$cc923ca0$65b6b5e0$@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: Ac7LYSj5MDOtixxPRDy0JiFfrd5NeAADQ+/A
Content-Language: el
Subject: Re: [forces] Agenda items
X-BeenThere: forces@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: ForCES WG mailing list <forces.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/forces>, <mailto:forces-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/forces>
List-Post: <mailto:forces@ietf.org>
List-Help: <mailto:forces-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/forces>, <mailto:forces-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Oct 2013 19:26:51 -0000

Greetings,

I would like to present the following two items for this session:
1. The current state of the parallelization draft (it's currently stable
with only one pending issue and also ask acceptance as a wg item).
2. The currest state of the model extension draft and finalization. The plan
is to make final adjustments based on the meeting's feedback and produce the
final document for LC right after the meeting.

So, I guess I'll need about 5-10' for the parallelization and another 5-10'
for the model.

Regards,
Evangelos Haleplidis.

> -----Original Message-----
> From: forces-bounces@ietf.org [mailto:forces-bounces@ietf.org] On
> Behalf Of Jamal Hadi Salim
> Sent: Thursday, October 17, 2013 8:49 PM
> To: forces@ietf.org
> Subject: [forces] Agenda items
> 
> Folks,
> If you have an item related to the WG that you would like to present on
> - please send DJ and myself an email.
> 
> All chartered wg items that are in progress get automatic
> consideration.
> 
> cheers,
> jamal
> _______________________________________________
> forces mailing list
> forces@ietf.org
> https://www.ietf.org/mailman/listinfo/forces


From hadi@mojatatu.com  Tue Oct 29 07:08:43 2013
Return-Path: <hadi@mojatatu.com>
X-Original-To: forces@ietfa.amsl.com
Delivered-To: forces@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A155211E8242 for <forces@ietfa.amsl.com>; Tue, 29 Oct 2013 07:08:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.977
X-Spam-Level: 
X-Spam-Status: No, score=-102.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oSb400jNjf1w for <forces@ietfa.amsl.com>; Tue, 29 Oct 2013 07:08:38 -0700 (PDT)
Received: from mail-ve0-f169.google.com (mail-ve0-f169.google.com [209.85.128.169]) by ietfa.amsl.com (Postfix) with ESMTP id 3759311E823E for <forces@ietf.org>; Tue, 29 Oct 2013 07:08:38 -0700 (PDT)
Received: by mail-ve0-f169.google.com with SMTP id c14so4675100vea.0 for <forces@ietf.org>; Tue, 29 Oct 2013 07:08:37 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-type; bh=jACx4mfUpugpmdYXD+bVBnilp68Ntw/LMIbuXXVpRSo=; b=OqLCSOFMxawF1ar+COmXG/6agfctl/nLumf5xVOY9c0yWENoVp3c4F+2HiziI/rd8C wfLfn/Bk2Li/sOGjz/Hp8wgty7CxPCzkIcF03Qs3x1bN2isiOiEBADDznMv2M+TIZO0Z fj2HrjMeiyzkPGR7AtUxBZJbyfKDaCQ+uYiMMGysWx9x5XTbFS6igM4tG7Tre4ZA+Pcn /bR8C7VP7xCfPa1x2izGrEhFIdSCHO5gL9RiF2KBfvsQKVlP0D27y2Fyn4Yew0eFRuhV 8XzIgn5kkZUl5pcOYX2gAhmLxoEddi3rAbG+z4DHI0aM/9IpifhVSjqMoUSd/VWuibVC NSqg==
X-Gm-Message-State: ALoCoQnrvSXDEuIV0nmtJi0wC3im2b9ZgHS9nVKuf4mP9bq4M7X3BA7uF9tanAgoREFJ5BJcMeHC
X-Received: by 10.220.110.7 with SMTP id l7mr25105vcp.63.1383055717393; Tue, 29 Oct 2013 07:08:37 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.58.8.19 with HTTP; Tue, 29 Oct 2013 07:08:17 -0700 (PDT)
From: Jamal Hadi Salim <hadi@mojatatu.com>
Date: Tue, 29 Oct 2013 10:08:17 -0400
Message-ID: <CAAFAkD-fL3cNJ92Kf0h00UudutnXqn_1awyW7oyqtHknS1opWg@mail.gmail.com>
To: "forces@ietf.org" <forces@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: [forces] Bits and Bites
X-BeenThere: forces@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: ForCES WG mailing list <forces.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/forces>, <mailto:forces-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/forces>
List-Post: <mailto:forces@ietf.org>
List-Help: <mailto:forces-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/forces>, <mailto:forces-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Oct 2013 14:08:43 -0000

Folks,

Just to let you know - at this meeting in Vancouver there will be demo
of Service aware networking (using ForCES at Bits and Bites on
thursday. For people who cant make it for bits and bites, we'll have
a shorter preview at the meeting's tail end.

The theme will constitute of three ingredients - all demonstrating the
versatility
of using ForCES in all 3 aspects of network programmability:

a) Open Network Devices.
We will demonstrate a variety of open datapaths running ForCES:
These include:
- physical machines with Linux
- VMs using KVM
- Cumulus Networks Open Network Devices (Broadcom ASIC based)

b)Open Network Functions.
These include a variety of ForCES LFBs:
- a variety of datapath LFBs needed for creating a PGW datapath
- a management LFB that is used to describe VMs
- a set of general purpose LFBs (which are available on all network devices):
       *switching/bridging (L2 FDB, L2 bridge ports, L2 Vlan filtering)
       *physical/virtual ports (wide range: physical, tunnels like
vxlan, to simple tuntap on Linux etc)
       *IP address LFB

c) Open Network Services.
These will be services and apps utilizing the network functions above.
At the moment on the list (it may grow) are:
      * illustration of  PGW control setting of the various LFBs for a UE
      * illustration of booting and managing VM lifecyles for virtual FEs/CEs
      * A CLI app at the controller controlling and managing all aspects of the
         different Network Devices as well as monitoring them.

I should point out that demonstrating a CLI is boring - wish we could dazzle you
with flashing lights on a GUI - but we had a very short  period to put
all of this together;
the purpose of the  CLI is to illustrates the power of ForCES being
agnostic to the underlying
infrastructure as long as one defines an XML, using the ForCES language,
for an arbitrary network function. Essentially we have a consistent API _defined
by the XML_ for the Control Abstraction Layer (CAL) etc.

Hope to see you there!

cheers,
jamal
