From exim@www1.ietf.org  Mon Jan 12 13:45:37 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10484
	for <midcom-archive@odin.ietf.org>; Mon, 12 Jan 2004 13:45:37 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ag73k-00006K-HP
	for midcom-archive@odin.ietf.org; Mon, 12 Jan 2004 13:45:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0CIj8ub000368
	for midcom-archive@odin.ietf.org; Mon, 12 Jan 2004 13:45:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ag73e-000053-3l; Mon, 12 Jan 2004 13:45:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ag72h-0008Vw-FO
	for midcom@optimus.ietf.org; Mon, 12 Jan 2004 13:44:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10459
	for <midcom@ietf.org>; Mon, 12 Jan 2004 13:44:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag72f-0000Sy-00
	for midcom@ietf.org; Mon, 12 Jan 2004 13:44:01 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ag70o-0000QF-00
	for midcom@ietf.org; Mon, 12 Jan 2004 13:42:07 -0500
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ag6zn-0000NG-00
	for midcom@ietf.org; Mon, 12 Jan 2004 13:41:03 -0500
Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17])
	by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id i0CIeVGN014124
	for <midcom@ietf.org>; Mon, 12 Jan 2004 10:40:31 -0800 (PST)
Received: from cisco.com ([10.25.65.181])
	by mira-sjc5-c.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with SMTP id APU60707;
	Mon, 12 Jan 2004 10:40:30 -0800 (PST)
Date: Mon, 12 Jan 2004 13:40:27 -0500
Mime-Version: 1.0 (Apple Message framework v553)
Content-Type: text/plain; charset=US-ASCII; format=flowed
From: Melinda Shore <mshore@cisco.com>
To: midcom@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <CA876B18-452E-11D8-9AF0-000A95E35274@cisco.com>
X-Mailer: Apple Mail (2.553)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [midcom] Speak Freely killed because of NAT
Sender: midcom-admin@ietf.org
Errors-To: midcom-admin@ietf.org
X-BeenThere: midcom@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/midcom>,
	<mailto:midcom-request@ietf.org?subject=unsubscribe>
List-Id: <midcom.ietf.org>
List-Post: <mailto:midcom@ietf.org>
List-Help: <mailto:midcom-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/midcom>,
	<mailto:midcom-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Of interest to the working group, I think:

http://www.fourmilab.ch/speakfree/eol/

Melinda


_______________________________________________
midcom mailing list
midcom@ietf.org
https://www1.ietf.org/mailman/listinfo/midcom



From exim@www1.ietf.org  Fri Jan 23 10:24:46 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04937
	for <midcom-archive@odin.ietf.org>; Fri, 23 Jan 2004 10:24:46 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ak3AR-0007Zi-KS
	for midcom-archive@odin.ietf.org; Fri, 23 Jan 2004 10:24:19 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0NFOJaU029117
	for midcom-archive@odin.ietf.org; Fri, 23 Jan 2004 10:24:19 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ak3AA-0007Ra-Ef; Fri, 23 Jan 2004 10:24:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ak39O-0007Kr-I0
	for midcom@optimus.ietf.org; Fri, 23 Jan 2004 10:23:14 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04719;
	Fri, 23 Jan 2004 10:23:10 -0500 (EST)
Message-Id: <200401231523.KAA04719@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: midcom@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Fri, 23 Jan 2004 10:23:10 -0500
Subject: [midcom] I-D ACTION:draft-ietf-midcom-semantics-07.txt
Sender: midcom-admin@ietf.org
Errors-To: midcom-admin@ietf.org
X-BeenThere: midcom@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/midcom>,
	<mailto:midcom-request@ietf.org?subject=unsubscribe>
List-Id: <midcom.ietf.org>
List-Post: <mailto:midcom@ietf.org>
List-Help: <mailto:midcom-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/midcom>,
	<mailto:midcom-request@ietf.org?subject=subscribe>

--NextPart

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		: MIDCOM Protocol Semantics
	Author(s)	: M. Stiemerling
	Filename	: draft-ietf-midcom-semantics-07.txt
	Pages		: 67
	Date		: 2004-1-22
	
