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

"Khosravi, Hormuzd M" <hormuzd.m.khosravi@intel.com> Fri, 19 March 2010 03:06 UTC

Return-Path: <hormuzd.m.khosravi@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 B38C13A6C8B for <forces@core3.amsl.com>; Thu, 18 Mar 2010 20:06:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.869
X-Spam-Level:
X-Spam-Status: No, score=-4.869 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, 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 vwQo-dpzpo3Y for <forces@core3.amsl.com>; Thu, 18 Mar 2010 20:06:52 -0700 (PDT)
Received: from mga14.intel.com (mga14.intel.com [143.182.124.37]) by core3.amsl.com (Postfix) with ESMTP id 7F97D3A6C5B for <forces@ietf.org>; Thu, 18 Mar 2010 20:06:52 -0700 (PDT)
Received: from azsmga001.ch.intel.com ([10.2.17.19]) by azsmga102.ch.intel.com with ESMTP; 18 Mar 2010 20:07:04 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="4.51,272,1267430400"; d="scan'208";a="256416847"
Received: from orsmsx603.amr.corp.intel.com ([10.22.226.49]) by azsmga001.ch.intel.com with ESMTP; 18 Mar 2010 20:07:04 -0700
Received: from orsmsx502.amr.corp.intel.com ([10.22.226.210]) by orsmsx603.amr.corp.intel.com ([10.22.226.49]) with mapi; Thu, 18 Mar 2010 20:07:03 -0700
From: "Khosravi, Hormuzd M" <hormuzd.m.khosravi@intel.com>
To: "Yang, Lily L" <lily.l.yang@intel.com>, "jmh@joelhalpern.com" <jmh@joelhalpern.com>, "ram.gopal@nsn.com" <ram.gopal@nsn.com>, "donglg@zjgsu.edu.cn" <donglg@zjgsu.edu.cn>, "wmwang@zjgsu.edu.cn" <wmwang@zjgsu.edu.cn>, "hadi@mojatatu.com" <hadi@mojatatu.com>, "avri@ltu.se" <avri@ltu.se>
Date: Thu, 18 Mar 2010 20:07:02 -0700
Thread-Topic: [forces] RFC 5810 on Forwarding and Control Element Separation (ForCES) Protocol Specification
Thread-Index: AcrHCmjOj3E1p8qZRmOdaaUd+3YdiQAAFIlAAAGYtGA=
Message-ID: <4C5E6457CD7911469A07260381288C286156C07A@orsmsx502.amr.corp.intel.com>
References: <20100319021752.CE897E0743@rfc-editor.org> <89A1C7FA02B5DF4A8A58BF8DC6B65FDF5931C391@orsmsx502.amr.corp.intel.com>
In-Reply-To: <89A1C7FA02B5DF4A8A58BF8DC6B65FDF5931C391@orsmsx502.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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "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: Fri, 19 Mar 2010 03:06:53 -0000

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