Middlebox Communication (midcom) Charter

来源：百度文库 编辑：神马文学网 时间：2024/04/28 15:42:53

Middlebox Communication (midcom)
Last Modified: 2006-03-24
Chair(s):
Melinda Shore
Transport Area Director(s):
Magnus Westerlund
Lars Eggert
Transport Area Advisor:
Magnus Westerlund
Mailing Lists:
General Discussion: midcom@ietf.org
To Subscribe:midcom-request@ietf.org
In Body: subscribe your_email_address
Archive:http://www.ietf.org/mail-archive/web/midcom/index.html
Description of Working Group:
As trusted third parties are increasingly being asked to make policy
decisions on behalf of the various entities participating in an
application‘s operation, a need has developed for applications to be
able to communicate their needs to the devices in the network that
provide transport policy enforcement. Examples of these devices
include firewalls, network address translators (both within and
between
address families), signature management for intrusion detection
systems, and multimedia buffer management. These devices are a subset
of what can be referred to as ‘middleboxes.‘
This working group will focus its attention on communication with
firewalls and network address translators (including translation
between IPv6 and IPv4). Work will not preclude extensibility to other
categories of middle box.
Decomposing applications requiring policy decisions by removing
application logic from the middle box and instead providing a
generalized communications interface provides a number of benefits,
including improved performance, lower software development and
maintenance costs, improved ability to support traversal of packet
filters by complex protocols, easier deployment of new applications,
and the ability to consolidate management functions. For example, by
moving stateful inspection of protocols such as H.323 and SIP out
of firewalls, it is possible to improve performance and scalability
and
reduce development and costs.
This working group will concern itself with an environment that
consists of:
- one or more middle boxes in the data path
- an external requesting entity
- a policy entity for consultation purposes when the
requesting entity is untrusted.
The requesting entity may be trusted or untrusted. In the case where
it
is trusted, the middle box will treat the request from the entity as
authoritative. In the case where it is not trusted, the intermediate
device will have to verify that it is authorized to complete the
request. That authorization could come from a separate or a built in
policy server.
The primary focus of the working group will be the application of this
architecture to communicating requests between applications and
firewalls or NATs. This will not preclude other uses, and care will be
taken to ensure that the protocol is extensible.
The working group will evaluate existing IETF protocols for their
applicability to this problem, using the framework and requirements
documents developed during the working group‘s first phase as criteria
for the evaluation. If a protocol is found to be suitable it will be
used as the basis for the development of a middlebox communication
protocol. In the unlikely case that one is not found to be suitable,
the working group will undertake development of a new protocol.
Discovery of middle boxes is out of scope.
The deliverables will be
o a document evaluating existing IETF protocols for their
suitability
o a document specifying a middlebox communication protocol
or profile based on the results of the protocol evaluation.
This working group will only deal with firewalls and network
address translators.
Ubiquitous deployment of midcom in all middleboxes could take many
years. In the interim, a solution is needed that allows applications
to
operate in the presence of midcom-unaware middleboxes. To support
this,
the midcom group will develop or document a protocol or approach that
allows clients to indirectly obtain address bindings from midcom-
unaware middleboxes, through communications with server elements on
the
public side of the middlebox. The key goals for this effort are rapid
delivery of a simple solution (since it is an interim solution),
consistency with the midcom framework, and security. In particular,
any
proposed interim approaches will address (and document) the
architectural and pragmatic concerns described in [UNSAF].
Goals and Milestones:
Done    submit Internet-Drafts of framework, architecture and interfaces documents to IESG for publication as Informational RFCs
Done    Submission of STUN document for standards-track publication
Done    Submission of pre-midcom document describing protocol for NAT traversal using relay for standards-track publication
Done    Submission of document evaluating existing IETF protocols against midcom framework and requirements for an Informational RFC.
Done    An analysis of the existing mibs and initial list of mibs (or portions of mibs) that need to be developed submitted to WG
Done    Semantics document submitted to IESG for publication as informational RFC
Done    Initial mibs ID submitted
Jun 2004    Mib documents submitted to IESG
Internet-Drafts:
Definitions of Managed Objects for Middlebox Communication (193394 bytes)
Request For Comments:
Middlebox Communications (MIDCOM) Protocol Requirements (RFC 3304) (16187 bytes)
Middlebox Communication Architecture and framework (RFC 3303) (91209 bytes)
STUN - Simple Traversal of UDP Through Network Address Translators (RFC 3489) (117562 bytes)
MIDCOM Protocol Semantics (RFC 3989) (160606 bytes)
Middlebox Communications (MIDCOM) Protocol Evaluation (RFC 4097) (99303 bytes)
IETF Secretariat - Please send questions, comments, and/or suggestions toietf-web@ietf.org.
Return to working group directory.
Return to IETF home page.
_xyz
Middlebox Communication (midcom) Charter communication Communication Models Knowledge, Competence And Communication 跨文化传播 INTERCULTURAL COMMUNICATION Rocci Luppicini, Department of Communication Communication Skills - making oral presentations communication with a Buddhism friend Cross-Cultural Communication In Global Integrating Grammar into Communication in English Teaching Windows Communication Foundation入门(Part One) ... Cross-Cultural Communication In Global Companies-论文 13 Tips for Effective Communication with Clie... Peer-to-Peer Communication Across Network Address Translators Communication on a serial port in NET 2.0 Windows Communication Foundation之旅（Part Four）... Seven tips for powering up your communication skills Some national and regional frameworks for integrating information and communication technology into school education Windows Workflow Foundation 与 Windows Communication Foundation 集成(转于MSDN) WCF之旅（3）：在WCF中实现双向通信（Bi-directional Communication） [转载]Flash　Communication　Server简易设定--闫老师博客-互相学... History of China's Tibetan Newspapers published //Research Institute on News Communication & Social Listing of Del.icio.us Tools, Plugins and Add-ons for Social Bookmarking ‘Change, Culture, Creativity, Communication’