This memo specifies semantics for a Middlebox Communication (MIDCOM)
protocol to be used by MIDCOM agents for interacting with
middleboxes, such as firewalls and 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 probably - a superset of
it.  The MIDCOM protocol semantics is derived from the MIDCOM
requirements, from the MIDCOM framework, and from working group
decisions.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-midcom-semantics-07.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-midcom-semantics-07.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


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-midcom-semantics-07.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2004-1-23104720.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-midcom-semantics-07.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-midcom-semantics-07.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2004-1-23104720.I-D@ietf.org>

--OtherAccess--

--NextPart--



_______________________________________________
midcom mailing list
midcom@ietf.org
https://www1.ietf.org/mailman/listinfo/midcom



From exim@www1.ietf.org  Fri Jan 23 18:42:31 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03013
	for <midcom-archive@odin.ietf.org>; Fri, 23 Jan 2004 18:42:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AkAw9-0000GJ-7r
	for midcom-archive@odin.ietf.org; Fri, 23 Jan 2004 18:42:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0NNg5TG000997
	for midcom-archive@odin.ietf.org; Fri, 23 Jan 2004 18:42:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AkAw4-0000FF-R6; Fri, 23 Jan 2004 18:42:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AkA96-0008Oe-MC
	for midcom@optimus.ietf.org; Fri, 23 Jan 2004 17:51:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00160
	for <midcom@ietf.org>; Fri, 23 Jan 2004 17:51:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AkA93-0003oG-00
	for midcom@ietf.org; Fri, 23 Jan 2004 17:51:21 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AkA7w-0003mY-00
	for midcom@ietf.org; Fri, 23 Jan 2004 17:50:13 -0500
