Re: [forces] RFC 5810 on Forwarding and Control Element Separation (ForCES) Protocol Specification
Jamal Hadi Salim <hadi@mojatatu.com> Tue, 23 March 2010 21:56 UTC
Return-Path: <hadi@mojatatu.com>
X-Original-To: forces@core3.amsl.com
Delivered-To: forces@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D3B973A68C0 for <forces@core3.amsl.com>; Tue, 23 Mar 2010 14:56:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.753
X-Spam-Level:
X-Spam-Status: No, score=0.753 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_93=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O4XAIJZk+ZQC for <forces@core3.amsl.com>; Tue, 23 Mar 2010 14:56:51 -0700 (PDT)
Received: from mail-iw0-f197.google.com (mail-iw0-f197.google.com [209.85.223.197]) by core3.amsl.com (Postfix) with ESMTP id A06103A6946 for <forces@ietf.org>; Tue, 23 Mar 2010 14:56:48 -0700 (PDT)
Received: by iwn35 with SMTP id 35so4059727iwn.31 for <forces@ietf.org>; Tue, 23 Mar 2010 14:57:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.154.77 with SMTP id n13mr449708ibw.11.1269381425216; Tue, 23 Mar 2010 14:57:05 -0700 (PDT)
In-Reply-To: <8F0C2E89B9AA20448D482EB589641EB357FEF9FE@orsmsx507.amr.corp.intel.com>
References: <20100319021752.CE897E0743@rfc-editor.org> <89A1C7FA02B5DF4A8A58BF8DC6B65FDF5931C391@orsmsx502.amr.corp.intel.com> <4C5E6457CD7911469A07260381288C286156C07A@orsmsx502.amr.corp.intel.com> <a1b3200c1003190141v5de65c35ucd972f570fe119ad@mail.gmail.com> <80769D7B14936844A23C0C43D9FBCF0F254E407584@orsmsx501.amr.corp.intel.com> <8F0C2E89B9AA20448D482EB589641EB357FEF9FE@orsmsx507.amr.corp.intel.com>
From: Jamal Hadi Salim <hadi@mojatatu.com>
Date: Tue, 23 Mar 2010 17:56:45 -0400
Message-ID: <af98005c1003231456i70dd1827p9dc5aea7dc87ccc7@mail.gmail.com>
To: "Yavatkar, Raj" <raj.yavatkar@intel.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Tue, 23 Mar 2010 14:58:46 -0700
Cc: "ram.gopal@nsn.com" <ram.gopal@nsn.com>, "jmh@joelhalpern.com" <jmh@joelhalpern.com>, "donglg@zjgsu.edu.cn" <donglg@zjgsu.edu.cn>, "avri@ltu.se" <avri@ltu.se>, "wmwang@zjgsu.edu.cn" <wmwang@zjgsu.edu.cn>, "forces@ietf.org" <forces@ietf.org>
Subject: Re: [forces] RFC 5810 on Forwarding and Control Element Separation (ForCES) Protocol Specification
X-BeenThere: forces@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: ForCES WG mailing list <forces.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 23 Mar 2010 21:56:52 -0000
In retrospect we could probably have done things slightly differently to get this out quicker - but as they say hindsight is 20/20. Perseverance was important in getting things complete. Many thanks to all who hang in and put much effort - and not to forget those who there earlier on whose work we stand. Thanks. cheers, jamal On Tue, Mar 23, 2010 at 11:18 AM, Yavatkar, Raj <raj.yavatkar@intel.com> wrote: > Yes, indeed! Has taken us almost 10 years to get here since we started. > > > > Great job! > > > > Raj > > > > From: forces-bounces@ietf.org [mailto:forces-bounces@ietf.org] On Behalf Of > Crouch, Alan > Sent: Monday, March 22, 2010 8:22 AM > To: Guo, Xiaoyi; Khosravi, Hormuzd M > Cc: ram.gopal@nsn.com; jmh@joelhalpern.com; donglg@zjgsu.edu.cn; > avri@ltu.se; wmwang@zjgsu.edu.cn; forces@ietf.org > Subject: Re: [forces] RFC 5810 on Forwarding and Control Element Separation > (ForCES) Protocol Specification > > > > Well done by all involved! > > > > From: forces-bounces@ietf.org [mailto:forces-bounces@ietf.org] On Behalf Of > Guo, Xiaoyi > Sent: Friday, March 19, 2010 1:41 AM > To: Khosravi, Hormuzd M > Cc: ram.gopal@nsn.com; donglg@zjgsu.edu.cn; avri@ltu.se; forces@ietf.org; > wmwang@zjgsu.edu.cn; jmh@joelhalpern.com > Subject: Re: [forces] RFC 5810 on Forwarding and Control Element Separation > (ForCES) Protocol Specification > > > > Finally see it ,so long time passed... thanks for your good work, > Congratulations!!!! > > 2010/3/19 Khosravi, Hormuzd M <hormuzd.m.khosravi@intel.com> > > Thanks a lot, Lily! We remember your good work as well, your RFC should be > next in line! :) > > Regards > Hormuzd > > -----Original Message----- > From: Yang, Lily L > Sent: Thursday, March 18, 2010 7:34 PM > To: jmh@joelhalpern.com; ram.gopal@nsn.com; donglg@zjgsu.edu.cn; > wmwang@zjgsu.edu.cn; Khosravi, Hormuzd M; hadi@mojatatu.com; avri@ltu.se > Cc: forces@ietf.org > Subject: RE: [forces] RFC 5810 on Forwarding and Control Element Separation > (ForCES) Protocol Specification > > > Wow, finally! Congratulations!!! I think I've stayed on this mailing list > for as long as I did just to see if this day would finally come :-) and YOU > DID IT!!! > > Jamal, Joel, Weiming, Ram, Hormuzd, Avri, and all the others whom I have not > seen for so long that I am not even sure that we would recognize each other > any more - but I remember your good work in the good old days and here is a > toast for you all! > > Lily (from Orlando @IEEE 802 meetings) > > > -----Original Message----- > From: forces-bounces@ietf.org [mailto:forces-bounces@ietf.org] On Behalf Of > rfc-editor@rfc-editor.org > Sent: Thursday, March 18, 2010 10:18 PM > To: ietf-announce@ietf.org; rfc-dist@rfc-editor.org > Cc: forces@ietf.org; rfc-editor@rfc-editor.org > Subject: [forces] RFC 5810 on Forwarding and Control Element Separation > (ForCES) Protocol Specification > > > A new Request for Comments is now available in online RFC libraries. > > > RFC 5810 > > Title: Forwarding and Control Element Separation > (ForCES) Protocol Specification > Author: A. Doria, Ed., > J. Hadi Salim, Ed., > R. Haas, Ed., > H. Khosravi, Ed., > W. Wang, Ed., L. Dong, > R. Gopal, J. Halpern > Status: Standards Track > Date: March 2010 > Mailbox: avri@ltu.se, > hadi@mojatatu.com, > rha@zurich.ibm.com, hormuzd.m.khosravi@intel.com, > wmwang@mail.zjgsu.edu.cn, donglg@zjgsu.edu.cn, > ram.gopal@nsn.com, jmh@joelhalpern.com > Pages: 124 > Characters: 239754 > Updates/Obsoletes/SeeAlso: None > > I-D Tag: draft-ietf-forces-protocol-22.txt > > URL: http://www.rfc-editor.org/rfc/rfc5810.txt > > This document specifies the Forwarding and Control Element Separation > (ForCES) protocol. The ForCES protocol is used for communications > between Control Elements (CEs) and Forwarding Elements (FEs) in a > ForCES Network Element (ForCES NE). This specification is intended > to meet the ForCES protocol requirements defined in RFC 3654. > Besides the ForCES protocol, this specification also defines the > requirements for the Transport Mapping Layer (TML). [STANDARDS TRACK] > > This document is a product of the Forwarding and Control Element Separation > Working Group of the IETF. > > This is now a Proposed Standard Protocol. > > STANDARDS TRACK: This document specifies an Internet standards track > protocol for the Internet community,and requests discussion and suggestions > for improvements. Please refer to the current edition of the Internet > Official Protocol Standards (STD 1) for the standardization state and > status of this protocol. Distribution of this memo is unlimited. > > This announcement is sent to the IETF-Announce and rfc-dist lists. > To subscribe or unsubscribe, see > http://www.ietf.org/mailman/listinfo/ietf-announce > http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist > > For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. > For downloading RFCs, see http://www.rfc-editor.org/rfc.html. > > Requests for special distribution should be addressed to either the > author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless > specifically noted otherwise on the RFC itself, all RFCs are for > unlimited distribution. > > > The RFC Editor Team > Association Management Solutions, LLC > > > _______________________________________________ > forces mailing list > forces@ietf.org > https://www.ietf.org/mailman/listinfo/forces > _______________________________________________ > forces mailing list > forces@ietf.org > https://www.ietf.org/mailman/listinfo/forces > > > > _______________________________________________ > forces mailing list > forces@ietf.org > https://www.ietf.org/mailman/listinfo/forces > >
- [forces] RFC 5810 on Forwarding and Control Eleme… rfc-editor
- Re: [forces] RFC 5810 on Forwarding and Control E… Yang, Lily L
- Re: [forces] RFC 5810 on Forwarding and Control E… Khosravi, Hormuzd M
- Re: [forces] RFC 5810 on Forwarding and Control E… Guo, Xiaoyi
- Re: [forces] RFC 5810 on Forwarding and Control E… Crouch, Alan
- Re: [forces] RFC 5810 on Forwarding and Control E… Yavatkar, Raj
- Re: [forces] RFC 5810 on Forwarding and Control E… Jamal Hadi Salim