Forwarding and Control Element Separation (forces)

Internet-Drafts | 7 Sep 2009 13:15

Picon

I-D Action:draft-ietf-forces-implementation-report-00.txt

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

	Title           : Implementation Report for ForCES
	Author(s)       : E. Haleplidis, et al.
	Filename        : draft-ietf-forces-implementation-report-00.txt
	Pages           : 38
	Date            : 2009-09-07

Forwarding and Control Element Separation (ForCES) defines an
architectural framework and associated protocols to standardize
information exchange between the control plane and the forwarding
plane in a ForCES Network Element (ForCES NE).  RFC3654 has defined
the ForCES requirements, and RFC3746 has defined the ForCES
framework.

This document is an implementation report of the ForCES Protocol,
Model and SCTP-TML, including the report on interoperability testing
and the current state of ForCES implementations.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-forces-implementation-report-00.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

(Continue reading)

Khosravi, Hormuzd M | 25 Jul 2003 22:53

Picon

Re: I-D ACTION:draft-ietf-forces-requirements-10.txt

Hi All

I have uploaded the latest rev of the Requirements draft.
It basically has couple of editorial changes based on
Chairs/IESG feedback and list discussion.

Here is a summary of the changes...

In section 7, point 6 changed
"ForCES MAY NOT impose strict reliability" -> "ForCES MUST NOT be
restricted to strict reliability"
This was based on comments from Robert Haas, Patrick Droz on the mailing
list

In section 6.5, point 8 changed
"In addition, FEs MUST allow logical functions..." -> "In addition, the
FE Model MUST allow logical functions..."
This was based on IESG feedback to avoid putting requirements on all FE
implementations.

Thanks
Hormuzd

-----Original Message-----
From: Internet-Drafts <at> ietf.org [mailto:Internet-Drafts <at> ietf.org] 
Sent: Friday, July 25, 2003 12:27 PM
To: FORCES <at> PEACH.EASE.LSOFT.COM
Subject: [FORCES] I-D ACTION:draft-ietf-forces-requirements-10.txt

A New Internet-Draft is available from the on-line Internet-Drafts

(Continue reading)

Yang, Lily L | 13 Jun 2003 19:13

Picon

Re: I-D ACTION:draft-ietf-forces-framework-06.txt

Hi, Alex, David and Patrick --
This is the new version with formatting and editorial changes, thanks to Randy's comments.
Please use this new version for the review process.

Thanks,
Lily

> -----Original Message-----
> From: Internet-Drafts <at> ietf.org [mailto:Internet-Drafts <at> ietf.org]
> Sent: Friday, June 13, 2003 4:50 AM
> To: FORCES <at> PEACH.EASE.LSOFT.COM
> Subject: I-D ACTION:draft-ietf-forces-framework-06.txt
> 
> 
> A New Internet-Draft is available from the on-line 
> Internet-Drafts directories.
> This draft is a work item of the Forwarding and Control 
> Element Separation Working Group of the IETF.
> 
>         Title           : Forwarding and Control Element 
> Separation (ForCES)
>                           Framework
>         Author(s)       : L. Yang et al.
>         Filename        : draft-ietf-forces-framework-06.txt
>         Pages           : 38
>         Date            : 2003-6-12
> 
> This document defines the architectural framework for the ForCES
> (Forwarding and Control Element Separation) network elements, and
> identifies the associated entities and the interaction among them.

(Continue reading)

Yang, Lily L | 13 Jun 2003 18:45

Picon

Re: I-D ACTION:draft-ietf-forces-framework-05.txt

Robert -- Thanks for catching this. 
Lily

-----Original Message-----
From: Robert Haas [mailto:rha <at> zurich.ibm.com]
Sent: Thursday, June 12, 2003 1:04 AM
To: FORCES <at> PEACH.EASE.LSOFT.COM
Subject: Re: I-D ACTION:draft-ietf-forces-framework-05.txt

Lily,
Now that we have updated the requirements draft regarding strict 
reliability, I think the framework draft should also be updated 
accordingly in section 4.2.1 (see below). In addition, in the local 
scope case with directly-attached CEs and FEs (such as PCI bus), I do 
not see the need for congestion avoidance mechanisms.

[excerpt of framework draft sec. 4.2.1]
"ForCES will make use of an existing RFC2914 ([2]) compliant L4 protocol 
with adequate reliability, security and congestion control (e.g. TCP, 
SCTP) for transport purposes. "

Regards,
-Robert

--

-- 
Robert Haas
IBM Zurich Research Laboratory
Säumerstrasse 4
CH-8803 Rüschlikon/Switzerland
phone +41-1-724-8698  fax +41-1-724-8578  http://www.zurich.ibm.com/~rha

(Continue reading)

Khosravi, Hormuzd M | 6 Jan 2006 07:36

Picon

Re: I-D ACTION:draft-ietf-forces-protocol-06.txt

Hi Avri,

I was under the impression that the authors needed to discuss some
issues based on your last email. Guess I misunderstood.

In any case we need to get things moving ahead. Either via a call or
just email, doesn't matter. It would be helpful if the chairs would set
a deadline for people to post any comments they have, so that way we
could move to IESG review soon. 