Received: from adsl-66-127-127-227.dsl.scrm01.pacbell.net ([66.127.127.227] helo=wes.hardakers.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AkA5t-0003kI-00
	for midcom@ietf.org; Fri, 23 Jan 2004 17:48:05 -0500
Received: by wes.hardakers.net (Postfix, from userid 274)
	id EA21611D82D; Fri, 23 Jan 2004 14:47:33 -0800 (PST)
To: midcom@ietf.org
From: Wes Hardaker <wes@hardakers.net>
Organization: Sparta
Date: Fri, 23 Jan 2004 14:47:32 -0800
Message-ID: <sdbroul1tn.fsf@wes.hardakers.net>
User-Agent: Gnus/5.1003 (Gnus v5.10.3) XEmacs/21.5 (celeriac, linux)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="=-=-="
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Subject: [midcom] [(nowhere)] I-D ACTION:draft-ietf-ipsp-spd-mib-00.txt
Sender: midcom-admin@ietf.org
Errors-To: midcom-admin@ietf.org
X-BeenThere: midcom@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/midcom>,
	<mailto:midcom-request@ietf.org?subject=unsubscribe>
List-Id: <midcom.ietf.org>
List-Post: <mailto:midcom@ietf.org>
List-Help: <mailto:midcom-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/midcom>,
	<mailto:midcom-request@ietf.org?subject=subscribe>

--=-=-=


This document is of interest to the MIDCOM working group since the
MIDCOM MIB might be based on this portion of the IPSP work.  Since the
WG wasn't forwarded this announcement, I'm doing so now:


--=-=-=
Content-Type: message/rfc822
Content-Disposition: inline

Received: via tmail-2002(14) (invoked by user hardaker) for
 hardaker+imap.ipsec.policy; Fri, 23 Jan 2004 13:32:36 -0800 (PST)
Return-Path: <owner-ipsec-policy@mail.vpnc.org>
Delivered-To: wes@hardakers.net
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by mail.hardakers.net (Postfix) with ESMTP id 1B4983820A
	for <wes@hardakers.net>; Fri, 23 Jan 2004 13:32:35 -0800 (PST)
Received: from above.proper.com (localhost [127.0.0.1])
	by above.proper.com (8.12.10/8.12.8) with ESMTP id i0NL1Aib018629;
	Fri, 23 Jan 2004 13:01:12 -0800 (PST)
	(envelope-from owner-ipsec-policy@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.10/8.12.9/Submit) id i0NL1Aaf018628;
	Fri, 23 Jan 2004 13:01:10 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to
 owner-ipsec-policy@mail.vpnc.org using -f
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by above.proper.com (8.12.10/8.12.8) with ESMTP id i0NL19ib018621
	for <ipsec-policy@vpnc.org>; Fri, 23 Jan 2004 13:01:09 -0800 (PST)
	(envelope-from dinaras@cnri.reston.va.us)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22363;
	Fri, 23 Jan 2004 16:01:08 -0500 (EST)
Message-Id: <200401232101.QAA22363@ietf.org>
To: IETF-Announce: ;
Cc: ipsec-policy@vpnc.org
From: Internet-Drafts@ietf.org
Reply-To: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-ipsp-spd-mib-00.txt
Date: Fri, 23 Jan 2004 16:01:07 -0500
Sender: owner-ipsec-policy@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ipsec-policy/mail-archive/>
List-ID: <ipsec-policy.vpnc.org>
List-Unsubscribe: <mailto:ipsec-policy-request@vpnc.org?body=unsubscribe>
X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on 
	dawn.hardakers.net
X-Spam-Status: No, hits=-4.2 required=5.0
 tests=BAYES_00,MIME_BOUND_NEXTPART,
	NO_REAL_NAME autolearn=no version=2.61
X-Spam-Level: 
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===-=-="

--===-=-=

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

	Title		: IPsec Security Policy Database Configuration MIB
	Author(s)	: W. Hardaker
	Filename	: draft-ietf-ipsp-spd-mib-00.txt
	Pages		: 66
	Date		: 2004-1-23
	
This document defines a SMIv2 Management Information Base (MIB)
module for configuring the security policy database of a device
implementing the IPSec protocol.  The policy-based packet filtering
and the corresponding execution of actions is of a more general
nature than for IPsec configuration only, such as for configuration
of a firewall.  This MIB module is designed with future extensibility
in mind.  It is thus possible to externally add other packet filters
and actions to the policy-based packet filtering system defined in
this document.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ipsp-spd-mib-00.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-ipsp-spd-mib-00.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


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-ipsp-spd-mib-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--===-=-=
Content-Type: multipart/alternative; boundary="====-=-="

--====-=-=
Content-Type: message/external-body; access-type=mail-server

Content-Type: text/plain
Content-ID:	<2004-1-23162104.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ipsp-spd-mib-00.txt

--====-=-=
Content-Type: message/external-body;
  name=draft-ietf-ipsp-spd-mib-00.txt; access-type=anon-ftp

Content-Type: text/plain
Content-ID:	<2004-1-23162104.I-D@ietf.org>

--====-=-=--

--===-=-=--

--=-=-=



-- 
Wes Hardaker
Sparta

--=-=-=--

_______________________________________________
midcom mailing list
midcom@ietf.org
https://www1.ietf.org/mailman/listinfo/midcom



From exim@www1.ietf.org  Sun Jan 25 13:44:37 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13568
	for <midcom-archive@odin.ietf.org>; Sun, 25 Jan 2004 13:44:37 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AkpEu-0003QX-PN
	for midcom-archive@odin.ietf.org; Sun, 25 Jan 2004 13:44:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0PIi8wX013170
	for midcom-archive@odin.ietf.org; Sun, 25 Jan 2004 13:44:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AkpEn-0003Px-Kk; Sun, 25 Jan 2004 13:44:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Akl1f-0003g8-44
	for midcom@optimus.ietf.org; Sun, 25 Jan 2004 09:14:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04395
	for <midcom@ietf.org>; Sun, 25 Jan 2004 09:14:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Akl1d-0007XA-00
	for midcom@ietf.org; Sun, 25 Jan 2004 09:14:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Akl0n-0007VM-00
	for midcom@ietf.org; Sun, 25 Jan 2004 09:13:18 -0500
Received: from tokyo.netlab.nec.de ([195.37.70.2] helo=tokyo.ccrle.nec.de)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Akl0E-0007Sx-00
	for midcom@ietf.org; Sun, 25 Jan 2004 09:12:42 -0500
Received: from venus.office (venus.office [10.1.1.11])
	by tokyo.ccrle.nec.de (8.12.10/8.12.9) with ESMTP id i0PECAkA002382
	for <midcom@ietf.org>; Sun, 25 Jan 2004 15:12:10 +0100 (CET)
Received: from yamato.ccrle.nec.de (jupiter.office [10.1.1.3])
	by venus.office (Postfix on SuSE Linux eMail Server 3.0) with SMTP id 4C355F8888
	for <midcom@ietf.org>; Sun, 25 Jan 2004 15:12:09 +0100 (CET)
Received: from 10.1.1.83
        (SquirrelMail authenticated user martin)
        by yamato.ccrle.nec.de with HTTP;
        Sun, 25 Jan 2004 15:12:09 +0100 (CET)
Message-ID: <1356.10.1.1.83.1075039929.squirrel@yamato.ccrle.nec.de>
Date: Sun, 25 Jan 2004 15:12:09 +0100 (CET)
Subject: [Fwd: [midcom] I-D ACTION:draft-ietf-midcom-semantics-07.txt]
From: "Martin Stiemerling" <stiemerling@netlab.nec.de>
To: midcom@ietf.org
Reply-To: stiemerling@netlab.nec.de
User-Agent: SquirrelMail/1.4.2
MIME-Version: 1.0
Content-Type: multipart/mixed;boundary="----=_20040125151209_84553"
X-Priority: 3
Importance: Normal
X-Scanned-By: MIMEDefang 2.35
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,PRIORITY_NO_NAME 
	autolearn=no version=2.60
Sender: midcom-admin@ietf.org
Errors-To: midcom-admin@ietf.org
X-BeenThere: midcom@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/midcom>,
	<mailto:midcom-request@ietf.org?subject=unsubscribe>
List-Id: <midcom.ietf.org>
List-Post: <mailto:midcom@ietf.org>
List-Help: <mailto:midcom-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/midcom>,
	<mailto:midcom-request@ietf.org?subject=subscribe>

------=_20040125151209_84553
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit

Hello,

the MIDCOM semantics I-D -06 have been reviewed by our AD  and only minor
changes have been remarked.

Here are the changes:

- Added section 7 about IESG considerations on UNSAF
- Added in section 2.3.8 a hint to PER transaction
- Added in section 2.3.13 a hint to REN message
- Fixed spelling in section 4.1. First sentence was "This examples
precludes" and is now
  "This example assumes"

Please note that the semantics I-D on the IETF draft repository seems to
be broken.  The document is at the IETF only 77kbytes long, but the
document is actually about 155kbytes.
The whole document can be downloaded here:

ftp://ftp.netlab.nec.de/pub/internet-drafts/draft-ietf-midcom-semantics-07.txt

Regards,

 Martin
---------------------------- Original Message ----------------------------
Subject: [midcom] I-D ACTION:draft-ietf-midcom-semantics-07.txt
From:    Internet-Drafts@ietf.org
Date:    Fri, January 23, 2004 4:23 pm
To:      IETF-Announce:;
Cc:      midcom@ietf.org
--------------------------------------------------------------------------

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		: MIDCOM Protocol Semantics
	Author(s)	: M. Stiemerling
	Filename	: draft-ietf-midcom-semantics-07.txt
	Pages		: 67
	Date		: 2004-1-22

This memo specifies semantics for a Middlebox Communication (MIDCOM)
protocol to be used by MIDCOM agents for interacting with
middleboxes, such as firewalls and 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 probably - a superset of it. 
The MIDCOM protocol semantics is derived from the MIDCOM
requirements, from the MIDCOM framework, and from working group
decisions.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-midcom-semantics-07.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-midcom-semantics-07.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


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-midcom-semantics-07.txt".

NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.


Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
Return-Path: <midcom-admin@ietf.org>
X-Sieve: cmu-sieve 2.0
Received: from tokyo.ccrle.nec.de (pluto.office [10.1.1.84])
	by venus.office (Postfix on SuSE Linux eMail Server 3.0) with ESMTP id
129E3FC62F; Fri, 23 Jan 2004 16:25:02 +0100 (CET)
Received: from optimus.ietf.org (optimus22.ietf.org [132.151.6.22])
	by tokyo.ccrle.nec.de (8.12.10/8.12.9) with ESMTP id i0NFP0kA069745; Fri,
23 Jan 2004 16:25:00 +0100 (CET)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ak3AA-0007RW-7Z; Fri, 23 Jan 2004 10:24:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ak39O-0007Kr-I0
	for midcom@optimus.ietf.org; Fri, 23 Jan 2004 10:23:14 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04719;
	Fri, 23 Jan 2004 10:23:10 -0500 (EST)
Message-Id: <200401231523.KAA04719@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: midcom@ietf.org
From: Internet-Drafts@ietf.org
Reply-To: Internet-Drafts@ietf.org
Date: Fri, 23 Jan 2004 10:23:10 -0500
Subject: [midcom] I-D ACTION:draft-ietf-midcom-semantics-07.txt
Sender: midcom-admin@ietf.org
Errors-To: midcom-admin@ietf.org
X-BeenThere: midcom@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/midcom>,
	<mailto:midcom-request@ietf.org?subject=unsubscribe>
List-Id: <midcom.ietf.org>
List-Post: <mailto:midcom@ietf.org>
List-Help: <mailto:midcom-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/midcom>,
	<mailto:midcom-request@ietf.org?subject=subscribe>
X-Scanned-By: MIMEDefang 2.35

--NextPart

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		: MIDCOM Protocol Semantics
	Author(s)	: M. Stiemerling
	Filename	: draft-ietf-midcom-semantics-07.txt
	Pages		: 67
	Date		: 2004-1-22

This memo specifies semantics for a Middlebox Communication (MIDCOM)
protocol to be used by MIDCOM agents for interacting with
middleboxes, such as firewalls and 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 probably - a superset of it. 
The MIDCOM protocol semantics is derived from the MIDCOM
requirements, from the MIDCOM framework, and from working group
decisions.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-midcom-semantics-07.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-midcom-semantics-07.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


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-midcom-semantics-07.txt".

NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.


Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2004-1-23104720.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-midcom-semantics-07.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-midcom-semantics-07.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2004-1-23104720.I-D@ietf.org>

--OtherAccess--

--NextPart--



_______________________________________________
midcom mailing list
midcom@ietf.org
https://www1.ietf.org/mailman/listinfo/midcom

------=_20040125151209_84553
Content-Type: message/external-body; name="untitled-2.1"
Content-Disposition: attachment; filename="untitled-2.1"
Content-Transfer-Encoding: 8bit

Content-Type: text/plain
Content-ID:	<2004-1-23104720.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-midcom-semantics-07.txt
------=_20040125151209_84553
Content-Type: message/external-body;
      name="draft-ietf-midcom-semantics-07.txt"
Content-Disposition: attachment;
      filename="draft-ietf-midcom-semantics-07.txt"
Content-Transfer-Encoding: 8bit

Content-Type: text/plain
Content-ID:	<2004-1-23104720.I-D@ietf.org>
------=_20040125151209_84553--


_______________________________________________
midcom mailing list
midcom@ietf.org
https://www1.ietf.org/mailman/listinfo/midcom



From exim@www1.ietf.org  Thu Jan 29 12:24:48 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02578
	for <midcom-archive@odin.ietf.org>; Thu, 29 Jan 2004 12:24:48 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AmFtp-0005Vo-6e
	for midcom-archive@odin.ietf.org; Thu, 29 Jan 2004 12:24:21 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0THOHWH021160
	for midcom-archive@odin.ietf.org; Thu, 29 Jan 2004 12:24:17 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AmFtl-0005S4-NG; Thu, 29 Jan 2004 12:24:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AmF3n-0002nS-VU
	for midcom@optimus.ietf.org; Thu, 29 Jan 2004 11:30:31 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29931
	for <midcom@ietf.org>; Thu, 29 Jan 2004 11:30:29 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmF3m-00057P-00
	for midcom@ietf.org; Thu, 29 Jan 2004 11:30:31 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AmF2u-0004yh-00
	for midcom@ietf.org; Thu, 29 Jan 2004 11:29:37 -0500
Received: from tokyo.netlab.nec.de ([195.37.70.2] helo=tokyo.ccrle.nec.de)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AmF2H-0004rA-00
	for midcom@ietf.org; Thu, 29 Jan 2004 11:28:57 -0500
Received: from venus.office (venus.office [10.1.1.11])
	by tokyo.ccrle.nec.de (8.12.10/8.12.9) with ESMTP id i0TGSQN8022955
	for <midcom@ietf.org>; Thu, 29 Jan 2004 17:28:26 +0100 (CET)
Received: from [10.1.1.109] (n-stiemerling.office [10.1.1.109])
	by venus.office (Postfix on SuSE Linux eMail Server 3.0) with ESMTP id 01CC5E0EFA
	for <midcom@ietf.org>; Thu, 29 Jan 2004 17:28:26 +0100 (CET)
Date: Thu, 29 Jan 2004 17:28:07 +0100
From: Martin Stiemerling <stiemerling@netlab.nec.de>
To: midcom@ietf.org
Message-ID: <2147483647.1075397287@[10.1.1.109]>
X-Mailer: Mulberry/3.1.0 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Scanned-By: MIMEDefang 2.35
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [midcom] New Internet Draft on SIMCO
Sender: midcom-admin@ietf.org
Errors-To: midcom-admin@ietf.org
X-BeenThere: midcom@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/midcom>,
	<mailto:midcom-request@ietf.org?subject=unsubscribe>
List-Id: <midcom.ietf.org>
List-Post: <mailto:midcom@ietf.org>
List-Help: <mailto:midcom-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/midcom>,
	<mailto:midcom-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi,

since the announcement of the new version of SIMCO has been
dropped somehow:

We have posted a new version of the SImple Middlebox Configuration
(SIMCO) protocol.  This version is now binary encoded and aligned
with the latest developments of the MIDCOM semantics.

You can find a copy here:

http://www.ietf.org/internet-drafts/draft-stiemerling-midcom-simco-04.txt


Abstract

This document describes a protocol for controlling middleboxes such
as firewalls and network address translators.  It is a fully
compliant implementation of the MIDCOM semantics described in
[RFCXXXX].  Compared to earlier experimental versions of the SIMCO
protocol, this version 3 uses binary message encodings in order to
reduce resource requirements.


Martin Stiemerling

NEC Europe Ltd. -- Network Laboratories Stiemerling@netlab.nec.de
PGP Key at:        http://www.stiemerling.org/stiemerling_nec.gpg
IPv4: http://www.ccrle.nec.de  IPv6: http://www.ipv6.ccrle.nec.de

_______________________________________________
midcom mailing list
midcom@ietf.org
https://www1.ietf.org/mailman/listinfo/midcom



From exim@www1.ietf.org  Fri Jan 30 12:11:31 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28805
	for <midcom-archive@odin.ietf.org>; Fri, 30 Jan 2004 12:11:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AmcAa-0003cK-A8
	for midcom-archive@odin.ietf.org; Fri, 30 Jan 2004 12:11:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0UHB4YL013894
	for midcom-archive@odin.ietf.org; Fri, 30 Jan 2004 12:11:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AmcAX-0003aw-Rm; Fri, 30 Jan 2004 12:11:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Amc9s-0003Yx-3p
	for midcom@optimus.ietf.org; Fri, 30 Jan 2004 12:10:20 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28707
	for <midcom@ietf.org>; Fri, 30 Jan 2004 12:10:16 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Amc9q-0001Ft-00
	for midcom@ietf.org; Fri, 30 Jan 2004 12:10:18 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Amc92-00019S-00
	for midcom@ietf.org; Fri, 30 Jan 2004 12:09:28 -0500
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Amc8i-0000zs-00
	for midcom@ietf.org; Fri, 30 Jan 2004 12:09:08 -0500
Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17])
	by sj-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id i0UH8a7U010456
	for <midcom@ietf.org>; Fri, 30 Jan 2004 09:08:36 -0800 (PST)
