Internet-Drafts | 11 Sep 14:01 2002
Picon

I-D ACTION:draft-ietf-forces-framework-01.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           : ForCES Architectural Framework
        Author(s)       : L. Yang et al.
        Filename        : draft-ietf-forces-framework-01.txt
        Pages           : 23
        Date            : 2002-9-10

This document defines the architectural framework for ForCES network
elements (NE), and identifies the associated entities and the
interaction among them.  This framework is intended to satisfy the
requirements specified in the ForCES requirements draft [FORCES-
REQ].

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

To remove yourself from the IETF Announcement list, send a message to
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
        "get draft-ietf-forces-framework-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

(Continue reading)

Yang, Lily L | 11 Sep 19:23 2002
Picon

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.

The technical comments we got since last revision are mostly concerning
Section 6. There are questions like where ARP should be done (CE or FE),
where ICMP error messages are generated etc. To calrify on this, a general
guideline is added in this section (more specifically, in 6.2):
"...ARP support may be implemented in either CEs or FEs. As we will see
        later, a number of behaviors that RFC1812 mandates fall into this
        category -- they may be performed by the FE and may be performed by
        the CE. A general guideline is needed to ensure interoperability
        between separated control and forwarding planes. The guideline we
        offer here is that CEs are required to be capable of these
        operations while FEs may or may not choose to implement them. FE
        model should indicate its capabilities in this regard. "
Some clarification along this line is also made in section 6.3 regarding IP
options like source route, record route, time stamp, etc.
There was also a error in previous revision regarding forwarding tables in
multiple FEs. That was also corrected in this revision.

Once again, we would like to thank all the people that have provided
comments to us. We would like to ask you to take one more look at the
document, esp. Section 6 and provide feedback.

Thanks,
Lily

-----Original Message-----
(Continue reading)

T. Sridhar | 13 Sep 02:46 2002

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.

The technical comments we got since last revision are mostly concerning
Section 6. There are questions like where ARP should be done (CE or FE),
where ICMP error messages are generated etc. To calrify on this, a general
guideline is added in this section (more specifically, in 6.2):
"...ARP support may be implemented in either CEs or FEs. As we will see
        later, a number of behaviors that RFC1812 mandates fall into this
        category -- they may be performed by the FE and may be performed by
        the CE. A general guideline is needed to ensure interoperability
        between separated control and forwarding planes. The guideline we
        offer here is that CEs are required to be capable of these
(Continue reading)

Yang, Lily L | 13 Sep 18:53 2002
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)

Putzolu, David | 18 Sep 14:23 2002
Picon

Fwd: CFP for IEEE Network Magazine -- Special Issues on Network P rocessors: Architectures, Tools and Applications

Forwarded as relevant to list content.

-----Original Message-----

Our apologies if you receive multiple copies of this CFP.

CALL FOR PAPERS

IEEE Network Magazine Special Issue on

Network Processors: Architectures, Tools, and Applications

Guest Editors:

Raj Yavatkar                                                    Prof.
Harrick Vin
Intel Corporation                                               Department
of Computer Sciences
2111 NE 25th Avenue, JF3-462                           University of Texas
at Austin
Hillsboro, OR, 97124                                          Austin, TX
78712-1188
raj.yavatkar <at> intel.com
vin <at> cs.utexas.edu
Tel: (503) 264 9077                                            Tel: (512)
471-9732

Scope:

The rapid and pervasive evolution of the Internet has created an insatiable
(Continue reading)


Gmane