[Fwd: RFC 4097 on Middlebox Communications (MIDCOM) Protocol Evaluation]

This is a multi-part message in MIME format.
--------------010805030100080900040401
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

As you may have seen, the midcom protocol evaluation
document has just been published as RFC 4097.  Many
thanks to everybody who partipated by providing
evaluations of individual protocols or by reviewing
the document, and thanks especially to Mary Barnes
for editing a particularly difficult document.

Melinda


-------- Original Message --------
Subject: [midcom] RFC 4097 on Middlebox Communications (MIDCOM) 
Protocol	Evaluation
Date: Wed, 15 Jun 2005 17:08:09 -0700
From: [email protected]
To: [email protected]
CC: [email protected], [email protected]


A new Request for Comments is now available in online RFC libraries.


         RFC 4097

         Title:      Middlebox Communications (MIDCOM)
                     Protocol Evaluation
         Author(s):  M. Barnes, Ed.
         Status:     Informational
         Date:       June 2005
         Mailbox:    [email protected]
         Pages:      44
         Characters: 99303
         Updates/Obsoletes/SeeAlso:    None

         I-D Tag:    draft-ietf-midcom-protocol-eval-06.txt

         URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4097.txt


This document provides an evaluation of the applicability of SNMP
(Simple Network Management Protocol), RSIP (Realm Specific Internet
Protocol), Megaco, Diameter, and COPS (Common Open Policy Service) as
the MIDCOM (Middlebox Communications) protocol.  A summary of each of
the proposed protocols against the MIDCOM requirements and the MIDCOM
framework is provided.  Compliancy of each of the protocols against
each requirement is detailed.  A conclusion summarizes how each of the
protocols fares in the evaluation.

This document is a product of the Middlebox Communication Working
Group of the IETF.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to [email protected].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [email protected].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [email protected] with the message body
help: ways_to_get_rfcs.  For example:

         To: [email protected]
         Subject: getting rfcs

         help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[email protected].  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------------------------------------------------------------------
CONTENT ABOVE THIS LINE IS *NOT* FROM CISCO INFORMATION TECHNOLOGY
-------------------------------------------------------------------------
In order to maintain computing infrastructure integrity, Cisco Systems
Enterprise Messaging Services and InfoSec teams have set a mail policy
disallowing executable attachments in email.

This message contained an executable attachment type that is prohibited
by this policy. The attachment has been removed from this message and
copied to quarantine by our systems. It will be held in quarantine for
seven days in the event that the content needs to be retrieved.

Please be aware many viruses attempt to look like legitimate email or
notifications from anti-virus systems. We will clearly mark a seperation
between our notifications and the original email as follows:

   "CONTENT ABOVE THIS LINE IS *NOT* FROM CISCO INFORMATION TECHNOLOGY"

For further reference information about viruses and email antivirus
efforts within Cisco, please visit:

http://wwwin.cisco.com/it/ems/services/antiviral

If your concern isn't addressed by the information in this notification
or the above web page, you may open a support request:

http://wwwin.cisco.com/support/

Select "Messaging", "Email-Related", "Mail Routing"

Please include in the text of your case the following information:

* Full headers of the message. Documentation on displaying the full
headers is available at this URL:

http://wwwin.cisco.com/support/library/faqs/solution002471.html

* This unique quarantine identifier: j5G5cjT5012117

If the matter is urgent, you may follow up by calling one of the below
referenced numbers. Please make every effort to provide the above
requested information via the support web tool prior to calling as it
will greatly aid the resolution of your issue.

Americas:
1 408 526 8888

Asiapac
+61 2 8446 8888

EMEA
+31 20 485 4888

Japan
+81 3 5549 6888

US (Toll Free)
1| 800| 888| 8187| (ext.68888)

Thank you for your cooperation,

Enterprise Messaging Services
Cisco Systems, Inc


--------------010805030100080900040401
Content-Type: text/plain; x-mac-type="0"; x-mac-creator="0";
	name="file:///tmp/nsmail.asc"
Content-Disposition: inline;
 filename="file:///tmp/nsmail.asc"
Content-Transfer-Encoding: 7bit

_______________________________________________
midcom mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/midcom


--------------010805030100080900040401
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
midcom mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/midcom

--------------010805030100080900040401--