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
>