If you need help on any of the remaining editorial work, pls do let us
know

Thanks
Hormuzd
-----Original Message-----
From: Forwarding and Control Element Separation
[mailto:FORCES <at> PEACH.EASE.LSOFT.COM] On Behalf Of Avri Doria
Sent: Tuesday, January 03, 2006 2:26 PM
To: FORCES <at> PEACH.EASE.LSOFT.COM
Subject: Re: [FORCES] I-D ACTION:draft-ietf-forces-protocol-06.txt

what issues need to be dealt with in a phone call?

My expectation was that those who had put in issues/change requests  
would decide whether more was still needed or if they had been  
addressed adequately.  and if they felt more was needed, would  
explicitly say what was needed.  so either people haven't reviewed  
-06 yet, or there are no issues ( i cannot believe this is the case -  
though it would make me happy)

(Continue reading)

Khosravi, Hormuzd M | 3 Jan 2006 02:38

Picon

Re: I-D ACTION:draft-ietf-forces-protocol-06.txt

Greetings, 

Wish all the WG members a very Happy New Year!! 

I haven't seen much activity on the protocol draft after the last update
by Avri.
Should I set up a conference call to close on any issues that need to be
discussed?

Avri, could you send us a list of issues that you feel need to be
further discussed, that would be very helpful.

I am trying to figure out what's needed to take the draft to the next
stage for IESG review.

Thanks
Hormuzd

-----Original Message-----
From: Forwarding and Control Element Separation
[mailto:FORCES <at> PEACH.EASE.LSOFT.COM] On Behalf Of Avri Doria
Sent: Thursday, December 15, 2005 9:19 AM
To: FORCES <at> PEACH.EASE.LSOFT.COM
Subject: Re: [FORCES] I-D ACTION:draft-ietf-forces-protocol-06.txt

On 15 dec 2005, at 04.45, Wang,Weiming wrote:

>
> To better reflect the editing work of the draft in the issue  
> trackers, may I

(Continue reading)

Weiming Wang | 3 Jan 2005 14:56

Picon

Re: I-D ACTION:draft-ietf-forces-protocol-06.txt

----- Original Message -----
From: "Khosravi, Hormuzd M" <hormuzd.m.khosravi <at> intel.com>
Subject: Re: I-D ACTION:draft-ietf-forces-protocol-06.txt

Greetings,

Wish all the WG members a very Happy New Year!!

I haven't seen much activity on the protocol draft after the last update
by Avri.
Should I set up a conference call to close on any issues that need to be
discussed?

- That would be very helpful. Thanks, Hormuzd.

Weiming

Avri Doria | 3 Jan 2006 23:25

Re: I-D ACTION:draft-ietf-forces-protocol-06.txt

Hi,

On 3 jan 2005, at 08.56, Weiming Wang wrote:

> ----- Original Message -----
> From: "Khosravi, Hormuzd M" <hormuzd.m.khosravi <at> intel.com>
> Subject: Re: I-D ACTION:draft-ietf-forces-protocol-06.txt
>
>
> Greetings,
>
> Wish all the WG members a very Happy New Year!!
>
> I haven't seen much activity on the protocol draft after the last  
> update
> by Avri.
> Should I set up a conference call to close on any issues that need  
> to be
> discussed?
>
> - That would be very helpful. Thanks, Hormuzd.

what issues need to be dealt with in a phone call?

My expectation was that those who had put in issues/change requests  
would decide whether more was still needed or if they had been  
addressed adequately.  and if they felt more was needed, would  
explicitly say what was needed.  so either people haven't reviewed  
-06 yet, or there are no issues ( i cannot believe this is the case -  
though it would make me happy)

(Continue reading)

Jamal Hadi Salim | 10 Jan 2006 15:27

Re: I-D ACTION:draft-ietf-forces-protocol-06.txt

Olla,

Apologies for not participating for a while now ..
I am trying to go over the emails - I hope i dont miss any.

I reviewed the -06 draft and don't see any issues that are technical;
rather they are mostly editorial. Perhaps we should close all the issues
that have been addressed in -06? You can certainly close all the
ones opened by myself.

As far as interop: - I strongly believe we should _not_ make it a
gating issue for the protocol to move to the RFC queue. The rules call out
for implementations existing not necessarily inter-oping. I can tell you
inter-op at the moment is very low prio for us (that doesnt equate we wouldnt
be interested in a future interop, just that it is something we cant adequately
allocate resources to at the moment)

cheers,
jamal

On Tue, 2006-03-01 at 17:25 -0500, Avri Doria wrote:
> Hi,
> 
> 
> On 3 jan 2005, at 08.56, Weiming Wang wrote:
> 
> > ----- Original Message -----
> > From: "Khosravi, Hormuzd M" <hormuzd.m.khosravi <at> intel.com>
> > Subject: Re: I-D ACTION:draft-ietf-forces-protocol-06.txt
> >

(Continue reading)

Khosravi, Hormuzd M | 2 May 2002 02:39

Picon

Re: I-D ACTION:draft-ietf-forces-requirements-03.txt