Received: from cisco.com ([10.25.65.182])
	by mira-sjc5-c.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with SMTP id AQL01214;
	Fri, 30 Jan 2004 06:30:31 -0800 (PST)
Date: Fri, 30 Jan 2004 09:30:27 -0500
Mime-Version: 1.0 (Apple Message framework v553)
Content-Type: text/plain; charset=US-ASCII; format=flowed
From: Melinda Shore <mshore@cisco.com>
To: midcom@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <D92269FA-5330-11D8-B46B-000A95E35274@cisco.com>
X-Mailer: Apple Mail (2.553)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [midcom] Korea meeting/update
Sender: midcom-admin@ietf.org
Errors-To: midcom-admin@ietf.org
X-BeenThere: midcom@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/midcom>,
	<mailto:midcom-request@ietf.org?subject=unsubscribe>
List-Id: <midcom.ietf.org>
List-Post: <mailto:midcom@ietf.org>
List-Help: <mailto:midcom-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/midcom>,
	<mailto:midcom-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

The MIB has been sent to the internet drafts repository and should be
posted here within the next few days.  It will be the main meeting
topic in Seoul.  Please let me know if there are other topics you
feel need to be covered.

On other fronts, publication of the protocol comparison document was
blocked on some problems with references.  Those have been resolved,
and I think we've satisfied the RFC editor.  The protocol semantics
document is in IESG review and looks to be in good shape.

Melinda


_______________________________________________
midcom mailing list
midcom@ietf.org
https://www1.ietf.org/mailman/listinfo/midcom



