headers
Sebastian Kiesel | 6 Jul 2009 11:35
Picon
Favicon

fwd: New Version Notification for draft-kiesel-mmusic-firewall-sip-00

Hi,
just in case anyone still reading this list:

(announcement also sent to NSIS and MMUSIC lists)

The IETF has worked on several architectures and protocols for dynamic
control of firewalls, namely MIDCOM and NSIS. This draft examines how
they work together with SIP, especially if something goes wrong. The
conclusion is basically that the normal SIP mechanisms are not
sufficient to handle all error conditions in a reasonable way, and
therefore a new SIP precondition should be standardized.
This would be the turf of the mmusic WG, therefore comments should
go to the mmusic list.

Thanks,
Sebastian

----- Forwarded message from IETF I-D Submission Tool <idsubmission <at> ietf.org> -----

From: IETF I-D Submission Tool <idsubmission <at> ietf.org>
To: sebastian.kiesel <at> nw.neclab.eu
Subject: New Version Notification for draft-kiesel-mmusic-firewall-sip-00 
Date: Mon,  6 Jul 2009 01:26:17 -0700 (PDT)

A new version of I-D, draft-kiesel-mmusic-firewall-sip-00.txt has been successfuly submitted by
Sebastian Kiesel and posted to the IETF repository.

Filename:	 draft-kiesel-mmusic-firewall-sip
Revision:	 00
Title:		 Interaction of dynamic firewall control protocols and SIP
(Continue reading)

Permalink | Reply | 0 comments |
headers
The IESG | 1 Apr 2008 15:00
Picon
Favicon

WG Action: Conclusion of Middlebox Communication (midcom)

The Middlebox Communication working group (midcom) in the Transport Area
has concluded.

The IESG contact persons are Magnus Westerlund and Lars Eggert.

The mailing list will remain active.

The MIDCOM WG has completed its chartered tasks, which primarily
regards control of middlebox such as firewalls and NAT. The WG has
produced documents that:

- Describe the architecture and framework (RFC 3303)

- Evaluate existing IETF protocols for usage for
middlebox control (RFC 4097)

- Specify a middlebox communication protocol
(RFC 5189 and RFC 5190)

This concludes the WG with a big thanks to the WG chair and the authors
and WG participants. The mailing list will be kept open for some
additional time.

Magnus Westerlund
_______________________________________________
IETF-Announce mailing list
IETF-Announce <at> ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce
(Continue reading)

Permalink | Reply | 0 comments |
headers
Magnus Westerlund | 26 Mar 2008 13:51
Picon
Favicon

WG has finished its work

Hi,

I would like to thank the authors and the chair for their work in 
completing the chartered items. I will now close the WG, but keep the 
mailing list at least for some time.

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund <at> ericsson.com
----------------------------------------------------------------------
Permalink | Reply | 0 comments |
headers
rfc-editor | 25 Mar 2008 22:47
Favicon

RFC 5190 on Definitions of Managed Objects for Middlebox Communication


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

        
        RFC 5190

        Title:      Definitions of Managed Objects for 
                    Middlebox Communication 
        Author:     J. Quittek, M. Stiemerling, P. Srisuresh
        Status:     Standards Track
        Date:       March 2008
        Mailbox:    quittek <at> nw.neclab.eu, 
                    stiemerling <at> nw.neclab.eu, 
                    srisuresh <at> yahoo.com
        Pages:      92
        Characters: 204929
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-midcom-mib-11.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5190.txt

This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes a set of managed objects that allow
configuring middleboxes, such as firewalls and network address 
translators, in order to enable communication across these devices.  
The definitions of managed objects in this documents follow closely 
the MIDCOM semantics defined in RFC 5189.  [STANDARDS TRACK]
(Continue reading)

Permalink | Reply | 0 comments |
headers
rfc-editor | 25 Mar 2008 22:47
Favicon

RFC 5189 on Middlebox Communication (MIDCOM) Protocol Semantics


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

        
        RFC 5189

        Title:      Middlebox Communication (MIDCOM) Protocol Semantics 
        Author:     M. Stiemerling, J. Quittek, T. Taylor
        Status:     Standards Track
        Date:       March 2008
        Mailbox:    stiemerling <at> nw.neclab.eu, 
                    quittek <at> nw.neclab.eu, 
                    tom.taylor <at> rogers.com
        Pages:      70
        Characters: 161167
        Obsoletes:  RFC3989

        I-D Tag:    draft-ietf-midcom-rfc3989-bis-02.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5189.txt

This document specifies semantics for a Middlebox Communication (MIDCOM)
protocol to be used by MIDCOM agents for interacting with middleboxes 
such as firewalls and Network Address Translators (NATs).  The semantics discussion does not include any
specification of a concrete syntax or a transport protocol.  However, a concrete protocol is expected to
implement the specified semantics or, more likely, a superset of it.  The MIDCOM protocol semantics is
derived from the MIDCOM requirements, from the 
MIDCOM framework, and from working group decisions.  This document obsoletes RFC 3989.  [STANDARDS TRACK]

This document is a product of the Middlebox Communication Working Group
(Continue reading)

Permalink | Reply | 0 comments |
headers
Martin Stiemerling | 3 Mar 2008 10:47
Picon
Favicon

SIMCO open source implementation

Hi all,

Just to let you know: 