The design team has put together the new revision of the Requirements draft.
We have tried to incorporate all the comments that we received for the last
version. I think the draft is in good shape and would like to last call it.
Any comments ?

Hormuzd
-----Original Message-----
From: Internet-Drafts <at> ietf.org [mailto:Internet-Drafts <at> ietf.org]
Sent: Tuesday, April 30, 2002 4:15 AM
To: FORCES <at> PEACH.EASE.LSOFT.COM
Subject: [FORCES] I-D ACTION:draft-ietf-forces-requirements-03.txt

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

        Title           : Requirements for Separation of IP Control and
                          Forwarding
        Author(s)       : T. Anderson et al.
        Filename        : draft-ietf-forces-requirements-03.txt
        Pages           : 15
        Date            : 29-Apr-02

This document introduces the ForCES architecture and defines a set
of associated terminology.  This document also defines a set of
architectural, modeling, and protocol requirements to logically
separate the control and data forwarding planes of an IP (IPv4,
IPv6, etc.) networking device.

(Continue reading)

Vip Sharma | 2 May 2002 14:57

Re: I-D ACTION:draft-ietf-forces-requirements-03.txt

Hormuzd,
        I agree with your summarry of the reqmnt. Draft... That it is
ready for last call..

vip

-----Original Message-----
From: Forwarding and Control Element Separation
[mailto:FORCES <at> PEACH.EASE.LSOFT.COM] On Behalf Of Khosravi, Hormuzd M
Sent: Wednesday, May 01, 2002 8:40 PM
To: FORCES <at> PEACH.EASE.LSOFT.COM
Subject: Re: I-D ACTION:draft-ietf-forces-requirements-03.txt

The design team has put together the new revision of the Requirements
draft.
We have tried to incorporate all the comments that we received for the
last
version. I think the draft is in good shape and would like to last call
it.
Any comments ?

Hormuzd
-----Original Message-----
From: Internet-Drafts <at> ietf.org [mailto:Internet-Drafts <at> ietf.org]
Sent: Tuesday, April 30, 2002 4:15 AM
To: FORCES <at> PEACH.EASE.LSOFT.COM
Subject: [FORCES] I-D ACTION:draft-ietf-forces-requirements-03.txt

A New Internet-Draft is available from the on-line Internet-Drafts
directories.

(Continue reading)

Khosravi, Hormuzd M | 11 Feb 2003 21:09

Picon

Re: I-D ACTION:draft-ietf-forces-requirements-08.txt

Hi All

This is the latest version of the Requirements draft and incorporates the
feedback received from the IESG.

Summary of changes :
Packet Duplication - added text to section 7 #9.
TLS and Reliable Transport - added comment to section 7 #2.
Introduction before Definitions - fixed, moved sections.
Layering Issue - fixed in definition of Addressable Entity (AE)

Thanks
Hormuzd
-----Original Message-----
From: Internet-Drafts <at> ietf.org [mailto:Internet-Drafts <at> ietf.org]
Sent: Tuesday, February 11, 2003 3:44 AM
To: FORCES <at> PEACH.EASE.LSOFT.COM
Subject: [FORCES] I-D ACTION:draft-ietf-forces-requirements-08.txt

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

        Title           : Requirements for Separation of IP Control and
                          Forwarding
        Author(s)       : H. Khosravi, T. Anderson
        Filename        : draft-ietf-forces-requirements-08.txt
        Pages           : 15
        Date            : 2003-2-10

(Continue reading)

Yang, Lily L | 13 Sep 2002 18:53

Picon

Re: I-D ACTION:draft-ietf-forces-framework-01.txt

Sridhar -- Sure. Here is my number at my office (503)264-8813. I have
meetings this morning. I should be around after 1:30 this afternoon.
Thanks,
Lily

-----Original Message-----
From: T. Sridhar [mailto:sridhar <at> futsoft.com]
Sent: Thursday, September 12, 2002 5:46 PM
To: FORCES <at> PEACH.EASE.LSOFT.COM
Subject: Re: I-D ACTION:draft-ietf-forces-framework-01.txt

Lily,

I have some minor comments/suggestions on the document - can I call you up
to discuss them?

Regards,
Sridhar

-----Original Message-----
From: Forwarding and Control Element Separation
[mailto:FORCES <at> peach.ease.lsoft.com]On Behalf Of Yang, Lily L
Sent: Wednesday, September 11, 2002 10:23 AM
To: FORCES <at> peach.ease.lsoft.com
Subject: FW: I-D ACTION:draft-ietf-forces-framework-01.txt

The changes occured in this revision of the ForCES framework document are
mostly minor except in Section 6 (Applicability to RFC1812). There are some
editorial revision throughout the document, and important correction to a
few cross reference errors.

(Continue reading)

Return

Return to gmane.ietf.forces.

Search Archive

Language

Change language

Options

Current view: Threads only / Showing only 20 lines / Not hiding cited text.
Change to All messages, whole messages, or hide cited text.

Post a message
NNTP Newsgroup
Classic Gmane web interface
XML

XML

RSS Feed
List Information

About Gmane