Re: [forces] RFC 5810 on Forwarding and Control Element Separation (ForCES) Protocol Specification

"Yavatkar, Raj" <raj.yavatkar@intel.com> Tue, 23 March 2010 15:17 UTC

Return-Path: <raj.yavatkar@intel.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 1488D3A6847 for <forces@core3.amsl.com>; Tue, 23 Mar 2010 08:17:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.268
X-Spam-Level:
X-Spam-Status: No, score=-2.268 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001, J_CHICKENPOX_93=0.6, RCVD_IN_DNSWL_MED=-4]
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 PuT40tb0GR2z for <forces@core3.amsl.com>; Tue, 23 Mar 2010 08:17:49 -0700 (PDT)
Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by core3.amsl.com (Postfix) with ESMTP id 37E893A66B4 for <forces@ietf.org>; Tue, 23 Mar 2010 08:17:49 -0700 (PDT)
Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga102.jf.intel.com with ESMTP; 23 Mar 2010 08:15:25 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos; i="4.51,295,1267430400"; d="scan'208,217"; a="606895775"
Received: from orsmsx602.amr.corp.intel.com ([10.22.226.211]) by orsmga001.jf.intel.com with ESMTP; 23 Mar 2010 08:17:40 -0700
Received: from orsmsx507.amr.corp.intel.com ([10.22.226.41]) by orsmsx602.amr.corp.intel.com ([10.22.226.211]) with mapi; Tue, 23 Mar 2010 08:18:06 -0700
From: "Yavatkar, Raj" <raj.yavatkar@intel.com>
To: "Crouch, Alan" <alan.crouch@intel.com>, "Guo, Xiaoyi" <xyi.guo@gmail.com>, "Khosravi, Hormuzd M" <hormuzd.m.khosravi@intel.com>
Date: Tue, 23 Mar 2010 08:18:03 -0700
Thread-Topic: [forces] RFC 5810 on Forwarding and Control Element Separation (ForCES) Protocol Specification
Thread-Index: AcrHP/jU7BbRQUShRdWdBrpgSkjZtwCk2A3QADInwVA=
Message-ID: <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>
In-Reply-To: <80769D7B14936844A23C0C43D9FBCF0F254E407584@orsmsx501.amr.corp.intel.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_8F0C2E89B9AA20448D482EB589641EB357FEF9FEorsmsx507amrcor_"
MIME-Version: 1.0
Cc: "ram.gopal@nsn.com" <ram.gopal@nsn.com>, "forces@ietf.org" <forces@ietf.org>, "donglg@zjgsu.edu.cn" <donglg@zjgsu.edu.cn>, "avri@ltu.se" <avri@ltu.se>, "wmwang@zjgsu.edu.cn" <wmwang@zjgsu.edu.cn>, "jmh@joelhalpern.com" <jmh@joelhalpern.com>
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 15:17:51 -0000

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<mailto: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<mailto:jmh@joelhalpern.com>; ram.gopal@nsn.com<mailto:ram.gopal@nsn.com>; donglg@zjgsu.edu.cn<mailto:donglg@zjgsu.edu.cn>; wmwang@zjgsu.edu.cn<mailto:wmwang@zjgsu.edu.cn>; Khosravi, Hormuzd M; hadi@mojatatu.com<mailto:hadi@mojatatu.com>; avri@ltu.se<mailto:avri@ltu.se>
Cc: forces@ietf.org<mailto: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> [mailto:forces-bounces@ietf.org<mailto:forces-bounces@ietf.org>] On Behalf Of rfc-editor@rfc-editor.org<mailto:rfc-editor@rfc-editor.org>
Sent: Thursday, March 18, 2010 10:18 PM
To: ietf-announce@ietf.org<mailto:ietf-announce@ietf.org>; rfc-dist@rfc-editor.org<mailto:rfc-dist@rfc-editor.org>
Cc: forces@ietf.org<mailto:forces@ietf.org>; rfc-editor@rfc-editor.org<mailto: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<mailto:avri@ltu.se>,
                   hadi@mojatatu.com<mailto:hadi@mojatatu.com>,
                   rha@zurich.ibm.com<mailto:rha@zurich.ibm.com>,  hormuzd.m.khosravi@intel.com<mailto:hormuzd.m.khosravi@intel.com>,
                   wmwang@mail.zjgsu.edu.cn<mailto:wmwang@mail.zjgsu.edu.cn>,  donglg@zjgsu.edu.cn<mailto:donglg@zjgsu.edu.cn>,
                   ram.gopal@nsn.com<mailto:ram.gopal@nsn.com>,  jmh@joelhalpern.com<mailto: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<mailto: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<mailto:forces@ietf.org>
https://www.ietf.org/mailman/listinfo/forces
_______________________________________________
forces mailing list
forces@ietf.org<mailto:forces@ietf.org>
https://www.ietf.org/mailman/listinfo/forces