There is an open source implementation of SIMCO (RFC 4540) done by Univeristy of Stuttgart in Germany:

http://sourceforge.net/projects/simco-firewall/

  Martin

stiemerling <at> nw.neclab.eu   <== NEW ADDRESS

NEC Laboratories Europe - Network Research Division
NEC Europe Limited | Registered Office: NEC House, 1 Victoria Road, London W3 6BL | Registered in England
2832014
Permalink | Reply | 0 comments |
headers
The IESG | 8 Jan 2008 23:50
Picon
Favicon

Protocol Action: 'Middlebox Communications (MIDCOM) Protocol Semantics' to Proposed Standard

The IESG has approved the following document:

- 'Middlebox Communications (MIDCOM) Protocol Semantics '
   <draft-ietf-midcom-rfc3989-bis-02.txt> as a Proposed Standard

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

The IESG contact persons are Magnus Westerlund and Lars Eggert.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-midcom-rfc3989-bis-02.txt

Technical Summary

   This memo specifies semantics for a Middlebox Communication (MIDCOM)
   protocol to be used by MIDCOM agents for interacting with middleboxes
   such as firewalls and Network Address Translators (NATs).  The
   semantics discussion does not include any specification of a concrete
   syntax or a transport protocol. However the implementation of the 
   sematics in draft-ietf-midcom-mib does require the sematics 
   description as normative reference. Therefore the semantics 
   declaration is reclassified from informational to proposed standard.

Working Group Summary

   There is consensus in the WG to reclassify this document to proposed 
   standard to provide the necessary normative language for 
   draft-ietf-midcom-mib.
(Continue reading)

Permalink | Reply | 1 comment |
headers
The IESG | 8 Jan 2008 23:49
Picon
Favicon

Protocol Action: 'Definitions of Managed Objects for Middlebox Communication' to Proposed Standard

The IESG has approved the following document:

- 'Definitions of Managed Objects for Middlebox Communication '
   <draft-ietf-midcom-mib-11.txt> as a Proposed Standard

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

The IESG contact persons are Magnus Westerlund and Lars Eggert.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-midcom-mib-11.txt

Technical summary:

The midcom working group was chartered to develop a protocol to
send requests from network endpoints/application participants to
network devices, initially focusing on firewalls and NATs.  The
charter required that the working group reuse an existing IETF
protocol if possible, and the working group followed an evaluation
process described in RFC 4097.  The protocol that best met
the evaluation criteria was SNMPv2.

The document being submitted for publication is the definition of
a MIB to be used to communicate pinhole requests to a firewall and
NAT table mapping requests to a NAT.

Working group summary:

There is working group consensus that this document is ready to
(Continue reading)

Permalink | Reply | 0 comments |
headers
Internet-Drafts | 6 Dec 2007 22:00
Picon
Favicon

I-D Action:draft-ietf-midcom-mib-11.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Middlebox Communication Working Group of the IETF.

	Title           : Definitions of Managed Objects for Middlebox Communication
	Author(s)       : J. Quittek, et al.
	Filename        : draft-ietf-midcom-mib-11.txt
	Pages           : 90
	Date            : 2007-12-06

This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes a set of managed objects that allow
configuring middleboxes, such as firewalls and network address
translators, in order to enable communication across these devices.
The definitions of managed objects in this documents follow closely
the MIDCOM semantics defined in [I-D.ietf-midcom-rfc3989-bis].

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-midcom-mib-11.txt

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request <at> ietf.org with the word unsubscribe in the body of 
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

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-midcom-mib-11.txt".
(Continue reading)

Permalink | Reply | 2 comments |
headers
Internet-Drafts | 16 Nov 2007 14:20
Picon
Favicon

I-D Action:draft-ietf-midcom-mib-10.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Middlebox Communication Working Group of the IETF.

	Title           : Definitions of Managed Objects for Middlebox Communication
	Author(s)       : J. Quittek, et al.
	Filename        : draft-ietf-midcom-mib-10.txt
	Pages           : 91
	Date            : 2007-11-16

This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes a set of managed objects that allow
configuring middleboxes, such as firewalls and network address
translators, in order to enable communication across these devices.
The definitions of managed objects in this documents follow closely
the MIDCOM semantics defined in [I-D.ietf-midcom-rfc3989-bis].

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-midcom-mib-10.txt

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request <at> ietf.org with the word unsubscribe in the body of 
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

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-midcom-mib-10.txt".
(Continue reading)

Permalink | Reply | 0 comments |
headers
IETF I-D Submission Tool | 16 Nov 2007 14:15
Picon
Favicon

New Version Notification for draft-ietf-midcom-mib-10


A new version of I-D, draft-ietf-midcom-mib-10.txt has been successfuly submitted by Juergen Quittek
and posted to the IETF repository.

Filename:	 draft-ietf-midcom-mib
Revision:	 10
Title:		 Definitions of Managed Objects for Middlebox Communication
Creation_date:	 2007-11-16
WG ID:		 midcom
Number_of_pages: 91

Abstract:
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes a set of managed objects that allow
configuring middleboxes, such as firewalls and network address
translators, in order to enable communication across these devices.
The definitions of managed objects in this documents follow closely
the MIDCOM semantics defined in [I-D.ietf-midcom-rfc3989-bis].

The IETF Secretariat.
Permalink | Reply | 0 comments |

Gmane