FCP rough specs + description - v.016 - 2001-01-15 - Nils Ohlmeier , Ulrich Abend

updated by Jiri Kuthan

feedback provided by Jan Janak

priority 2 features are blue colored; they will be implemented in the second stage;

examples are attached

The protocol specification follows the SMTPi/HTTP/SIP request-response, textual, AVP protocol family. Letter capitalization does not matter. Unknown AVPs may be ignored by receivers. Multiple transactionsi may utilize a single transport channel (TCP connection).^MAll FCP-maintained rules are uniquely identified by packet-matching expressions (regardless if their elements are specified explicitly or by a default value).

FCP rough specs + description - v.015 - 11-28-00 - Nils Ohlmeier , Ulrich Abend

<FCP>::=

<Request>|<Response>

<Request>::=

        SET <RequestHeader> <PacketMatching Expression> [<SetOptions>] |
        RELEASE <RequestHeader> <PacketMatching Expression> |
        QUERY <RequestHeader> [<PacketMatching Expression>] |
        QUERYNAT <RequestHeader> IP=<value> PORT=<value>
                   [UPPERPORT=<value>] PROTO=<value> |
 

    
» login or register to post comments | read more
		

Internet Engineering Task Force                             Jiri Kuthan
Internet Draft                                                GMD Fokus
draft-kuthan-midcom-framework-00.txt                 Jonathan Rosenberg
November, 2000                                              dynamicsoft
Expires: May 2001


          Middlebox Communication: Framework and Requirements

Status of this Memo

   This document is an Internet-Draft and is in full conformance with
   all provisions of Section 10 of RFC2026 [1].

   Internet-Drafts are working documents of the Internet Engineering
 

    
» login or register to post comments | read more
		

Internet Engineering Task Force                              Jiri Kuthan
Internet Draft                                                 GMD Fokus
draft-kuthan-fcp-01.txt                               Jonathan Rosenberg
June, 2000                                                   dynamicsoft
Expires: December 2000

          Firewall Control Protocol Framework and Requirements

Status of this Memo

   This document is an Internet-Draft and is in full conformance with
   all provisions of Section 10 of RFC2026 [1].

   Internet-Drafts are working documents of the Internet Engineering
 

    
» login or register to post comments | read more
		

Network Working Group                                       P. Srisuresh
INTERNET-DRAFT                                          Jasmine Networks
Expires as of August 21, 2001                                  J. Kuthan
                                                               GMD Fokus
                                                            J. Rosenberg
                                                             Dynamicsoft
                                                          February, 2001


                 Middlebox Communication Architecture and framework
                   
 

    
» login or register to post comments | read more
		

FCP Presentation at IETF47

Middlebox Communication Framework and Requirements

20/12/00

Start presentation

Table of Contents

• Middlebox Communication Framework and Requirements
• Outline
• Background: ALGs
• Ultimately Secure Firewall
• Static Filtering Policy is not Enough
• Application-awareness to Deal with Dynamic Conditions
• Suggestion: Decomposition
• Missing Piece
• A MidCom Network
• Summary: We have ...
• Conclusions
• Information Resources

Author: Jiri Kuthan

Email: kuthan@fokus.gmd.de

Home Page: http://www.fokus.gmd.de/research/cc/glone/employees/jiri.kuthan/private/fcp/

Other information:

• Standardization efforts
  • List of related Internet Drafts
  • Aravox FCI (A Tiphon Submission) (Aravox also published a short paper on their firewall control.)
  • RFC 2979 on Firewall Requirements
• Internet Telephony ALGs
  • SIP Linux
    » login or register to post comments | read more

Short Description

It is hard to impossible for Internet telephony to traverse firwalls and NATs. This inhibits a considerable number of Internet users from using Internet telephony services. Firewall Communication Protocol (FCP) is being designed to attack this problem. It connects signaling servers such as SIP Proxies or H.323 gatekeepers with firewalls, NATs and possibly other intermediate network devices ("middleboxes"). This construct enables to introduce application patchwork dealing with problems caused by firewalls and NATs in a scalable, easy-to-maintain and efficient manner.