From idwg-public-request@semper.org  Mon Jun 10 17:09:58 2002
Received: from www.opencard.org (www.opencard.org [195.212.119.145])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25778
	for <idwg-archive@odin.ietf.org>; Mon, 10 Jun 2002 17:09:56 -0400 (EDT)
Received: by www.opencard.org (Postfix, from userid 503)
	id C5C23344E2; Mon, 10 Jun 2002 23:11:12 +0200 (CEST)
Old-Return-Path: <rij@zurich.ibm.com>
Delivered-To: semper-idwg-public@opencard.org
Date: Mon, 10 Jun 2002 23:09:33 +0200 (CEST)
From: James Riordan <rij@zurich.ibm.com>
To: idwg-public@semper.org
Subject: [glenn@cysols.com: Re:Last Call: The Intrusion Detection Exchange
 Protocol (IDXP) to Proposed Standard] (fwd)
Message-Id: <Pine.LNX.4.44.0206102308570.1544-110000@elba.zurich.ibm.com>
Mime-Version: 1.0
Content-Type: MULTIPART/Mixed; BOUNDARY="R3G7APHDIzY6R/pk"
Content-Id: <Pine.LNX.4.44.0206102308571.1544@elba.zurich.ibm.com>
Content-Disposition: INLINE
Resent-Message-ID: <qm2K7.A.ZvB.wXRB9@www.opencard.org>
Resent-From: idwg-public@semper.org
X-Mailing-List: <idwg-public@semper.org> archive/latest/514
X-Loop: idwg-public@semper.org
Precedence: list
Resent-Sender: idwg-public-request@semper.org
Resent-Date: Mon, 10 Jun 2002 23:11:12 +0200 (CEST)

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--R3G7APHDIzY6R/pk
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.LNX.4.44.0206102308572.1544@elba.zurich.ibm.com>
Content-Disposition: INLINE


Forwarded to list.

As a reminder, please remember that a message only gets distributed if it
is posted from an account subscribed to the list (an anti-spam measure).  
Checking the archive is not a bad idea.

---------- Forwarded message ----------
Date: Mon, 10 Jun 2002 21:09:37 +0200 (CEST)
From: Jeffrey I. Schiller <jis@mit.edu>
To: idwg-public@zurich.ibm.com
Subject: [glenn@cysols.com: Re:Last Call: The Intrusion Detection Exchange
    Protocol (IDXP) to Proposed Standard]

I have not seen any response to these comments. Can someone please do
so. This is currently holding up the progress of this document
set. Thanks.

Note: I cannot find this message in the WG List archives, so perhaps
no one has seen it!

			-Jeff

--R3G7APHDIzY6R/pk
Content-Type: MESSAGE/RFC822; CHARSET=US-ASCII
Content-ID: <Pine.LNX.4.44.0206102308573.1544@elba.zurich.ibm.com>
Content-Description: 
Content-Disposition: INLINE

Return-Path: <iesg-admin@ietf.org>
Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76])
	by jis.mit.edu (8.9.2/8.9.3) with ESMTP id JAA27704
	for <jis@jis.mit.edu>; Sun, 21 Apr 2002 09:35:46 -0400 (EDT)
Received: from optimus.ietf.org (ietf.org [132.151.1.19])
	by fort-point-station.mit.edu (8.9.2/8.9.2) with ESMTP id JAA14825
	for <jis@mit.edu>; Sun, 21 Apr 2002 09:35:45 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA29431;
	Sun, 21 Apr 2002 09:35:42 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA28481
	for <iesg@optimus.ietf.org>; Sun, 21 Apr 2002 09:20:45 -0400 (EDT)
Received: from geto.cysol.co.jp (geto.cysol.co.jp [210.169.247.73])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA24550
	for <iesg@ietf.org>; Sun, 21 Apr 2002 09:20:41 -0400 (EDT)
Received: from cysols.com (naeba.cysol.co.jp [210.169.247.72])
	by geto.cysol.co.jp (8.11.3/3.7W) with ESMTP id g3LDK7U03358;
	Sun, 21 Apr 2002 22:20:07 +0900 (JST)
Message-ID: <3CC2BC7C.4090203@cysols.com>
Date: Sun, 21 Apr 2002 22:19:56 +0900
From: Glenn Mansfield Keeni <glenn@cysols.com>
Organization: Cyber Solutions Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:0.9.4.1) Gecko/20020314 Netscape6/6.2.2
X-Accept-Language: en-gb, en, ja
MIME-Version: 1.0
To: iesg@ietf.org
CC: idwg-public@zurich.ibm.com
Subject: Re:Last Call: The Intrusion Detection Exchange Protocol (IDXP) to 
	Proposed Standard
Content-Type: text/plain; charset=ISO-2022-JP
Sender: iesg-admin@ietf.org
Errors-To: iesg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id:  <iesg.ietf.org>
X-BeenThere: iesg@ietf.org
Content-Transfer-Encoding: 7bit

Hi,

Comments on  draft-ietf-idwg-beep-idxp-02 [These should have come
up during the WG-last call. I missed it - apologies for that.]


1.  Section 5 Page 20

=5. Fulfillment of IDWG Communications Protocol Requirements
=
=   The following lists the communications protocol requirements
=   established in Section 6 of [8] and, for each requirement, describes
=   the manner in which it is fulfilled by IDXP.

If reference [8]
=   [8]  Wood, M. and M. Erlinger, "Intrusion Detection Message Exchange
=        Requirements", RFC XXXX, Month YYYY.

points to draft-ietf-idwg-requirements-06.txt in the ietf repository
then  "Section 6 of [8]" should be "Section 5 of [8]". (Section 6 in
draft-ietf-idwg-requirements-06.txt is about "Message Content
Requirements ").

2.  Section 10.2 Page 31
    Same comment as in 1 above

3. In  draft-ietf-idwg-requirements-06.txt there are 4 sets of
requirements
     - General requirements (Section 3)
     - Message Format requirements (Section 4)
     - Communication Protocol requirements (Section 5)
     - Message Content requirements (Section 6)

In the present IDXP draft there is no mention about compliance to
the general requirements.
Are those requirements not applicable to the communications protocol?
The particular requirement that I have in mind is
=3.2
=
=   The IDMEF specification MUST take into account that IDMEF should be
=   able to operate in environments that contain IPv4 and IPv6
=   implementations.

In  section 8.1 (IDXP DTD) the attribute %IP may not be a dotted-quad
for IPv6 addresses.

4. Sec 5 Page 21
=  The [protocol] SHOULD be able to ensure non-repudiation of the
=  origin of IDMEF messages.
=
=      IDXP supports non-repudiation of message origin through the use
=      of an appropriate underlying BEEP security profile.  The TLS
=      profile is an example of a security profile that offers non-
=      repudiation of message origin through the authentication of

The above may be misleading. It is not clear how this will be done.
To my knowledge TLS does not guarantee non-repudiation of message
origin. (It can ensure non repudiation of TLS session origination
- but that does not ensure non-repudiation of message origin.). This
is probably a message content matter and thus beyond the communication
protocol.


5. It would be helpful to have some reference to the term "DTD"
(and, may be XML too) that appears in section 8 onwards.

6. Page 23 Section 6
The context of the terms "Option Identification:", "Contains:", etc.,
are not clear.
What are "NMTOKENS" ?
It would probably be better to have the registration template DTD in
this section/document.

7. Section 8 Page 28
Would be helpful if the semantics of the Data types used in the DTD's
were explained. Presently, for explanations one has to make do with
the comments/examples in the DTD itself.

8. The examples/enumerations are not clear too. E.g.
=         role       MSG               RPY      ERR
=         ====       ===               ===      ===
=         I or L     IDXP-Greeting     ok       error
=         C          IDMEF-Message     ok       error

What is "I", "L", "C" above ?

It is probably necessary to copy the following text from RFC3080 -
RFC3080 Page 61
:   o  When a BEEP session is established, the peer that awaits new
:      connections is acting in the listening role, and the other peer,
:      which establishes a connection to the listener, is acting in the
:     initiating role.  In the examples which follow, these are referred
:      to as "L:" and "I:", respectively.
:
:   o  A BEEP peer starting an exchange is termed the client; similarly,
:      the other BEEP peer is termed the server.  In the examples which
:      follow, these are referred to as "C:" and "S:", respectively.

9. Regarding tunnelling and communication across firewalls - I may
have missed the details - but how does the whole thing work? How
does one configure an analyzer to send a message to the manager
via the "proxy" ?
In  Page 6 Section 2.1
=  The following sequence shows how TUNNEL might be used to create an
=  application-layer tunnel through which IDXP would operate.  An ID
=  entity 'Alice' initiates the creation of a BEEP session using the
=  IDXP profile with the entity 'Bob' by first contacting 'proxy1'.  In
=  the greeting exchange between 'Alice' and 'proxy1', the TUNNEL
=  profile is selected, and subsequently the use of the TUNNEL profile
=  is extended to reach through 'proxy2' to 'Bob'.
How is the TUNNEL profile "extended" to reach proxy2 and then onto Bob,
I apologize for my ignorance ( I am sure that this has been discussed
in the WG-meetings I have missed ) but how does Alice know about proxy1
and how does proxy1 know about proxy2. Will it need to know all the
proxies if, there are any and, if IDXP is used ?


10. Page 12 Section 12.3.1
=  The "IDXP-Greeting" element serves to identify the analyzer or
=  manager at one end of the BEEP channel to the analyzer or manager at
=  the other end of the channel.  The "IDXP-Greeting" element MUST
=  include the role of the peer on the channel (client or server) and
=  the Uniform Resource Identifier (URI) [1] of the peer.  Additionally,
There are 2 peers - it is not very clear which one is being referred to
in the above. Maybe we should qualify with "originating-"peer and
"receiving-"peer.
And then in the same paragraph
=  qualified domain name (c.f., [5]) and IP address of the peer.  The IP
=  address chosen SHOULD correspond to the IP address associated with
=  the underlying transport protocol carrying the channel.
It is not clear what exactly is meant by the "IP address associated
with the underlying transport ... ".

11. Page 12 Section 3.4.1
=  For example, a successful creation with an embedded "IDXP-Greeting"
=  might look like this:

=  I: MSG 0 10 . 1592 187
=  I: Content-Type: text/xml

What do those "I:"s signify ?
 

Other minor editorial matters:

12. Page 5 Section 1.3
=  used in the context of BEEP [7].  In particular, Section 2.1 of the
=  BEEP framework memo discusses the roles that a BEEP peer may perform.

A pointer/reference for the "BEEP framework memo" will be helpful.


13. Page 6 Section 2.1
There is a definition of IDXP Peers in
=  Intrusion detection entities using IDXP to transfer data are termed
=  IDXP peers.
But then a paragraph later
=  An ID entity wishing to establish IDXP communications with another ID
=  entity does so by opening a BEEP channel, which may entail initiating
we have the description in terms of "ID entity".
In section 2.2 the text reverts to "peers". For the sake of uniformity
and clarity it would be better to stick to same terminology.

Comment that may not be specific to document:

I understand that some of the referenced documents are expected to
become RFCs in the the (near) future. But, having references to some
future form of the document which does not exist now is problematic
as one doesn't know which is the document that is being referred to.

Any comments from the RFC/I-D editor ?


Glenn





--R3G7APHDIzY6R/pk--



From idwg-public-request@semper.org  Wed Jun 12 00:27:57 2002
Received: from www.opencard.org (www.opencard.org [195.212.119.145])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA23806
	for <idwg-archive@odin.ietf.org>; Wed, 12 Jun 2002 00:27:56 -0400 (EDT)
Received: by www.opencard.org (Postfix, from userid 503)
	id 3A248344E2; Wed, 12 Jun 2002 06:29:10 +0200 (CEST)
Old-Return-Path: <mike@cs.hmc.edu>
Delivered-To: semper-idwg-public@opencard.org
Date: Tue, 11 Jun 2002 21:27:36 -0700
From: Mike Erlinger <mike@cs.hmc.edu>
To: intrusion detection wg <idwg-public@zurich.ibm.com>
Cc: Mike Erlinger <mike@cs.hmc.edu>,
        Stuart Staniford <stuart@SiliconDefense.com>
Subject: Comments on IDXP
Message-Id: <20020612042736.GA24540@cs.hmc.edu>
Reply-To: mike@cs.hmc.edu
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.27i
Resent-Message-ID: <S6vk0.A.whE.V4sB9@www.opencard.org>
Resent-From: idwg-public@semper.org
X-Mailing-List: <idwg-public@semper.org> archive/latest/515
X-Loop: idwg-public@semper.org
Precedence: list
Resent-Sender: idwg-public-request@semper.org
Resent-Date: Wed, 12 Jun 2002 06:29:10 +0200 (CEST)

Hi all 

A set of comments on idxp never made it to the mailing list, but did make it
to the IESG.  The IESG has been waiting for our response before proceeding,
we have been waiting for the IESG to act - oh well.  

If you have any comments, please send them to the list.  We would like to
resolve this asap.

thanks
mike



Here are the comments from Glenn:

Date: Sun, 21 Apr 2002 22:19:56 +0900
From: Glenn Mansfield Keeni <glenn@cysols.com>
Subject: Re:Last Call: The Intrusion Detection Exchange Protocol (IDXP) to
        Proposed Standard
To: iesg@ietf.org
CC: idwg-public@zurich.ibm.com


Hi,

Comments on  draft-ietf-idwg-beep-idxp-02 [These should have come
up during the WG-last call. I missed it - apologies for that.]


1.  Section 5 Page 20

=5. Fulfillment of IDWG Communications Protocol Requirements
=
=   The following lists the communications protocol requirements
=   established in Section 6 of [8] and, for each requirement, describes
=   the manner in which it is fulfilled by IDXP.

If reference [8]
=   [8]  Wood, M. and M. Erlinger, "Intrusion Detection Message Exchange
=        Requirements", RFC XXXX, Month YYYY.

points to draft-ietf-idwg-requirements-06.txt in the ietf repository
then  "Section 6 of [8]" should be "Section 5 of [8]". (Section 6 in
draft-ietf-idwg-requirements-06.txt is about "Message Content
Requirements ").

2.  Section 10.2 Page 31
    Same comment as in 1 above

3. In  draft-ietf-idwg-requirements-06.txt there are 4 sets of
requirements
     - General requirements (Section 3)
     - Message Format requirements (Section 4)
     - Communication Protocol requirements (Section 5)
     - Message Content requirements (Section 6)

In the present IDXP draft there is no mention about compliance to
the general requirements.
Are those requirements not applicable to the communications protocol?
The particular requirement that I have in mind is
=3.2
=
=   The IDMEF specification MUST take into account that IDMEF should be
=   able to operate in environments that contain IPv4 and IPv6
=   implementations.

In  section 8.1 (IDXP DTD) the attribute %IP may not be a dotted-quad
for IPv6 addresses.

4. Sec 5 Page 21
=  The [protocol] SHOULD be able to ensure non-repudiation of the
=  origin of IDMEF messages.
=
=      IDXP supports non-repudiation of message origin through the use
=      of an appropriate underlying BEEP security profile.  The TLS
=      profile is an example of a security profile that offers non-
=      repudiation of message origin through the authentication of

The above may be misleading. It is not clear how this will be done.
To my knowledge TLS does not guarantee non-repudiation of message
origin. (It can ensure non repudiation of TLS session origination
- but that does not ensure non-repudiation of message origin.). This
is probably a message content matter and thus beyond the communication
protocol.


5. It would be helpful to have some reference to the term "DTD"
(and, may be XML too) that appears in section 8 onwards.

6. Page 23 Section 6
The context of the terms "Option Identification:", "Contains:", etc.,
are not clear.
What are "NMTOKENS" ?
It would probably be better to have the registration template DTD in
this section/document.

7. Section 8 Page 28
Would be helpful if the semantics of the Data types used in the DTD's
were explained. Presently, for explanations one has to make do with
the comments/examples in the DTD itself.

8. The examples/enumerations are not clear too. E.g.
=         role       MSG               RPY      ERR
=         ====       ===               ===      ===
=         I or L     IDXP-Greeting     ok       error
=         C          IDMEF-Message     ok       error

What is "I", "L", "C" above ?

It is probably necessary to copy the following text from RFC3080 -
RFC3080 Page 61
:   o  When a BEEP session is established, the peer that awaits new
:      connections is acting in the listening role, and the other peer,
:      which establishes a connection to the listener, is acting in the
:     initiating role.  In the examples which follow, these are referred
:      to as "L:" and "I:", respectively.
:
:   o  A BEEP peer starting an exchange is termed the client; similarly,
:      the other BEEP peer is termed the server.  In the examples which
:      follow, these are referred to as "C:" and "S:", respectively.

9. Regarding tunnelling and communication across firewalls - I may
have missed the details - but how does the whole thing work? How
does one configure an analyzer to send a message to the manager
via the "proxy" ?
In  Page 6 Section 2.1
=  The following sequence shows how TUNNEL might be used to create an
=  application-layer tunnel through which IDXP would operate.  An ID
=  entity 'Alice' initiates the creation of a BEEP session using the
=  IDXP profile with the entity 'Bob' by first contacting 'proxy1'.  In
=  the greeting exchange between 'Alice' and 'proxy1', the TUNNEL
=  profile is selected, and subsequently the use of the TUNNEL profile
=  is extended to reach through 'proxy2' to 'Bob'.
How is the TUNNEL profile "extended" to reach proxy2 and then onto Bob,
I apologize for my ignorance ( I am sure that this has been discussed
in the WG-meetings I have missed ) but how does Alice know about proxy1
and how does proxy1 know about proxy2. Will it need to know all the
proxies if, there are any and, if IDXP is used ?


10. Page 12 Section 12.3.1
=  The "IDXP-Greeting" element serves to identify the analyzer or
=  manager at one end of the BEEP channel to the analyzer or manager at
=  the other end of the channel.  The "IDXP-Greeting" element MUST
=  include the role of the peer on the channel (client or server) and
=  the Uniform Resource Identifier (URI) [1] of the peer.  Additionally,
There are 2 peers - it is not very clear which one is being referred to
in the above. Maybe we should qualify with "originating-"peer and
"receiving-"peer.
And then in the same paragraph
=  qualified domain name (c.f., [5]) and IP address of the peer.  The IP
=  address chosen SHOULD correspond to the IP address associated with
=  the underlying transport protocol carrying the channel.
It is not clear what exactly is meant by the "IP address associated
with the underlying transport ... ".

11. Page 12 Section 3.4.1
=  For example, a successful creation with an embedded "IDXP-Greeting"
=  might look like this:

=  I: MSG 0 10 . 1592 187
=  I: Content-Type: text/xml

What do those "I:"s signify ?
 

Other minor editorial matters:

12. Page 5 Section 1.3
=  used in the context of BEEP [7].  In particular, Section 2.1 of the
=  BEEP framework memo discusses the roles that a BEEP peer may perform.

A pointer/reference for the "BEEP framework memo" will be helpful.


13. Page 6 Section 2.1
There is a definition of IDXP Peers in
=  Intrusion detection entities using IDXP to transfer data are termed
=  IDXP peers.
But then a paragraph later
=  An ID entity wishing to establish IDXP communications with another ID
=  entity does so by opening a BEEP channel, which may entail initiating
we have the description in terms of "ID entity".
In section 2.2 the text reverts to "peers". For the sake of uniformity
and clarity it would be better to stick to same terminology.

Comment that may not be specific to document:

I understand that some of the referenced documents are expected to
become RFCs in the the (near) future. But, having references to some
future form of the document which does not exist now is problematic
as one doesn't know which is the document that is being referred to.

Any comments from the RFC/I-D editor ?


Glenn







-- 
Mike Erlinger, Professor and Chair Computer Science
www:      http://www.cs.hmc.edu/~mike
email:    mike@cs.hmc.edu
smail:    Computer Science Dept., Harvey Mudd College,
          301 E. 12th Street, Claremont, CA, 91711 
          909-621-8912,   FAX: 909-607-8364



From idwg-public-request@semper.org  Wed Jun 12 12:35:18 2002
Received: from www.opencard.org (www.opencard.org [195.212.119.145])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04011
	for <idwg-archive@odin.ietf.org>; Wed, 12 Jun 2002 12:35:17 -0400 (EDT)
Received: by www.opencard.org (Postfix, from userid 503)
	id D929E344E3; Wed, 12 Jun 2002 18:36:26 +0200 (CEST)
Old-Return-Path: <dnew@san.rr.com>
Delivered-To: semper-idwg-public@opencard.org
Message-Id: <3D077850.50AAEC1D@san.rr.com>
Date: Wed, 12 Jun 2002 09:35:28 -0700
From: Darren New <dnew@san.rr.com>
Organization: Boxes!
X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U)
X-Accept-Language: en
Mime-Version: 1.0
To: intrusion detection wg <idwg-public@zurich.ibm.com>
Subject: Re: Comments on IDXP
References: <20020612042736.GA24540@cs.hmc.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <MvI02D.A.g9F.Ki3B9@www.opencard.org>
Resent-From: idwg-public@semper.org
X-Mailing-List: <idwg-public@semper.org> archive/latest/516
X-Loop: idwg-public@semper.org
Precedence: list
Resent-Sender: idwg-public-request@semper.org
Resent-Date: Wed, 12 Jun 2002 18:36:26 +0200 (CEST)
Content-Transfer-Encoding: 7bit

> 5. It would be helpful to have some reference to the term "DTD"
> (and, may be XML too) that appears in section 8 onwards.

A cite in the bibliography should suffice.

> What are "NMTOKENS" ?

It's a term defined by XML, as a list of NMTOKEN separated by whitespace.

> What is "I", "L", "C" above ?

These are terms from BEEP.

> 9. Regarding tunnelling and communication across firewalls - I may
> have missed the details - but how does the whole thing work?

This is described in the TUNNEL profile document.

> How
> does one configure an analyzer to send a message to the manager
> via the "proxy" ?

This would be implementation-specific. You provision the analyzer and
manager as required by the authors of that software.

> How is the TUNNEL profile "extended" to reach proxy2 and then onto Bob,
> I apologize for my ignorance ( I am sure that this has been discussed
> in the WG-meetings I have missed ) but how does Alice know about proxy1
> and how does proxy1 know about proxy2. Will it need to know all the
> proxies if, there are any and, if IDXP is used ?

They must be configured to know this. No automated mechanism for TUNNEL
proxy detection has been proposed.

> It is not clear what exactly is meant by the "IP address associated
> with the underlying transport ... ".

If a host has more than one IP address, the IP address it encodes into a
message sent on a particular TCP connection is the IP address in the TCP
headers of that connection, rather than some other IP address on the same
physical device.

> What do those "I:"s signify ?

The same thing they signify in the BEEP document.



-- 
Darren New 
San Diego, CA, USA (PST). Cryptokeys on demand.
** http://home.san.rr.com/dnew/DNResume.html **
** http://images.fbrtech.com/dnew/ **

     My brain needs a "back" button so I can
         remember where I left my coffee mug.



From idwg-public-request@semper.org  Thu Jun 13 01:45:54 2002
Received: from www.opencard.org (www.opencard.org [195.212.119.145])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23263
	for <idwg-archive@odin.ietf.org>; Thu, 13 Jun 2002 01:45:53 -0400 (EDT)
Received: by www.opencard.org (Postfix, from userid 503)
	id 814BD344DE; Thu, 13 Jun 2002 07:47:08 +0200 (CEST)
Old-Return-Path: <rij@zurich.ibm.com>
Delivered-To: semper-idwg-public@opencard.org
X-Received: from localhost (localhost.localdomain [127.0.0.1])
	by zurich.ibm.com (8.11.6/8.11.2) with ESMTP id g5D126B10436
	for <rij@localhost>; Thu, 13 Jun 2002 03:02:06 +0200
X-Received: from d12lmsgate-2.de.ibm.com (d12lmsgate-2.emea.ibm.com [9.165.215.10])
	by d12relay01.de.ibm.com (8.11.1m3/NCO/VER6.1) with ESMTP id g5D0wRr33536
	for <idwg-public@zurich.ibm.com>; Thu, 13 Jun 2002 02:58:27 +0200
X-Received: from usbosmx01.guardent.com (mail.guardent.com [208.9.212.220])
	by d12lmsgate-2.de.ibm.com (8.12.3/8.12.3) with ESMTP id g5D0wOUi015388
	for <idwg-public@zurich.ibm.com>; Thu, 13 Jun 2002 02:58:25 +0200
X-Received: by USBOSMX01 with Internet Mail Service (5.5.2653.19)
	id <MJCJ7KRM>; Wed, 12 Jun 2002 21:00:09 -0400
Message-Id: <397E0659AA2DD411843500508B64F1CE0431023F@USBOSMX01>
X-Afs-Authentication: NONE
From: Benjamin.Feinstein@guardent.com
To: glenn@cysols.com, iesg@ietf.org, idwg-public@zurich.ibm.com
Cc: jis@mit.edu, mrose@dbc.mtview.ca.us, gmatthew@nas.nasa.gov, jccw@mitre.org,
        dnew@san.rr.com, mike@cs.hmu.edu, stuart@silicondefense.com
Subject: IDXP comments
Old-Date: Wed, 12 Jun 2002 21:00:04 -0400
Importance: high
X-Priority: 1
Mime-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Old-X-Envelope-To: idwg-public
Date: Thu, 13 Jun 2002 03:00:48 +0200 (CEST)
Resent-Date: Thu, 13 Jun 2002 07:44:48 +0200 (CEST)
Resent-From: James Riordan <rij@zurich.ibm.com>
Resent-To: idwg-public@zurich.ibm.com
Resent-Subject: IDXP comments
Resent-Message-Id: <Pine.LNX.4.44.0206130744480.11219@elba.zurich.ibm.com>
X-Mailing-List: <idwg-public@semper.org> archive/latest/517
X-Loop: idwg-public@semper.org
Precedence: list
Resent-Sender: idwg-public-request@semper.org

 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hey ya'll,

What follows is my response to Glenn's comments on
draft-ietf-idwg-beep-idxp-04.  This response also includes some
material input from Darren New.

Sections from the IDXP draft are prefixed with an 'ID'.  Glenn's
comments are prefixed with an 'GMK'. My commends are prefixed with an
'BSF'.  Sections from RFC 3080 are prefixed with a 'BEEP'.

Another revision of IDXP, draft-ietf-idwg-beep-idxp-05 will be sent
out to this distribution list as soon as I can get xml2rfc to play
nicely.

Cheers,
Ben

- -------------------------

GMK  1.  Section 5 Page 20

ID  5. Fulfillment of IDWG Communications Protocol Requirements
ID
ID     The following lists the communications protocol requirements
ID     established in Section 6 of [8] and, for each requirement,
describes
ID     the manner in which it is fulfilled by IDXP.

GMK  If reference [8]
ID    [8]  Wood, M. and M. Erlinger, "Intrusion Detection Message
Exchange
ID         Requirements", RFC XXXX, Month YYYY.

GMK  points to draft-ietf-idwg-requirements-06.txt in the ietf
repository
GMK  then  "Section 6 of [8]" should be "Section 5 of [8]". (Section
6 in
GMK  draft-ietf-idwg-requirements-06.txt is about "Message Content
GMK  Requirements ").

BSF  Agreed.  Change made.

GMK  2.  Section 10.2 Page 31
GMK      Same comment as in 1 above

BSF  Agreed.  Change made.

GMK  3. In  draft-ietf-idwg-requirements-06.txt there are 4 sets of
GMK  requirements
GMK       - General requirements (Section 3)
GMK       - Message Format requirements (Section 4)
GMK       - Communication Protocol requirements (Section 5)
GMK       - Message Content requirements (Section 6)

GMK  In the present IDXP draft there is no mention about compliance
to
GMK  the general requirements.
GMK  Are those requirements not applicable to the communications
protocol?
GMK  The particular requirement that I have in mind is
ID  3.2
ID  
ID     The IDMEF specification MUST take into account that IDMEF
should be
ID     able to operate in environments that contain IPv4 and IPv6
ID     implementations.

GMK  In section 8.1 (IDXP DTD) the attribute %IP may not be a
dotted-quad
GMK  for IPv6 addresses.

BSF  I think you have a point here.  One option would be to allow
both IPv4 and
BSF  IPv6 style IP addresses within the optional %IP attribute. 
However, we
BSF  really shouldn't assume that the BEEP session underlying an IDXP
channel is
BSF  running over an IP-based transport (e.g., the RFC 3081 mapping
of BEEP onto
BSF  TCP).  To my knowledge, RFC 3080 does not contain any transport
requirement
BSF  for IP.  Therefore, I've removed any references to IP, and
hence, the %IP
BSF  attribute.

GMK  4. Sec 5 Page 21
ID    The [protocol] SHOULD be able to ensure non-repudiation of the
ID    origin of IDMEF messages.
ID  
ID        IDXP supports non-repudiation of message origin through the
use
ID        of an appropriate underlying BEEP security profile.  The
TLS
ID        profile is an example of a security profile that offers
non-
ID        repudiation of message origin through the authentication of

GMK  The above may be misleading. It is not clear how this will be
done.
GMK  To my knowledge TLS does not guarantee non-repudiation of
message
GMK  origin. (It can ensure non repudiation of TLS session
origination
GMK  - but that does not ensure non-repudiation of message origin.).
This
GMK  is probably a message content matter and thus beyond the
communication
GMK  protocol.

BSF  Point taken.  I've rewritten this section, hopefully more to
Glenn's liking.

GMK  5. It would be helpful to have some reference to the term "DTD"
GMK  (and, may be XML too) that appears in section 8 onwards.

BSF  A bibliographical reference to the W3C XML Recommendation has
been added
BSF  in Section 1.3 "Terminology".

GMK  6. Page 23 Section 6
GMK  The context of the terms "Option Identification:", "Contains:",
etc.,
GMK  are not clear.
GMK  What are "NMTOKENS" ?
GMK  It would probably be better to have the registration template
DTD in
GMK  this section/document.

BSF  NMTOKENS is defined in the W3C XML Recommendation.  We assume
BSF  familiarity with XML and the data types defined therein

GMK  7. Section 8 Page 28
GMK  Would be helpful if the semantics of the Data types used in the
DTD's
GMK  were explained. Presently, for explanations one has to make do
with
GMK  the comments/examples in the DTD itself.

BSF  The semantics of the IDXP Profile are described in Section 3.4
and formally
BSF  specified in the DTD in Section 8.1.  The semantics of the two
IDXP Options
BSF  are described in Section 4.1 and 4.2 and formally specified in
the DTDs in
BSF  Section 8.2 and Section 8.3.  I think this is enough
explanation.

GMK  8. The examples/enumerations are not clear too. E.g.
ID          role       MSG               RPY      ERR
ID          ====       ===               ===      ===
ID          I or L     IDXP-Greeting     ok       error
ID          C          IDMEF-Message     ok       error
GMK  What is "I", "L", "C" above ?
GMK  It is probably necessary to copy the following text from RFC3080
- -
GMK  RFC3080 Page 61
BEEP     o  When a BEEP session is established, the peer that awaits
new
BEEP        connections is acting in the listening role, and the
other peer,
BEEP        which establishes a connection to the listener, is acting
in the
BEEP       initiating role.  In the examples which follow, these are
referred
BEEP        to as "L:" and "I:", respectively.
BEEP  
BEEP     o  A BEEP peer starting an exchange is termed the client;
similarly,
BEEP        the other BEEP peer is termed the server.  In the
examples which
BEEP        follow, these are referred to as "C:" and "S:",
respectively.

BSF  I think a reference to RFC 3080 in Section 1.3 "Terminology"
should
BSF  suffice.  I've added an explicit mention of the "I", "L", "C",
"S"
BSF  shorthand used in RFC 3080 and IDXP.  We assume familiarity with
RFC
BSF  3080.

GMK  9. Regarding tunnelling and communication across firewalls - I
may
GMK  have missed the details - but how does the whole thing work? How
GMK  does one configure an analyzer to send a message to the manager
GMK  via the "proxy" ?
GMK  In  Page 6 Section 2.1
ID   The following sequence shows how TUNNEL might be used to create
an
ID   application-layer tunnel through which IDXP would operate.  An
ID
ID   entity 'Alice' initiates the creation of a BEEP session using
the
ID   IDXP profile with the entity 'Bob' by first contacting 'proxy1'.
 In
ID   the greeting exchange between 'Alice' and 'proxy1', the TUNNEL
ID   profile is selected, and subsequently the use of the TUNNEL
profile
ID   is extended to reach through 'proxy2' to 'Bob'.
GMK  How is the TUNNEL profile "extended" to reach proxy2 and then
onto Bob,
GMK  I apologize for my ignorance ( I am sure that this has been
discussed
GMK  in the WG-meetings I have missed ) but how does Alice know about
proxy1
GMK  and how does proxy1 know about proxy2. Will it need to know all
the
GMK  proxies if, there are any and, if IDXP is used ?

BSF  The IDXP and TUNNEL peers must be configured to understand how
to proxy.
BSF  There have been no methods for automated TUNNEL proxy discovery
proposed as of yet.

GMK  10. Page 12 Section 12.3.1
ID   The "IDXP-Greeting" element serves to identify the analyzer or
ID   manager at one end of the BEEP channel to the analyzer or
manager at
ID   the other end of the channel.  The "IDXP-Greeting" element MUST
ID   include the role of the peer on the channel (client or server)
and
ID   the Uniform Resource Identifier (URI) [1] of the peer. 
Additionally,
GMK  There are 2 peers - it is not very clear which one is being
referred to
GMK  in the above. Maybe we should qualify with "originating-"peer
and
GMK  "receiving-"peer.
GMK  And then in the same paragraph
ID   qualified domain name (c.f., [5]) and IP address of the peer. 
The IP
ID   address chosen SHOULD correspond to the IP address associated
with
ID   the underlying transport protocol carrying the channel.
GMK  It is not clear what exactly is meant by the "IP address
associated
GMK  with the underlying transport ... ".

BSF  I've removed any reference to IP or the %IP attribute, for the
reasons
BSF  stated above.

GMK  11. Page 12 Section 3.4.1
ID   For example, a successful creation with an embedded
"IDXP-Greeting"
ID   might look like this:

ID   I: MSG 0 10 . 1592 187
ID   I: Content-Type: text/xml

GMK  What do those "I:"s signify ?

BSF  See the new Section 1.3.  See comments above.

GMK  Other minor editorial matters:

GMK  12. Page 5 Section 1.3
ID   used in the context of BEEP [7].  In particular, Section 2.1 of
the
ID   BEEP framework memo discusses the roles that a BEEP peer may
perform.

GMK  A pointer/reference for the "BEEP framework memo" will be
helpful.

BSF  I've changed this to say just "BEEP".

GMK  13. Page 6 Section 2.1
GMK  There is a definition of IDXP Peers in
ID   Intrusion detection entities using IDXP to transfer data are
termed
ID   IDXP peers.
GMK  But then a paragraph later
ID   An ID entity wishing to establish IDXP communications with
another ID
ID   entity does so by opening a BEEP channel, which may entail
initiating
GMK  we have the description in terms of "ID entity".
GMK  In section 2.2 the text reverts to "peers". For the sake of
uniformity
GMK  and clarity it would be better to stick to same terminology.

BSF  All "entities" have been replaced with "peers".

GMK  Comment that may not be specific to document:

GMK  I understand that some of the referenced documents are expected
to
GMK  become RFCs in the the (near) future. But, having references to
some
GMK  future form of the document which does not exist now is
problematic
GMK  as one doesn't know which is the document that is being referred
to.
BSF  I modified the references to contain placeholders for 

GMK  Any comments from the RFC/I-D editor ?

GMK  Glenn

-----BEGIN PGP SIGNATURE-----
Version: PGP 7.0.4

iQA/AwUBPQfvfvt7bOk+HH2bEQKA5gCg+apRDSceWSB78JDllQ7xOiv77w8AoKmy
X1BSWP4IwpuBCuz8OtoN1Vsj
=kCcg
-----END PGP SIGNATURE-----




From idwg-public-request@semper.org  Fri Jun 14 14:29:39 2002
Received: from www.opencard.org (www.opencard.org [195.212.119.145])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09508
	for <idwg-archive@odin.ietf.org>; Fri, 14 Jun 2002 14:29:38 -0400 (EDT)
Received: by www.opencard.org (Postfix, from userid 503)
	id D6549344DE; Fri, 14 Jun 2002 20:30:53 +0200 (CEST)
Old-Return-Path: <rij@zurich.ibm.com>
Delivered-To: semper-idwg-public@opencard.org
X-Received: from internet-fence.zurich.ihost.com (internet-fence.zurich.ihost.com [195.212.119.225])
	by www.opencard.org (Postfix) with ESMTP id 0CB38344DE
	for <idwg-public@semper.org>; Fri, 14 Jun 2002 19:51:56 +0200 (CEST)
X-Received: from guh.nu (prophecy.ece.utexas.edu [128.83.51.56]) by internet-fence.zurich.ihost.com (AIX4.3/8.9.3/8.8.8) with ESMTP id TAA07340 for <idwg-public@semper.org>; Fri, 14 Jun 2002 19:50:36 +0200
X-Received: (from drew@localhost)
	by guh.nu (8.11.6/8.11.6) id g5EHvrh05954
	for idwg-public@semper.org; Fri, 14 Jun 2002 12:57:53 -0500
Old-Date: Fri, 14 Jun 2002 12:57:53 -0500
X-Afs-Authentication: NONE
From: "Andrew Hintz (Drew)" <mail.drew@overt.org>
To: idwg-public@semper.org
Subject: IDMEF Implementations besides Snort?
Message-Id: <20020614125753.G5171@guh.nu>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.2.5i
Old-X-Envelope-To: idwg-public
Date: Fri, 14 Jun 2002 19:51:56 +0200 (CEST)
Resent-Date: Fri, 14 Jun 2002 20:29:00 +0200 (CEST)
Resent-From: James Riordan <rij@zurich.ibm.com>
Resent-To: idwg-public@semper.org
Resent-Subject: IDMEF Implementations besides Snort?
Resent-Message-Id: <Pine.LNX.4.44.0206142029000.18134@elba.zurich.ibm.com>
X-Mailing-List: <idwg-public@semper.org> archive/latest/518
X-Loop: idwg-public@semper.org
Precedence: list
Resent-Sender: idwg-public-request@semper.org
Content-Transfer-Encoding: 8bit

Does anyone know of any IDMEF output plugins/converters for existing
IDSs or loggers, such as RealSecure, NFR, syslog, MS event log, etc?
The only one that I'm aware of is the Silicon Defense IDMEF output
plugin for Snort.

Thanks in advance,
-- 
^Drew

http://guh.nu

--Begin PGP Fingerprint--
3C6C F712 0A52 BD33 C518  5798 9014 CA99 2DA0 5E78
--End PGP Fingerprint--




From idwg-public-request@semper.org  Fri Jun 14 18:36:36 2002
Received: from www.opencard.org (www.opencard.org [195.212.119.145])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA18408
	for <idwg-archive@odin.ietf.org>; Fri, 14 Jun 2002 18:36:35 -0400 (EDT)
Received: by www.opencard.org (Postfix, from userid 503)
	id 38FBC344E2; Sat, 15 Jun 2002 00:37:57 +0200 (CEST)
Old-Return-Path: <ltinnel@teknowledge.com>
Delivered-To: semper-idwg-public@opencard.org
Message-Id: <5.1.0.14.2.20020614183827.029af0f8@192.168.100.10>
X-Sender: ltinnel@192.168.100.10
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Fri, 14 Jun 2002 18:41:22 -0400
To: "Andrew Hintz (Drew)" <mail.drew@overt.org>
From: "Laura S. Tinnel" <ltinnel@teknowledge.com>
Subject: Re: IDMEF Implementations besides Snort?
Cc: idwg-public@semper.org
In-Reply-To: <20020614125753.G5171@guh.nu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Resent-Message-ID: <q-J34B.A.k1C.EBnC9@www.opencard.org>
Resent-From: idwg-public@semper.org
X-Mailing-List: <idwg-public@semper.org> archive/latest/519
X-Loop: idwg-public@semper.org
Precedence: list
Resent-Sender: idwg-public-request@semper.org
Resent-Date: Sat, 15 Jun 2002 00:37:57 +0200 (CEST)

Drew,

We have existing ones for Tripwire (Windows version), ZoneAlarm Pro, and 
the IPTables firewall (alerts on policy violations as defined in the rules 
file.) We have one partially working for the freeware Tripwire for Linux.

-Laura

At 01:51 PM 6/14/2002, Andrew Hintz (Drew) wrote:
>Does anyone know of any IDMEF output plugins/converters for existing
>IDSs or loggers, such as RealSecure, NFR, syslog, MS event log, etc?
>The only one that I'm aware of is the Silicon Defense IDMEF output
>plugin for Snort.
>
>Thanks in advance,
>--
>^Drew
>
>http://guh.nu
>
>--Begin PGP Fingerprint--
>3C6C F712 0A52 BD33 C518  5798 9014 CA99 2DA0 5E78
>--End PGP Fingerprint--




From idwg-public-request@semper.org  Fri Jun 14 18:38:09 2002
Received: from www.opencard.org (www.opencard.org [195.212.119.145])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA18453
	for <idwg-archive@odin.ietf.org>; Fri, 14 Jun 2002 18:38:08 -0400 (EDT)
Received: by www.opencard.org (Postfix, from userid 503)
	id 8FB1D344E1; Sat, 15 Jun 2002 00:39:31 +0200 (CEST)
Old-Return-Path: <oudot.laurent@wanadoo.fr>
Delivered-To: semper-idwg-public@opencard.org
Message-ID: <3D0A6FDC.DAFF9F1A@wanadoo.fr>
Date: Sat, 15 Jun 2002 00:36:12 +0200
From: Oudot Laurent <oudot.laurent@wanadoo.fr>
X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Andrew Hintz (Drew)" <mail.drew@overt.org>
Cc: idwg-public@semper.org,
        "prelude-user@prelude-ids.org" <prelude-user@prelude-ids.org>
Subject: Re: IDMEF Implementations besides Snort?
References: <20020614125753.G5171@guh.nu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <2reRVB.A.n9C.jCnC9@www.opencard.org>
Resent-From: idwg-public@semper.org
X-Mailing-List: <idwg-public@semper.org> archive/latest/520
X-Loop: idwg-public@semper.org
Precedence: list
Resent-Sender: idwg-public-request@semper.org
Resent-Date: Sat, 15 Jun 2002 00:39:31 +0200 (CEST)
Content-Transfer-Encoding: 7bit


Hi,

You should reach http://www.prelude-ids.org which is the site of a GNU
IDS project.
This IDS is hybrid (host & network based) and can be distributed easily
all around a big network.
Prelude is very fast and it's difficult to evade from it (whereas many
others IDS are easy to bypass...).
The output is fully IDMEF v6 compliant and is stocked in databases.
You can read thoses databases by using a web frontend that uses IDMEF
tags to show the alerts.

bye,

laurent oudot


"Andrew Hintz (Drew)" wrote:

> Does anyone know of any IDMEF output plugins/converters for existing
> IDSs or loggers, such as RealSecure, NFR, syslog, MS event log, etc?
> The only one that I'm aware of is the Silicon Defense IDMEF output
> plugin for Snort.
>
> Thanks in advance,
> --
> ^Drew
>
> http://guh.nu
>
> --Begin PGP Fingerprint--
> 3C6C F712 0A52 BD33 C518  5798 9014 CA99 2DA0 5E78
> --End PGP Fingerprint--



From idwg-public-request@semper.org  Mon Jun 17 15:15:26 2002
Received: from www.opencard.org (www.opencard.org [195.212.119.145])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17002
	for <idwg-archive@odin.ietf.org>; Mon, 17 Jun 2002 15:15:05 -0400 (EDT)
Received: by www.opencard.org (Postfix, from userid 503)
	id 0B385344DE; Mon, 17 Jun 2002 21:13:20 +0200 (CEST)
Old-Return-Path: <Benjamin.Feinstein@guardent.com>
Delivered-To: semper-idwg-public@opencard.org
Message-Id: <397E0659AA2DD411843500508B64F1CE04310253@USBOSMX01>
From: Benjamin.Feinstein@guardent.com
To: iesg@ietf.org, idwg-public@zurich.ibm.com
Cc: glenn@cysols.com, jis@mit.edu, mrose@dbc.mtview.ca.us,
        gmatthew@nas.nasa.gov, jccw@mitre.org, dnew@san.rr.com,
        mike@cs.hmc.edu, stuart@silicondefense.com
Subject: draft-ietf-idwg-beep-idxp-05
Date: Mon, 17 Jun 2002 15:11:52 -0400
Importance: high
X-Priority: 1
Mime-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_000_01C21632.D6E39490"
Resent-Message-ID: <6YpQ7.A.jAB.PTjD9@www.opencard.org>
Resent-From: idwg-public@semper.org
X-Mailing-List: <idwg-public@semper.org> archive/latest/521
X-Loop: idwg-public@semper.org
Precedence: list
Resent-Sender: idwg-public-request@semper.org
Resent-Date: Mon, 17 Jun 2002 21:13:20 +0200 (CEST)

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_000_01C21632.D6E39490
Content-Type: text/plain;
	charset="iso-8859-1"

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Here it is, fresh off the xml2rfc press...

   
Ben Feinstein
  Software Development Engineer, R & D
  W: 678.585.7865 x6726 F: 770.645.8311 M: 678.772.4126
  8302 Dunwoody Pl., Suite 320, Atlanta, GA 30350 www.guardent.com
_____________________________________________________
G U A R D E N T
  Enterprise Security and Privacy Programs


-----BEGIN PGP SIGNATURE-----
Version: PGP 7.0.4

iQA/AwUBPQ41bft7bOk+HH2bEQImYgCggAMYNA8OvTl+xCI0V5mX/x38x5QAnAxg
+Gh1GIagALV0lknJdgP1b+Fc
=4v6j
-----END PGP SIGNATURE-----



------_=_NextPart_000_01C21632.D6E39490
Content-Type: application/octet-stream;
	name="draft-ietf-idwg-beep-idxp-05.nr"
Content-Disposition: attachment;
	filename="draft-ietf-idwg-beep-idxp-05.nr"
Content-Transfer-Encoding: quoted-printable

=0A=
.\" automatically generated by xml2rfc v1.13 on 17 Jun 2002 18:49:02 =
+0000=0A=
.\" =0A=
.pl 10.0i=0A=
.po 0=0A=
.ll 7.2i=0A=
.lt 7.2i=0A=
.nr LL 7.2i=0A=
.nr LT 7.2i=0A=
.ds LF Feinstein, et al.=0A=
.ds RF FORMFEED[Page %]=0A=
.ds CF Expires December 16, 2002=0A=
.ds LH Internet-Draft=0A=
.ds RH June 2002=0A=
.ds CH The IDXP=0A=
.hy 0=0A=
.ad l=0A=
.nf=0A=
Intrusion Detection Exchange                                B. =
Feinstein=0A=
Format                                                    Guardent, =
Inc.=0A=
Internet-Draft                                               G. =
Matthews=0A=
Expires: December 16, 2002                 CSC/NASA Ames Research =
Center=0A=
                                                                J. =
White=0A=
                                                       MITRE =
Corporation=0A=
                                                           June 17, =
2002=0A=
=0A=
=0A=
.ce=0A=
The Intrusion Detection Exchange Protocol (IDXP)=0A=
.ce=0A=
draft-ietf-idwg-beep-idxp-05=0A=
=0A=
.in 3=0A=
.ti 0=0A=
Status of this Memo=0A=
=0A=
.fi=0A=
This document is an Internet-Draft and is in full conformance with=0A=
all provisions of Section 10 of RFC2026.=0A=
=0A=
Internet-Drafts are working documents of the Internet Engineering=0A=
Task Force (IETF), its areas, and its working groups.  Note that=0A=
other groups may also distribute working documents as Internet-=0A=
Drafts.=0A=
=0A=
Internet-Drafts are draft documents valid for a maximum of six =
months=0A=
and may be updated, replaced, or obsoleted by other documents at any=0A=
time.  It is inappropriate to use Internet-Drafts as reference=0A=
material or to cite them other than as "work in progress."=0A=
=0A=
The list of current Internet-Drafts can be accessed at http://=0A=
www.ietf.org/ietf/1id-abstracts.txt.=0A=
=0A=
The list of Internet-Draft Shadow Directories can be accessed at=0A=
http://www.ietf.org/shadow.html.=0A=
=0A=
This Internet-Draft will expire on December 16, 2002.=0A=
=0A=
.ti 0=0A=
Copyright Notice=0A=
=0A=
Copyright (C) The Internet Society (2002).  All Rights Reserved.=0A=
=0A=
.ti 0=0A=
Abstract=0A=
=0A=
This memo describes the Intrusion Detection Exchange Protocol =
(IDXP),=0A=
an application-level protocol for exchanging data between intrusion=0A=
detection entities.  IDXP supports mutual-authentication, integrity,=0A=
and confidentiality over a connection-oriented protocol.  The=0A=
protocol provides for the exchange of IDMEF messages, unstructured=0A=
text, and binary data.  The IDMEF message elements are described in=0A=
.bp=0A=
the Intrusion Detection Message Exchange Format (IDMEF)[4], a=0A=
companion document of the Intrusion Detection Exchange Format (IDWG)=0A=
working group of the IETF.=0A=
=0A=
.ti 0=0A=
Table of Contents=0A=
=0A=
.nf=0A=
1.    Introduction . . . . . . . . . . . . . . . . . . . . . . . .  =
4=0A=
1.1   Purpose  . . . . . . . . . . . . . . . . . . . . . . . . . .  =
4=0A=
1.2   Profiles . . . . . . . . . . . . . . . . . . . . . . . . . .  =
4=0A=
1.3   Terminology  . . . . . . . . . . . . . . . . . . . . . . . .  =
4=0A=
=0A=
2.    The Model  . . . . . . . . . . . . . . . . . . . . . . . . .  =
6=0A=
2.1   Connection Provisioning  . . . . . . . . . . . . . . . . . .  =
6=0A=
2.2   Data Transfer  . . . . . . . . . . . . . . . . . . . . . . .  =
8=0A=
2.3   Connection Teardown  . . . . . . . . . . . . . . . . . . . .  =
9=0A=
2.4   Trust Model  . . . . . . . . . . . . . . . . . . . . . . . .  =
9=0A=
=0A=
3.    The IDXP Profile . . . . . . . . . . . . . . . . . . . . . . =
11=0A=
3.1   IDXP Profile Overview  . . . . . . . . . . . . . . . . . . . =
11=0A=
3.2   IDXP Profile Identification and Initialization . . . . . . . =
11=0A=
3.3   IDXP Profile Message Syntax  . . . . . . . . . . . . . . . . =
12=0A=
3.4   IDXP Profile Semantics . . . . . . . . . . . . . . . . . . . =
12=0A=
3.4.1 The IDXP-GREETING Element  . . . . . . . . . . . . . . . . . =
12=0A=
3.4.2 The OPTION Element . . . . . . . . . . . . . . . . . . . . . =
14=0A=
3.4.3 The IDMEF-MESSAGE Element  . . . . . . . . . . . . . . . . . =
14=0A=
=0A=
4.    IDXP Options . . . . . . . . . . . . . . . . . . . . . . . . =
15=0A=
4.1   The channelPriority Option . . . . . . . . . . . . . . . . . =
16=0A=
4.2   The streamType Option  . . . . . . . . . . . . . . . . . . . =
17=0A=
=0A=
5.    Fulfillment of IDWG Communications Protocol Requirements . . =
20=0A=
=0A=
6.    IDXP Option Registration Template  . . . . . . . . . . . . . =
23=0A=
=0A=
7.    Initial Registrations  . . . . . . . . . . . . . . . . . . . =
24=0A=
7.1   Registration: The IDXP Profile . . . . . . . . . . . . . . . =
24=0A=
7.2   Registration: The System (Well-Known) TCP port number for      =
=0A=
         IDXP . . . . . . . . . . . . . . . . . . . . . . . . . . . . =
24=0A=
7.3   Registration: The channelPriority Option . . . . . . . . . . =
24=0A=
7.4   Registration: The streamType Option  . . . . . . . . . . . . =
25=0A=
=0A=
8.    The DTDs . . . . . . . . . . . . . . . . . . . . . . . . . . =
26=0A=
8.1   The IDXP DTD . . . . . . . . . . . . . . . . . . . . . . . . =
26=0A=
8.2   The channelPriority Option DTD . . . . . . . . . . . . . . . =
27=0A=
8.3   The streamType DTD . . . . . . . . . . . . . . . . . . . . . =
28=0A=
=0A=
9.    Reply Codes  . . . . . . . . . . . . . . . . . . . . . . . . =
30=0A=
=0A=
.bp=0A=
10.   Security Considerations  . . . . . . . . . . . . . . . . . . =
31=0A=
10.1  Use of the TUNNEL Profile  . . . . . . . . . . . . . . . . . =
31=0A=
10.2  Use of Underlying Security Profiles  . . . . . . . . . . . . =
31=0A=
=0A=
      References . . . . . . . . . . . . . . . . . . . . . . . . . =
32=0A=
=0A=
      Authors' Addresses . . . . . . . . . . . . . . . . . . . . . =
32=0A=
=0A=
A.    IANA Considerations  . . . . . . . . . . . . . . . . . . . . =
34=0A=
=0A=
B.    History of Significant Changes . . . . . . . . . . . . . . . =
35=0A=
B.1   Significant Changes Since beep-idxp-04 . . . . . . . . . . . =
35=0A=
B.2   Significant Changes Since beep-idxp-03 . . . . . . . . . . . =
35=0A=
B.3   Significant Changes Since beep-idxp-02 . . . . . . . . . . . =
35=0A=
B.4   Significant Changes Since beep-idxp-01 . . . . . . . . . . . =
36=0A=
B.5   Significant Changes Since beep-idxp-00 . . . . . . . . . . . =
36=0A=
=0A=
C.    Acknowledgements . . . . . . . . . . . . . . . . . . . . . . =
38=0A=
=0A=
      Full Copyright Statement . . . . . . . . . . . . . . . . . . =
39=0A=
.bp=0A=
.fi=0A=
.in 3=0A=
.ti 0=0A=
1. Introduction=0A=
=0A=
IDXP is specified, in part, as a Blocks Extensible Exchange Protocol=0A=
(BEEP)[8] "profile".  BEEP is a generic application protocol=0A=
framework for connection-oriented, asynchronous interactions. =0A=
Features such as authentication and confidentiality are provided=0A=
through the use of other BEEP profiles.  Accordingly, many aspects =
of=0A=
IDXP (e.g., confidentiality) are provided within the BEEP framework.=0A=
=0A=
.in 4=0A=
.ti 0=0A=
1.1 Purpose=0A=
.in 3=0A=
=0A=
IDXP provides for the exchange of IDMEF[4] messages, unstructured=0A=
text, and binary data between intrusion detection entities. =0A=
Addressing the security-sensitive nature of exchanges between=0A=
intrusion detection entities, underlying BEEP security profiles=0A=
should be used to offer IDXP the required set of security =
properties.=0A=
See Section 5 for a discussion of how IDXP fulfills the IDWG=0A=
communication protocol requirements.  See Section 10 for a =
discussion=0A=
of security considerations.=0A=
=0A=
IDXP is primarily intended for the exchange of data created by=0A=
intrusion detection entities.  IDMEF[4] messages should be used for=0A=
the structured representation of this intrusion detection data,=0A=
although IDXP may be used to exchange unstructured text and binary=0A=
data.=0A=
=0A=
.in 4=0A=
.ti 0=0A=
1.2 Profiles=0A=
.in 3=0A=
=0A=
There are several BEEP profiles discussed, the first of which we=0A=
define in this memo:=0A=
=0A=
.in 6=0A=
.ti 3=0A=
The IDXP Profile=0A=
=0A=
.ti 3=0A=
The TUNNEL Profile[7]=0A=
=0A=
.ti 3=0A=
The Simple Authentication and Security Layer (SASL) Family of=0A=
Profiles (c.f., Section 4.1 of [8])=0A=
=0A=
.ti 3=0A=
The TLS Profile (c.f., Section 3.1 of [8])=0A=
=0A=
.in 3=0A=
=0A=
.in 4=0A=
.ti 0=0A=
1.3 Terminology=0A=
.in 3=0A=
=0A=
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",=0A=
"SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and "OPTIONAL" in =
this=0A=
document are to be interpreted as described in RFC 2119[2].=0A=
=0A=
Throughout this memo, the terms "analyzer" and "manager" are used in=0A=
.bp=0A=
the context of the Intrusion Detection Message Exchange=0A=
Requirements[9].  In particular, Section 3.2 of [9] defines the=0A=
meaning of a collection of intrusion detection terms.=0A=
=0A=
The terms "peer", "initiator", "listener", "client", and "server",=0A=
and the characters "I", "L", "C", and "S" are used in the context of=0A=
BEEP[8].  In particular, Section 2.1 of BEEP discusses the roles =
that=0A=
a BEEP peer may perform.=0A=
=0A=
The term "Document Type Declaration" is abbreviated as "DTD" and is=0A=
defined in Section 2.8 of the Extensible Markup Language (XML)[3].=0A=
=0A=
Note that the term "proxy" is specific to IDXP, and does not exist =
in=0A=
the context of BEEP.  The term "intrusion detection" is abbreviated=0A=
as "ID".=0A=
.bp=0A=
.ti 0=0A=
2. The Model=0A=
=0A=
.in 4=0A=
.ti 0=0A=
2.1 Connection Provisioning=0A=
.in 3=0A=
=0A=
Intrusion detection entities using IDXP to transfer data are termed=0A=
IDXP peers.  Peers can exist only in pairs, and these pairs=0A=
communicate over a single BEEP session with one or more BEEP =
channels=0A=
opened for transferring data.  Peers are either managers or=0A=
analyzers, as defined in Section 3.2 of [9].=0A=
=0A=
The relationship between analyzers and managers is potentially many-=0A=
to-many.  I.e., an analyzer MAY communicate with many managers;=0A=
similarly, a manager MAY communicate with many analyzers.  Likewise,=0A=
the relationship between different managers is potentially many-to-=0A=
many, so that a manager MAY receive the alerts sent by a large =
number=0A=
of analyzers by receiving them through intermediate managers. =0A=
Analyzers MUST NOT establish IDXP exchanges with other analyzers.=0A=
=0A=
An IDXP peer wishing to establish IDXP communications with another=0A=
IDXP peer does so by opening a BEEP channel, which may entail=0A=
initiating a BEEP session.  A BEEP security profile offering the=0A=
required security properties SHOULD initially be negotiated (see=0A=
Section 10 for a discussion of security considerations).  Following=0A=
the successful negotiation of the BEEP security profile, IDXP=0A=
greetings are exchanged and connection provisioning proceeds.=0A=
=0A=
In the following sequence a peer 'Alice' initiates an IDXP exchange=0A=
with the peer 'Bob'.=0A=
.nf=0A=
=0A=
     Alice                                               Bob=0A=
       ---------------- xport connect[1] ------------------>=0A=
      <-------------------- greeting ---------------------->=0A=
      <-------------start security profile[2] ------------->=0A=
      <-------------------- greeting ---------------------->=0A=
      <------------------ start IDXP[3] ------------------->=0A=
=0A=
.fi=0A=
Notes:=0A=
=0A=
.in 6=0A=
.ti 3=0A=
[1] 'Alice' initiates a transport connection to 'Bob', triggering =
the=0A=
exchange of BEEP greeting messages.=0A=
=0A=
.ti 3=0A=
[2] both entities negotiate the use of a BEEP security profile.=0A=
=0A=
.ti 3=0A=
[3] both entities negotiate the use of the IDXP profile.=0A=
=0A=
.in 3=0A=
In between a pair of IDXP peers may be an arbitrary number of=0A=
proxies.  A proxy may be necessary for administrative reasons, such=0A=
as running on a firewall to allow restricted access.  Another use=0A=
.bp=0A=
might be one proxy per company department, which forwards data from=0A=
the analyzer peers in the department onto a company-wide manager=0A=
peer.=0A=
=0A=
A BEEP tuning profile MAY be used to create an application-layer=0A=
tunnel that transparently forwards data over a chain of proxies.  =
The=0A=
TUNNEL profile[7] SHOULD be used for this purpose; see [7] for more=0A=
detail concerning the options available to setup an =
application-layer=0A=
tunnel using TUNNEL, and see Section 10.1 for a discussion of TUNNEL=0A=
related security considerations.  TUNNEL MUST be offered as a tuning=0A=
profile for the creation of application-layer tunnels.  The TUNNEL=0A=
profile MUST offer the use of some form of SASL authentication =
(c.f.,=0A=
Section 4.1 of [8]).  Once a tunnel has been created a BEEP security=0A=
profile offering the required security properties SHOULD be=0A=
negotiated, followed by negotiation of the IDXP profile.=0A=
=0A=
The following sequence shows how TUNNEL might be used to create an=0A=
application-layer tunnel through which IDXP would operate.  A peer=0A=
'Alice' initiates the creation of a BEEP session using the IDXP=0A=
profile with the entity 'Bob' by first contacting 'proxy1'.  In the=0A=
greeting exchange between 'Alice' and 'proxy1', the TUNNEL profile =
is=0A=
selected, and subsequently the use of the TUNNEL profile is extended=0A=
to reach through 'proxy2' to 'Bob'.=0A=
.nf=0A=
=0A=
Alice              proxy1               proxy2               Bob=0A=
  -- xport connect -->=0A=
 <---- greeting ----->=0A=
  -- start TUNNEL --->=0A=
                      - xport connect[1] ->=0A=
                     <----- greeting ----->=0A=
                      --- start TUNNEL --->=0A=
                                           --- xport connect -->=0A=
                                          <----- greeting ----->=0A=
                                           --- start TUNNEL --->=0A=
                                          <----- <ok>[2] ------=0A=
                     <------- <ok> -------=0A=
 <------ <ok> -------=0A=
 <------------------------- greeting -------------------------->=0A=
 <------------------ start security profile ------------------->=0A=
 <------------------------- greeting -------------------------->=0A=
 <------------------------ start IDXP ------------------------->=0A=
=0A=
.fi=0A=
Notes:=0A=
=0A=
.in 6=0A=
.ti 3=0A=
[1] Instead of immediately acknowledging the request from 'Alice' to=0A=
start TUNNEL, 'proxy1' attempts to establish use of TUNNEL with=0A=
'proxy2'.  'proxy2' also delays its acknowledgment to 'proxy1'.=0A=
=0A=
.bp=0A=
.ti 3=0A=
[2] 'Bob' acknowledges the request from 'proxy2' to start TUNNEL, =
and=0A=
this acknowledgment propagates back to 'Alice' so that a TUNNEL=0A=
application-layer tunnel is established from 'Alice' to 'Bob'.=0A=
=0A=
.in 3=0A=
=0A=
.in 4=0A=
.ti 0=0A=
2.2 Data Transfer=0A=
.in 3=0A=
=0A=
Between a pair of ID entities communicating over a BEEP session, one=0A=
or more BEEP channels MAY be opened using the IDXP profile.  If=0A=
desired, additional BEEP sessions MAY be established to offer=0A=
additional channels using the IDXP profile.  However, in most=0A=
situations additional channels using the IDXP profile SHOULD be=0A=
opened within an existing BEEP session, as opposed to provisioning a=0A=
new BEEP session containing the additional channels using the IDXP=0A=
profile.=0A=
=0A=
Peers assume the role of client or server on a per-channel basis,=0A=
with one acting as the client and the other as the server.  A peer's=0A=
role of client or server is determined independent of whether the=0A=
peer assumed the role of initiator or listener during the BEEP=0A=
session establishment.  Clients and servers act as sources and =
sinks,=0A=
respectively, for exchanging data.=0A=
=0A=
In a simple case, an analyzer peer sends data to a manager peer. =0A=
E.g.,=0A=
.nf=0A=
=0A=
        +----------+                          +----------+=0A=
        |          |                          |          |=0A=
        |          |****** BEEP session ******|          |=0A=
        |          |                          |          |=0A=
        | Analyzer | ----- IDXP profile ----> | Manager  |=0A=
        | (Client) |                          | (Server) |=0A=
        |          |                          |          |=0A=
        |          |**************************|          |=0A=
        |          |                          |          |=0A=
        +----------+                          +----------+=0A=
=0A=
.fi=0A=
Use of multiple BEEP channels in a BEEP session facilitates=0A=
categorization and prioritization of data sent between IDXP peers. =0A=
For example, a manager 'M1', sending alert data to another manager,=0A=
'M2', may choose to open a separate channel to exchange different=0A=
categories of alerts.  'M1' would act as the client on each of these=0A=
channels, and manager 'M2' can then process and act on the incoming=0A=
alerts based on their respective channel categorizations.  See=0A=
Section 4 for more detail on how to incorporate categorization =
and/or=0A=
prioritization into channel creation.=0A=
.bp=0A=
.nf=0A=
.in 3=0A=
+----------+                                            +----------+=0A=
|          |                                            |          |=0A=
|          |*************** BEEP session ***************|          |=0A=
|          |                                            |          |=0A=
|          | -- IDXP profile, network-based alerts ---> |          |=0A=
| Manager  |                                            | Manager  |=0A=
|   M1     | ---- IDXP profile, host-based alerts ----> |   M2     |=0A=
| (Client) |                                            | (Server) |=0A=
|          | ------ IDXP profile, other alerts -------> |          |=0A=
|          |                                            |          |=0A=
|          |********************************************|          |=0A=
|          |                                            |          |=0A=
+----------+                                            +----------+=0A=
=0A=
=0A=
.fi=0A=
.in 4=0A=
.ti 0=0A=
2.3 Connection Teardown=0A=
.in 3=0A=
=0A=
An IDXP peer may choose to close an IDXP channel under many =
different=0A=
circumstances (e.g., an error in processing has occurred).  To close=0A=
a channel, the peer sends a "close" element (c.f., Section 2.3.1.3 =
of=0A=
[8]) on channel zero indicating which channel is being closed.  An=0A=
IDXP peer may also choose to close an entire BEEP session by sending=0A=
a "close" element indicating that channel zero is to be closed. =0A=
Section 2.3.1.3 of [8] offers a more complete discussion of the=0A=
circumstances under which a BEEP peer is permitted to close a =
channel=0A=
and the mechanisms for doing so.=0A=
=0A=
It is anticipated that due to the overhead of provisioning an=0A=
application-layer tunnel and/or a BEEP security profile, BEEP=0A=
sessions containing IDXP channels will be long-lived.  Additionally,=0A=
the repeated overhead of IDXP channel provisioning (i.e., the=0A=
exchange of IDXP greetings) may be avoided by keeping IDXP channels=0A=
open even while data is not actively being exchanged on them.  These=0A=
are recommendations and, as such, IDXP peers may choose to close and=0A=
re-provision BEEP sessions and/or IDXP channels as they see fit.=0A=
=0A=
.in 4=0A=
.ti 0=0A=
2.4 Trust Model=0A=
.in 3=0A=
=0A=
In our model, trust is placed exclusively in the IDXP peers.  =
Proxies=0A=
are always assumed to be untrustworthy.  A BEEP security profile is=0A=
used to establish end-to-end security between pairs of IDXP peers,=0A=
doing away with the need to place trust in any intervening proxies. =0A=
Only after successful negotiation of the underlying security profile=0A=
are IDXP peers to be trusted.  Only BEEP security profiles offering=0A=
at least the protections required by Section 5 of [9] should be used=0A=
to secure a BEEP session containing channels using the IDXP profile. =
=0A=
See Section 3 of [8] for the registration of the TLS profile, an=0A=
example of a BEEP security profile meeting the requirements of=0A=
.bp=0A=
Section 5 of [9].  See Section 5 for a discussion of how IDXP=0A=
fulfills the IDWG communications protocol requirements.=0A=
.bp=0A=
.ti 0=0A=
3. The IDXP Profile=0A=
=0A=
.in 4=0A=
.ti 0=0A=
3.1 IDXP Profile Overview=0A=
.in 3=0A=
=0A=
The IDXP profile provides a mechanism for exchanging information=0A=
between intrusion detection entities.  A BEEP tuning profile MAY be=0A=
used to create an application-layer tunnel that transparently=0A=
forwards data over a chain of proxies.  The TUNNEL profile[7] SHOULD=0A=
be used for this purpose; see [7] for more detail concerning the=0A=
options available to setup an application-layer tunnel using TUNNEL,=0A=
and see Section 10.1 for a discussion of TUNNEL related security=0A=
considerations.  TUNNEL MUST be offered as a tuning profile for the=0A=
creation of application-layer tunnels.  The TUNNEL profile MUST =
offer=0A=
the use of some form of SASL authentication (c.f., Section 4.1 of=0A=
[8]).  The TLS profile SHOULD be used to provide the required=0A=
combination of mutual-authentication, integrity, and confidentiality=0A=
for the IDXP profile.  For further discussion of application-layer=0A=
tunnel and security issues see Section 2.1 and Section 10.=0A=
=0A=
The IDXP profile supports several elements of interest:=0A=
=0A=
.in 6=0A=
.ti 3=0A=
o  The "IDXP-Greeting" element identifies an analyzer or manager at=0A=
one end of a BEEP channel to the analyzer or manager at the other=0A=
end of the channel.=0A=
=0A=
.ti 3=0A=
o  The "Option" element is used to convey optional channel =
parameters=0A=
between peers during the exchange of "IDXP-Greeting" elements. =0A=
This element is OPTIONAL.=0A=
=0A=
.ti 3=0A=
o  The "IDMEF-Message" element carries the structured information to=0A=
be exchanged between the peers.=0A=
=0A=
.in 3=0A=
=0A=
.in 4=0A=
.ti 0=0A=
3.2 IDXP Profile Identification and Initialization=0A=
.in 3=0A=
=0A=
The IDXP profile is identified as=0A=
=0A=
.in 6=0A=
.ti 3=0A=
http://iana.org/beep/transient/idwg/idxp=0A=
=0A=
.in 3=0A=
in the BEEP "profile" element during channel creation.=0A=
=0A=
During channel creation, "IDXP-Greeting" elements MUST be mutually=0A=
exchanged between the peers.  An "IDXP-Greeting" element MAY be=0A=
contained within the corresponding "profile" element in the BEEP=0A=
"start" element.  Including an "IDXP-Greeting" element in the =
initial=0A=
"start" element has exactly the same semantics as passing it as the=0A=
first "MSG" message on the channel.  If channel creation is=0A=
successful, then before sending the corresponding reply, the BEEP=0A=
.bp=0A=
peer processes the "IDXP-Greeting" element and includes the =
resulting=0A=
response in the reply.  This response will be an "ok" element or an=0A=
"error" element.  The choice of which element is returned is=0A=
dependent on local provisioning of the peer.=0A=
=0A=
.in 4=0A=
.ti 0=0A=
3.3 IDXP Profile Message Syntax=0A=
.in 3=0A=
=0A=
BEEP messages in the profile MUST have a MIME Content-Type[5] of=0A=
"text/xml", "text/plain", or "application/octet-stream".  The syntax=0A=
of the individual elements is specified in Section 8.1 and Section 5=0A=
of [4].=0A=
=0A=
.in 4=0A=
.ti 0=0A=
3.4 IDXP Profile Semantics=0A=
.in 3=0A=
=0A=
Each BEEP peer issues the "IDXP-Greeting" element using "MSG"=0A=
messages.  The "IDXP-Greeting" element MAY contain one or more=0A=
"Option" sub-elements, conveying optional channel parameters.  Each=0A=
BEEP peer then issues "ok" in "RPY" messages or "error" in "ERR"=0A=
messages.  (See Section 2.3.1 of [8] for the definitions of the=0A=
"error" and "ok" elements.) An "error" element MAY be issued within =
a=0A=
"RPY" message when piggy-backed within a BEEP "profile" element.  =
See=0A=
section 3.4.1 for an example of an "error" element being issued=0A=
within a "RPY" message.  Based on the respective client/server roles=0A=
negotiated during the exchange of "IDXP-Greeting" elements, the=0A=
client sends data using "MSG" messages.  Depending on the MIME=0A=
Content-Type, this data may be an "IDMEF-Message" element, plain=0A=
text, or binary.  The server then issues "ok" in "RPY" messages or=0A=
"error" in "ERR" messages.=0A=
=0A=
.in 6=0A=
.ti 0=0A=
3.4.1 The IDXP-GREETING Element=0A=
.in 3=0A=
=0A=
The "IDXP-Greeting" element serves to identify the analyzer or=0A=
manager at one end of the BEEP channel to the analyzer or manager at=0A=
the other end of the channel.  The "IDXP-Greeting" element MUST=0A=
include the role of the peer on the channel (client or server) and=0A=
the Uniform Resource Identifier (URI)[1] of the peer.  Additionally,=0A=
the "IDXP-Greeting" element MAY include the fully qualified domain=0A=
name (c.f., [6]) of the peer.  One or more "Option" sub-elements MAY=0A=
be present.=0A=
=0A=
An "IDXP-Greeting" element MAY be sent by either peer at any time. =0A=
The peer receiving the "IDXP-Greeting" MUST respond with an "ok"=0A=
(indicating acceptance), or an "error" (indicating rejection).  A=0A=
peer's identity and role on a channel and any optional channel=0A=
parameters are, in effect, specified by the most recent "IDXP-=0A=
Greeting" it sent that was answered with an "ok".=0A=
=0A=
An "IDXP-Greeting" may be rejected (with an "error" element) under=0A=
.bp=0A=
many circumstances.  These include, but are not limited to,=0A=
authentication failure, lack of authorization to connect under the=0A=
specified role, the negotiation of an inadequate ciphersuite, or the=0A=
presence of a channel option that must be understood but was=0A=
unrecognized.=0A=
=0A=
For example, a successful creation with an embedded "IDXP-Greeting"=0A=
might look like this:=0A=
.nf=0A=
=0A=
I: MSG 0 10 . 1592 187=0A=
I: Content-Type: text/xml=0A=
I:=0A=
I: <start number=3D'1'>=0A=
I:   <profile uri=3D'http://iana.org/beep/transient/idwg/idxp'>=0A=
I:     <![CDATA[ <IDXP-Greeting uri=3D'http://example.com/alice'=0A=
I:       role=3D'client' /> ]]>=0A=
I:   </profile>=0A=
I: </start>=0A=
I: END=0A=
L: RPY 0 10 . 1865 91=0A=
L: Content-Type: text/xml=0A=
L:=0A=
L: <profile uri=3D'http://iana.org/beep/transient/idwg/idxp'>=0A=
L:   <![CDATA[ <ok /> ]]>=0A=
L: </profile>=0A=
L: END=0A=
L: MSG 0 11 . 1956 61=0A=
L: Content-Type: text/xml=0A=
L:=0A=
L: <IDXP-Greeting uri=3D'http://example.com/bob' role=3D'server' />=0A=
L: END=0A=
I: RPY 0 11 . 1779 7=0A=
I: Content-Type: text/xml=0A=
I:=0A=
I: <ok />=0A=
I: END=0A=
=0A=
.bp=0A=
.fi=0A=
A creation with an embedded "IDXP-Greeting" that fails might look=0A=
like this:=0A=
.nf=0A=
=0A=
.in 3=0A=
I: MSG 0 10 . 1776 185=0A=
I: Content-Type: text/xml=0A=
I:=0A=
I: <start number=3D'1'>=0A=
I:   <profile uri=3D'http://iana.org/beep/transient/idwg/idxp'>=0A=
I:     <![CDATA[ <IDXP-Greeting uri=3D'http://example.com/eve'=0A=
I:       role=3D'client' /> ]]>=0A=
I:   </profile>=0A=
I: </start>=0A=
I: END=0A=
L: RPY 0 10 . 1592 182=0A=
L: Content-Type: text/xml=0A=
L:=0A=
L: <profile uri=3D'http://iana.org/beep/transient/idwg/idxp'>=0A=
L:   <![CDATA[=0A=
L:     <error code=3D'530'>'http://example.com/eve' must first=0A=
L:       negotiate the TLS profile</error> ]]>=0A=
L: </profile>=0A=
L: END=0A=
=0A=
=0A=
.fi=0A=
.in 6=0A=
.ti 0=0A=
3.4.2 The OPTION Element=0A=
.in 3=0A=
=0A=
If present, the "Option" element MUST be contained within an "IDXP-=0A=
Greeting" element.  An individual "IDXP-Greeting" element MAY =
contain=0A=
one or more "Option" sub-elements.  Each "Option" element within an=0A=
"IDXP-Greeting" element represents a request to enable an IDXP =
option=0A=
on the channel being negotiated.  See Section 4 for a complete=0A=
description of IDXP options and the "Option" element.=0A=
=0A=
.in 6=0A=
.ti 0=0A=
3.4.3 The IDMEF-MESSAGE Element=0A=
.in 3=0A=
=0A=
The "IDMEF-Message" element carries the information to be exchanged=0A=
between the peers.  See Section 5 of [4] for the definition of this=0A=
element.=0A=
.bp=0A=
.ti 0=0A=
4. IDXP Options=0A=
=0A=
IDXP provides a service for the reliable exchange of data between=0A=
intrusion detection entities.  Options are used to alter the=0A=
semantics of the service.=0A=
=0A=
The specification of an IDXP option MUST define:=0A=
=0A=
.in 6=0A=
.ti 3=0A=
o  the identity of the option;=0A=
=0A=
.ti 3=0A=
o  what content, if any, is contained within the option; and,=0A=
=0A=
.ti 3=0A=
o  the processing rules for the option.=0A=
=0A=
.in 3=0A=
An option registration template (c.f.  Section 6) organizes this=0A=
information.=0A=
=0A=
An "Option" element is contained within an "IDXP-Greeting" element. =0A=
The "IDXP-Greeting" element itself MAY contain one or more "Option"=0A=
elements.  The "Option" element has several attributes and contains=0A=
arbitrary content:=0A=
=0A=
.in 6=0A=
.ti 3=0A=
o  the "internal" and the "external" attributes, exactly one of =
which=0A=
MUST be present, uniquely identify the option;=0A=
=0A=
.ti 3=0A=
o  the "mustUnderstand" attribute, whose presence is OPTIONAL and=0A=
whose default value is "false", specifies whether the option, if=0A=
unrecognized, MUST cause an error in processing to occur; and,=0A=
=0A=
.ti 3=0A=
o  the "localize" attribute, whose presence is OPTIONAL, specifies=0A=
one or more language tokens, each identifying a desirable language=0A=
tag to be used if textual diagnostics are returned to the=0A=
originator.=0A=
=0A=
.in 3=0A=
The value of the "internal" attribute is the IANA-registered name =
for=0A=
the option.  If the "internal" attribute is not present, then the=0A=
value of the "external" attribute is a URI or URI with a fragment-=0A=
identifier.  Note that a relative-URI value is not allowed.=0A=
=0A=
The "mustUnderstand" attribute specifies whether the peer may ignore=0A=
the option if it is unrecognized.  If the value of the=0A=
"mustUnderstand" attribute is "true", and if the peer does not=0A=
recognize the option, then an error in processing has occurred.  =
When=0A=
absent, the value of the "mustUnderstand" attribute is defined to be=0A=
"false".=0A=
.bp=0A=
.in 4=0A=
.ti 0=0A=
4.1 The channelPriority Option=0A=
.in 3=0A=
=0A=
Section 7.3 contains the IDXP option registration for the=0A=
"channelPriority" option.  This option contains a "channelPriority"=0A=
element (c.f., Section 8.2).=0A=
=0A=
By default, IDXP does not place any requirements on how peers should=0A=
manage multiple IDXP channels.  The "channelPriority" option =
provides=0A=
a way for peers using multiple IDXP channels to request relative=0A=
priorities for each channel.  When sending an "IDXP-Greeting" =
element=0A=
during the provisioning of an IDXP channel, the originating peer MAY=0A=
request that the remote peer assign a priority to the channel by=0A=
including an "Option" element containing a "channelPriority" =
element.=0A=
=0A=
The "channelPriority" element has one attribute named "priority", of=0A=
range 0..2147483647.  This attribute is REQUIRED.  Not=0A=
coincidentally, this is the maximum range of possible BEEP channel=0A=
numbers.  0 is defined to represent the highest priority, with=0A=
relative priority decreasing as the "priority" value ascends.=0A=
=0A=
For example, during the exchange of "IDXP-Greeting" elements during=0A=
channel provisioning, an analyzer successfully requests that a=0A=
manager assign a priority to the channel:=0A=
.nf=0A=
=0A=
=0A=
    analyzer                                           manager=0A=
       --------------- greeting w/ option ----------------->=0A=
      <---------------------- <ok> ------------------------=0A=
=0A=
C: MSG 1 17 . 1984 165=0A=
C: Content-Type: text/xml=0A=
C:=0A=
C: <IDXP-Greeting uri=3D'http://example.com/alice' role=3D'client'>=0A=
C:   <Option internal=3D'channelPriority'>=0A=
C:     <channelPriority priority=3D'0' />=0A=
C:   </Option>=0A=
C: </IDXP-Greeting>=0A=
C: END=0A=
S: RPY 1 17 . 2001 7=0A=
S: Content-Type: text/xml=0A=
S:=0A=
S: <ok />=0A=
S: END=0A=
=0A=
.bp=0A=
.fi=0A=
For example, during the exchange of "IDXP-Greeting" elements during=0A=
channel provisioning, a manager unsuccessfully requests that an=0A=
analyzer assign a priority to the channel:=0A=
.nf=0A=
=0A=
=0A=
.in 3=0A=
    analyzer                                           manager=0A=
      <---------------- greeting w/ option ----------------=0A=
       --------------------- <error> ---------------------->=0A=
=0A=
S: MSG 1 17 . 1312 194=0A=
S: Content-Type: text/xml=0A=
S:=0A=
S: <IDXP-Greeting uri=3D'http://example.com/bob' role=3D'server'>=0A=
S:   <Option internal=3D'channelPriority' mustUnderstand=3D'true'>=0A=
S:     <channelPriority priority=3D'2147483647' />=0A=
S:   </Option>=0A=
S: </IDXP-Greeting>=0A=
S: END=0A=
C: ERR 1 17 . 451 68=0A=
C: Content-Type: text/xml=0A=
C:=0A=
C: <error code=3D'504'>'channelPriority' option was =
unrecognized</error>=0A=
C: END=0A=
=0A=
=0A=
.fi=0A=
.in 4=0A=
.ti 0=0A=
4.2 The streamType Option=0A=
.in 3=0A=
=0A=
Section 7.4 contains the IDXP option registration for the=0A=
"streamType" option.  This option contains a "streamType" element=0A=
(c.f., Section 8.3).=0A=
=0A=
By default, IDXP provides no explicit method for categorizing=0A=
channels.  The "streamType" option provides a way for peers to=0A=
request that a channel be categorized as a particular stream type. =0A=
When sending an "IDXP-Greeting" element during the provisioning of =
an=0A=
IDXP channel, the originating peer MAY request that the remote peer=0A=
assign a stream type to the channel by including an "Option" element=0A=
containing a "streamType" element.=0A=
=0A=
The "streamType" element has one attribute named "type", with the=0A=
possible values of "alert", "heartbeat", or "config".  This =
attribute=0A=
is REQUIRED.  A value of "alert" indicates that the channel should =
be=0A=
categorized as being used for the exchange of ID alerts.  A value of=0A=
"heartbeat" indicates that the channel should be categorized as =
being=0A=
used for the exchange of heartbeat messages such as the "Heartbeat"=0A=
element (c.f., Section 5 of [4]).  A value of "config" indicates =
that=0A=
the channel should be categorized as being used for the exchange of=0A=
configuration messages.=0A=
.bp=0A=
For example, during the exchange of "IDXP-Greeting" elements during=0A=
channel provisioning, an analyzer successfully requests that a=0A=
manager assign a stream type to the channel:=0A=
.nf=0A=
=0A=
=0A=
    analyzer                                           manager=0A=
       --------------- greeting w/ option ----------------->=0A=
      <---------------------- <ok> ------------------------=0A=
=0A=
C: MSG 1 21 . 1963 155=0A=
C: Content-Type: text/xml=0A=
C:=0A=
C: <IDXP-Greeting uri=3D'http://example.com/alice' role=3D'client'>=0A=
C:   <Option internal=3D'streamType'>=0A=
C:     <streamType type=3D'alert' />=0A=
C:   </Option>=0A=
C: </IDXP-Greeting>=0A=
C: END=0A=
S: RPY 1 21 . 1117 7=0A=
S: Content-Type: text/xml=0A=
S:=0A=
S: <ok />=0A=
S: END=0A=
=0A=
.bp=0A=
.fi=0A=
For example, during the exchange of "IDXP-Greeting" elements during=0A=
channel provisioning, a manager unsuccessfully requests that an=0A=
analyzer assign a stream type to the channel:=0A=
.nf=0A=
=0A=
=0A=
=0A=
.in 3=0A=
    analyzer                                           manager=0A=
      <---------------- greeting w/ option ----------------=0A=
       --------------------- <error> ---------------------->=0A=
=0A=
S: MSG 1 21 . 1969 176=0A=
S: Content-Type: text/xml=0A=
S:=0A=
S: <IDXP-Greeting uri=3D'http://example.com/bob' role=3D'server'>=0A=
S:   <Option internal=3D'streamType' mustUnderstand=3D'true'>=0A=
S:     <streamType type=3D'config' />=0A=
S:   </Option>=0A=
S: </IDXP-Greeting>=0A=
S: END=0A=
C: ERR 1 21 . 1292 63=0A=
C: Content-Type: text/xml=0A=
C:=0A=
C: <error code=3D'504'>'streamType' option was unrecognized</error>=0A=
C: END=0A=
=0A=
.bp=0A=
.fi=0A=
.in 3=0A=
.ti 0=0A=
5. Fulfillment of IDWG Communications Protocol Requirements=0A=
=0A=
The following lists the communications protocol requirements=0A=
established in Section 5 of [9] and, for each requirement, describes=0A=
the manner in which it is fulfilled by IDXP.=0A=
=0A=
The [protocol] MUST support reliable transmission of messages.=0A=
=0A=
.in 6=0A=
.ti 3=0A=
IDXP operates over BEEP, which operates only over reliable=0A=
connection-oriented transport protocols (e.g., TCP).  In addition,=0A=
BEEP peers communicate using a simple request-response protocol,=0A=
which provides end-to-end reliability between peers.=0A=
=0A=
.in 3=0A=
The [protocol] MUST support transmission of messages between ID=0A=
components across firewall boundaries without compromising security.=0A=
=0A=
.in 6=0A=
.ti 3=0A=
The TUNNEL profile [7] MUST be offered as an option for creation=0A=
of application-layer tunnels to allow operation across firewalls. =0A=
The TUNNEL profile SHOULD be used to provide an application-layer=0A=
tunnel.  The ability to authenticate hosts during the creation of=0A=
an application-layer tunnel MUST be provided by the mechanism=0A=
chosen to create such tunnels.  A firewall may therefore be=0A=
configured to authenticate all hosts attempting to tunnel into the=0A=
protected network.  If the TUNNEL profile is used, SASL (c.f.,=0A=
Section 4.1 of [8]) MUST be offered as a mechanism by which hosts=0A=
can be authenticated.=0A=
=0A=
.in 3=0A=
The [protocol] MUST support mutual authentication of the analyzer =
and=0A=
the manager to each other.=0A=
=0A=
.in 6=0A=
.ti 3=0A=
IDXP supports mutual authentication of the peers through the use=0A=
of an appropriate underlying BEEP security profile.  The TLS=0A=
profile and members of the SASL family of profiles (c.f., Section=0A=
4.1 of [8]) are examples of security profiles that may be used to=0A=
authenticate the identity of communicating ID components.  TLS=0A=
MUST be offered as a mechanism to provide mutual authentication,=0A=
and TLS SHOULD be used to provide mutual authentication.=0A=
=0A=
.in 3=0A=
The [protocol] MUST support confidentiality of the message content=0A=
during message exchange.  The selected design MUST be capable of=0A=
supporting a variety of encryption algorithms and MUST be adaptable=0A=
to a wide variety of environments.=0A=
=0A=
.in 6=0A=
.ti 3=0A=
IDXP supports confidentiality through the use of an appropriate=0A=
underlying BEEP security profile.  The TLS profile is an example a=0A=
security profile that offers confidentiality.  The TLS profile=0A=
with the TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA cipher suite MUST be=0A=
offered as a mechanism to provide confidentiality, and TLS with=0A=
.bp=0A=
this cipher suite SHOULD be used to provide confidentiality.  The=0A=
TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA cipher suite uses ephemeral=0A=
Diffie-Hellman (DHE) with DSS signatures for key exchange and=0A=
triple DES (3DES) and cipher-block chaining (CBC) for encryption. =0A=
Stronger cipher suites are optional.=0A=
=0A=
.in 3=0A=
The [protocol] MUST ensure the integrity of the message content.  =
The=0A=
selected design MUST be capable of supporting a variety of integrity=0A=
mechanisms and MUST be adaptable to a wide variety of environments.=0A=
=0A=
.in 6=0A=
.ti 3=0A=
IDXP supports message integrity through the use of an appropriate=0A=
underlying BEEP security profile.  The TLS profile and members of=0A=
the SASL family of profiles (c.f., Section 4.1 of [8]) are=0A=
examples of security profiles that offer message integrity.  The=0A=
TLS profile with the TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA cipher=0A=
suite MUST be offered as a mechanism to provide integrity, and TLS=0A=
with this cipher suite SHOULD be used to provide integrity.  The=0A=
TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA cipher suite uses the Secure=0A=
Hash Algorithm (SHA) for integrity protection using a keyed=0A=
message authentication code.  Stronger cipher suites are optional.=0A=
=0A=
.in 3=0A=
The [protocol] SHOULD be able to ensure non-repudiation of the =
origin=0A=
of IDMEF messages.=0A=
=0A=
.in 6=0A=
.ti 3=0A=
IDXP supports non-repudiation of session origin through the use of=0A=
an appropriate underlying BEEP security profile.  An IDXP peer=0A=
application MAY use IDMEF content and/or BEEP session credentials=0A=
to provide for non-repudiation of message origin.  The TLS profile=0A=
is an example of a security profile that offers non-repudiation of=0A=
session origin through the authentication of public-key=0A=
certificates.  TLS MUST be offered as a mechanism to provide non-=0A=
repudiation of session origin, and TLS SHOULD be used to provide=0A=
non-repudiation of session origin.=0A=
=0A=
.in 3=0A=
The [protocol] SHOULD resist protocol denial of service attacks.=0A=
=0A=
.in 6=0A=
.ti 3=0A=
IDXP supports resistance to denial of service (DoS) attacks=0A=
through the use of an appropriate underlying BEEP security=0A=
profile.  BEEP peers offering the IDXP profile MUST offer the use=0A=
of TLS with the TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA cipher suite,=0A=
and SHOULD use TLS with that cipher suite.  To resist DoS attacks=0A=
it is helpful to discard traffic arising from a non-authenticated=0A=
source.  BEEP peers MUST support the use of authentication in=0A=
conjunction with any mechanism used to create application-layer=0A=
tunnels.  In particular, the use of some form of SASL=0A=
authentication (c.f., Section 4.1 of [8]) MUST be offered to=0A=
provide authentication in the use of the TUNNEL profile.  See=0A=
Section 7 of [7] for a discussion of security considerations in=0A=
.bp=0A=
the use of the TUNNEL profile.=0A=
=0A=
.in 3=0A=
The [protocol] SHOULD resist malicious duplication of messages.=0A=
=0A=
.in 6=0A=
.ti 3=0A=
IDXP supports resistance to malicious duplication of messages=0A=
(i.e., replay attacks) through the use of an appropriate=0A=
underlying BEEP security profile.  The TLS profile is an example=0A=
of a security profile offering resistance to replay attacks.  The=0A=
TLS profile with the TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA cipher=0A=
suite MUST be offered as a mechanism to provide resistance against=0A=
replay attacks, and TLS with this cipher suite SHOULD be used to=0A=
provide resistance against replay attacks.  The=0A=
TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA cipher suite uses cipher-block=0A=
chaining (CBC) to ensure that even if a message is duplicated the=0A=
cipher-text duplicate will produce a very different plain-text=0A=
result.  Stronger cipher suites are optional.=0A=
=0A=
.in 3=0A=
.bp=0A=
.ti 0=0A=
6. IDXP Option Registration Template=0A=
=0A=
When an IDXP option is registered, the following information is=0A=
supplied:=0A=
=0A=
Option Identification: specify the NMTOKEN or the URI that=0A=
authoritatively identifies this option.=0A=
=0A=
Contains: specify the XML content that is contained within the=0A=
"Option" element.=0A=
=0A=
Processing Rules: specify the processing rules associated with the=0A=
option.=0A=
=0A=
Contact Information: specify the postal and electronic contact=0A=
information for the author(s) of the option.=0A=
.bp=0A=
.ti 0=0A=
7. Initial Registrations=0A=
=0A=
.in 4=0A=
.ti 0=0A=
7.1 Registration: The IDXP Profile=0A=
.in 3=0A=
=0A=
Profile identification: http://iana.org/beep/transient/idwg/idxp=0A=
=0A=
Messages exchanged during channel creation: "IDXP-Greeting"=0A=
=0A=
Messages starting one-to-one exchanges: "IDXP-Greeting", "IDMEF-=0A=
Message"=0A=
=0A=
Messages in positive replies: "ok"=0A=
=0A=
Messages in negative replies: "error"=0A=
=0A=
Messages in one-to-many exchanges: none=0A=
=0A=
Message syntax: c.f., Section 3.3=0A=
=0A=
Message semantics: c.f., Section 3.4=0A=
=0A=
Contact information: c.f., the "Authors' Addresses" section of this=0A=
memo=0A=
=0A=
.in 4=0A=
.ti 0=0A=
7.2 Registration: The System (Well-Known) TCP port number for IDXP=0A=
.in 3=0A=
=0A=
Protocol Number: TCP=0A=
=0A=
Message Formats, Types, Opcodes, and Sequences: c.f., Section 3.3=0A=
=0A=
Functions: c.f., Section 3.4=0A=
=0A=
Use of Broadcast/Multicast: none=0A=
=0A=
Proposed Name: Intrusion Detection Exchange Protocol=0A=
=0A=
Short name: idxp=0A=
=0A=
Contact Information: c.f., the "Authors' Addresses" section of this=0A=
memo=0A=
=0A=
.in 4=0A=
.ti 0=0A=
7.3 Registration: The channelPriority Option=0A=
.in 3=0A=
=0A=
Option Identification: channelPriority=0A=
=0A=
Contains: channelPriority (c.f., Section 8.2)=0A=
=0A=
Processing Rules: c.f., Section 4.1=0A=
.bp=0A=
Contact Information: c.f., the "Authors' Addresses" section of this=0A=
memo=0A=
=0A=
.in 4=0A=
.ti 0=0A=
7.4 Registration: The streamType Option=0A=
.in 3=0A=
=0A=
Option Identification: streamType=0A=
=0A=
Contains: streamType (c.f., Section 8.3)=0A=
=0A=
Processing Rules: c.f., Section 4.2=0A=
=0A=
Contact Information: c.f., the "Authors' Addresses" section of this=0A=
memo=0A=
.bp=0A=
.ti 0=0A=
8. The DTDs=0A=
=0A=
.in 4=0A=
.ti 0=0A=
8.1 The IDXP DTD=0A=
.in 3=0A=
=0A=
The following is the DTD defining the valid elements for the IDXP=0A=
profile=0A=
.nf=0A=
=0A=
  <!--=0A=
  DTD for the IDXP Profile, as of 2002-01-08=0A=
=0A=
  Refer to this DTD as:=0A=
=0A=
    <!ENTITY % IDXP PUBLIC "-//IETF//DTD RFC XXXX IDXP v1.0//EN">=0A=
=0A=
    %IDXP;=0A=
  -->=0A=
=0A=
  <!-- Includes -->=0A=
=0A=
    <!ENTITY % BEEP PUBLIC "-//IETF//DTD BEEP//EN">=0A=
=0A=
    %BEEP;=0A=
=0A=
=0A=
    <!ENTITY % IDMEF-Message PUBLIC "-//IETF//DTD RFC XXXX IDMEF =
v1.0//EN">=0A=
=0A=
    %IDMEF;=0A=
=0A=
  <!--=0A=
    Profile Summary=0A=
=0A=
      BEEP profile http://iana.org/beep/transient/idwg/idxp=0A=
=0A=
      role       MSG               RPY      ERR=0A=
      =3D=3D=3D=3D       =3D=3D=3D               =3D=3D=3D      =
=3D=3D=3D=0A=
      I or L     IDXP-Greeting     ok       error=0A=
      C          IDMEF-Message     ok       error=0A=
  -->=0A=
=0A=
  <!--=0A=
    Entity Definitions=0A=
=0A=
          entity        syntax/reference     example=0A=
          =3D=3D=3D=3D=3D=3D        =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D     =
=3D=3D=3D=3D=3D=3D=3D=0A=
      an authoritative identification=0A=
          URI           c.f., [RFC-2396]       http://example.com=0A=
=0A=
      a fully qualified domain name=0A=
.bp=0A=
          FQDN          c.f., [RFC-1034]       www.example.com=0A=
  -->=0A=
=0A=
  <!ENTITY % URI      "CDATA">=0A=
  <!ENTITY % FQDN     "CDATA">=0A=
=0A=
  <!--=0A=
    The IDXP-Greeting element declares the role and identity of=0A=
    the peer issuing it, on a per channel basis. The=0A=
    IDXP-Greeting element may contain one or more Option=0A=
    sub-elements.=0A=
  -->=0A=
=0A=
<!ELEMENT IDXP-Greeting  (Option*)>=0A=
<!ATTLIST IDXP-Greeting=0A=
          uri            %URI;                #REQUIRED=0A=
          role           (client|server)      #REQUIRED=0A=
          fqdn           %FQDN;               #IMPLIED>=0A=
=0A=
  <!--=0A=
    The Option element conveys an IDXP channel option.=0A=
    Note that the %LOCS entity is imported from the BEEP Channel=0A=
    Management DTD.=0A=
  -->=0A=
=0A=
<!ELEMENT Option (ANY)>=0A=
<!ATTLIST Option=0A=
          internal       NMTOKEN              ""=0A=
          external       %URI;                ""=0A=
          mustUnderstand (true|false)         "false"=0A=
          localize       %LOCS;               "i-default">=0A=
=0A=
  <!--=0A=
    The IDMEF-Message element conveys the intrusion detection=0A=
    information that is exchanged.  This element is defined in the=0A=
    idmef-message.dtd=0A=
  -->=0A=
=0A=
<!-- End of DTD -->=0A=
=0A=
=0A=
.fi=0A=
.in 4=0A=
.ti 0=0A=
8.2 The channelPriority Option DTD=0A=
.in 3=0A=
=0A=
The following is the DTD defining the valid elements for the=0A=
channelPriority option=0A=
.bp=0A=
.nf=0A=
  <!--=0A=
  DTD for the channelPriority IDXP option, as of 2002-01-08=0A=
=0A=
  Refer to this DTD as:=0A=
=0A=
    <!ENTITY % IDXP-channelPriority PUBLIC=0A=
      "-//IETF//DTD RFC XXXX IDXP-channelPriority v1.0//EN">=0A=
=0A=
    %IDXP-channelPriority;=0A=
  -->=0A=
=0A=
  <!--=0A=
    Entity Definitions=0A=
=0A=
          entity        syntax/reference     example=0A=
          =3D=3D=3D=3D=3D=3D        =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D     =
=3D=3D=3D=3D=3D=3D=3D=0A=
    a priority number=0A=
          PRIORITY      0..2147483647        1=0A=
  -->=0A=
=0A=
<!ENTITY % PRIORITY          "CDATA">=0A=
=0A=
<!ELEMENT channelPriority    EMPTY>=0A=
<!ATTLIST channelPriority=0A=
          priority           %PRIORITY    #REQUIRED>=0A=
=0A=
<!-- End of DTD -->=0A=
=0A=
=0A=
.fi=0A=
.in 4=0A=
.ti 0=0A=
8.3 The streamType DTD=0A=
.in 3=0A=
=0A=
The following is the DTD defining the valid elements for the=0A=
streamType option=0A=
.bp=0A=
.nf=0A=
  <!--=0A=
  DTD for the streamType IDXP option, as of 2002-01-08=0A=
=0A=
  Refer to this DTD as:=0A=
=0A=
    <!ENTITY % IDXP-streamType PUBLIC=0A=
      "-//IETF//DTD RFC XXXX IDXP-streamType v1.0//EN">=0A=
=0A=
    %IDXP-streamType;=0A=
  -->=0A=
=0A=
  <!--=0A=
    Entity Definitions=0A=
=0A=
          entity        syntax/reference                example=0A=
          =3D=3D=3D=3D=3D=3D        =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D                =
=3D=3D=3D=3D=3D=3D=3D=0A=
     a stream type=0A=
          STYPE         (alert | heartbeat | config)    "alert"=0A=
  -->=0A=
=0A=
<!ENTITY % STYPE        (alert|heartbeat|config)>=0A=
=0A=
<!ELEMENT streamType    EMPTY>=0A=
<!ATTLIST streamType=0A=
          type          %STYPE    #REQUIRED>=0A=
=0A=
<!-- End of DTD -->=0A=
=0A=
.bp=0A=
.fi=0A=
.in 3=0A=
.ti 0=0A=
9. Reply Codes=0A=
=0A=
This section lists the three-digit error codes the IDXP profile may=0A=
generate.=0A=
.nf=0A=
=0A=
code    meaning=0A=
=3D=3D=3D=3D    =3D=3D=3D=3D=3D=3D=3D=0A=
421     Service not available=0A=
        (E.g., the peer does not have sufficient resources.)=0A=
=0A=
450     Requested action not taken=0A=
        (E.g., DNS lookup failed or connection could not=0A=
         be established. See also 550.)=0A=
=0A=
454     Temporary authentication failure=0A=
=0A=
500     General syntax error=0A=
        (E.g., poorly-formed XML)=0A=
=0A=
501     Syntax error in parameters=0A=
        (E.g., non-valid XML)=0A=
=0A=
504     Parameter not implemented=0A=
=0A=
530     Authentication required=0A=
=0A=
534     Authentication mechanism insufficient=0A=
        (E.g., cipher suite too weak, sequence exhausted, etc.)=0A=
=0A=
535     Authentication failure=0A=
=0A=
537     Action not authorized for user=0A=
=0A=
550     Requested action not taken=0A=
        (E.g., peer could be contacted, but=0A=
         malformed greeting or no IDXP profile advertised.)=0A=
=0A=
553     Parameter invalid=0A=
=0A=
554     Transaction failed=0A=
        (E.g., policy violation)=0A=
=0A=
.bp=0A=
.fi=0A=
.in 4=0A=
.ti 0=0A=
10. Security Considerations=0A=
.in 3=0A=
=0A=
The IDXP profile is a profile of BEEP.  In BEEP, transport security,=0A=
user authentication, and data exchange are orthogonal.  Refer to=0A=
Section 8 of [8] for a discussion of this.  It is strongly=0A=
recommended that those wanting to use the IDXP profile initially=0A=
negotiate a BEEP security profile between the peers that offers the=0A=
required security properties.  The TLS profile SHOULD be used to=0A=
provide for transport security.  See Section 5 for a discussion of=0A=
how IDXP fulfills the IDWG communications protocol requirements.=0A=
=0A=
See Section 2.4 for a discussion of the trust model.=0A=
=0A=
.in 5=0A=
.ti 0=0A=
10.1 Use of the TUNNEL Profile=0A=
.in 3=0A=
=0A=
See Section 5 for IDXP's requirements on application-layer tunneling=0A=
and the TUNNEL profile specifically.  See Section 7 of [7] for a=0A=
discussion of the security considerations inherent in the use of the=0A=
TUNNEL profile.=0A=
=0A=
.in 5=0A=
.ti 0=0A=
10.2 Use of Underlying Security Profiles=0A=
.in 3=0A=
=0A=
At present, the TLS profile is the only BEEP security profile known=0A=
to meet all of the requirements set forth in Section 5 of [9].  When=0A=
securing a BEEP session with the TLS profile, the=0A=
TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA cipher suite offers an acceptable=0A=
level of security.  See Section 5 for a discussion of how IDXP=0A=
fulfills the IDWG communications requirements through the use of an=0A=
underlying security profile.=0A=
.bp=0A=
.ti 0=0A=
References=0A=
=0A=
.in 8=0A=
.ti 3=0A=
[1]  Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform =
Resource=0A=
Identifiers (URI): Generic Syntax", RFC 2396, August 1998.=0A=
=0A=
.ti 3=0A=
[2]  Bradner, S., "Key words for use in RFCs to Indicate Requirement=0A=
Levels", BCP 14, RFC 2119, March 1997.=0A=
=0A=
.ti 3=0A=
[3]  Bray, T., Paoli, J., Sperberg-McQueen, C. and E. Maler,=0A=
"Extensible Markup Language (XML) 1.0 (2nd ed)", W3C REC-xml,=0A=
October 2000, <http://www.w3.org/TR/REC-xml>.=0A=
=0A=
.ti 3=0A=
[4]  Curry, D. and H. Debar, "Intrusion Detection Message Exchange=0A=
Format Data Model and Extensible Markup Language (XML) Document=0A=
Type Definition", RFC XXXX, Month YYYY.=0A=
=0A=
.ti 3=0A=
[5]  Freed, N. and N. Borenstein, "Multipurpose Internet Mail=0A=
Extensions (MIME) Part Two: Media Types", RFC 2046, November=0A=
1996.=0A=
=0A=
.ti 3=0A=
[6]  Mockapetris, P., "Domain names - concepts and facilities", STD=0A=
13, RFC 1034, November 1987.=0A=
=0A=
.ti 3=0A=
[7]  New, D., "The TUNNEL Profile Registration", RFC XXXX, Month=0A=
YYYY.=0A=
=0A=
.ti 3=0A=
[8]  Rose, M., "The Blocks Extensible Exchange Protocol Core", RFC=0A=
3080, March 2001.=0A=
=0A=
.ti 3=0A=
[9]  Wood, M. and M. Erlinger, "Intrusion Detection Message Exchange=0A=
Requirements", RFC XXXX, Month YYYY.=0A=
=0A=
=0A=
.in 3=0A=
.nf=0A=
.ti 0=0A=
Authors' Addresses=0A=
=0A=
Benjamin S. Feinstein=0A=
Guardent, Inc.=0A=
=0A=
EMail: Ben.Feinstein@guardent.com=0A=
URI:   http://www.guardent.com/=0A=
=0A=
=0A=
Gregory A. Matthews=0A=
CSC/NASA Ames Research Center=0A=
=0A=
EMail: gmatthew@nas.nasa.gov=0A=
URI:   http://www.nas.nasa.gov/=0A=
.bp=0A=
John C. C. White=0A=
MITRE Corporation=0A=
=0A=
EMail: jccw@mitre.org=0A=
URI:   http://www.mitre.org/=0A=
.bp=0A=
.fi=0A=
.in 12=0A=
.ti 0=0A=
Appendix A. IANA Considerations=0A=
.in 3=0A=
=0A=
The IANA registers "IDXP" as a standards-track BEEP profile, as=0A=
specified in Section 7.1.  The IANA changes the IDXP profile=0A=
identification to "http://iana.org/beep/IDXP".=0A=
=0A=
The IANA registers "idxp" as a TCP port number, as specified in=0A=
Section 7.2=0A=
=0A=
The IANA maintains a list of:=0A=
=0A=
.in 6=0A=
.ti 3=0A=
IDXP options, c.f., Section 6.=0A=
=0A=
.in 3=0A=
For this list, the IESG is responsible for assigning a designated=0A=
expert to review the specification prior to the IANA making the=0A=
assignment.  As a courtesy to developers of non-standards track IDXP=0A=
options, the mailing list idxp-java-users@lists.sourceforge.net may=0A=
be used to solicit commentary.=0A=
=0A=
The IANA makes the registrations specified in Section 7.3 and =
Section=0A=
7.4.=0A=
.bp=0A=
.in 12=0A=
.ti 0=0A=
Appendix B. History of Significant Changes=0A=
.in 3=0A=
=0A=
The RFC Editor should remove this section and its corresponding TOC=0A=
references prior to publication.=0A=
=0A=
.in 4=0A=
.ti 0=0A=
B.1 Significant Changes Since beep-idxp-04=0A=
.in 3=0A=
=0A=
Added sentence to Section 3.4 explaining the situation in which an=0A=
"error" element may be issued within an "RPY" message.=0A=
=0A=
Modified examples in Section 4.1 and 4.2, changing the message types=0A=
from "RPY" to "ERR" for the negative response sent by the client.=0A=
=0A=
Fixed two locations where we were referencing the wrong section of=0A=
the requirements document.=0A=
=0A=
Removed references to IP and the %IP attribute.=0A=
=0A=
Modified part of Section 5 dealing with non-repudiation of message=0A=
origin.=0A=
=0A=
Modified Section 1.3 to further refine terminology.=0A=
=0A=
Replaced all remaining references to "entities" with references to=0A=
"peers".=0A=
=0A=
.in 4=0A=
.ti 0=0A=
B.2 Significant Changes Since beep-idxp-03=0A=
.in 3=0A=
=0A=
Modified references to Internet-Drafts to contain placeholders for=0A=
their forthcoming RFC numbers.=0A=
=0A=
Modified IDMEF formal public identifier (FPI) in the IDXP DTD to=0A=
reflect the changes in draft-ietf-idwg-idmef-xml-06.=0A=
=0A=
Modified IDXP FPI for the IDXP DTD to be more in line with the IDMEF=0A=
FPI.=0A=
=0A=
.in 4=0A=
.ti 0=0A=
B.3 Significant Changes Since beep-idxp-02=0A=
.in 3=0A=
=0A=
Added IDXP option registration template and registered two initial=0A=
options.=0A=
=0A=
Indicated that the IANA should change the profile identification to=0A=
"http://iana.org/beep/IDXP" upon adoption of IDXP as a standards-=0A=
track BEEP profile.=0A=
=0A=
Renamed the "Options" element to "Option" and allowed multiple=0A=
"Option" sub-elements within an "IDXP-Greeting" element.  Also added=0A=
.bp=0A=
attributes to "Option" element.=0A=
=0A=
Modified IANA profile registration and added TCP port number IANA=0A=
registration.=0A=
=0A=
Reordered some sections to improve the flow of the document.=0A=
=0A=
Changed IDXP DTD identifier to be more IETF-like and removed URLs=0A=
from ENTITY declarations.=0A=
=0A=
Changed IDXP profile URI to fall under the "http://iana.org/beep/=0A=
transient" namespace.=0A=
=0A=
Modified Section 1.3 to reference the requirements language =
specified=0A=
by [2].=0A=
=0A=
Eliminated the use of the "endpoint" terminology, in favor of =
"peer".=0A=
=0A=
Modified figures to make them more understandable.=0A=
=0A=
Modified Sections 2, 3, and 4 to use the requirements language=0A=
specified by [2].=0A=
=0A=
Indicated that the RFC Editor should remove Appendix B and its=0A=
corresponding TOC reference prior to publication.=0A=
=0A=
Fixed several typos.=0A=
=0A=
.in 4=0A=
.ti 0=0A=
B.4 Significant Changes Since beep-idxp-01=0A=
.in 3=0A=
=0A=
Added new MUST and SHOULD language for use of TLS and TUNNEL=0A=
profiles.=0A=
=0A=
Modified the "IDXP-Greeting" element to include an "Options" sub-=0A=
element.=0A=
=0A=
Changed IDXP profile URI.=0A=
=0A=
.in 4=0A=
.ti 0=0A=
B.5 Significant Changes Since beep-idxp-00=0A=
.in 3=0A=
=0A=
Added Section 5, describing how IDXP fulfills the communication=0A=
protocol requirements of the IDWG.=0A=
=0A=
Moved IDXP profile registration to Appendix A.=0A=
=0A=
Clarified the role that underlying BEEP security profiles must play.=0A=
=0A=
Clarified how IDMEF messages fit into IDXP.=0A=
.bp=0A=
Clarified how the IDXP profile channels and BEEP sessions interact.=0A=
=0A=
Made terminology clarifications and changes for overall consistency.=0A=
.bp=0A=
.in 12=0A=
.ti 0=0A=
Appendix C. Acknowledgements=0A=
.in 3=0A=
=0A=
The authors gratefully acknowledge the contributions of Darren New,=0A=
Marshall T.  Rose, Roy Pollock, Tim Buchheim, Mike Erlinger, and =
Paul=0A=
Osterwald.=0A=
.bp=0A=
.ti 0=0A=
Full Copyright Statement=0A=
=0A=
Copyright (C) The Internet Society (2002).  All Rights Reserved.=0A=
=0A=
This document and translations of it may be copied and furnished to=0A=
others, and derivative works that comment on or otherwise explain it=0A=
or assist in its implementation may be prepared, copied, published=0A=
and distributed, in whole or in part, without restriction of any=0A=
kind, provided that the above copyright notice and this paragraph =
are=0A=
included on all such copies and derivative works.  However, this=0A=
document itself may not be modified in any way, such as by removing=0A=
the copyright notice or references to the Internet Society or other=0A=
Internet organizations, except as needed for the purpose of=0A=
developing Internet standards in which case the procedures for=0A=
copyrights defined in the Internet Standards process must be=0A=
followed, or as required to translate it into languages other than=0A=
English.=0A=
=0A=
The limited permissions granted above are perpetual and will not be=0A=
revoked by the Internet Society or its successors or assigns.=0A=
=0A=
This document and the information contained herein is provided on an=0A=
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING=0A=
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING=0A=
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION=0A=
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF=0A=
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.=0A=
=0A=
.ti 0=0A=
Acknowledgement=0A=
=0A=
Funding for the RFC Editor function is currently provided by the=0A=
Internet Society.=0A=
=0A=

------_=_NextPart_000_01C21632.D6E39490
Content-Type: text/html;
	name="draft-ietf-idwg-beep-idxp-05.html"
Content-Disposition: attachment;
	filename="draft-ietf-idwg-beep-idxp-05.html"
Content-Transfer-Encoding: quoted-printable

Content-Type: text/html=0A=
=0A=
<html><head><title>The Intrusion Detection Exchange Protocol =
(IDXP)</title>=0A=
<STYLE type=3D'text/css'>=0A=
    .title { color: #990000; font-size: 22px; line-height: 22px; =
font-weight: bold; text-align: right;=0A=
             font-family: helvetica, arial, sans-serif }=0A=
    .filename { color: #666666; font-size: 18px; line-height: 28px; =
font-weight: bold; text-align: right;=0A=
                  font-family: helvetica, arial, sans-serif }=0A=
    p.copyright { color: #000000; font-size: 10px;=0A=
                  font-family: verdana, charcoal, helvetica, arial, =
sans-serif }=0A=
    p { margin-left: 2em; margin-right: 2em; }=0A=
    li { margin-left: 3em;  }=0A=
    ol { margin-left: 2em; margin-right: 2em; }=0A=
    ul.text { margin-left: 2em; margin-right: 2em; }=0A=
    pre { margin-left: 3em; color: #333333 }=0A=
    ul.toc { color: #000000; line-height: 16px;=0A=
             font-family: verdana, charcoal, helvetica, arial, =
sans-serif }=0A=
    H3 { color: #333333; font-size: 16px; line-height: 16px; =
font-family: helvetica, arial, sans-serif }=0A=
    H4 { color: #000000; font-size: 14px; font-family: helvetica, =
arial, sans-serif }=0A=
    TD.header { color: #ffffff; font-size: 10px; font-family: arial, =
helvetica, san-serif; valign: top }=0A=
    TD.author-text { color: #000000; font-size: 10px;=0A=
                     font-family: verdana, charcoal, helvetica, arial, =
sans-serif }=0A=
    TD.author { color: #000000; font-weight: bold; margin-left: 4em; =
font-size: 10px; font-family: verdana, charcoal, helvetica, arial, =
sans-serif }=0A=
     A:link { color: #990000; font-weight: bold;=0A=
              font-family: MS Sans Serif, verdana, charcoal, helvetica, =
arial, sans-serif }=0A=
     A:visited { color: #333333; font-weight: bold;=0A=
                 font-family: MS Sans Serif, verdana, charcoal, =
helvetica, arial, sans-serif }=0A=
     A:name { color: #333333; font-weight: bold;=0A=
              font-family: MS Sans Serif, verdana, charcoal, helvetica, =
arial, sans-serif }=0A=
    .link2 { color:#ffffff; font-weight: bold; text-decoration: =
none;=0A=
             font-family: monaco, charcoal, geneva, MS Sans Serif, =
helvetica, monotype, verdana, sans-serif;=0A=
             font-size: 9px }=0A=
    .RFC { color:#666666; font-weight: bold; text-decoration: none;=0A=
           font-family: monaco, charcoal, geneva, MS Sans Serif, =
helvetica, monotype, verdana, sans-serif;=0A=
           font-size: 9px }=0A=
    .hotText { color:#ffffff; font-weight: normal; text-decoration: =
none;=0A=
               font-family: charcoal, monaco, geneva, MS Sans Serif, =
helvetica, monotype, verdana, sans-serif;=0A=
               font-size: 9px }=0A=
</style>=0A=
</head>=0A=
<body bgcolor=3D"#ffffff" text=3D"#000000" alink=3D"#000000" =
vlink=3D"#666666" link=3D"#990000">=0A=
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>=0A=
<table width=3D"66%" border=3D"0" cellpadding=3D"0" =
cellspacing=3D"0"><tr><td><table width=3D"100%" border=3D"0" =
cellpadding=3D"2" cellspacing=3D"1">=0A=
<tr valign=3D"top"><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">Intrusion Detection Exchange</td><td width=3D"33%" =
bgcolor=3D"#666666" class=3D"header">B. Feinstein</td></tr>=0A=
<tr valign=3D"top"><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">Format</td><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">Guardent, Inc.</td></tr>=0A=
<tr valign=3D"top"><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">Internet-Draft</td><td width=3D"33%" =
bgcolor=3D"#666666" class=3D"header">G. Matthews</td></tr>=0A=
<tr valign=3D"top"><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">Expires: December 16, 2002</td><td width=3D"33%" =
bgcolor=3D"#666666" class=3D"header">CSC/NASA Ames Research =
Center</td></tr>=0A=
<tr valign=3D"top"><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">&nbsp;</td><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">J. White</td></tr>=0A=
<tr valign=3D"top"><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">&nbsp;</td><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">MITRE Corporation</td></tr>=0A=
<tr valign=3D"top"><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">&nbsp;</td><td width=3D"33%" bgcolor=3D"#666666" =
class=3D"header">June 17, 2002</td></tr>=0A=
</table></td></tr></table>=0A=
<div align=3D"right"><font face=3D"monaco, MS Sans Serif" =
color=3D"#990000" size=3D"+3"><b><br><span class=3D"title">The =
Intrusion Detection Exchange Protocol (IDXP)</span></b></font></div>=0A=
<div align=3D"right"><font face=3D"monaco, MS Sans Serif" =
color=3D"#666666" size=3D"+2"><b><span =
class=3D"filename">draft-ietf-idwg-beep-idxp-05</span></b></font></div>=0A=
<font face=3D"verdana, helvetica, arial, sans-serif" size=3D"2">=0A=
=0A=
<h3>Status of this Memo</h3>=0A=
<p>=0A=
This document is an Internet-Draft and is in full conformance with all =
provisions of Section 10 of RFC2026.</p>=0A=
<p>=0A=
Internet-Drafts are working documents of the Internet Engineering=0A=
Task Force (IETF), its areas, and its working groups.=0A=
Note that other groups may also distribute working documents as=0A=
Internet-Drafts.</p>=0A=
<p>=0A=
Internet-Drafts are draft documents valid for a maximum of six =
months=0A=
and may be updated, replaced, or obsoleted by other documents at any =
time.=0A=
It is inappropriate to use Internet-Drafts as reference material or to =
cite=0A=
them other than as "work in progress."</p>=0A=
<p>=0A=
The list of current Internet-Drafts can be accessed at=0A=
<a =
href=3D'http://www.ietf.org/ietf/1id-abstracts.txt'>http://www.ietf.org/=
ietf/1id-abstracts.txt</a>.</p>=0A=
<p>=0A=
The list of Internet-Draft Shadow Directories can be accessed at=0A=
<a =
href=3D'http://www.ietf.org/shadow.html'>http://www.ietf.org/shadow.html=
</a>.</p>=0A=
<p>=0A=
This Internet-Draft will expire on December 16, 2002.</p>=0A=
=0A=
<h3>Copyright Notice</h3>=0A=
<p>=0A=
Copyright (C) The Internet Society (2002). All Rights Reserved.</p>=0A=
=0A=
<h3>Abstract</h3>=0A=
=0A=
<p>This memo describes the Intrusion Detection Exchange Protocol =
(IDXP), an application-level protocol for exchanging data between =
intrusion detection entities. IDXP supports mutual-authentication, =
integrity, and confidentiality over a connection-oriented protocol. The =
protocol provides for the exchange of IDMEF messages, unstructured =
text, and binary data. The IDMEF message elements are described in the =
<a href=3D"#refs.IDMEF">Intrusion Detection Message Exchange Format =
(IDMEF)</a>[4], a companion document of the Intrusion Detection =
Exchange Format (IDWG) working group of the IETF.=0A=
</p><a name=3D"toc"><br><hr size=3D"1" shade=3D"0"></a>=0A=
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>=0A=
<h3>Table of Contents</h3>=0A=
<ul compact class=3D"toc">=0A=
<b><a href=3D"#intro">1.</a>&nbsp;=0A=
Introduction<br></b>=0A=
<b><a href=3D"#purpose">1.1</a>&nbsp;=0A=
Purpose<br></b>=0A=
<b><a href=3D"#anchor1">1.2</a>&nbsp;=0A=
Profiles<br></b>=0A=
<b><a href=3D"#terminology">1.3</a>&nbsp;=0A=
Terminology<br></b>=0A=
<b><a href=3D"#model">2.</a>&nbsp;=0A=
The Model<br></b>=0A=
<b><a href=3D"#connect">2.1</a>&nbsp;=0A=
Connection Provisioning<br></b>=0A=
<b><a href=3D"#transfer">2.2</a>&nbsp;=0A=
Data Transfer<br></b>=0A=
<b><a href=3D"#anchor2">2.3</a>&nbsp;=0A=
Connection Teardown<br></b>=0A=
<b><a href=3D"#trust">2.4</a>&nbsp;=0A=
Trust Model<br></b>=0A=
<b><a href=3D"#IDXP-profile">3.</a>&nbsp;=0A=
The IDXP Profile<br></b>=0A=
<b><a href=3D"#anchor3">3.1</a>&nbsp;=0A=
IDXP Profile Overview<br></b>=0A=
<b><a href=3D"#anchor4">3.2</a>&nbsp;=0A=
IDXP Profile Identification and Initialization<br></b>=0A=
<b><a href=3D"#IDXP-syntax">3.3</a>&nbsp;=0A=
IDXP Profile Message Syntax<br></b>=0A=
<b><a href=3D"#IDXP-semantics">3.4</a>&nbsp;=0A=
IDXP Profile Semantics<br></b>=0A=
<b><a href=3D"#anchor5">3.4.1</a>&nbsp;=0A=
The IDXP-GREETING Element<br></b>=0A=
<b><a href=3D"#anchor6">3.4.2</a>&nbsp;=0A=
The OPTION Element<br></b>=0A=
<b><a href=3D"#anchor7">3.4.3</a>&nbsp;=0A=
The IDMEF-MESSAGE Element<br></b>=0A=
<b><a href=3D"#idxp_options">4.</a>&nbsp;=0A=
IDXP Options<br></b>=0A=
<b><a href=3D"#priority_option">4.1</a>&nbsp;=0A=
The channelPriority Option<br></b>=0A=
<b><a href=3D"#type_option">4.2</a>&nbsp;=0A=
The streamType Option<br></b>=0A=
<b><a href=3D"#proto-reqs">5.</a>&nbsp;=0A=
Fulfillment of IDWG Communications Protocol Requirements<br></b>=0A=
<b><a href=3D"#option_reg">6.</a>&nbsp;=0A=
IDXP Option Registration Template<br></b>=0A=
<b><a href=3D"#anchor8">7.</a>&nbsp;=0A=
Initial Registrations<br></b>=0A=
<b><a href=3D"#idxp-registration">7.1</a>&nbsp;=0A=
Registration: The IDXP Profile<br></b>=0A=
<b><a href=3D"#port-registration">7.2</a>&nbsp;=0A=
Registration: The System (Well-Known) TCP port number for =
IDXP<br></b>=0A=
<b><a href=3D"#priority_opt_reg">7.3</a>&nbsp;=0A=
Registration: The channelPriority Option<br></b>=0A=
<b><a href=3D"#type_opt_reg">7.4</a>&nbsp;=0A=
Registration: The streamType Option<br></b>=0A=
<b><a href=3D"#anchor9">8.</a>&nbsp;=0A=
The DTDs<br></b>=0A=
<b><a href=3D"#idxp_dtd">8.1</a>&nbsp;=0A=
The IDXP DTD<br></b>=0A=
<b><a href=3D"#priority_dtd">8.2</a>&nbsp;=0A=
The channelPriority Option DTD<br></b>=0A=
<b><a href=3D"#st_dtd">8.3</a>&nbsp;=0A=
The streamType DTD<br></b>=0A=
<b><a href=3D"#anchor10">9.</a>&nbsp;=0A=
Reply Codes<br></b>=0A=
<b><a href=3D"#security">10.</a>&nbsp;=0A=
Security Considerations<br></b>=0A=
<b><a href=3D"#security.tunnel">10.1</a>&nbsp;=0A=
Use of the TUNNEL Profile<br></b>=0A=
<b><a href=3D"#anchor11">10.2</a>&nbsp;=0A=
Use of Underlying Security Profiles<br></b>=0A=
<b><a href=3D"#rfc.references1">&#167;</a>&nbsp;=0A=
References<br></b>=0A=
<b><a href=3D"#rfc.authors">&#167;</a>&nbsp;=0A=
Authors' Addresses<br></b>=0A=
<b><a href=3D"#IANA">A.</a>&nbsp;=0A=
IANA Considerations<br></b>=0A=
<b><a href=3D"#changes">B.</a>&nbsp;=0A=
History of Significant Changes<br></b>=0A=
<b><a href=3D"#anchor12">B.1</a>&nbsp;=0A=
Significant Changes Since beep-idxp-04<br></b>=0A=
<b><a href=3D"#anchor13">B.2</a>&nbsp;=0A=
Significant Changes Since beep-idxp-03<br></b>=0A=
<b><a href=3D"#anchor14">B.3</a>&nbsp;=0A=
Significant Changes Since beep-idxp-02<br></b>=0A=
<b><a href=3D"#anchor15">B.4</a>&nbsp;=0A=
Significant Changes Since beep-idxp-01<br></b>=0A=
<b><a href=3D"#anchor16">B.5</a>&nbsp;=0A=
Significant Changes Since beep-idxp-00<br></b>=0A=
<b><a href=3D"#anchor17">C.</a>&nbsp;=0A=
Acknowledgements<br></b>=0A=
<b><a href=3D"#rfc.copyright">&#167;</a>&nbsp;=0A=
Full Copyright Statement<br></b>=0A=
</ul>=0A=
<br clear=3D"all">=0A=
=0A=
<a name=3D"intro"><br><hr size=3D"1" shade=3D"0"></a>=0A=
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>=0A=
<a name=3D"rfc.section.1"></a><h3>1.&nbsp;Introduction</h3>=0A=
=0A=
<p>IDXP is specified, in part, as a <a href=3D"#RFC3080">Blocks =
Extensible Exchange Protocol (BEEP)</a>[8] "profile". BEEP is a generic =
application protocol framework for connection-oriented, asynchronous =
interactions. Features such as authentication and confidentiality are =
provided through the use of other BEEP profiles. Accordingly, many =
aspects of IDXP (e.g., confidentiality) are provided within the BEEP =
framework.=0A=
</p>=0A=
<a name=3D"rfc.section.1.1"></a><h4><a =
name=3D"purpose">1.1</a>&nbsp;Purpose</h4>=0A=
=0A=
<p>IDXP provides for the exchange of <a =
href=3D"#refs.IDMEF">IDMEF</a>[4] messages, unstructured text, and =
binary data between intrusion detection entities. Addressing the =
security-sensitive nature of exchanges between intrusion detection =
entities, underlying BEEP security profiles should be used to offer =
IDXP the required set of security properties. See <a =
href=3D"#proto-reqs">Fulfillment of IDWG Communications Protocol =
Requirements</a> for a discussion of how IDXP fulfills the IDWG =
communication protocol requirements. See <a href=3D"#security">Security =
Considerations</a> for a discussion of security considerations.=0A=
</p>=0A=
<p>IDXP is primarily intended for the exchange of data created by =
intrusion detection entities. <a href=3D"#refs.IDMEF">IDMEF</a>[4] =
messages should be used for the structured representation of this =
intrusion detection data, although IDXP may be used to exchange =
unstructured text and binary data.=0A=
</p>=0A=
<a name=3D"rfc.section.1.2"></a><h4><a =
name=3D"anchor1">1.2</a>&nbsp;Profiles</h4>=0A=
=0A=
<p>There are several BEEP profiles discussed, the first of which we =
define in this memo:=0A=
</p>=0A=
<p>=0A=
<blockquote class=3D"text">=0A=
<p>The IDXP Profile=0A=
</p>=0A=
<p><a href=3D"#refs.tunnel">The TUNNEL Profile</a>[7]=0A=
</p>=0A=
<p>The Simple Authentication and Security Layer (SASL) Family of =
Profiles (c.f., Section 4.1 of <a href=3D"#RFC3080">[8]</a>)=0A=
</p>=0A=
<p>The TLS Profile (c.f., Section 3.1 of <a =
href=3D"#RFC3080">[8]</a>)=0A=
</p>=0A=
</blockquote><p>=0A=
</p>=0A=
<a name=3D"rfc.section.1.3"></a><h4><a =
name=3D"terminology">1.3</a>&nbsp;Terminology</h4>=0A=
=0A=
<p>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", =
"SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and "OPTIONAL" in this =
document are to be interpreted as described in <a href=3D"#RFC2119">RFC =
2119</a>[2].=0A=
</p>=0A=
<p>Throughout this memo, the terms "analyzer" and "manager" are used in =
the context of the <a href=3D"#refs.IDWG-reqs">Intrusion Detection =
Message Exchange Requirements</a>[9]. In particular, Section 3.2 of <a =
href=3D"#refs.IDWG-reqs">[9]</a> defines the meaning of a collection of =
intrusion detection terms.=0A=
</p>=0A=
<p>The terms "peer", "initiator", "listener", "client", and "server", =
and the=0A=
characters "I", "L", "C", and "S" are used in the context of <a =
href=3D"#RFC3080">BEEP</a>[8].=0A=
 In particular, Section 2.1 of BEEP discusses the roles that a BEEP =
peer may perform.=0A=
</p>=0A=
<p>The term "Document Type Declaration" is abbreviated as "DTD" and is =
defined in Section 2.8 of the=0A=
<a href=3D"#W3C.REC-xml">Extensible Markup Language (XML)</a>[3].=0A=
</p>=0A=
<p>Note that the term "proxy" is specific to IDXP, and does not exist =
in the=0A=
context of BEEP. The term "intrusion detection" is abbreviated as =
"ID".=0A=
</p>=0A=
<a name=3D"model"><br><hr size=3D"1" shade=3D"0"></a>=0A=
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>=0A=
<a name=3D"rfc.section.2"></a><h3>2.&nbsp;The Model</h3>=0A=
=0A=
<a name=3D"rfc.section.2.1"></a><h4><a =
name=3D"connect">2.1</a>&nbsp;Connection Provisioning</h4>=0A=
=0A=
<p>Intrusion detection entities using IDXP to transfer data are termed =
IDXP peers. Peers can exist only in pairs, and these pairs communicate =
over a single BEEP session with one or more BEEP channels opened for =
transferring data. Peers are either managers or analyzers, as defined =
in Section 3.2 of <a href=3D"#refs.IDWG-reqs">[9]</a>.=0A=
</p>=0A=
<p> The relationship between analyzers and managers is potentially =
many-to-many. I.e., an analyzer MAY communicate with many managers; =
similarly, a manager MAY communicate with many analyzers. Likewise, the =
relationship between different managers is potentially many-to-many, so =
that a manager MAY receive the alerts sent by a large number of =
analyzers by receiving them through intermediate managers. Analyzers =
MUST NOT establish IDXP exchanges with other analyzers.=0A=
</p>=0A=
<p>An IDXP peer wishing to establish IDXP communications with another =
IDXP peer does so by opening a BEEP channel, which may entail =
initiating a BEEP session. A BEEP security profile offering the =
required security properties SHOULD initially be negotiated (see <a =
href=3D"#security">Security Considerations</a> for a discussion of =
security considerations). Following the successful negotiation of the =
BEEP security profile, IDXP greetings are exchanged and connection =
provisioning proceeds.=0A=
</p>=0A=
<p>In the following sequence a peer 'Alice' initiates an IDXP exchange =
with the peer 'Bob'.=0A=
</p></font><pre>=0A=
     Alice                                               Bob=0A=
       ---------------- xport connect[1] ------------------>=0A=
      &lt;-------------------- greeting ---------------------->=0A=
      &lt;-------------start security profile[2] ------------->=0A=
      &lt;-------------------- greeting ---------------------->=0A=
      &lt;------------------ start IDXP[3] ------------------->=0A=
</pre><font face=3D"verdana, helvetica, arial, sans-serif" =
size=3D"2">=0A=
=0A=
<p>Notes:=0A=
</p>=0A=
<p>=0A=
<blockquote class=3D"text"><dl>=0A=
<dt>[1]</dt>=0A=
<dd>'Alice' initiates a transport connection to 'Bob', triggering the =
exchange of BEEP greeting messages.=0A=
</dd>=0A=
<dt>[2]</dt>=0A=
<dd>both entities negotiate the use of a BEEP security profile.=0A=
</dd>=0A=
<dt>[3]</dt>=0A=
<dd>both entities negotiate the use of the IDXP profile.=0A=
</dd>=0A=
</dl></blockquote><p>=0A=
</p>=0A=
<p>In between a pair of IDXP peers may be an arbitrary number of =
proxies. A proxy may be necessary for administrative reasons, such as =
running on a firewall to allow restricted access. Another use might be =
one proxy per company department, which forwards data from the analyzer =
peers in the department onto a company-wide manager peer.=0A=
</p>=0A=
<p>A BEEP tuning profile MAY be used to create an application-layer =
tunnel that transparently forwards data over a chain of proxies. The <a =
href=3D"#refs.tunnel">TUNNEL profile</a>[7] SHOULD be used for this =
purpose; see <a href=3D"#refs.tunnel">[7]</a> for more detail =
concerning the options available to setup an application-layer tunnel =
using TUNNEL, and see <a href=3D"#security.tunnel">Use of the TUNNEL =
Profile</a> for a discussion of TUNNEL related security considerations. =
TUNNEL MUST be offered as a tuning profile for the creation of =
application-layer tunnels. The TUNNEL profile MUST offer the use of =
some form of SASL authentication (c.f., Section 4.1 of <a =
href=3D"#RFC3080">[8]</a>). Once a tunnel has been created a BEEP =
security profile offering the required security properties SHOULD be =
negotiated, followed by negotiation of the IDXP profile.=0A=
</p>=0A=
<p>The following sequence shows how TUNNEL might be used to create an =
application-layer tunnel through which IDXP would operate. A peer =
'Alice' initiates the creation of a BEEP session using the IDXP profile =
with the entity 'Bob' by first contacting 'proxy1'. In the greeting =
exchange between 'Alice' and 'proxy1', the TUNNEL profile is selected, =
and subsequently the use of the TUNNEL profile is extended to reach =
through 'proxy2' to 'Bob'.=0A=
</p></font><pre>=0A=
Alice              proxy1               proxy2               Bob=0A=
  -- xport connect -->=0A=
 &lt;---- greeting ----->=0A=
  -- start TUNNEL --->=0A=
                      - xport connect[1] ->=0A=
                     &lt;----- greeting ----->=0A=
                      --- start TUNNEL --->=0A=
                                           --- xport connect -->=0A=
                                          &lt;----- greeting ----->=0A=
                                           --- start TUNNEL --->=0A=
                                          &lt;----- &lt;ok>[2] =
------=0A=
                     &lt;------- &lt;ok> -------=0A=
 &lt;------ &lt;ok> -------=0A=
 &lt;------------------------- greeting -------------------------->=0A=
 &lt;------------------ start security profile ------------------->=0A=
 &lt;------------------------- greeting -------------------------->=0A=
 &lt;------------------------ start IDXP ------------------------->=0A=
</pre><font face=3D"verdana, helvetica, arial, sans-serif" =
size=3D"2">=0A=
=0A=
<p>Notes:=0A=
</p>=0A=
<p>=0A=
<blockquote class=3D"text"><dl>=0A=
<dt>[1]</dt>=0A=
<dd>Instead of immediately acknowledging the request from 'Alice' to =
start TUNNEL, 'proxy1' attempts to establish use of TUNNEL with =
'proxy2'. 'proxy2' also delays its acknowledgment to 'proxy1'.=0A=
</dd>=0A=
<dt>[2]</dt>=0A=
<dd>'Bob' acknowledges the request from 'proxy2' to start TUNNEL, and =
this acknowledgment propagates back to 'Alice' so that a TUNNEL =
application-layer tunnel is established from 'Alice' to 'Bob'.=0A=
</dd>=0A=
</dl></blockquote><p>=0A=
</p>=0A=
<a name=3D"rfc.section.2.2"></a><h4><a =
name=3D"transfer">2.2</a>&nbsp;Data Transfer</h4>=0A=
=0A=
<p>Between a pair of ID entities communicating over a BEEP session, one =
or more BEEP channels MAY be opened using the IDXP profile. If desired, =
additional BEEP sessions MAY be established to offer additional =
channels using the IDXP profile. However, in most situations additional =
channels using the IDXP profile SHOULD be opened within an existing =
BEEP session, as opposed to provisioning a new BEEP session containing =
the additional channels using the IDXP profile.=0A=
</p>=0A=
<p>Peers assume the role of client or server on a per-channel basis, =
with one acting as the client and the other as the server. A peer's =
role of client or server is determined independent of whether the peer =
assumed the role of initiator or listener during the BEEP session =
establishment. Clients and servers act as sources and sinks, =
respectively, for exchanging data.=0A=
</p>=0A=
<p>In a simple case, an analyzer peer sends data to a manager peer. =
E.g.,=0A=
</p></font><pre>=0A=
        +----------+                          +----------+=0A=
        |          |                          |          |=0A=
        |          |****** BEEP session ******|          |=0A=
        |          |                          |          |=0A=
        | Analyzer | ----- IDXP profile ----> | Manager  |=0A=
        | (Client) |                          | (Server) |=0A=
        |          |                          |          |=0A=
        |          |**************************|          |=0A=
        |          |                          |          |=0A=
        +----------+                          +----------+=0A=
</pre><font face=3D"verdana, helvetica, arial, sans-serif" =
size=3D"2">=0A=
=0A=
<p>Use of multiple BEEP channels in a BEEP session facilitates =
categorization and prioritization of data sent between IDXP peers. For =
example, a manager 'M1', sending alert data to another manager, 'M2', =
may choose to open a separate channel to exchange different categories =
of alerts. 'M1' would act as the client on each of these channels, and =
manager 'M2' can then process and act on the incoming alerts based on =
their respective channel categorizations. See <a =
href=3D"#idxp_options">IDXP Options</a> for more detail on how to =
incorporate categorization and/or prioritization into channel =
creation.=0A=
</p></font><pre>=0A=
+----------+                                            +----------+=0A=
|          |                                            |          |=0A=
|          |*************** BEEP session ***************|          |=0A=
|          |                                            |          |=0A=
|          | -- IDXP profile, network-based alerts ---> |          |=0A=
| Manager  |                                            | Manager  |=0A=
|   M1     | ---- IDXP profile, host-based alerts ----> |   M2     |=0A=
| (Client) |                                            | (Server) |=0A=
|          | ------ IDXP profile, other alerts -------> |          |=0A=
|          |                                            |          |=0A=
|          |********************************************|          |=0A=
|          |                                            |          |=0A=
+----------+                                            +----------+=0A=
</pre><font face=3D"verdana, helvetica, arial, sans-serif" =
size=3D"2">=0A=
=0A=
<a name=3D"rfc.section.2.3"></a><h4><a =
name=3D"anchor2">2.3</a>&nbsp;Connection Teardown</h4>=0A=
=0A=
<p>An IDXP peer may choose to close an IDXP channel under many =
different circumstances (e.g., an error in processing has occurred). To =
close a channel, the peer sends a "close" element (c.f., Section =
2.3.1.3 of <a href=3D"#RFC3080">[8]</a>) on channel zero indicating =
which channel is being closed. An IDXP peer may also choose to close an =
entire BEEP session by sending a "close" element indicating that =
channel zero is to be closed. Section 2.3.1.3 of <a =
href=3D"#RFC3080">[8]</a> offers a more complete discussion of the =
circumstances under which a BEEP peer is permitted to close a channel =
and the mechanisms for doing so.=0A=
</p>=0A=
<p>It is anticipated that due to the overhead of provisioning an =
application-layer tunnel and/or a BEEP security profile, BEEP sessions =
containing IDXP channels will be long-lived. Additionally, the repeated =
overhead of IDXP channel provisioning (i.e., the exchange of IDXP =
greetings) may be avoided by keeping IDXP channels open even while data =
is not actively being exchanged on them. These are recommendations and, =
as such, IDXP peers may choose to close and re-provision BEEP sessions =
and/or IDXP channels as they see fit.=0A=
</p>=0A=
<a name=3D"rfc.section.2.4"></a><h4><a =
name=3D"trust">2.4</a>&nbsp;Trust Model</h4>=0A=
=0A=
<p>In our model, trust is placed exclusively in the IDXP peers. Proxies =
are always assumed to be untrustworthy. A BEEP security profile is used =
to establish end-to-end security between pairs of IDXP peers, doing =
away with the need to place trust in any intervening proxies. Only =
after successful negotiation of the underlying security profile are =
IDXP peers to be trusted. Only BEEP security profiles offering at least =
the protections required by Section 5 of <a =
href=3D"#refs.IDWG-reqs">[9]</a> should be used to secure a BEEP =
session containing channels using the IDXP profile. See Section 3 of <a =
href=3D"#RFC3080">[8]</a> for the registration of the TLS profile, an =
example of a BEEP security profile meeting the requirements of Section =
5 of <a href=3D"#refs.IDWG-reqs">[9]</a>. See <a =
href=3D"#proto-reqs">Fulfillment of IDWG Communications Protocol =
Requirements</a> for a discussion of how IDXP fulfills the IDWG =
communications protocol requirements.=0A=
</p>=0A=
<a name=3D"IDXP-profile"><br><hr size=3D"1" shade=3D"0"></a>=0A=
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>=0A=
<a name=3D"rfc.section.3"></a><h3>3.&nbsp;The IDXP Profile</h3>=0A=
=0A=
<a name=3D"rfc.section.3.1"></a><h4><a =
name=3D"anchor3">3.1</a>&nbsp;IDXP Profile Overview</h4>=0A=
=0A=
<p>The IDXP profile provides a mechanism for exchanging information =
between intrusion detection entities. A BEEP tuning profile MAY be used =
to create an application-layer tunnel that transparently forwards data =
over a chain of proxies. The <a href=3D"#refs.tunnel">TUNNEL =
profile</a>[7] SHOULD be used for this purpose; see <a =
href=3D"#refs.tunnel">[7]</a> for more detail concerning the options =
available to setup an application-layer tunnel using TUNNEL, and see <a =
href=3D"#security.tunnel">Use of the TUNNEL Profile</a> for a =
discussion of TUNNEL related security considerations. TUNNEL MUST be =
offered as a tuning profile for the creation of application-layer =
tunnels. The TUNNEL profile MUST offer the use of some form of SASL =
authentication (c.f., Section 4.1 of <a href=3D"#RFC3080">[8]</a>). The =
TLS profile SHOULD be used to provide the required combination of =
mutual-authentication, integrity, and confidentiality for the IDXP =
profile. For further discussion of application-layer tunnel and =
security issues see <a href=3D"#connect">Connection Provisioning</a> =
and <a href=3D"#security">Security Considerations</a>.=0A=
</p>=0A=
<p>The IDXP profile supports several elements of interest:=0A=
</p>=0A=
<p>=0A=
<ul class=3D"text">=0A=
<li>The "IDXP-Greeting" element identifies an analyzer or manager at =
one end of a BEEP channel to the analyzer or manager at the other end =
of the channel.=0A=
</li>=0A=
<li>The "Option" element is used to convey optional channel parameters =
between peers during the exchange of "IDXP-Greeting" elements. This =
element is OPTIONAL.=0A=
</li>=0A=
<li>The "IDMEF-Message" element carries the structured information to =
be exchanged between the peers.=0A=
</li>=0A=
</ul><p>=0A=
</p>=0A=
<a name=3D"rfc.section.3.2"></a><h4><a =
name=3D"anchor4">3.2</a>&nbsp;IDXP Profile Identification and =
Initialization</h4>=0A=
=0A=
<p>The IDXP profile is identified as=0A=
</p>=0A=
<p>=0A=
<blockquote class=3D"text">=0A=
<p>http://iana.org/beep/transient/idwg/idxp=0A=
</p>=0A=
</blockquote><p>=0A=
</p>=0A=
<p>in the BEEP "profile" element during channel creation.=0A=
</p>=0A=
<p>During channel creation, "IDXP-Greeting" elements MUST be mutually =
exchanged between the peers. An "IDXP-Greeting" element MAY be =
contained within the corresponding "profile" element in the BEEP =
"start" element. Including an "IDXP-Greeting" element in the initial =
"start" element has exactly the same semantics as passing it as the =
first "MSG" message on the channel. If channel creation is successful, =
then before sending the corresponding reply, the BEEP peer processes =
the "IDXP-Greeting" element and includes the resulting response in the =
reply. This response will be an "ok" element or an "error" element. The =
choice of which element is returned is dependent on local provisioning =
of the peer.=0A=
</p>=0A=
<a name=3D"rfc.section.3.3"></a><h4><a =
name=3D"IDXP-syntax">3.3</a>&nbsp;IDXP Profile Message Syntax</h4>=0A=
=0A=
<p>BEEP messages in the profile MUST have a <a href=3D"#RFC2046">MIME =
Content-Type</a>[5] of "text/xml", "text/plain", or =
"application/octet-stream". The syntax of the individual elements is =
specified in <a href=3D"#idxp_dtd">The IDXP DTD</a> and Section 5 of <a =
href=3D"#refs.IDMEF">[4]</a>.=0A=
</p>=0A=
<a name=3D"rfc.section.3.4"></a><h4><a =
name=3D"IDXP-semantics">3.4</a>&nbsp;IDXP Profile Semantics</h4>=0A=
=0A=
<p>Each BEEP peer issues the "IDXP-Greeting" element using "MSG"=0A=
messages. The "IDXP-Greeting" element MAY contain one or more =
"Option"=0A=
sub-elements, conveying optional channel parameters. Each BEEP peer=0A=
then issues "ok" in "RPY" messages or "error" in "ERR" messages. =
(See=0A=
Section 2.3.1 of <a href=3D"#RFC3080">[8]</a> for the definitions of =
the=0A=
"error" and "ok" elements.) An "error" element MAY be issued within a =
"RPY"=0A=
message when piggy-backed within a BEEP "profile" element. See section =
3.4.1 for an=0A=
example of an "error" element being issued within a "RPY" message.=0A=
Based on the respective client/server=0A=
roles negotiated during the exchange of "IDXP-Greeting" elements, =
the=0A=
client sends data using "MSG" messages. Depending on the MIME=0A=
Content-Type, this data may be an "IDMEF-Message" element, plain =
text,=0A=
or binary. The server then issues "ok" in "RPY" messages or "error" =
in=0A=
"ERR" messages.=0A=
</p>=0A=
<a name=3D"rfc.section.3.4.1"></a><h4><a =
name=3D"anchor5">3.4.1</a>&nbsp;The IDXP-GREETING Element</h4>=0A=
=0A=
<p>The "IDXP-Greeting" element serves to identify the analyzer or =
manager at one end of the BEEP channel to the analyzer or manager at =
the other end of the channel. The "IDXP-Greeting" element MUST include =
the role of the peer on the channel (client or server) and the <a =
href=3D"#RFC2396">Uniform Resource Identifier (URI)</a>[1] of the peer. =
Additionally, the "IDXP-Greeting" element MAY include the fully =
qualified domain name (c.f., <a href=3D"#RFC1034">[6]</a>) of the peer. =
One or more "Option" sub-elements MAY be present.=0A=
</p>=0A=
<p>An "IDXP-Greeting" element MAY be sent by either peer at any time. =
The peer receiving the "IDXP-Greeting" MUST respond with an "ok" =
(indicating acceptance), or an "error" (indicating rejection). A peer's =
identity and role on a channel and any optional channel parameters are, =
in effect, specified by the most recent "IDXP-Greeting" it sent that =
was answered with an "ok".=0A=
</p>=0A=
<p>An "IDXP-Greeting" may be rejected (with an "error" element) under =
many circumstances. These include, but are not limited to, =
authentication failure, lack of authorization to connect under the =
specified role, the negotiation of an inadequate ciphersuite, or the =
presence of a channel option that must be understood but was =
unrecognized.=0A=
</p>=0A=
<p>For example, a successful creation with an embedded "IDXP-Greeting" =
might look like this:=0A=
</p></font><pre>=0A=
I: MSG 0 10 . 1592 187=0A=
I: Content-Type: text/xml=0A=
I:=0A=
I: &lt;start number=3D'1'&gt;=0A=
I:   &lt;profile =
uri=3D'http://iana.org/beep/transient/idwg/idxp'&gt;=0A=
I:     &lt;![CDATA[ &lt;IDXP-Greeting =
uri=3D'http://example.com/alice'=0A=
I:       role=3D'client' /&gt; ]]&gt;=0A=
I:   &lt;/profile&gt;=0A=
I: &lt;/start&gt;=0A=
I: END=0A=
L: RPY 0 10 . 1865 91=0A=
L: Content-Type: text/xml=0A=
L:=0A=
L: &lt;profile uri=3D'http://iana.org/beep/transient/idwg/idxp'&gt;=0A=
L:   &lt;![CDATA[ &lt;ok /&gt; ]]&gt;=0A=
L: &lt;/profile&gt;=0A=
L: END=0A=
L: MSG 0 11 . 1956 61=0A=
L: Content-Type: text/xml=0A=
L:=0A=
L: &lt;IDXP-Greeting uri=3D'http://example.com/bob' role=3D'server' =
/&gt;=0A=
L: END=0A=
I: RPY 0 11 . 1779 7=0A=
I: Content-Type: text/xml=0A=
I:=0A=
I: &lt;ok /&gt;=0A=
I: END=0A=
</pre><font face=3D"verdana, helvetica, arial, sans-serif" =
size=3D"2">=0A=
=0A=
<p>A creation with an embedded "IDXP-Greeting" that fails might look =
like this:=0A=
</p></font><pre>=0A=
I: MSG 0 10 . 1776 185=0A=
I: Content-Type: text/xml=0A=
I:=0A=
I: &lt;start number=3D'1'&gt;=0A=
I:   &lt;profile =
uri=3D'http://iana.org/beep/transient/idwg/idxp'&gt;=0A=
I:     &lt;![CDATA[ &lt;IDXP-Greeting uri=3D'http://example.com/eve'=0A=
I:       role=3D'client' /&gt; ]]&gt;=0A=
I:   &lt;/profile&gt;=0A=
I: &lt;/start&gt;=0A=
I: END=0A=
L: RPY 0 10 . 1592 182=0A=
L: Content-Type: text/xml=0A=
L:=0A=
L: &lt;profile uri=3D'http://iana.org/beep/transient/idwg/idxp'&gt;=0A=
L:   &lt;![CDATA[=0A=
L:     &lt;error code=3D'530'&gt;'http://example.com/eve' must first=0A=
L:       negotiate the TLS profile&lt;/error&gt; ]]&gt;=0A=
L: &lt;/profile&gt;=0A=
L: END=0A=
</pre><font face=3D"verdana, helvetica, arial, sans-serif" =
size=3D"2">=0A=
=0A=
<a name=3D"rfc.section.3.4.2"></a><h4><a =
name=3D"anchor6">3.4.2</a>&nbsp;The OPTION Element</h4>=0A=
=0A=
<p>If present, the "Option" element MUST be contained within an =
"IDXP-Greeting" element. An individual "IDXP-Greeting" element MAY =
contain one or more "Option" sub-elements. Each "Option" element within =
an "IDXP-Greeting" element represents a request to enable an IDXP =
option on the channel being negotiated. See <a =
href=3D"#idxp_options">IDXP Options</a> for a complete description of =
IDXP options and the "Option" element.=0A=
</p>=0A=
<a name=3D"rfc.section.3.4.3"></a><h4><a =
name=3D"anchor7">3.4.3</a>&nbsp;The IDMEF-MESSAGE Element</h4>=0A=
=0A=
<p>The "IDMEF-Message" element carries the information to be exchanged =
between the peers. See Section 5 of <a href=3D"#refs.IDMEF">[4]</a> for =
the definition of this element.=0A=
</p>=0A=
<a name=3D"idxp_options"><br><hr size=3D"1" shade=3D"0"></a>=0A=
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>=0A=
<a name=3D"rfc.section.4"></a><h3>4.&nbsp;IDXP Options</h3>=0A=
=0A=
<p>IDXP provides a service for the reliable exchange of data between =
intrusion detection entities. Options are used to alter the semantics =
of the service.=0A=
</p>=0A=
<p>The specification of an IDXP option MUST define:=0A=
</p>=0A=
<p>=0A=
<ul class=3D"text">=0A=
<li>the identity of the option;=0A=
</li>=0A=
<li>what content, if any, is contained within the option; and,=0A=
</li>=0A=
<li>the processing rules for the option.=0A=
</li>=0A=
</ul><p>=0A=
</p>=0A=
<p>An option registration template (c.f. <a href=3D"#option_reg">IDXP =
Option Registration Template</a>) organizes this information.=0A=
</p>=0A=
<p>An "Option" element is contained within an "IDXP-Greeting" element. =
The "IDXP-Greeting" element itself MAY contain one or more "Option" =
elements. The "Option" element has several attributes and contains =
arbitrary content:=0A=
</p>=0A=
<p>=0A=
<ul class=3D"text">=0A=
<li>the "internal" and the "external" attributes, exactly one of which =
MUST be present, uniquely identify the option;=0A=
</li>=0A=
<li>the "mustUnderstand" attribute, whose presence is OPTIONAL and =
whose default value is "false", specifies whether the option, if =
unrecognized, MUST cause an error in processing to occur; and,=0A=
</li>=0A=
<li>the "localize" attribute, whose presence is OPTIONAL, specifies one =
or more language tokens, each identifying a desirable language tag to =
be used if textual diagnostics are returned to the originator.=0A=
</li>=0A=
</ul><p>=0A=
</p>=0A=
<p>The value of the "internal" attribute is the IANA-registered name =
for the option. If the "internal" attribute is not present, then the =
value of the "external" attribute is a URI or URI with a =
fragment-identifier. Note that a relative-URI value is not allowed.=0A=
</p>=0A=
<p>The "mustUnderstand" attribute specifies whether the peer may ignore =
the option if it is unrecognized. If the value of the "mustUnderstand" =
attribute is "true", and if the peer does not recognize the option, =
then an error in processing has occurred. When absent, the value of the =
"mustUnderstand" attribute is defined to be "false".=0A=
</p>=0A=
<a name=3D"rfc.section.4.1"></a><h4><a =
name=3D"priority_option">4.1</a>&nbsp;The channelPriority =
Option</h4>=0A=
=0A=
<p><a href=3D"#priority_opt_reg">Registration: The channelPriority =
Option</a> contains the IDXP option registration for the =
"channelPriority" option. This option contains a "channelPriority" =
element (c.f., <a href=3D"#priority_dtd">The channelPriority Option =
DTD</a>).=0A=
</p>=0A=
<p>By default, IDXP does not place any requirements on how peers should =
manage multiple IDXP channels. The "channelPriority" option provides a =
way for peers using multiple IDXP channels to request relative =
priorities for each channel. When sending an "IDXP-Greeting" element =
during the provisioning of an IDXP channel, the originating peer MAY =
request that the remote peer assign a priority to the channel by =
including an "Option" element containing a "channelPriority" =
element.=0A=
</p>=0A=
<p>The "channelPriority" element has one attribute named "priority", of =
range 0..2147483647. This attribute is REQUIRED. Not coincidentally, =
this is the maximum range of possible BEEP channel numbers. 0 is =
defined to represent the highest priority, with relative priority =
decreasing as the "priority" value ascends.=0A=
</p>=0A=
<p>For example, during the exchange of "IDXP-Greeting" elements during =
channel provisioning, an analyzer successfully requests that a manager =
assign a priority to the channel:=0A=
</p></font><pre>=0A=
=0A=
    analyzer                                           manager=0A=
       --------------- greeting w/ option ----------------->=0A=
      &lt;---------------------- &lt;ok> ------------------------=0A=
=0A=
C: MSG 1 17 . 1984 165=0A=
C: Content-Type: text/xml=0A=
C:=0A=
C: &lt;IDXP-Greeting uri=3D'http://example.com/alice' =
role=3D'client'>=0A=
C:   &lt;Option internal=3D'channelPriority'>=0A=
C:     &lt;channelPriority priority=3D'0' />=0A=
C:   &lt;/Option>=0A=
C: &lt;/IDXP-Greeting>=0A=
C: END=0A=
S: RPY 1 17 . 2001 7=0A=
S: Content-Type: text/xml=0A=
S:=0A=
S: &lt;ok />=0A=
S: END=0A=
</pre><font face=3D"verdana, helvetica, arial, sans-serif" =
size=3D"2">=0A=
=0A=
<p>For example, during the exchange of "IDXP-Greeting" elements during =
channel provisioning, a manager unsuccessfully requests that an =
analyzer assign a priority to the channel:=0A=
</p></font><pre>=0A=
=0A=
    analyzer                                           manager=0A=
      &lt;---------------- greeting w/ option ----------------=0A=
       --------------------- &lt;error> ---------------------->=0A=
=0A=
S: MSG 1 17 . 1312 194=0A=
S: Content-Type: text/xml=0A=
S:=0A=
S: &lt;IDXP-Greeting uri=3D'http://example.com/bob' role=3D'server'>=0A=
S:   &lt;Option internal=3D'channelPriority' =
mustUnderstand=3D'true'>=0A=
S:     &lt;channelPriority priority=3D'2147483647' />=0A=
S:   &lt;/Option>=0A=
S: &lt;/IDXP-Greeting>=0A=
S: END=0A=
C: ERR 1 17 . 451 68=0A=
C: Content-Type: text/xml=0A=
C:=0A=
C: &lt;error code=3D'504'>'channelPriority' option was =
unrecognized&lt;/error>=0A=
C: END=0A=
</pre><font face=3D"verdana, helvetica, arial, sans-serif" =
size=3D"2">=0A=
=0A=
<a name=3D"rfc.section.4.2"></a><h4><a =
name=3D"type_option">4.2</a>&nbsp;The streamType Option</h4>=0A=
=0A=
<p><a href=3D"#type_opt_reg">Registration: The streamType Option</a> =
contains the IDXP option registration for the "streamType" option. This =
option contains a "streamType" element (c.f., <a href=3D"#st_dtd">The =
streamType DTD</a>).=0A=
</p>=0A=
<p>By default, IDXP provides no explicit method for categorizing =
channels. The "streamType" option provides a way for peers to request =
that a channel be categorized as a particular stream type. When sending =
an "IDXP-Greeting" element during the provisioning of an IDXP channel, =
the originating peer MAY request that the remote peer assign a stream =
type to the channel by including an "Option" element containing a =
"streamType" element.=0A=
</p>=0A=
<p>The "streamType" element has one attribute named "type", with the =
possible values of "alert", "heartbeat", or "config". This attribute is =
REQUIRED. A value of "alert" indicates that the channel should be =
categorized as being used for the exchange of ID alerts. A value of =
"heartbeat" indicates that the channel should be categorized as being =
used for the exchange of heartbeat messages such as the "Heartbeat" =
element (c.f., Section 5 of <a href=3D"#refs.IDMEF">[4]</a>). A value =
of "config" indicates that the channel should be categorized as being =
used for the exchange of configuration messages.=0A=
</p>=0A=
<p>For example, during the exchange of "IDXP-Greeting" elements during =
channel provisioning, an analyzer successfully requests that a manager =
assign a stream type to the channel:=0A=
</p></font><pre>=0A=
=0A=
    analyzer                                           manager=0A=
       --------------- greeting w/ option ----------------->=0A=
      &lt;---------------------- &lt;ok> ------------------------=0A=
=0A=
C: MSG 1 21 . 1963 155=0A=
C: Content-Type: text/xml=0A=
C:=0A=
C: &lt;IDXP-Greeting uri=3D'http://example.com/alice' =
role=3D'client'>=0A=
C:   &lt;Option internal=3D'streamType'>=0A=
C:     &lt;streamType type=3D'alert' />=0A=
C:   &lt;/Option>=0A=
C: &lt;/IDXP-Greeting>=0A=
C: END=0A=
S: RPY 1 21 . 1117 7=0A=
S: Content-Type: text/xml=0A=
S:=0A=
S: &lt;ok />=0A=
S: END=0A=
</pre><font face=3D"verdana, helvetica, arial, sans-serif" =
size=3D"2">=0A=
=0A=
<p>For example, during the exchange of "IDXP-Greeting" elements during =
channel provisioning, a manager unsuccessfully requests that an =
analyzer assign a stream type to the channel:=0A=
</p></font><pre>=0A=
=0A=
=0A=
    analyzer                                           manager=0A=
      &lt;---------------- greeting w/ option ----------------=0A=
       --------------------- &lt;error> ---------------------->=0A=
=0A=
S: MSG 1 21 . 1969 176=0A=
S: Content-Type: text/xml=0A=
S:=0A=
S: &lt;IDXP-Greeting uri=3D'http://example.com/bob' role=3D'server'>=0A=
S:   &lt;Option internal=3D'streamType' mustUnderstand=3D'true'>=0A=
S:     &lt;streamType type=3D'config' />=0A=
S:   &lt;/Option>=0A=
S: &lt;/IDXP-Greeting>=0A=
S: END=0A=
C: ERR 1 21 . 1292 63=0A=
C: Content-Type: text/xml=0A=
C:=0A=
C: &lt;error code=3D'504'>'streamType' option was =
unrecognized&lt;/error>=0A=
C: END=0A=
</pre><font face=3D"verdana, helvetica, arial, sans-serif" =
size=3D"2">=0A=
=0A=
<a name=3D"proto-reqs"><br><hr size=3D"1" shade=3D"0"></a>=0A=
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>=0A=
<a name=3D"rfc.section.5"></a><h3>5.&nbsp;Fulfillment of IDWG =
Communications Protocol Requirements</h3>=0A=
=0A=
<p>The following lists the communications protocol requirements =
established in Section 5 of <a href=3D"#refs.IDWG-reqs">[9]</a> and, =
for each requirement, describes the manner in which it is fulfilled by =
IDXP.=0A=
</p>=0A=
<p>The [protocol] MUST support reliable transmission of messages.=0A=
</p>=0A=
<p>=0A=
<blockquote class=3D"text">=0A=
<p>IDXP operates over BEEP, which operates only over reliable =
connection-oriented transport protocols (e.g., TCP). In addition, BEEP =
peers communicate using a simple request-response protocol, which =
provides end-to-end reliability between peers.=0A=
</p>=0A=
</blockquote><p>=0A=
</p>=0A=
<p>The [protocol] MUST support transmission of messages between ID =
components across firewall boundaries without compromising security.=0A=
</p>=0A=
<p>=0A=
<blockquote class=3D"text">=0A=
<p>The TUNNEL profile <a href=3D"#refs.tunnel">[7]</a> MUST be offered =
as an option for creation of application-layer tunnels to allow =
operation across firewalls. The TUNNEL profile SHOULD be used to =
provide an application-layer tunnel. The ability to authenticate hosts =
during the creation of an application-layer tunnel MUST be provided by =
the mechanism chosen to create such tunnels. A firewall may therefore =
be configured to authenticate all hosts attempting to tunnel into the =
protected network. If the TUNNEL profile is used, SASL (c.f., Section =
4.1 of <a href=3D"#RFC3080">[8]</a>) MUST be offered as a mechanism by =
which hosts can be authenticated.=0A=
</p>=0A=
</blockquote><p>=0A=
</p>=0A=
<p>The [protocol] MUST support mutual authentication of the analyzer =
and the manager to each other.=0A=
</p>=0A=
<p>=0A=
<blockquote class=3D"text">=0A=
<p>IDXP supports mutual authentication of the peers through the use of =
an appropriate underlying BEEP security profile. The TLS profile and =
members of the SASL family of profiles (c.f., Section 4.1 of <a =
href=3D"#RFC3080">[8]</a>) are examples of security profiles that may =
be used to authenticate the identity of communicating ID components. =
TLS MUST be offered as a mechanism to provide mutual authentication, =
and TLS SHOULD be used to provide mutual authentication.=0A=
</p>=0A=
</blockquote><p>=0A=
</p>=0A=
<p>The [protocol] MUST support confidentiality of the message content =
during message exchange. The selected design MUST be capable of =
supporting a variety of encryption algorithms and MUST be adaptable to =
a wide variety of environments.=0A=
</p>=0A=
<p>=0A=
<blockquote class=3D"text">=0A=
<p>IDXP supports confidentiality through the use of an appropriate =
underlying BEEP security profile. The TLS profile is an example a =
security profile that offers confidentiality. The TLS profile with the =
TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA cipher suite MUST be offered as a =
mechanism to provide confidentiality, and TLS with this cipher suite =
SHOULD be used to provide confidentiality. The =
TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA cipher suite uses ephemeral =
Diffie-Hellman (DHE) with DSS signatures for key exchange and triple =
DES (3DES) and cipher-block chaining (CBC) for encryption. Stronger =
cipher suites are optional.=0A=
</p>=0A=
</blockquote><p>=0A=
</p>=0A=
<p>The [protocol] MUST ensure the integrity of the message content. The =
selected design MUST be capable of supporting a variety of integrity =
mechanisms and MUST be adaptable to a wide variety of environments.=0A=
</p>=0A=
<p>=0A=
<blockquote class=3D"text">=0A=
<p>IDXP supports message integrity through the use of an appropriate =
underlying BEEP security profile. The TLS profile and members of the =
SASL family of profiles (c.f., Section 4.1 of <a =
href=3D"#RFC3080">[8]</a>) are examples of security profiles that offer =
message integrity. The TLS profile with the =
TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA cipher suite MUST be offered as a =
mechanism to provide integrity, and TLS with this cipher suite SHOULD =
be used to provide integrity. The TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA =
cipher suite uses the Secure Hash Algorithm (SHA) for integrity =
protection using a keyed message authentication code. Stronger cipher =
suites are optional.=0A=
</p>=0A=
</blockquote><p>=0A=
</p>=0A=
<p>The [protocol] SHOULD be able to ensure non-repudiation of the =
origin of IDMEF messages.=0A=
</p>=0A=
<p>=0A=
<blockquote class=3D"text">=0A=
<p>IDXP supports non-repudiation of session origin through the use of =
an=0A=
appropriate underlying BEEP security profile. An IDXP peer application =
MAY use=0A=
IDMEF content and/or BEEP session credentials to provide for =
non-repudiation of=0A=
message origin. The TLS profile is an example of a security profile =
that offers=0A=
non-repudiation of session origin through the=0A=
authentication of public-key certificates. TLS MUST be offered as a =
mechanism to=0A=
provide non-repudiation of session origin, and TLS SHOULD be used to =
provide=0A=
non-repudiation of session origin.=0A=
</p>=0A=
</blockquote><p>=0A=
</p>=0A=
<p>The [protocol] SHOULD resist protocol denial of service attacks.=0A=
</p>=0A=
<p>=0A=
<blockquote class=3D"text">=0A=
<p>IDXP supports resistance to denial of service (DoS) attacks through =
the use of an appropriate underlying BEEP security profile. BEEP peers =
offering the IDXP profile MUST offer the use of TLS with the =
TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA cipher suite, and SHOULD use TLS with =
that cipher suite. To resist DoS attacks it is helpful to discard =
traffic arising from a non-authenticated source. BEEP peers MUST =
support the use of authentication in conjunction with any mechanism =
used to create application-layer tunnels. In particular, the use of =
some form of SASL authentication (c.f., Section 4.1 of <a =
href=3D"#RFC3080">[8]</a>) MUST be offered to provide authentication in =
the use of the TUNNEL profile. See Section 7 of <a =
href=3D"#refs.tunnel">[7]</a> for a discussion of security =
considerations in the use of the TUNNEL profile.=0A=
</p>=0A=
</blockquote><p>=0A=
</p>=0A=
<p>The [protocol] SHOULD resist malicious duplication of messages.=0A=
</p>=0A=
<p>=0A=
<blockquote class=3D"text">=0A=
<p>IDXP supports resistance to malicious duplication of messages (i.e., =
replay attacks) through the use of an appropriate underlying BEEP =
security profile. The TLS profile is an example of a security profile =
offering resistance to replay attacks. The TLS profile with the =
TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA cipher suite MUST be offered as a =
mechanism to provide resistance against replay attacks, and TLS with =
this cipher suite SHOULD be used to provide resistance against replay =
attacks. The TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA cipher suite uses =
cipher-block chaining (CBC) to ensure that even if a message is =
duplicated the cipher-text duplicate will produce a very different =
plain-text result. Stronger cipher suites are optional.=0A=
</p>=0A=
</blockquote><p>=0A=
</p>=0A=
<a name=3D"option_reg"><br><hr size=3D"1" shade=3D"0"></a>=0A=
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>=0A=
<a name=3D"rfc.section.6"></a><h3>6.&nbsp;IDXP Option Registration =
Template</h3>=0A=
=0A=
<p>When an IDXP option is registered, the following information is =
supplied:=0A=
</p>=0A=
<p>Option Identification: specify the NMTOKEN or the URI that =
authoritatively identifies this option.=0A=
</p>=0A=
<p>Contains: specify the XML content that is contained within the =
"Option" element.=0A=
</p>=0A=
<p>Processing Rules: specify the processing rules associated with the =
option.=0A=
</p>=0A=
<p>Contact Information: specify the postal and electronic contact =
information for the author(s) of the option.=0A=
</p>=0A=
<a name=3D"anchor8"><br><hr size=3D"1" shade=3D"0"></a>=0A=
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>=0A=
<a name=3D"rfc.section.7"></a><h3>7.&nbsp;Initial Registrations</h3>=0A=
=0A=
<a name=3D"rfc.section.7.1"></a><h4><a =
name=3D"idxp-registration">7.1</a>&nbsp;Registration: The IDXP =
Profile</h4>=0A=
=0A=
<p>Profile identification: http://iana.org/beep/transient/idwg/idxp=0A=
</p>=0A=
<p>Messages exchanged during channel creation: "IDXP-Greeting"=0A=
</p>=0A=
<p>Messages starting one-to-one exchanges: "IDXP-Greeting", =
"IDMEF-Message"=0A=
</p>=0A=
<p>Messages in positive replies: "ok"=0A=
</p>=0A=
<p>Messages in negative replies: "error"=0A=
</p>=0A=
<p>Messages in one-to-many exchanges: none=0A=
</p>=0A=
<p>Message syntax: c.f., <a href=3D"#IDXP-syntax">IDXP Profile Message =
Syntax</a>=0A=
</p>=0A=
<p>Message semantics: c.f., <a href=3D"#IDXP-semantics">IDXP Profile =
Semantics</a>=0A=
</p>=0A=
<p>Contact information: c.f., the "Authors' Addresses" section of this =
memo=0A=
</p>=0A=
<a name=3D"rfc.section.7.2"></a><h4><a =
name=3D"port-registration">7.2</a>&nbsp;Registration: The System =
(Well-Known) TCP port number for IDXP</h4>=0A=
=0A=
<p>Protocol Number: TCP=0A=
</p>=0A=
<p>Message Formats, Types, Opcodes, and Sequences: c.f., <a =
href=3D"#IDXP-syntax">IDXP Profile Message Syntax</a>=0A=
</p>=0A=
<p>Functions: c.f., <a href=3D"#IDXP-semantics">IDXP Profile =
Semantics</a>=0A=
</p>=0A=
<p>Use of Broadcast/Multicast: none=0A=
</p>=0A=
<p>Proposed Name: Intrusion Detection Exchange Protocol=0A=
</p>=0A=
<p>Short name: idxp=0A=
</p>=0A=
<p>Contact Information: c.f., the "Authors' Addresses" section of this =
memo=0A=
</p>=0A=
<a name=3D"rfc.section.7.3"></a><h4><a =
name=3D"priority_opt_reg">7.3</a>&nbsp;Registration: The =
channelPriority Option</h4>=0A=
=0A=
<p>Option Identification: channelPriority=0A=
</p>=0A=
<p>Contains: channelPriority (c.f., <a href=3D"#priority_dtd">The =
channelPriority Option DTD</a>)=0A=
</p>=0A=
<p>Processing Rules: c.f., <a href=3D"#priority_option">The =
channelPriority Option</a>=0A=
</p>=0A=
<p>Contact Information: c.f., the "Authors' Addresses" section of this =
memo=0A=
</p>=0A=
<a name=3D"rfc.section.7.4"></a><h4><a =
name=3D"type_opt_reg">7.4</a>&nbsp;Registration: The streamType =
Option</h4>=0A=
=0A=
<p>Option Identification: streamType=0A=
</p>=0A=
<p>Contains: streamType (c.f., <a href=3D"#st_dtd">The streamType =
DTD</a>)=0A=
</p>=0A=
<p>Processing Rules: c.f., <a href=3D"#type_option">The streamType =
Option</a>=0A=
</p>=0A=
<p>Contact Information: c.f., the "Authors' Addresses" section of this =
memo=0A=
</p>=0A=
<a name=3D"anchor9"><br><hr size=3D"1" shade=3D"0"></a>=0A=
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>=0A=
<a name=3D"rfc.section.8"></a><h3>8.&nbsp;The DTDs</h3>=0A=
=0A=
<a name=3D"rfc.section.8.1"></a><h4><a =
name=3D"idxp_dtd">8.1</a>&nbsp;The IDXP DTD</h4>=0A=
=0A=
<p>The following is the DTD defining the valid elements for the IDXP =
profile=0A=
</p></font><pre>=0A=
  &lt;!--=0A=
  DTD for the IDXP Profile, as of 2002-01-08=0A=
=0A=
  Refer to this DTD as:=0A=
=0A=
    &lt;!ENTITY % IDXP PUBLIC "-//IETF//DTD RFC XXXX IDXP v1.0//EN">=0A=
=0A=
    %IDXP;=0A=
  -->=0A=
=0A=
  &lt;!-- Includes -->=0A=
=0A=
    &lt;!ENTITY % BEEP PUBLIC "-//IETF//DTD BEEP//EN">=0A=
=0A=
    %BEEP;=0A=
=0A=
=0A=
    &lt;!ENTITY % IDMEF-Message PUBLIC "-//IETF//DTD RFC XXXX IDMEF =
v1.0//EN">=0A=
=0A=
    %IDMEF;=0A=
=0A=
  &lt;!--=0A=
    Profile Summary=0A=
=0A=
      BEEP profile http://iana.org/beep/transient/idwg/idxp=0A=
=0A=
      role       MSG               RPY      ERR=0A=
      =3D=3D=3D=3D       =3D=3D=3D               =3D=3D=3D      =
=3D=3D=3D=0A=
      I or L     IDXP-Greeting     ok       error=0A=
      C          IDMEF-Message     ok       error=0A=
  -->=0A=
=0A=
  &lt;!--=0A=
    Entity Definitions=0A=
=0A=
          entity        syntax/reference     example=0A=
          =3D=3D=3D=3D=3D=3D        =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D     =
=3D=3D=3D=3D=3D=3D=3D=0A=
      an authoritative identification=0A=
          URI           c.f., [RFC-2396]       http://example.com=0A=
=0A=
      a fully qualified domain name=0A=
          FQDN          c.f., [RFC-1034]       www.example.com=0A=
  -->=0A=
=0A=
  &lt;!ENTITY % URI      "CDATA">=0A=
  &lt;!ENTITY % FQDN     "CDATA">=0A=
=0A=
  &lt;!--=0A=
    The IDXP-Greeting element declares the role and identity of=0A=
    the peer issuing it, on a per channel basis. The=0A=
    IDXP-Greeting element may contain one or more Option=0A=
    sub-elements.=0A=
  -->=0A=
=0A=
&lt;!ELEMENT IDXP-Greeting  (Option*)>=0A=
&lt;!ATTLIST IDXP-Greeting=0A=
          uri            %URI;                #REQUIRED=0A=
          role           (client|server)      #REQUIRED=0A=
          fqdn           %FQDN;               #IMPLIED>=0A=
=0A=
  &lt;!--=0A=
    The Option element conveys an IDXP channel option.=0A=
    Note that the %LOCS entity is imported from the BEEP Channel=0A=
    Management DTD.=0A=
  -->=0A=
=0A=
&lt;!ELEMENT Option (ANY)>=0A=
&lt;!ATTLIST Option=0A=
          internal       NMTOKEN              ""=0A=
          external       %URI;                ""=0A=
          mustUnderstand (true|false)         "false"=0A=
          localize       %LOCS;               "i-default">  =0A=
=0A=
  &lt;!--=0A=
    The IDMEF-Message element conveys the intrusion detection=0A=
    information that is exchanged.  This element is defined in the=0A=
    idmef-message.dtd=0A=
  -->=0A=
=0A=
&lt;!-- End of DTD -->=0A=
</pre><font face=3D"verdana, helvetica, arial, sans-serif" =
size=3D"2">=0A=
=0A=
<a name=3D"rfc.section.8.2"></a><h4><a =
name=3D"priority_dtd">8.2</a>&nbsp;The channelPriority Option =
DTD</h4>=0A=
=0A=
<p>The following is the DTD defining the valid elements for the =
channelPriority option=0A=
</p></font><pre>=0A=
  &lt;!--=0A=
  DTD for the channelPriority IDXP option, as of 2002-01-08=0A=
=0A=
  Refer to this DTD as:=0A=
=0A=
    &lt;!ENTITY % IDXP-channelPriority PUBLIC=0A=
      "-//IETF//DTD RFC XXXX IDXP-channelPriority v1.0//EN">=0A=
=0A=
    %IDXP-channelPriority;=0A=
  -->=0A=
=0A=
  &lt;!--=0A=
    Entity Definitions=0A=
=0A=
          entity        syntax/reference     example=0A=
          =3D=3D=3D=3D=3D=3D        =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D     =
=3D=3D=3D=3D=3D=3D=3D=0A=
    a priority number=0A=
          PRIORITY      0..2147483647        1=0A=
  -->=0A=
=0A=
&lt;!ENTITY % PRIORITY          "CDATA">=0A=
=0A=
&lt;!ELEMENT channelPriority    EMPTY>=0A=
&lt;!ATTLIST channelPriority=0A=
          priority           %PRIORITY    #REQUIRED>=0A=
=0A=
&lt;!-- End of DTD --> =0A=
</pre><font face=3D"verdana, helvetica, arial, sans-serif" =
size=3D"2">=0A=
=0A=
<a name=3D"rfc.section.8.3"></a><h4><a name=3D"st_dtd">8.3</a>&nbsp;The =
streamType DTD</h4>=0A=
=0A=
<p>The following is the DTD defining the valid elements for the =
streamType option=0A=
</p></font><pre>=0A=
  &lt;!--=0A=
  DTD for the streamType IDXP option, as of 2002-01-08=0A=
=0A=
  Refer to this DTD as:=0A=
=0A=
    &lt;!ENTITY % IDXP-streamType PUBLIC=0A=
      "-//IETF//DTD RFC XXXX IDXP-streamType v1.0//EN">=0A=
=0A=
    %IDXP-streamType;=0A=
  -->=0A=
=0A=
  &lt;!--=0A=
    Entity Definitions=0A=
=0A=
          entity        syntax/reference                example=0A=
          =3D=3D=3D=3D=3D=3D        =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D                =
=3D=3D=3D=3D=3D=3D=3D=0A=
     a stream type=0A=
          STYPE         (alert | heartbeat | config)    "alert"=0A=
  -->=0A=
=0A=
&lt;!ENTITY % STYPE        (alert|heartbeat|config)>=0A=
=0A=
&lt;!ELEMENT streamType    EMPTY>=0A=
&lt;!ATTLIST streamType=0A=
          type          %STYPE    #REQUIRED>=0A=
=0A=
&lt;!-- End of DTD -->=0A=
</pre><font face=3D"verdana, helvetica, arial, sans-serif" =
size=3D"2">=0A=
=0A=
<a name=3D"anchor10"><br><hr size=3D"1" shade=3D"0"></a>=0A=
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>=0A=
<a name=3D"rfc.section.9"></a><h3>9.&nbsp;Reply Codes</h3>=0A=
=0A=
<p>This section lists the three-digit error codes the IDXP profile may =
generate.=0A=
</p></font><pre>=0A=
code    meaning=0A=
=3D=3D=3D=3D    =3D=3D=3D=3D=3D=3D=3D=0A=
421     Service not available=0A=
        (E.g., the peer does not have sufficient resources.)=0A=
=0A=
450     Requested action not taken=0A=
        (E.g., DNS lookup failed or connection could not=0A=
         be established. See also 550.)=0A=
=0A=
454     Temporary authentication failure=0A=
=0A=
500     General syntax error=0A=
        (E.g., poorly-formed XML)=0A=
=0A=
501     Syntax error in parameters=0A=
        (E.g., non-valid XML)=0A=
=0A=
504     Parameter not implemented=0A=
=0A=
530     Authentication required=0A=
=0A=
534     Authentication mechanism insufficient=0A=
        (E.g., cipher suite too weak, sequence exhausted, etc.)=0A=
=0A=
535     Authentication failure=0A=
=0A=
537     Action not authorized for user=0A=
=0A=
550     Requested action not taken=0A=
        (E.g., peer could be contacted, but=0A=
         malformed greeting or no IDXP profile advertised.)=0A=
=0A=
553     Parameter invalid=0A=
=0A=
554     Transaction failed=0A=
        (E.g., policy violation)=0A=
</pre><font face=3D"verdana, helvetica, arial, sans-serif" =
size=3D"2">=0A=
=0A=
<a name=3D"security"><br><hr size=3D"1" shade=3D"0"></a>=0A=
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>=0A=
<a name=3D"rfc.section.10"></a><h3>10.&nbsp;Security =
Considerations</h3>=0A=
=0A=
<p>The IDXP profile is a profile of BEEP. In BEEP, transport =
security,=0A=
user authentication, and data exchange are orthogonal. Refer to Section =
8=0A=
of <a href=3D"#RFC3080">[8]</a> for a discussion of this. It is =
strongly recommended that those wanting to use the IDXP profile =
initially negotiate a BEEP security profile between the peers that =
offers the required security properties. The TLS profile SHOULD be used =
to provide for transport security. See <a =
href=3D"#proto-reqs">Fulfillment of IDWG Communications Protocol =
Requirements</a> for a discussion of how IDXP fulfills the IDWG =
communications protocol requirements.=0A=
</p>=0A=
<p>See <a href=3D"#trust">Trust Model</a> for a discussion of the trust =
model.=0A=
</p>=0A=
<a name=3D"rfc.section.10.1"></a><h4><a =
name=3D"security.tunnel">10.1</a>&nbsp;Use of the TUNNEL =
Profile</h4>=0A=
=0A=
<p>See <a href=3D"#proto-reqs">Fulfillment of IDWG Communications =
Protocol Requirements</a> for IDXP's requirements on application-layer =
tunneling and the TUNNEL profile specifically. See Section 7 of <a =
href=3D"#refs.tunnel">[7]</a> for a discussion of the security =
considerations inherent in the use of the TUNNEL profile.=0A=
</p>=0A=
<a name=3D"rfc.section.10.2"></a><h4><a =
name=3D"anchor11">10.2</a>&nbsp;Use of Underlying Security =
Profiles</h4>=0A=
=0A=
<p>At present, the TLS profile is the only BEEP security profile known =
to meet all of the requirements set forth in Section 5 of <a =
href=3D"#refs.IDWG-reqs">[9]</a>. When securing a BEEP session with the =
TLS profile, the TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA cipher suite offers =
an acceptable level of security. See <a =
href=3D"#proto-reqs">Fulfillment of IDWG Communications Protocol =
Requirements</a> for a discussion of how IDXP fulfills the IDWG =
communications requirements through the use of an underlying security =
profile.=0A=
</p>=0A=
<a name=3D"rfc.references1"><br><hr size=3D"1" shade=3D"0"></a>=0A=
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>=0A=
<h3>References</h3>=0A=
<table width=3D"99%" border=3D"0">=0A=
<tr><td class=3D"author-text" valign=3D"top"><b><a =
name=3D"RFC2396">[1]</a></b></td>=0A=
<td class=3D"author-text"><a href=3D"mailto:timbl@w3.org">Berners-Lee, =
T.</a>, <a href=3D"mailto:fielding@ics.uci.edu">Fielding, R.</a> and <a =
href=3D"mailto:masinter@parc.xerox.com">L. Masinter</a>, "<a =
href=3D"ftp://ftp.isi.edu/in-notes/rfc2396.txt">Uniform Resource =
Identifiers (URI): Generic Syntax</a>", RFC 2396, August =
1998.</td></tr>=0A=
<tr><td class=3D"author-text" valign=3D"top"><b><a =
name=3D"RFC2119">[2]</a></b></td>=0A=
<td class=3D"author-text"><a href=3D"mailto:-">Bradner, S.</a>, "<a =
href=3D"ftp://ftp.isi.edu/in-notes/rfc2119.txt">Key words for use in =
RFCs to Indicate Requirement Levels</a>", BCP 14, RFC 2119, March =
1997.</td></tr>=0A=
<tr><td class=3D"author-text" valign=3D"top"><b><a =
name=3D"W3C.REC-xml">[3]</a></b></td>=0A=
<td class=3D"author-text"><a href=3D"mailto:tbray@textuality.com">Bray, =
T.</a>, <a href=3D"mailto:jeanpa@microsoft.com">Paoli, J.</a>, <a =
href=3D"mailto:cmsmcq@uic.edu">Sperberg-McQueen, C.</a> and <a =
href=3D"mailto:eve.maler@east.sun.com">E. Maler</a>, "<a =
href=3D"http://www.w3.org/TR/REC-xml">Extensible Markup Language (XML) =
1.0 (2nd ed)</a>", W3C REC-xml, October 2000.</td></tr>=0A=
<tr><td class=3D"author-text" valign=3D"top"><b><a =
name=3D"refs.IDMEF">[4]</a></b></td>=0A=
<td class=3D"author-text">Curry, D. and H. Debar, "<a =
href=3D"ftp://ftp.isi.edu/in-notes/rfc.txt">Intrusion Detection Message =
Exchange Format Data Model and Extensible Markup Language (XML) =
Document Type Definition</a>", RFC XXXX, Month YYYY.</td></tr>=0A=
<tr><td class=3D"author-text" valign=3D"top"><b><a =
name=3D"RFC2046">[5]</a></b></td>=0A=
<td class=3D"author-text"><a href=3D"mailto:ned@innosoft.com">Freed, =
N.</a> and <a href=3D"mailto:nsb@nsb.fv.com">N. Borenstein</a>, "<a =
href=3D"ftp://ftp.isi.edu/in-notes/rfc2046.txt">Multipurpose Internet =
Mail Extensions (MIME) Part Two: Media Types</a>", RFC 2046, November =
1996.</td></tr>=0A=
<tr><td class=3D"author-text" valign=3D"top"><b><a =
name=3D"RFC1034">[6]</a></b></td>=0A=
<td class=3D"author-text">Mockapetris, P., "<a =
href=3D"ftp://ftp.isi.edu/in-notes/rfc1034.txt">Domain names - concepts =
and facilities</a>", STD 13, RFC 1034, November 1987.</td></tr>=0A=
<tr><td class=3D"author-text" valign=3D"top"><b><a =
name=3D"refs.tunnel">[7]</a></b></td>=0A=
<td class=3D"author-text">New, D., "<a =
href=3D"ftp://ftp.isi.edu/in-notes/rfc.txt">The TUNNEL Profile =
Registration</a>", RFC XXXX, Month YYYY.</td></tr>=0A=
<tr><td class=3D"author-text" valign=3D"top"><b><a =
name=3D"RFC3080">[8]</a></b></td>=0A=
<td class=3D"author-text"><a href=3D"mailto:mrose@invisible.net">Rose, =
M.</a>, "<a href=3D"ftp://ftp.isi.edu/in-notes/rfc3080.txt">The Blocks =
Extensible Exchange Protocol Core</a>", RFC 3080, March =
2001.</td></tr>=0A=
<tr><td class=3D"author-text" valign=3D"top"><b><a =
name=3D"refs.IDWG-reqs">[9]</a></b></td>=0A=
<td class=3D"author-text">Wood, M. and M. Erlinger, "<a =
href=3D"ftp://ftp.isi.edu/in-notes/rfc.txt">Intrusion Detection Message =
Exchange Requirements</a>", RFC XXXX, Month YYYY.</td></tr>=0A=
</table>=0A=
=0A=
<a name=3D"rfc.authors"><br><hr size=3D"1" shade=3D"0"></a>=0A=
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>=0A=
<h3>Authors' Addresses</h3>=0A=
<table width=3D"99%" border=3D"0" cellpadding=3D"0" =
cellspacing=3D"0">=0A=
<tr><td class=3D"author-text">&nbsp;</td>=0A=
<td class=3D"author-text">Benjamin S. Feinstein</td></tr>=0A=
<tr><td class=3D"author-text">&nbsp;</td>=0A=
<td class=3D"author-text">Guardent, Inc.</td></tr>=0A=
<tr><td class=3D"author" align=3D"right">EMail:&nbsp;</td>=0A=
<td class=3D"author-text"><a =
href=3D"mailto:Ben.Feinstein@guardent.com">Ben.Feinstein@guardent.com</a=
></td></tr>=0A=
<tr><td class=3D"author" align=3D"right">URI:&nbsp;</td>=0A=
<td class=3D"author-text"><a =
href=3D"http://www.guardent.com/">http://www.guardent.com/</a></td></tr>=
=0A=
<tr cellpadding=3D"3"><td>&nbsp;</td><td>&nbsp;</td></tr>=0A=
<tr><td class=3D"author-text">&nbsp;</td>=0A=
<td class=3D"author-text">Gregory A. Matthews</td></tr>=0A=
<tr><td class=3D"author-text">&nbsp;</td>=0A=
<td class=3D"author-text">CSC/NASA Ames Research Center</td></tr>=0A=
<tr><td class=3D"author" align=3D"right">EMail:&nbsp;</td>=0A=
<td class=3D"author-text"><a =
href=3D"mailto:gmatthew@nas.nasa.gov">gmatthew@nas.nasa.gov</a></td></tr=
>=0A=
<tr><td class=3D"author" align=3D"right">URI:&nbsp;</td>=0A=
<td class=3D"author-text"><a =
href=3D"http://www.nas.nasa.gov/">http://www.nas.nasa.gov/</a></td></tr>=
=0A=
<tr cellpadding=3D"3"><td>&nbsp;</td><td>&nbsp;</td></tr>=0A=
<tr><td class=3D"author-text">&nbsp;</td>=0A=
<td class=3D"author-text">John C. C. White</td></tr>=0A=
<tr><td class=3D"author-text">&nbsp;</td>=0A=
<td class=3D"author-text">MITRE Corporation</td></tr>=0A=
<tr><td class=3D"author" align=3D"right">EMail:&nbsp;</td>=0A=
<td class=3D"author-text"><a =
href=3D"mailto:jccw@mitre.org">jccw@mitre.org</a></td></tr>=0A=
<tr><td class=3D"author" align=3D"right">URI:&nbsp;</td>=0A=
<td class=3D"author-text"><a =
href=3D"http://www.mitre.org/">http://www.mitre.org/</a></td></tr>=0A=
</table>=0A=
=0A=
<a name=3D"IANA"><br><hr size=3D"1" shade=3D"0"></a>=0A=
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>=0A=
<a name=3D"rfc.section.A"></a><h3>Appendix A.&nbsp;IANA =
Considerations</h3>=0A=
=0A=
<p>The IANA registers "IDXP" as a standards-track BEEP profile, as =
specified in <a href=3D"#idxp-registration">Registration: The IDXP =
Profile</a>. The IANA changes the IDXP profile identification to =
"http://iana.org/beep/IDXP".=0A=
</p>=0A=
<p>The IANA registers "idxp" as a TCP port number, as specified in <a =
href=3D"#port-registration">Registration: The System (Well-Known) TCP =
port number for IDXP</a>=0A=
</p>=0A=
<p>The IANA maintains a list of:=0A=
</p>=0A=
<p>=0A=
<blockquote class=3D"text">=0A=
<p>IDXP options, c.f., <a href=3D"#option_reg">IDXP Option Registration =
Template</a>.=0A=
</p>=0A=
</blockquote><p>=0A=
</p>=0A=
<p>For this list, the IESG is responsible for assigning a designated =
expert to review the specification prior to the IANA making the =
assignment. As a courtesy to developers of non-standards track IDXP =
options, the mailing list idxp-java-users@lists.sourceforge.net may be =
used to solicit commentary.=0A=
</p>=0A=
<p>The IANA makes the registrations specified in <a =
href=3D"#priority_opt_reg">Registration: The channelPriority Option</a> =
and <a href=3D"#type_opt_reg">Registration: The streamType =
Option</a>.=0A=
</p>=0A=
<a name=3D"changes"><br><hr size=3D"1" shade=3D"0"></a>=0A=
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>=0A=
<a name=3D"rfc.section.B"></a><h3>Appendix B.&nbsp;History of =
Significant Changes</h3>=0A=
=0A=
<p>The RFC Editor should remove this section and its corresponding TOC =
references prior to publication.=0A=
</p>=0A=
<a name=3D"rfc.section.B.1"></a><h4><a =
name=3D"anchor12">B.1</a>&nbsp;Significant Changes Since =
beep-idxp-04</h4>=0A=
=0A=
<p>Added sentence to Section 3.4 explaining the situation in which an =
"error" element may be issued within an "RPY" message.=0A=
</p>=0A=
<p>Modified examples in Section 4.1 and 4.2, changing the message types =
from "RPY" to "ERR" for the negative response sent by the client.=0A=
</p>=0A=
<p>Fixed two locations where we were referencing the wrong section of =
the requirements document.=0A=
</p>=0A=
<p>Removed references to IP and the %IP attribute.=0A=
</p>=0A=
<p>Modified part of Section 5 dealing with non-repudiation of message =
origin.=0A=
</p>=0A=
<p>Modified Section 1.3 to further refine terminology.=0A=
</p>=0A=
<p>Replaced all remaining references to "entities" with references to =
"peers".=0A=
</p>=0A=
<a name=3D"rfc.section.B.2"></a><h4><a =
name=3D"anchor13">B.2</a>&nbsp;Significant Changes Since =
beep-idxp-03</h4>=0A=
=0A=
<p>Modified references to Internet-Drafts to contain placeholders for =
their forthcoming RFC numbers.=0A=
</p>=0A=
<p>Modified IDMEF formal public identifier (FPI) in the IDXP DTD to =
reflect the changes in draft-ietf-idwg-idmef-xml-06.=0A=
</p>=0A=
<p>Modified IDXP FPI for the IDXP DTD to be more in line with the IDMEF =
FPI.=0A=
</p>=0A=
<a name=3D"rfc.section.B.3"></a><h4><a =
name=3D"anchor14">B.3</a>&nbsp;Significant Changes Since =
beep-idxp-02</h4>=0A=
=0A=
<p>Added IDXP option registration template and registered two initial =
options.=0A=
</p>=0A=
<p>Indicated that the IANA should change the profile identification to =
"http://iana.org/beep/IDXP" upon adoption of IDXP as a standards-track =
BEEP profile.=0A=
</p>=0A=
<p>Renamed the "Options" element to "Option" and allowed multiple =
"Option" sub-elements within an "IDXP-Greeting" element. Also added =
attributes to "Option" element.=0A=
</p>=0A=
<p>Modified IANA profile registration and added TCP port number IANA =
registration.=0A=
</p>=0A=
<p>Reordered some sections to improve the flow of the document.=0A=
</p>=0A=
<p>Changed IDXP DTD identifier to be more IETF-like and removed URLs =
from ENTITY declarations.=0A=
</p>=0A=
<p>Changed IDXP profile URI to fall under the =
"http://iana.org/beep/transient" namespace.=0A=
</p>=0A=
<p>Modified <a href=3D"#terminology">Terminology</a> to reference the =
requirements language specified by <a href=3D"#RFC2119">[2]</a>.=0A=
</p>=0A=
<p>Eliminated the use of the "endpoint" terminology, in favor of =
"peer".=0A=
</p>=0A=
<p>Modified figures to make them more understandable.=0A=
</p>=0A=
<p>Modified Sections 2, 3, and 4 to use the requirements language =
specified by <a href=3D"#RFC2119">[2]</a>.=0A=
</p>=0A=
<p>Indicated that the RFC Editor should remove <a =
href=3D"#changes">History of Significant Changes</a> and its =
corresponding TOC reference prior to publication.=0A=
</p>=0A=
<p>Fixed several typos.=0A=
</p>=0A=
<a name=3D"rfc.section.B.4"></a><h4><a =
name=3D"anchor15">B.4</a>&nbsp;Significant Changes Since =
beep-idxp-01</h4>=0A=
=0A=
<p>Added new MUST and SHOULD language for use of TLS and TUNNEL =
profiles.=0A=
</p>=0A=
<p>Modified the "IDXP-Greeting" element to include an "Options" =
sub-element.=0A=
</p>=0A=
<p>Changed IDXP profile URI.=0A=
</p>=0A=
<a name=3D"rfc.section.B.5"></a><h4><a =
name=3D"anchor16">B.5</a>&nbsp;Significant Changes Since =
beep-idxp-00</h4>=0A=
=0A=
<p>Added <a href=3D"#proto-reqs">Fulfillment of IDWG Communications =
Protocol Requirements</a>, describing how IDXP fulfills the =
communication protocol requirements of the IDWG.=0A=
</p>=0A=
<p>Moved IDXP profile registration to <a href=3D"#IANA">IANA =
Considerations</a>.=0A=
</p>=0A=
<p>Clarified the role that underlying BEEP security profiles must =
play.=0A=
</p>=0A=
<p>Clarified how IDMEF messages fit into IDXP.=0A=
</p>=0A=
<p>Clarified how the IDXP profile channels and BEEP sessions =
interact.=0A=
</p>=0A=
<p>Made terminology clarifications and changes for overall =
consistency.=0A=
</p>=0A=
<a name=3D"anchor17"><br><hr size=3D"1" shade=3D"0"></a>=0A=
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>=0A=
<a name=3D"rfc.section.C"></a><h3>Appendix =
C.&nbsp;Acknowledgements</h3>=0A=
=0A=
<p>The authors gratefully acknowledge the contributions of Darren New, =
Marshall T. Rose, Roy Pollock, Tim Buchheim, Mike Erlinger, and Paul =
Osterwald.=0A=
</p><a name=3D"rfc.copyright"><br><hr size=3D"1" shade=3D"0"></a>=0A=
<table border=3D"0" cellpadding=3D"0" cellspacing=3D"2" width=3D"30" =
height=3D"15" align=3D"right"><tr><td bgcolor=3D"#990000" =
align=3D"center" width=3D"30" height=3D"15"><a href=3D"#toc" =
CLASS=3D"link2"><font face=3D"monaco, MS Sans Serif" color=3D"#ffffff" =
size=3D"1"><b>&nbsp;TOC&nbsp;</b></font></a><br></td></tr></table>=0A=
<h3>Full Copyright Statement</h3>=0A=
<p class=3D'copyright'>=0A=
Copyright (C) The Internet Society (2002). All Rights Reserved.</p>=0A=
<p class=3D'copyright'>=0A=
This document and translations of it may be copied and furnished to=0A=
others, and derivative works that comment on or otherwise explain it=0A=
or assist in its implementation may be prepared, copied, published =
and=0A=
distributed, in whole or in part, without restriction of any kind,=0A=
provided that the above copyright notice and this paragraph are=0A=
included on all such copies and derivative works. However, this=0A=
document itself may not be modified in any way, such as by removing=0A=
the copyright notice or references to the Internet Society or other=0A=
Internet organizations, except as needed for the purpose of=0A=
developing Internet standards in which case the procedures for=0A=
copyrights defined in the Internet Standards process must be=0A=
followed, or as required to translate it into languages other than=0A=
English.</p>=0A=
<p class=3D'copyright'>=0A=
The limited permissions granted above are perpetual and will not be=0A=
revoked by the Internet Society or its successors or assigns.</p>=0A=
<p class=3D'copyright'>=0A=
This document and the information contained herein is provided on an=0A=
&quot;AS IS&quot; basis and THE INTERNET SOCIETY AND THE INTERNET =
ENGINEERING=0A=
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING=0A=
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION=0A=
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF=0A=
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.</p>=0A=
<h3>Acknowledgement</h3>=0A=
<p class=3D'copyright'>=0A=
Funding for the RFC Editor function is currently provided by the=0A=
Internet Society.</p>=0A=
</font></body></html>=0A=
=0A=

------_=_NextPart_000_01C21632.D6E39490
Content-Type: text/plain;
	name="draft-ietf-idwg-beep-idxp-05.txt"
Content-Disposition: attachment;
	filename="draft-ietf-idwg-beep-idxp-05.txt"
Content-Transfer-Encoding: quoted-printable

=0A=
=0A=
=0A=
Intrusion Detection Exchange                                B. =
Feinstein=0A=
Format                                                    Guardent, =
Inc.=0A=
Internet-Draft                                               G. =
Matthews=0A=
Expires: December 16, 2002                 CSC/NASA Ames Research =
Center=0A=
                                                                J. =
White=0A=
                                                       MITRE =
Corporation=0A=
                                                           June 17, =
2002=0A=
=0A=
=0A=
            The Intrusion Detection Exchange Protocol (IDXP)=0A=
                      draft-ietf-idwg-beep-idxp-05=0A=
=0A=
Status of this Memo=0A=
=0A=
   This document is an Internet-Draft and is in full conformance =
with=0A=
   all provisions of Section 10 of RFC2026.=0A=
=0A=
   Internet-Drafts are working documents of the Internet Engineering=0A=
   Task Force (IETF), its areas, and its working groups.  Note that=0A=
   other groups may also distribute working documents as Internet-=0A=
   Drafts.=0A=
=0A=
   Internet-Drafts are draft documents valid for a maximum of six =
months=0A=
   and may be updated, replaced, or obsoleted by other documents at =
any=0A=
   time.  It is inappropriate to use Internet-Drafts as reference=0A=
   material or to cite them other than as "work in progress."=0A=
=0A=
   The list of current Internet-Drafts can be accessed at http://=0A=
   www.ietf.org/ietf/1id-abstracts.txt.=0A=
=0A=
   The list of Internet-Draft Shadow Directories can be accessed at=0A=
   http://www.ietf.org/shadow.html.=0A=
=0A=
   This Internet-Draft will expire on December 16, 2002.=0A=
=0A=
Copyright Notice=0A=
=0A=
   Copyright (C) The Internet Society (2002).  All Rights Reserved.=0A=
=0A=
Abstract=0A=
=0A=
   This memo describes the Intrusion Detection Exchange Protocol =
(IDXP),=0A=
   an application-level protocol for exchanging data between =
intrusion=0A=
   detection entities.  IDXP supports mutual-authentication, =
integrity,=0A=
   and confidentiality over a connection-oriented protocol.  The=0A=
   protocol provides for the exchange of IDMEF messages, =
unstructured=0A=
   text, and binary data.  The IDMEF message elements are described =
in=0A=
   the Intrusion Detection Message Exchange Format (IDMEF) [4], a=0A=
   companion document of the Intrusion Detection Exchange Format =
(IDWG)=0A=
=0A=
=0A=
=0A=
Feinstein, et al.       Expires December 16, 2002               [Page =
1]=0A=
=0C=0A=
Internet-Draft                  The IDXP                       June =
2002=0A=
=0A=
=0A=
   working group of the IETF.=0A=
=0A=
Table of Contents=0A=
=0A=
   1.    Introduction . . . . . . . . . . . . . . . . . . . . . . . .  =
4=0A=
   1.1   Purpose  . . . . . . . . . . . . . . . . . . . . . . . . . .  =
4=0A=
   1.2   Profiles . . . . . . . . . . . . . . . . . . . . . . . . . .  =
4=0A=
   1.3   Terminology  . . . . . . . . . . . . . . . . . . . . . . . .  =
4=0A=
   2.    The Model  . . . . . . . . . . . . . . . . . . . . . . . . .  =
6=0A=
   2.1   Connection Provisioning  . . . . . . . . . . . . . . . . . .  =
6=0A=
   2.2   Data Transfer  . . . . . . . . . . . . . . . . . . . . . . .  =
8=0A=
   2.3   Connection Teardown  . . . . . . . . . . . . . . . . . . . .  =
9=0A=
   2.4   Trust Model  . . . . . . . . . . . . . . . . . . . . . . . .  =
9=0A=
   3.    The IDXP Profile . . . . . . . . . . . . . . . . . . . . . . =
11=0A=
   3.1   IDXP Profile Overview  . . . . . . . . . . . . . . . . . . . =
11=0A=
   3.2   IDXP Profile Identification and Initialization . . . . . . . =
11=0A=
   3.3   IDXP Profile Message Syntax  . . . . . . . . . . . . . . . . =
12=0A=
   3.4   IDXP Profile Semantics . . . . . . . . . . . . . . . . . . . =
12=0A=
   3.4.1 The IDXP-GREETING Element  . . . . . . . . . . . . . . . . . =
12=0A=
   3.4.2 The OPTION Element . . . . . . . . . . . . . . . . . . . . . =
14=0A=
   3.4.3 The IDMEF-MESSAGE Element  . . . . . . . . . . . . . . . . . =
14=0A=
   4.    IDXP Options . . . . . . . . . . . . . . . . . . . . . . . . =
15=0A=
   4.1   The channelPriority Option . . . . . . . . . . . . . . . . . =
16=0A=
   4.2   The streamType Option  . . . . . . . . . . . . . . . . . . . =
17=0A=
   5.    Fulfillment of IDWG Communications Protocol Requirements . . =
20=0A=
   6.    IDXP Option Registration Template  . . . . . . . . . . . . . =
23=0A=
   7.    Initial Registrations  . . . . . . . . . . . . . . . . . . . =
24=0A=
   7.1   Registration: The IDXP Profile . . . . . . . . . . . . . . . =
24=0A=
   7.2   Registration: The System (Well-Known) TCP port number for=0A=
         IDXP . . . . . . . . . . . . . . . . . . . . . . . . . . . . =
24=0A=
   7.3   Registration: The channelPriority Option . . . . . . . . . . =
24=0A=
   7.4   Registration: The streamType Option  . . . . . . . . . . . . =
25=0A=
   8.    The DTDs . . . . . . . . . . . . . . . . . . . . . . . . . . =
26=0A=
   8.1   The IDXP DTD . . . . . . . . . . . . . . . . . . . . . . . . =
26=0A=
   8.2   The channelPriority Option DTD . . . . . . . . . . . . . . . =
27=0A=
   8.3   The streamType DTD . . . . . . . . . . . . . . . . . . . . . =
28=0A=
   9.    Reply Codes  . . . . . . . . . . . . . . . . . . . . . . . . =
30=0A=
   10.   Security Considerations  . . . . . . . . . . . . . . . . . . =
31=0A=
   10.1  Use of the TUNNEL Profile  . . . . . . . . . . . . . . . . . =
31=0A=
   10.2  Use of Underlying Security Profiles  . . . . . . . . . . . . =
31=0A=
         References . . . . . . . . . . . . . . . . . . . . . . . . . =
32=0A=
         Authors' Addresses . . . . . . . . . . . . . . . . . . . . . =
32=0A=
   A.    IANA Considerations  . . . . . . . . . . . . . . . . . . . . =
34=0A=
   B.    History of Significant Changes . . . . . . . . . . . . . . . =
35=0A=
   B.1   Significant Changes Since beep-idxp-04 . . . . . . . . . . . =
35=0A=
   B.2   Significant Changes Since beep-idxp-03 . . . . . . . . . . . =
35=0A=
   B.3   Significant Changes Since beep-idxp-02 . . . . . . . . . . . =
35=0A=
   B.4   Significant Changes Since beep-idxp-01 . . . . . . . . . . . =
36=0A=
=0A=
=0A=
=0A=
Feinstein, et al.       Expires December 16, 2002               [Page =
2]=0A=
=0C=0A=
Internet-Draft                  The IDXP                       June =
2002=0A=
=0A=
=0A=
   B.5   Significant Changes Since beep-idxp-00 . . . . . . . . . . . =
36=0A=
   C.    Acknowledgements . . . . . . . . . . . . . . . . . . . . . . =
38=0A=
         Full Copyright Statement . . . . . . . . . . . . . . . . . . =
39=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Feinstein, et al.       Expires December 16, 2002               [Page =
3]=0A=
=0C=0A=
Internet-Draft                  The IDXP                       June =
2002=0A=
=0A=
=0A=
1. Introduction=0A=
=0A=
   IDXP is specified, in part, as a Blocks Extensible Exchange =
Protocol=0A=
   (BEEP) [8] "profile".  BEEP is a generic application protocol=0A=
   framework for connection-oriented, asynchronous interactions.=0A=
   Features such as authentication and confidentiality are provided=0A=
   through the use of other BEEP profiles.  Accordingly, many aspects =
of=0A=
   IDXP (e.g., confidentiality) are provided within the BEEP =
framework.=0A=
=0A=
1.1 Purpose=0A=
=0A=
   IDXP provides for the exchange of IDMEF [4] messages, =
unstructured=0A=
   text, and binary data between intrusion detection entities.=0A=
   Addressing the security-sensitive nature of exchanges between=0A=
   intrusion detection entities, underlying BEEP security profiles=0A=
   should be used to offer IDXP the required set of security =
properties.=0A=
   See Section 5 for a discussion of how IDXP fulfills the IDWG=0A=
   communication protocol requirements.  See Section 10 for a =
discussion=0A=
   of security considerations.=0A=
=0A=
   IDXP is primarily intended for the exchange of data created by=0A=
   intrusion detection entities.  IDMEF [4] messages should be used =
for=0A=
   the structured representation of this intrusion detection data,=0A=
   although IDXP may be used to exchange unstructured text and =
binary=0A=
   data.=0A=
=0A=
1.2 Profiles=0A=
=0A=
   There are several BEEP profiles discussed, the first of which we=0A=
   define in this memo:=0A=
=0A=
      The IDXP Profile=0A=
=0A=
      The TUNNEL Profile [7]=0A=
=0A=
      The Simple Authentication and Security Layer (SASL) Family of=0A=
      Profiles (c.f., Section 4.1 of [8])=0A=
=0A=
      The TLS Profile (c.f., Section 3.1 of [8])=0A=
=0A=
=0A=
1.3 Terminology=0A=
=0A=
   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL =
NOT",=0A=
   "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and "OPTIONAL" in =
this=0A=
   document are to be interpreted as described in RFC 2119 [2].=0A=
=0A=
   Throughout this memo, the terms "analyzer" and "manager" are used =
in=0A=
=0A=
=0A=
=0A=
Feinstein, et al.       Expires December 16, 2002               [Page =
4]=0A=
=0C=0A=
Internet-Draft                  The IDXP                       June =
2002=0A=
=0A=
=0A=
   the context of the Intrusion Detection Message Exchange =
Requirements=0A=
   [9].  In particular, Section 3.2 of [9] defines the meaning of a=0A=
   collection of intrusion detection terms.=0A=
=0A=
   The terms "peer", "initiator", "listener", "client", and =
"server",=0A=
   and the characters "I", "L", "C", and "S" are used in the context =
of=0A=
   BEEP [8].  In particular, Section 2.1 of BEEP discusses the roles=0A=
   that a BEEP peer may perform.=0A=
=0A=
   The term "Document Type Declaration" is abbreviated as "DTD" and =
is=0A=
   defined in Section 2.8 of the Extensible Markup Language (XML) =
[3].=0A=
=0A=
   Note that the term "proxy" is specific to IDXP, and does not exist =
in=0A=
   the context of BEEP.  The term "intrusion detection" is =
abbreviated=0A=
   as "ID".=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Feinstein, et al.       Expires December 16, 2002               [Page =
5]=0A=
=0C=0A=
Internet-Draft                  The IDXP                       June =
2002=0A=
=0A=
=0A=
2. The Model=0A=
=0A=
2.1 Connection Provisioning=0A=
=0A=
   Intrusion detection entities using IDXP to transfer data are =
termed=0A=
   IDXP peers.  Peers can exist only in pairs, and these pairs=0A=
   communicate over a single BEEP session with one or more BEEP =
channels=0A=
   opened for transferring data.  Peers are either managers or=0A=
   analyzers, as defined in Section 3.2 of [9].=0A=
=0A=
   The relationship between analyzers and managers is potentially =
many-=0A=
   to-many.  I.e., an analyzer MAY communicate with many managers;=0A=
   similarly, a manager MAY communicate with many analyzers.  =
Likewise,=0A=
   the relationship between different managers is potentially =
many-to-=0A=
   many, so that a manager MAY receive the alerts sent by a large =
number=0A=
   of analyzers by receiving them through intermediate managers.=0A=
   Analyzers MUST NOT establish IDXP exchanges with other analyzers.=0A=
=0A=
   An IDXP peer wishing to establish IDXP communications with =
another=0A=
   IDXP peer does so by opening a BEEP channel, which may entail=0A=
   initiating a BEEP session.  A BEEP security profile offering the=0A=
   required security properties SHOULD initially be negotiated (see=0A=
   Section 10 for a discussion of security considerations).  =
Following=0A=
   the successful negotiation of the BEEP security profile, IDXP=0A=
   greetings are exchanged and connection provisioning proceeds.=0A=
=0A=
   In the following sequence a peer 'Alice' initiates an IDXP =
exchange=0A=
   with the peer 'Bob'.=0A=
=0A=
        Alice                                               Bob=0A=
          ---------------- xport connect[1] ------------------>=0A=
         <-------------------- greeting ---------------------->=0A=
         <-------------start security profile[2] ------------->=0A=
         <-------------------- greeting ---------------------->=0A=
         <------------------ start IDXP[3] ------------------->=0A=
=0A=
   Notes:=0A=
=0A=
   [1] 'Alice' initiates a transport connection to 'Bob', triggering =
the=0A=
      exchange of BEEP greeting messages.=0A=
=0A=
   [2] both entities negotiate the use of a BEEP security profile.=0A=
=0A=
   [3] both entities negotiate the use of the IDXP profile.=0A=
=0A=
   In between a pair of IDXP peers may be an arbitrary number of=0A=
   proxies.  A proxy may be necessary for administrative reasons, =
such=0A=
   as running on a firewall to allow restricted access.  Another use=0A=
=0A=
=0A=
=0A=
Feinstein, et al.       Expires December 16, 2002               [Page =
6]=0A=
=0C=0A=
Internet-Draft                  The IDXP                       June =
2002=0A=
=0A=
=0A=
   might be one proxy per company department, which forwards data =
from=0A=
   the analyzer peers in the department onto a company-wide manager=0A=
   peer.=0A=
=0A=
   A BEEP tuning profile MAY be used to create an application-layer=0A=
   tunnel that transparently forwards data over a chain of proxies.  =
The=0A=
   TUNNEL profile [7] SHOULD be used for this purpose; see [7] for =
more=0A=
   detail concerning the options available to setup an =
application-layer=0A=
   tunnel using TUNNEL, and see Section 10.1 for a discussion of =
TUNNEL=0A=
   related security considerations.  TUNNEL MUST be offered as a =
tuning=0A=
   profile for the creation of application-layer tunnels.  The =
TUNNEL=0A=
   profile MUST offer the use of some form of SASL authentication =
(c.f.,=0A=
   Section 4.1 of [8]).  Once a tunnel has been created a BEEP =
security=0A=
   profile offering the required security properties SHOULD be=0A=
   negotiated, followed by negotiation of the IDXP profile.=0A=
=0A=
   The following sequence shows how TUNNEL might be used to create =
an=0A=
   application-layer tunnel through which IDXP would operate.  A =
peer=0A=
   'Alice' initiates the creation of a BEEP session using the IDXP=0A=
   profile with the entity 'Bob' by first contacting 'proxy1'.  In =
the=0A=
   greeting exchange between 'Alice' and 'proxy1', the TUNNEL profile =
is=0A=
   selected, and subsequently the use of the TUNNEL profile is =
extended=0A=
   to reach through 'proxy2' to 'Bob'.=0A=
=0A=
   Alice              proxy1               proxy2               Bob=0A=
     -- xport connect -->=0A=
    <---- greeting ----->=0A=
     -- start TUNNEL --->=0A=
                         - xport connect[1] ->=0A=
                        <----- greeting ----->=0A=
                         --- start TUNNEL --->=0A=
                                              --- xport connect -->=0A=
                                             <----- greeting ----->=0A=
                                              --- start TUNNEL --->=0A=
                                             <----- <ok>[2] ------=0A=
                        <------- <ok> -------=0A=
    <------ <ok> -------=0A=
    <------------------------- greeting -------------------------->=0A=
    <------------------ start security profile ------------------->=0A=
    <------------------------- greeting -------------------------->=0A=
    <------------------------ start IDXP ------------------------->=0A=
=0A=
   Notes:=0A=
=0A=
   [1] Instead of immediately acknowledging the request from 'Alice' =
to=0A=
      start TUNNEL, 'proxy1' attempts to establish use of TUNNEL =
with=0A=
      'proxy2'.  'proxy2' also delays its acknowledgment to =
'proxy1'.=0A=
=0A=
=0A=
=0A=
=0A=
Feinstein, et al.       Expires December 16, 2002               [Page =
7]=0A=
=0C=0A=
Internet-Draft                  The IDXP                       June =
2002=0A=
=0A=
=0A=
   [2] 'Bob' acknowledges the request from 'proxy2' to start TUNNEL, =
and=0A=
      this acknowledgment propagates back to 'Alice' so that a =
TUNNEL=0A=
      application-layer tunnel is established from 'Alice' to 'Bob'.=0A=
=0A=
=0A=
2.2 Data Transfer=0A=
=0A=
   Between a pair of ID entities communicating over a BEEP session, =
one=0A=
   or more BEEP channels MAY be opened using the IDXP profile.  If=0A=
   desired, additional BEEP sessions MAY be established to offer=0A=
   additional channels using the IDXP profile.  However, in most=0A=
   situations additional channels using the IDXP profile SHOULD be=0A=
   opened within an existing BEEP session, as opposed to provisioning =
a=0A=
   new BEEP session containing the additional channels using the =
IDXP=0A=
   profile.=0A=
=0A=
   Peers assume the role of client or server on a per-channel basis,=0A=
   with one acting as the client and the other as the server.  A =
peer's=0A=
   role of client or server is determined independent of whether the=0A=
   peer assumed the role of initiator or listener during the BEEP=0A=
   session establishment.  Clients and servers act as sources and =
sinks,=0A=
   respectively, for exchanging data.=0A=
=0A=
   In a simple case, an analyzer peer sends data to a manager peer.=0A=
   E.g.,=0A=
=0A=
           +----------+                          +----------+=0A=
           |          |                          |          |=0A=
           |          |****** BEEP session ******|          |=0A=
           |          |                          |          |=0A=
           | Analyzer | ----- IDXP profile ----> | Manager  |=0A=
           | (Client) |                          | (Server) |=0A=
           |          |                          |          |=0A=
           |          |**************************|          |=0A=
           |          |                          |          |=0A=
           +----------+                          +----------+=0A=
=0A=
   Use of multiple BEEP channels in a BEEP session facilitates=0A=
   categorization and prioritization of data sent between IDXP =
peers.=0A=
   For example, a manager 'M1', sending alert data to another =
manager,=0A=
   'M2', may choose to open a separate channel to exchange different=0A=
   categories of alerts.  'M1' would act as the client on each of =
these=0A=
   channels, and manager 'M2' can then process and act on the =
incoming=0A=
   alerts based on their respective channel categorizations.  See=0A=
   Section 4 for more detail on how to incorporate categorization =
and/or=0A=
   prioritization into channel creation.=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Feinstein, et al.       Expires December 16, 2002               [Page =
8]=0A=
=0C=0A=
Internet-Draft                  The IDXP                       June =
2002=0A=
=0A=
=0A=
   +----------+                                            =
+----------+=0A=
   |          |                                            |          =
|=0A=
   |          |*************** BEEP session ***************|          =
|=0A=
   |          |                                            |          =
|=0A=
   |          | -- IDXP profile, network-based alerts ---> |          =
|=0A=
   | Manager  |                                            | Manager  =
|=0A=
   |   M1     | ---- IDXP profile, host-based alerts ----> |   M2     =
|=0A=
   | (Client) |                                            | (Server) =
|=0A=
   |          | ------ IDXP profile, other alerts -------> |          =
|=0A=
   |          |                                            |          =
|=0A=
   |          |********************************************|          =
|=0A=
   |          |                                            |          =
|=0A=
   +----------+                                            =
+----------+=0A=
=0A=
=0A=
2.3 Connection Teardown=0A=
=0A=
   An IDXP peer may choose to close an IDXP channel under many =
different=0A=
   circumstances (e.g., an error in processing has occurred).  To =
close=0A=
   a channel, the peer sends a "close" element (c.f., Section 2.3.1.3 =
of=0A=
   [8]) on channel zero indicating which channel is being closed.  =
An=0A=
   IDXP peer may also choose to close an entire BEEP session by =
sending=0A=
   a "close" element indicating that channel zero is to be closed.=0A=
   Section 2.3.1.3 of [8] offers a more complete discussion of the=0A=
   circumstances under which a BEEP peer is permitted to close a =
channel=0A=
   and the mechanisms for doing so.=0A=
=0A=
   It is anticipated that due to the overhead of provisioning an=0A=
   application-layer tunnel and/or a BEEP security profile, BEEP=0A=
   sessions containing IDXP channels will be long-lived.  =
Additionally,=0A=
   the repeated overhead of IDXP channel provisioning (i.e., the=0A=
   exchange of IDXP greetings) may be avoided by keeping IDXP =
channels=0A=
   open even while data is not actively being exchanged on them.  =
These=0A=
   are recommendations and, as such, IDXP peers may choose to close =
and=0A=
   re-provision BEEP sessions and/or IDXP channels as they see fit.=0A=
=0A=
2.4 Trust Model=0A=
=0A=
   In our model, trust is placed exclusively in the IDXP peers.  =
Proxies=0A=
   are always assumed to be untrustworthy.  A BEEP security profile =
is=0A=
   used to establish end-to-end security between pairs of IDXP =
peers,=0A=
   doing away with the need to place trust in any intervening =
proxies.=0A=
   Only after successful negotiation of the underlying security =
profile=0A=
   are IDXP peers to be trusted.  Only BEEP security profiles =
offering=0A=
   at least the protections required by Section 5 of [9] should be =
used=0A=
   to secure a BEEP session containing channels using the IDXP =
profile.=0A=
   See Section 3 of [8] for the registration of the TLS profile, an=0A=
   example of a BEEP security profile meeting the requirements of=0A=
=0A=
=0A=
=0A=
Feinstein, et al.       Expires December 16, 2002               [Page =
9]=0A=
=0C=0A=
Internet-Draft                  The IDXP                       June =
2002=0A=
=0A=
=0A=
   Section 5 of [9].  See Section 5 for a discussion of how IDXP=0A=
   fulfills the IDWG communications protocol requirements.=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Feinstein, et al.       Expires December 16, 2002              [Page =
10]=0A=
=0C=0A=
Internet-Draft                  The IDXP                       June =
2002=0A=
=0A=
=0A=
3. The IDXP Profile=0A=
=0A=
3.1 IDXP Profile Overview=0A=
=0A=
   The IDXP profile provides a mechanism for exchanging information=0A=
   between intrusion detection entities.  A BEEP tuning profile MAY =
be=0A=
   used to create an application-layer tunnel that transparently=0A=
   forwards data over a chain of proxies.  The TUNNEL profile [7] =
SHOULD=0A=
   be used for this purpose; see [7] for more detail concerning the=0A=
   options available to setup an application-layer tunnel using =
TUNNEL,=0A=
   and see Section 10.1 for a discussion of TUNNEL related security=0A=
   considerations.  TUNNEL MUST be offered as a tuning profile for =
the=0A=
   creation of application-layer tunnels.  The TUNNEL profile MUST =
offer=0A=
   the use of some form of SASL authentication (c.f., Section 4.1 of=0A=
   [8]).  The TLS profile SHOULD be used to provide the required=0A=
   combination of mutual-authentication, integrity, and =
confidentiality=0A=
   for the IDXP profile.  For further discussion of =
application-layer=0A=
   tunnel and security issues see Section 2.1 and Section 10.=0A=
=0A=
   The IDXP profile supports several elements of interest:=0A=
=0A=
   o  The "IDXP-Greeting" element identifies an analyzer or manager =
at=0A=
      one end of a BEEP channel to the analyzer or manager at the =
other=0A=
      end of the channel.=0A=
=0A=
   o  The "Option" element is used to convey optional channel =
parameters=0A=
      between peers during the exchange of "IDXP-Greeting" elements.=0A=
      This element is OPTIONAL.=0A=
=0A=
   o  The "IDMEF-Message" element carries the structured information =
to=0A=
      be exchanged between the peers.=0A=
=0A=
=0A=
3.2 IDXP Profile Identification and Initialization=0A=
=0A=
   The IDXP profile is identified as=0A=
=0A=
      http://iana.org/beep/transient/idwg/idxp=0A=
=0A=
   in the BEEP "profile" element during channel creation.=0A=
=0A=
   During channel creation, "IDXP-Greeting" elements MUST be =
mutually=0A=
   exchanged between the peers.  An "IDXP-Greeting" element MAY be=0A=
   contained within the corresponding "profile" element in the BEEP=0A=
   "start" element.  Including an "IDXP-Greeting" element in the =
initial=0A=
   "start" element has exactly the same semantics as passing it as =
the=0A=
   first "MSG" message on the channel.  If channel creation is=0A=
   successful, then before sending the corresponding reply, the BEEP=0A=
=0A=
=0A=
=0A=
Feinstein, et al.       Expires December 16, 2002              [Page =
11]=0A=
=0C=0A=
Internet-Draft                  The IDXP                       June =
2002=0A=
=0A=
=0A=
   peer processes the "IDXP-Greeting" element and includes the =
resulting=0A=
   response in the reply.  This response will be an "ok" element or =
an=0A=
   "error" element.  The choice of which element is returned is=0A=
   dependent on local provisioning of the peer.=0A=
=0A=
3.3 IDXP Profile Message Syntax=0A=
=0A=
   BEEP messages in the profile MUST have a MIME Content-Type [5] of=0A=
   "text/xml", "text/plain", or "application/octet-stream".  The =
syntax=0A=
   of the individual elements is specified in Section 8.1 and Section =
5=0A=
   of [4].=0A=
=0A=
3.4 IDXP Profile Semantics=0A=
=0A=
   Each BEEP peer issues the "IDXP-Greeting" element using "MSG"=0A=
   messages.  The "IDXP-Greeting" element MAY contain one or more=0A=
   "Option" sub-elements, conveying optional channel parameters.  =
Each=0A=
   BEEP peer then issues "ok" in "RPY" messages or "error" in "ERR"=0A=
   messages.  (See Section 2.3.1 of [8] for the definitions of the=0A=
   "error" and "ok" elements.) An "error" element MAY be issued within =
a=0A=
   "RPY" message when piggy-backed within a BEEP "profile" element.  =
See=0A=
   section 3.4.1 for an example of an "error" element being issued=0A=
   within a "RPY" message.  Based on the respective client/server =
roles=0A=
   negotiated during the exchange of "IDXP-Greeting" elements, the=0A=
   client sends data using "MSG" messages.  Depending on the MIME=0A=
   Content-Type, this data may be an "IDMEF-Message" element, plain=0A=
   text, or binary.  The server then issues "ok" in "RPY" messages =
or=0A=
   "error" in "ERR" messages.=0A=
=0A=
3.4.1 The IDXP-GREETING Element=0A=
=0A=
   The "IDXP-Greeting" element serves to identify the analyzer or=0A=
   manager at one end of the BEEP channel to the analyzer or manager =
at=0A=
   the other end of the channel.  The "IDXP-Greeting" element MUST=0A=
   include the role of the peer on the channel (client or server) =
and=0A=
   the Uniform Resource Identifier (URI) [1] of the peer.  =
Additionally,=0A=
   the "IDXP-Greeting" element MAY include the fully qualified =
domain=0A=
   name (c.f., [6]) of the peer.  One or more "Option" sub-elements =
MAY=0A=
   be present.=0A=
=0A=
   An "IDXP-Greeting" element MAY be sent by either peer at any =
time.=0A=
   The peer receiving the "IDXP-Greeting" MUST respond with an "ok"=0A=
   (indicating acceptance), or an "error" (indicating rejection).  A=0A=
   peer's identity and role on a channel and any optional channel=0A=
   parameters are, in effect, specified by the most recent "IDXP-=0A=
   Greeting" it sent that was answered with an "ok".=0A=
=0A=
   An "IDXP-Greeting" may be rejected (with an "error" element) =
under=0A=
=0A=
=0A=
=0A=
Feinstein, et al.       Expires December 16, 2002              [Page =
12]=0A=
=0C=0A=
Internet-Draft                  The IDXP                       June =
2002=0A=
=0A=
=0A=
   many circumstances.  These include, but are not limited to,=0A=
   authentication failure, lack of authorization to connect under =
the=0A=
   specified role, the negotiation of an inadequate ciphersuite, or =
the=0A=
   presence of a channel option that must be understood but was=0A=
   unrecognized.=0A=
=0A=
   For example, a successful creation with an embedded =
"IDXP-Greeting"=0A=
   might look like this:=0A=
=0A=
   I: MSG 0 10 . 1592 187=0A=
   I: Content-Type: text/xml=0A=
   I:=0A=
   I: <start number=3D'1'>=0A=
   I:   <profile uri=3D'http://iana.org/beep/transient/idwg/idxp'>=0A=
   I:     <![CDATA[ <IDXP-Greeting uri=3D'http://example.com/alice'=0A=
   I:       role=3D'client' /> ]]>=0A=
   I:   </profile>=0A=
   I: </start>=0A=
   I: END=0A=
   L: RPY 0 10 . 1865 91=0A=
   L: Content-Type: text/xml=0A=
   L:=0A=
   L: <profile uri=3D'http://iana.org/beep/transient/idwg/idxp'>=0A=
   L:   <![CDATA[ <ok /> ]]>=0A=
   L: </profile>=0A=
   L: END=0A=
   L: MSG 0 11 . 1956 61=0A=
   L: Content-Type: text/xml=0A=
   L:=0A=
   L: <IDXP-Greeting uri=3D'http://example.com/bob' role=3D'server' =
/>=0A=
   L: END=0A=
   I: RPY 0 11 . 1779 7=0A=
   I: Content-Type: text/xml=0A=
   I:=0A=
   I: <ok />=0A=
   I: END=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Feinstein, et al.       Expires December 16, 2002              [Page =
13]=0A=
=0C=0A=
Internet-Draft                  The IDXP                       June =
2002=0A=
=0A=
=0A=
   A creation with an embedded "IDXP-Greeting" that fails might look=0A=
   like this:=0A=
=0A=
   I: MSG 0 10 . 1776 185=0A=
   I: Content-Type: text/xml=0A=
   I:=0A=
   I: <start number=3D'1'>=0A=
   I:   <profile uri=3D'http://iana.org/beep/transient/idwg/idxp'>=0A=
   I:     <![CDATA[ <IDXP-Greeting uri=3D'http://example.com/eve'=0A=
   I:       role=3D'client' /> ]]>=0A=
   I:   </profile>=0A=
   I: </start>=0A=
   I: END=0A=
   L: RPY 0 10 . 1592 182=0A=
   L: Content-Type: text/xml=0A=
   L:=0A=
   L: <profile uri=3D'http://iana.org/beep/transient/idwg/idxp'>=0A=
   L:   <![CDATA[=0A=
   L:     <error code=3D'530'>'http://example.com/eve' must first=0A=
   L:       negotiate the TLS profile</error> ]]>=0A=
   L: </profile>=0A=
   L: END=0A=
=0A=
=0A=
3.4.2 The OPTION Element=0A=
=0A=
   If present, the "Option" element MUST be contained within an =
"IDXP-=0A=
   Greeting" element.  An individual "IDXP-Greeting" element MAY =
contain=0A=
   one or more "Option" sub-elements.  Each "Option" element within =
an=0A=
   "IDXP-Greeting" element represents a request to enable an IDXP =
option=0A=
   on the channel being negotiated.  See Section 4 for a complete=0A=
   description of IDXP options and the "Option" element.=0A=
=0A=
3.4.3 The IDMEF-MESSAGE Element=0A=
=0A=
   The "IDMEF-Message" element carries the information to be =
exchanged=0A=
   between the peers.  See Section 5 of [4] for the definition of =
this=0A=
   element.=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Feinstein, et al.       Expires December 16, 2002              [Page =
14]=0A=
=0C=0A=
Internet-Draft                  The IDXP                       June =
2002=0A=
=0A=
=0A=
4. IDXP Options=0A=
=0A=
   IDXP provides a service for the reliable exchange of data between=0A=
   intrusion detection entities.  Options are used to alter the=0A=
   semantics of the service.=0A=
=0A=
   The specification of an IDXP option MUST define:=0A=
=0A=
   o  the identity of the option;=0A=
=0A=
   o  what content, if any, is contained within the option; and,=0A=
=0A=
   o  the processing rules for the option.=0A=
=0A=
   An option registration template (c.f.  Section 6) organizes this=0A=
   information.=0A=
=0A=
   An "Option" element is contained within an "IDXP-Greeting" =
element.=0A=
   The "IDXP-Greeting" element itself MAY contain one or more =
"Option"=0A=
   elements.  The "Option" element has several attributes and contains=0A=
   arbitrary content:=0A=
=0A=
   o  the "internal" and the "external" attributes, exactly one of =
which=0A=
      MUST be present, uniquely identify the option;=0A=
=0A=
   o  the "mustUnderstand" attribute, whose presence is OPTIONAL and=0A=
      whose default value is "false", specifies whether the option, =
if=0A=
      unrecognized, MUST cause an error in processing to occur; and,=0A=
=0A=
   o  the "localize" attribute, whose presence is OPTIONAL, =
specifies=0A=
      one or more language tokens, each identifying a desirable =
language=0A=
      tag to be used if textual diagnostics are returned to the=0A=
      originator.=0A=
=0A=
   The value of the "internal" attribute is the IANA-registered name =
for=0A=
   the option.  If the "internal" attribute is not present, then the=0A=
   value of the "external" attribute is a URI or URI with a =
fragment-=0A=
   identifier.  Note that a relative-URI value is not allowed.=0A=
=0A=
   The "mustUnderstand" attribute specifies whether the peer may =
ignore=0A=
   the option if it is unrecognized.  If the value of the=0A=
   "mustUnderstand" attribute is "true", and if the peer does not=0A=
   recognize the option, then an error in processing has occurred.  =
When=0A=
   absent, the value of the "mustUnderstand" attribute is defined to =
be=0A=
   "false".=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Feinstein, et al.       Expires December 16, 2002              [Page =
15]=0A=
=0C=0A=
Internet-Draft                  The IDXP                       June =
2002=0A=
=0A=
=0A=
4.1 The channelPriority Option=0A=
=0A=
   Section 7.3 contains the IDXP option registration for the=0A=
   "channelPriority" option.  This option contains a =
"channelPriority"=0A=
   element (c.f., Section 8.2).=0A=
=0A=
   By default, IDXP does not place any requirements on how peers =
should=0A=
   manage multiple IDXP channels.  The "channelPriority" option =
provides=0A=
   a way for peers using multiple IDXP channels to request relative=0A=
   priorities for each channel.  When sending an "IDXP-Greeting" =
element=0A=
   during the provisioning of an IDXP channel, the originating peer =
MAY=0A=
   request that the remote peer assign a priority to the channel by=0A=
   including an "Option" element containing a "channelPriority" =
element.=0A=
=0A=
   The "channelPriority" element has one attribute named "priority", =
of=0A=
   range 0..2147483647.  This attribute is REQUIRED.  Not=0A=
   coincidentally, this is the maximum range of possible BEEP =
channel=0A=
   numbers.  0 is defined to represent the highest priority, with=0A=
   relative priority decreasing as the "priority" value ascends.=0A=
=0A=
   For example, during the exchange of "IDXP-Greeting" elements =
during=0A=
   channel provisioning, an analyzer successfully requests that a=0A=
   manager assign a priority to the channel:=0A=
=0A=
=0A=
       analyzer                                           manager=0A=
          --------------- greeting w/ option ----------------->=0A=
         <---------------------- <ok> ------------------------=0A=
=0A=
   C: MSG 1 17 . 1984 165=0A=
   C: Content-Type: text/xml=0A=
   C:=0A=
   C: <IDXP-Greeting uri=3D'http://example.com/alice' =
role=3D'client'>=0A=
   C:   <Option internal=3D'channelPriority'>=0A=
   C:     <channelPriority priority=3D'0' />=0A=
   C:   </Option>=0A=
   C: </IDXP-Greeting>=0A=
   C: END=0A=
   S: RPY 1 17 . 2001 7=0A=
   S: Content-Type: text/xml=0A=
   S:=0A=
   S: <ok />=0A=
   S: END=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Feinstein, et al.       Expires December 16, 2002              [Page =
16]=0A=
=0C=0A=
Internet-Draft                  The IDXP                       June =
2002=0A=
=0A=
=0A=
   For example, during the exchange of "IDXP-Greeting" elements =
during=0A=
   channel provisioning, a manager unsuccessfully requests that an=0A=
   analyzer assign a priority to the channel:=0A=
=0A=
=0A=
       analyzer                                           manager=0A=
         <---------------- greeting w/ option ----------------=0A=
          --------------------- <error> ---------------------->=0A=
=0A=
   S: MSG 1 17 . 1312 194=0A=
   S: Content-Type: text/xml=0A=
   S:=0A=
   S: <IDXP-Greeting uri=3D'http://example.com/bob' role=3D'server'>=0A=
   S:   <Option internal=3D'channelPriority' =
mustUnderstand=3D'true'>=0A=
   S:     <channelPriority priority=3D'2147483647' />=0A=
   S:   </Option>=0A=
   S: </IDXP-Greeting>=0A=
   S: END=0A=
   C: ERR 1 17 . 451 68=0A=
   C: Content-Type: text/xml=0A=
   C:=0A=
   C: <error code=3D'504'>'channelPriority' option was =
unrecognized</error>=0A=
   C: END=0A=
=0A=
=0A=
4.2 The streamType Option=0A=
=0A=
   Section 7.4 contains the IDXP option registration for the=0A=
   "streamType" option.  This option contains a "streamType" element=0A=
   (c.f., Section 8.3).=0A=
=0A=
   By default, IDXP provides no explicit method for categorizing=0A=
   channels.  The "streamType" option provides a way for peers to=0A=
   request that a channel be categorized as a particular stream =
type.=0A=
   When sending an "IDXP-Greeting" element during the provisioning of =
an=0A=
   IDXP channel, the originating peer MAY request that the remote =
peer=0A=
   assign a stream type to the channel by including an "Option" =
element=0A=
   containing a "streamType" element.=0A=
=0A=
   The "streamType" element has one attribute named "type", with the=0A=
   possible values of "alert", "heartbeat", or "config".  This =
attribute=0A=
   is REQUIRED.  A value of "alert" indicates that the channel should =
be=0A=
   categorized as being used for the exchange of ID alerts.  A value =
of=0A=
   "heartbeat" indicates that the channel should be categorized as =
being=0A=
   used for the exchange of heartbeat messages such as the =
"Heartbeat"=0A=
   element (c.f., Section 5 of [4]).  A value of "config" indicates =
that=0A=
   the channel should be categorized as being used for the exchange =
of=0A=
   configuration messages.=0A=
=0A=
=0A=
=0A=
Feinstein, et al.       Expires December 16, 2002              [Page =
17]=0A=
=0C=0A=
Internet-Draft                  The IDXP                       June =
2002=0A=
=0A=
=0A=
   For example, during the exchange of "IDXP-Greeting" elements =
during=0A=
   channel provisioning, an analyzer successfully requests that a=0A=
   manager assign a stream type to the channel:=0A=
=0A=
=0A=
       analyzer                                           manager=0A=
          --------------- greeting w/ option ----------------->=0A=
         <---------------------- <ok> ------------------------=0A=
=0A=
   C: MSG 1 21 . 1963 155=0A=
   C: Content-Type: text/xml=0A=
   C:=0A=
   C: <IDXP-Greeting uri=3D'http://example.com/alice' =
role=3D'client'>=0A=
   C:   <Option internal=3D'streamType'>=0A=
   C:     <streamType type=3D'alert' />=0A=
   C:   </Option>=0A=
   C: </IDXP-Greeting>=0A=
   C: END=0A=
   S: RPY 1 21 . 1117 7=0A=
   S: Content-Type: text/xml=0A=
   S:=0A=
   S: <ok />=0A=
   S: END=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Feinstein, et al.       Expires December 16, 2002              [Page =
18]=0A=
=0C=0A=
Internet-Draft                  The IDXP                       June =
2002=0A=
=0A=
=0A=
   For example, during the exchange of "IDXP-Greeting" elements =
during=0A=
   channel provisioning, a manager unsuccessfully requests that an=0A=
   analyzer assign a stream type to the channel:=0A=
=0A=
=0A=
=0A=
       analyzer                                           manager=0A=
         <---------------- greeting w/ option ----------------=0A=
          --------------------- <error> ---------------------->=0A=
=0A=
   S: MSG 1 21 . 1969 176=0A=
   S: Content-Type: text/xml=0A=
   S:=0A=
   S: <IDXP-Greeting uri=3D'http://example.com/bob' role=3D'server'>=0A=
   S:   <Option internal=3D'streamType' mustUnderstand=3D'true'>=0A=
   S:     <streamType type=3D'config' />=0A=
   S:   </Option>=0A=
   S: </IDXP-Greeting>=0A=
   S: END=0A=
   C: ERR 1 21 . 1292 63=0A=
   C: Content-Type: text/xml=0A=
   C:=0A=
   C: <error code=3D'504'>'streamType' option was =
unrecognized</error>=0A=
   C: END=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Feinstein, et al.       Expires December 16, 2002              [Page =
19]=0A=
=0C=0A=
Internet-Draft                  The IDXP                       June =
2002=0A=
=0A=
=0A=
5. Fulfillment of IDWG Communications Protocol Requirements=0A=
=0A=
   The following lists the communications protocol requirements=0A=
   established in Section 5 of [9] and, for each requirement, =
describes=0A=
   the manner in which it is fulfilled by IDXP.=0A=
=0A=
   The [protocol] MUST support reliable transmission of messages.=0A=
=0A=
      IDXP operates over BEEP, which operates only over reliable=0A=
      connection-oriented transport protocols (e.g., TCP).  In =
addition,=0A=
      BEEP peers communicate using a simple request-response =
protocol,=0A=
      which provides end-to-end reliability between peers.=0A=
=0A=
   The [protocol] MUST support transmission of messages between ID=0A=
   components across firewall boundaries without compromising =
security.=0A=
=0A=
      The TUNNEL profile [7] MUST be offered as an option for =
creation=0A=
      of application-layer tunnels to allow operation across =
firewalls.=0A=
      The TUNNEL profile SHOULD be used to provide an =
application-layer=0A=
      tunnel.  The ability to authenticate hosts during the creation =
of=0A=
      an application-layer tunnel MUST be provided by the mechanism=0A=
      chosen to create such tunnels.  A firewall may therefore be=0A=
      configured to authenticate all hosts attempting to tunnel into =
the=0A=
      protected network.  If the TUNNEL profile is used, SASL (c.f.,=0A=
      Section 4.1 of [8]) MUST be offered as a mechanism by which =
hosts=0A=
      can be authenticated.=0A=
=0A=
   The [protocol] MUST support mutual authentication of the analyzer =
and=0A=
   the manager to each other.=0A=
=0A=
      IDXP supports mutual authentication of the peers through the =
use=0A=
      of an appropriate underlying BEEP security profile.  The TLS=0A=
      profile and members of the SASL family of profiles (c.f., =
Section=0A=
      4.1 of [8]) are examples of security profiles that may be used =
to=0A=
      authenticate the identity of communicating ID components.  TLS=0A=
      MUST be offered as a mechanism to provide mutual =
authentication,=0A=
      and TLS SHOULD be used to provide mutual authentication.=0A=
=0A=
   The [protocol] MUST support confidentiality of the message =
content=0A=
   during message exchange.  The selected design MUST be capable of=0A=
   supporting a variety of encryption algorithms and MUST be =
adaptable=0A=
   to a wide variety of environments.=0A=
=0A=
      IDXP supports confidentiality through the use of an =
appropriate=0A=
      underlying BEEP security profile.  The TLS profile is an example =
a=0A=
      security profile that offers confidentiality.  The TLS profile=0A=
      with the TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA cipher suite MUST =
be=0A=
      offered as a mechanism to provide confidentiality, and TLS =
with=0A=
=0A=
=0A=
=0A=
Feinstein, et al.       Expires December 16, 2002              [Page =
20]=0A=
=0C=0A=
Internet-Draft                  The IDXP                       June =
2002=0A=
=0A=
=0A=
      this cipher suite SHOULD be used to provide confidentiality.  =
The=0A=
      TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA cipher suite uses ephemeral=0A=
      Diffie-Hellman (DHE) with DSS signatures for key exchange and=0A=
      triple DES (3DES) and cipher-block chaining (CBC) for =
encryption.=0A=
      Stronger cipher suites are optional.=0A=
=0A=
   The [protocol] MUST ensure the integrity of the message content.  =
The=0A=
   selected design MUST be capable of supporting a variety of =
integrity=0A=
   mechanisms and MUST be adaptable to a wide variety of =
environments.=0A=
=0A=
      IDXP supports message integrity through the use of an =
appropriate=0A=
      underlying BEEP security profile.  The TLS profile and members =
of=0A=
      the SASL family of profiles (c.f., Section 4.1 of [8]) are=0A=
      examples of security profiles that offer message integrity.  =
The=0A=
      TLS profile with the TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA cipher=0A=
      suite MUST be offered as a mechanism to provide integrity, and =
TLS=0A=
      with this cipher suite SHOULD be used to provide integrity.  =
The=0A=
      TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA cipher suite uses the Secure=0A=
      Hash Algorithm (SHA) for integrity protection using a keyed=0A=
      message authentication code.  Stronger cipher suites are =
optional.=0A=
=0A=
   The [protocol] SHOULD be able to ensure non-repudiation of the =
origin=0A=
   of IDMEF messages.=0A=
=0A=
      IDXP supports non-repudiation of session origin through the use =
of=0A=
      an appropriate underlying BEEP security profile.  An IDXP peer=0A=
      application MAY use IDMEF content and/or BEEP session =
credentials=0A=
      to provide for non-repudiation of message origin.  The TLS =
profile=0A=
      is an example of a security profile that offers non-repudiation =
of=0A=
      session origin through the authentication of public-key=0A=
      certificates.  TLS MUST be offered as a mechanism to provide =
non-=0A=
      repudiation of session origin, and TLS SHOULD be used to =
provide=0A=
      non-repudiation of session origin.=0A=
=0A=
   The [protocol] SHOULD resist protocol denial of service attacks.=0A=
=0A=
      IDXP supports resistance to denial of service (DoS) attacks=0A=
      through the use of an appropriate underlying BEEP security=0A=
      profile.  BEEP peers offering the IDXP profile MUST offer the =
use=0A=
      of TLS with the TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA cipher =
suite,=0A=
      and SHOULD use TLS with that cipher suite.  To resist DoS =
attacks=0A=
      it is helpful to discard traffic arising from a =
non-authenticated=0A=
      source.  BEEP peers MUST support the use of authentication in=0A=
      conjunction with any mechanism used to create =
application-layer=0A=
      tunnels.  In particular, the use of some form of SASL=0A=
      authentication (c.f., Section 4.1 of [8]) MUST be offered to=0A=
      provide authentication in the use of the TUNNEL profile.  See=0A=
      Section 7 of [7] for a discussion of security considerations =
in=0A=
=0A=
=0A=
=0A=
Feinstein, et al.       Expires December 16, 2002              [Page =
21]=0A=
=0C=0A=
Internet-Draft                  The IDXP                       June =
2002=0A=
=0A=
=0A=
      the use of the TUNNEL profile.=0A=
=0A=
   The [protocol] SHOULD resist malicious duplication of messages.=0A=
=0A=
      IDXP supports resistance to malicious duplication of messages=0A=
      (i.e., replay attacks) through the use of an appropriate=0A=
      underlying BEEP security profile.  The TLS profile is an =
example=0A=
      of a security profile offering resistance to replay attacks.  =
The=0A=
      TLS profile with the TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA cipher=0A=
      suite MUST be offered as a mechanism to provide resistance =
against=0A=
      replay attacks, and TLS with this cipher suite SHOULD be used =
to=0A=
      provide resistance against replay attacks.  The=0A=
      TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA cipher suite uses =
cipher-block=0A=
      chaining (CBC) to ensure that even if a message is duplicated =
the=0A=
      cipher-text duplicate will produce a very different plain-text=0A=
      result.  Stronger cipher suites are optional.=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Feinstein, et al.       Expires December 16, 2002              [Page =
22]=0A=
=0C=0A=
Internet-Draft                  The IDXP                       June =
2002=0A=
=0A=
=0A=
6. IDXP Option Registration Template=0A=
=0A=
   When an IDXP option is registered, the following information is=0A=
   supplied:=0A=
=0A=
   Option Identification: specify the NMTOKEN or the URI that=0A=
   authoritatively identifies this option.=0A=
=0A=
   Contains: specify the XML content that is contained within the=0A=
   "Option" element.=0A=
=0A=
   Processing Rules: specify the processing rules associated with =
the=0A=
   option.=0A=
=0A=
   Contact Information: specify the postal and electronic contact=0A=
   information for the author(s) of the option.=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Feinstein, et al.       Expires December 16, 2002              [Page =
23]=0A=
=0C=0A=
Internet-Draft                  The IDXP                       June =
2002=0A=
=0A=
=0A=
7. Initial Registrations=0A=
=0A=
7.1 Registration: The IDXP Profile=0A=
=0A=
   Profile identification: http://iana.org/beep/transient/idwg/idxp=0A=
=0A=
   Messages exchanged during channel creation: "IDXP-Greeting"=0A=
=0A=
   Messages starting one-to-one exchanges: "IDXP-Greeting", "IDMEF-=0A=
   Message"=0A=
=0A=
   Messages in positive replies: "ok"=0A=
=0A=
   Messages in negative replies: "error"=0A=
=0A=
   Messages in one-to-many exchanges: none=0A=
=0A=
   Message syntax: c.f., Section 3.3=0A=
=0A=
   Message semantics: c.f., Section 3.4=0A=
=0A=
   Contact information: c.f., the "Authors' Addresses" section of =
this=0A=
   memo=0A=
=0A=
7.2 Registration: The System (Well-Known) TCP port number for IDXP=0A=
=0A=
   Protocol Number: TCP=0A=
=0A=
   Message Formats, Types, Opcodes, and Sequences: c.f., Section 3.3=0A=
=0A=
   Functions: c.f., Section 3.4=0A=
=0A=
   Use of Broadcast/Multicast: none=0A=
=0A=
   Proposed Name: Intrusion Detection Exchange Protocol=0A=
=0A=
   Short name: idxp=0A=
=0A=
   Contact Information: c.f., the "Authors' Addresses" section of =
this=0A=
   memo=0A=
=0A=
7.3 Registration: The channelPriority Option=0A=
=0A=
   Option Identification: channelPriority=0A=
=0A=
   Contains: channelPriority (c.f., Section 8.2)=0A=
=0A=
   Processing Rules: c.f., Section 4.1=0A=
=0A=
=0A=
=0A=
Feinstein, et al.       Expires December 16, 2002              [Page =
24]=0A=
=0C=0A=
Internet-Draft                  The IDXP                       June =
2002=0A=
=0A=
=0A=
   Contact Information: c.f., the "Authors' Addresses" section of =
this=0A=
   memo=0A=
=0A=
7.4 Registration: The streamType Option=0A=
=0A=
   Option Identification: streamType=0A=
=0A=
   Contains: streamType (c.f., Section 8.3)=0A=
=0A=
   Processing Rules: c.f., Section 4.2=0A=
=0A=
   Contact Information: c.f., the "Authors' Addresses" section of =
this=0A=
   memo=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Feinstein, et al.       Expires December 16, 2002              [Page =
25]=0A=
=0C=0A=
Internet-Draft                  The IDXP                       June =
2002=0A=
=0A=
=0A=
8. The DTDs=0A=
=0A=
8.1 The IDXP DTD=0A=
=0A=
   The following is the DTD defining the valid elements for the IDXP=0A=
   profile=0A=
=0A=
     <!--=0A=
     DTD for the IDXP Profile, as of 2002-01-08=0A=
=0A=
     Refer to this DTD as:=0A=
=0A=
       <!ENTITY % IDXP PUBLIC "-//IETF//DTD RFC XXXX IDXP v1.0//EN">=0A=
=0A=
       %IDXP;=0A=
     -->=0A=
=0A=
     <!-- Includes -->=0A=
=0A=
       <!ENTITY % BEEP PUBLIC "-//IETF//DTD BEEP//EN">=0A=
=0A=
       %BEEP;=0A=
=0A=
=0A=
       <!ENTITY % IDMEF-Message PUBLIC "-//IETF//DTD RFC XXXX IDMEF =
v1.0//EN">=0A=
=0A=
       %IDMEF;=0A=
=0A=
     <!--=0A=
       Profile Summary=0A=
=0A=
         BEEP profile http://iana.org/beep/transient/idwg/idxp=0A=
=0A=
         role       MSG               RPY      ERR=0A=
         =3D=3D=3D=3D       =3D=3D=3D               =3D=3D=3D      =
=3D=3D=3D=0A=
         I or L     IDXP-Greeting     ok       error=0A=
         C          IDMEF-Message     ok       error=0A=
     -->=0A=
=0A=
     <!--=0A=
       Entity Definitions=0A=
=0A=
             entity        syntax/reference     example=0A=
             =3D=3D=3D=3D=3D=3D        =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D     =
=3D=3D=3D=3D=3D=3D=3D=0A=
         an authoritative identification=0A=
             URI           c.f., [RFC-2396]       http://example.com=0A=
=0A=
         a fully qualified domain name=0A=
=0A=
=0A=
=0A=
Feinstein, et al.       Expires December 16, 2002              [Page =
26]=0A=
=0C=0A=
Internet-Draft                  The IDXP                       June =
2002=0A=
=0A=
=0A=
             FQDN          c.f., [RFC-1034]       www.example.com=0A=
     -->=0A=
=0A=
     <!ENTITY % URI      "CDATA">=0A=
     <!ENTITY % FQDN     "CDATA">=0A=
=0A=
     <!--=0A=
       The IDXP-Greeting element declares the role and identity of=0A=
       the peer issuing it, on a per channel basis. The=0A=
       IDXP-Greeting element may contain one or more Option=0A=
       sub-elements.=0A=
     -->=0A=
=0A=
   <!ELEMENT IDXP-Greeting  (Option*)>=0A=
   <!ATTLIST IDXP-Greeting=0A=
             uri            %URI;                #REQUIRED=0A=
             role           (client|server)      #REQUIRED=0A=
             fqdn           %FQDN;               #IMPLIED>=0A=
=0A=
     <!--=0A=
       The Option element conveys an IDXP channel option.=0A=
       Note that the %LOCS entity is imported from the BEEP Channel=0A=
       Management DTD.=0A=
     -->=0A=
=0A=
   <!ELEMENT Option (ANY)>=0A=
   <!ATTLIST Option=0A=
             internal       NMTOKEN              ""=0A=
             external       %URI;                ""=0A=
             mustUnderstand (true|false)         "false"=0A=
             localize       %LOCS;               "i-default">=0A=
=0A=
     <!--=0A=
       The IDMEF-Message element conveys the intrusion detection=0A=
       information that is exchanged.  This element is defined in =
the=0A=
       idmef-message.dtd=0A=
     -->=0A=
=0A=
   <!-- End of DTD -->=0A=
=0A=
=0A=
8.2 The channelPriority Option DTD=0A=
=0A=
   The following is the DTD defining the valid elements for the=0A=
   channelPriority option=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Feinstein, et al.       Expires December 16, 2002              [Page =
27]=0A=
=0C=0A=
Internet-Draft                  The IDXP                       June =
2002=0A=
=0A=
=0A=
     <!--=0A=
     DTD for the channelPriority IDXP option, as of 2002-01-08=0A=
=0A=
     Refer to this DTD as:=0A=
=0A=
       <!ENTITY % IDXP-channelPriority PUBLIC=0A=
         "-//IETF//DTD RFC XXXX IDXP-channelPriority v1.0//EN">=0A=
=0A=
       %IDXP-channelPriority;=0A=
     -->=0A=
=0A=
     <!--=0A=
       Entity Definitions=0A=
=0A=
             entity        syntax/reference     example=0A=
             =3D=3D=3D=3D=3D=3D        =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D     =
=3D=3D=3D=3D=3D=3D=3D=0A=
       a priority number=0A=
             PRIORITY      0..2147483647        1=0A=
     -->=0A=
=0A=
   <!ENTITY % PRIORITY          "CDATA">=0A=
=0A=
   <!ELEMENT channelPriority    EMPTY>=0A=
   <!ATTLIST channelPriority=0A=
             priority           %PRIORITY    #REQUIRED>=0A=
=0A=
   <!-- End of DTD -->=0A=
=0A=
=0A=
8.3 The streamType DTD=0A=
=0A=
   The following is the DTD defining the valid elements for the=0A=
   streamType option=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Feinstein, et al.       Expires December 16, 2002              [Page =
28]=0A=
=0C=0A=
Internet-Draft                  The IDXP                       June =
2002=0A=
=0A=
=0A=
     <!--=0A=
     DTD for the streamType IDXP option, as of 2002-01-08=0A=
=0A=
     Refer to this DTD as:=0A=
=0A=
       <!ENTITY % IDXP-streamType PUBLIC=0A=
         "-//IETF//DTD RFC XXXX IDXP-streamType v1.0//EN">=0A=
=0A=
       %IDXP-streamType;=0A=
     -->=0A=
=0A=
     <!--=0A=
       Entity Definitions=0A=
=0A=
             entity        syntax/reference                example=0A=
             =3D=3D=3D=3D=3D=3D        =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D                =
=3D=3D=3D=3D=3D=3D=3D=0A=
        a stream type=0A=
             STYPE         (alert | heartbeat | config)    "alert"=0A=
     -->=0A=
=0A=
   <!ENTITY % STYPE        (alert|heartbeat|config)>=0A=
=0A=
   <!ELEMENT streamType    EMPTY>=0A=
   <!ATTLIST streamType=0A=
             type          %STYPE    #REQUIRED>=0A=
=0A=
   <!-- End of DTD -->=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Feinstein, et al.       Expires December 16, 2002              [Page =
29]=0A=
=0C=0A=
Internet-Draft                  The IDXP                       June =
2002=0A=
=0A=
=0A=
9. Reply Codes=0A=
=0A=
   This section lists the three-digit error codes the IDXP profile =
may=0A=
   generate.=0A=
=0A=
   code    meaning=0A=
   =3D=3D=3D=3D    =3D=3D=3D=3D=3D=3D=3D=0A=
   421     Service not available=0A=
           (E.g., the peer does not have sufficient resources.)=0A=
=0A=
   450     Requested action not taken=0A=
           (E.g., DNS lookup failed or connection could not=0A=
            be established. See also 550.)=0A=
=0A=
   454     Temporary authentication failure=0A=
=0A=
   500     General syntax error=0A=
           (E.g., poorly-formed XML)=0A=
=0A=
   501     Syntax error in parameters=0A=
           (E.g., non-valid XML)=0A=
=0A=
   504     Parameter not implemented=0A=
=0A=
   530     Authentication required=0A=
=0A=
   534     Authentication mechanism insufficient=0A=
           (E.g., cipher suite too weak, sequence exhausted, etc.)=0A=
=0A=
   535     Authentication failure=0A=
=0A=
   537     Action not authorized for user=0A=
=0A=
   550     Requested action not taken=0A=
           (E.g., peer could be contacted, but=0A=
            malformed greeting or no IDXP profile advertised.)=0A=
=0A=
   553     Parameter invalid=0A=
=0A=
   554     Transaction failed=0A=
           (E.g., policy violation)=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Feinstein, et al.       Expires December 16, 2002              [Page =
30]=0A=
=0C=0A=
Internet-Draft                  The IDXP                       June =
2002=0A=
=0A=
=0A=
10. Security Considerations=0A=
=0A=
   The IDXP profile is a profile of BEEP.  In BEEP, transport =
security,=0A=
   user authentication, and data exchange are orthogonal.  Refer to=0A=
   Section 8 of [8] for a discussion of this.  It is strongly=0A=
   recommended that those wanting to use the IDXP profile initially=0A=
   negotiate a BEEP security profile between the peers that offers =
the=0A=
   required security properties.  The TLS profile SHOULD be used to=0A=
   provide for transport security.  See Section 5 for a discussion =
of=0A=
   how IDXP fulfills the IDWG communications protocol requirements.=0A=
=0A=
   See Section 2.4 for a discussion of the trust model.=0A=
=0A=
10.1 Use of the TUNNEL Profile=0A=
=0A=
   See Section 5 for IDXP's requirements on application-layer =
tunneling=0A=
   and the TUNNEL profile specifically.  See Section 7 of [7] for a=0A=
   discussion of the security considerations inherent in the use of =
the=0A=
   TUNNEL profile.=0A=
=0A=
10.2 Use of Underlying Security Profiles=0A=
=0A=
   At present, the TLS profile is the only BEEP security profile =
known=0A=
   to meet all of the requirements set forth in Section 5 of [9].  =
When=0A=
   securing a BEEP session with the TLS profile, the=0A=
   TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA cipher suite offers an =
acceptable=0A=
   level of security.  See Section 5 for a discussion of how IDXP=0A=
   fulfills the IDWG communications requirements through the use of =
an=0A=
   underlying security profile.=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Feinstein, et al.       Expires December 16, 2002              [Page =
31]=0A=
=0C=0A=
Internet-Draft                  The IDXP                       June =
2002=0A=
=0A=
=0A=
References=0A=
=0A=
   [1]  Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform =
Resource=0A=
        Identifiers (URI): Generic Syntax", RFC 2396, August 1998.=0A=
=0A=
   [2]  Bradner, S., "Key words for use in RFCs to Indicate =
Requirement=0A=
        Levels", BCP 14, RFC 2119, March 1997.=0A=
=0A=
   [3]  Bray, T., Paoli, J., Sperberg-McQueen, C. and E. Maler,=0A=
        "Extensible Markup Language (XML) 1.0 (2nd ed)", W3C =
REC-xml,=0A=
        October 2000, <http://www.w3.org/TR/REC-xml>.=0A=
=0A=
   [4]  Curry, D. and H. Debar, "Intrusion Detection Message =
Exchange=0A=
        Format Data Model and Extensible Markup Language (XML) =
Document=0A=
        Type Definition", RFC XXXX, Month YYYY.=0A=
=0A=
   [5]  Freed, N. and N. Borenstein, "Multipurpose Internet Mail=0A=
        Extensions (MIME) Part Two: Media Types", RFC 2046, November=0A=
        1996.=0A=
=0A=
   [6]  Mockapetris, P., "Domain names - concepts and facilities", =
STD=0A=
        13, RFC 1034, November 1987.=0A=
=0A=
   [7]  New, D., "The TUNNEL Profile Registration", RFC XXXX, Month=0A=
        YYYY.=0A=
=0A=
   [8]  Rose, M., "The Blocks Extensible Exchange Protocol Core", =
RFC=0A=
        3080, March 2001.=0A=
=0A=
   [9]  Wood, M. and M. Erlinger, "Intrusion Detection Message =
Exchange=0A=
        Requirements", RFC XXXX, Month YYYY.=0A=
=0A=
=0A=
Authors' Addresses=0A=
=0A=
   Benjamin S. Feinstein=0A=
   Guardent, Inc.=0A=
=0A=
   EMail: Ben.Feinstein@guardent.com=0A=
   URI:   http://www.guardent.com/=0A=
=0A=
=0A=
   Gregory A. Matthews=0A=
   CSC/NASA Ames Research Center=0A=
=0A=
   EMail: gmatthew@nas.nasa.gov=0A=
   URI:   http://www.nas.nasa.gov/=0A=
=0A=
=0A=
=0A=
=0A=
Feinstein, et al.       Expires December 16, 2002              [Page =
32]=0A=
=0C=0A=
Internet-Draft                  The IDXP                       June =
2002=0A=
=0A=
=0A=
   John C. C. White=0A=
   MITRE Corporation=0A=
=0A=
   EMail: jccw@mitre.org=0A=
   URI:   http://www.mitre.org/=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Feinstein, et al.       Expires December 16, 2002              [Page =
33]=0A=
=0C=0A=
Internet-Draft                  The IDXP                       June =
2002=0A=
=0A=
=0A=
Appendix A. IANA Considerations=0A=
=0A=
   The IANA registers "IDXP" as a standards-track BEEP profile, as=0A=
   specified in Section 7.1.  The IANA changes the IDXP profile=0A=
   identification to "http://iana.org/beep/IDXP".=0A=
=0A=
   The IANA registers "idxp" as a TCP port number, as specified in=0A=
   Section 7.2=0A=
=0A=
   The IANA maintains a list of:=0A=
=0A=
      IDXP options, c.f., Section 6.=0A=
=0A=
   For this list, the IESG is responsible for assigning a designated=0A=
   expert to review the specification prior to the IANA making the=0A=
   assignment.  As a courtesy to developers of non-standards track =
IDXP=0A=
   options, the mailing list idxp-java-users@lists.sourceforge.net =
may=0A=
   be used to solicit commentary.=0A=
=0A=
   The IANA makes the registrations specified in Section 7.3 and =
Section=0A=
   7.4.=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Feinstein, et al.       Expires December 16, 2002              [Page =
34]=0A=
=0C=0A=
Internet-Draft                  The IDXP                       June =
2002=0A=
=0A=
=0A=
Appendix B. History of Significant Changes=0A=
=0A=
   The RFC Editor should remove this section and its corresponding =
TOC=0A=
   references prior to publication.=0A=
=0A=
B.1 Significant Changes Since beep-idxp-04=0A=
=0A=
   Added sentence to Section 3.4 explaining the situation in which =
an=0A=
   "error" element may be issued within an "RPY" message.=0A=
=0A=
   Modified examples in Section 4.1 and 4.2, changing the message =
types=0A=
   from "RPY" to "ERR" for the negative response sent by the client.=0A=
=0A=
   Fixed two locations where we were referencing the wrong section =
of=0A=
   the requirements document.=0A=
=0A=
   Removed references to IP and the %IP attribute.=0A=
=0A=
   Modified part of Section 5 dealing with non-repudiation of =
message=0A=
   origin.=0A=
=0A=
   Modified Section 1.3 to further refine terminology.=0A=
=0A=
   Replaced all remaining references to "entities" with references =
to=0A=
   "peers".=0A=
=0A=
B.2 Significant Changes Since beep-idxp-03=0A=
=0A=
   Modified references to Internet-Drafts to contain placeholders =
for=0A=
   their forthcoming RFC numbers.=0A=
=0A=
   Modified IDMEF formal public identifier (FPI) in the IDXP DTD to=0A=
   reflect the changes in draft-ietf-idwg-idmef-xml-06.=0A=
=0A=
   Modified IDXP FPI for the IDXP DTD to be more in line with the =
IDMEF=0A=
   FPI.=0A=
=0A=
B.3 Significant Changes Since beep-idxp-02=0A=
=0A=
   Added IDXP option registration template and registered two =
initial=0A=
   options.=0A=
=0A=
   Indicated that the IANA should change the profile identification =
to=0A=
   "http://iana.org/beep/IDXP" upon adoption of IDXP as a standards-=0A=
   track BEEP profile.=0A=
=0A=
   Renamed the "Options" element to "Option" and allowed multiple=0A=
   "Option" sub-elements within an "IDXP-Greeting" element.  Also =
added=0A=
=0A=
=0A=
=0A=
Feinstein, et al.       Expires December 16, 2002              [Page =
35]=0A=
=0C=0A=
Internet-Draft                  The IDXP                       June =
2002=0A=
=0A=
=0A=
   attributes to "Option" element.=0A=
=0A=
   Modified IANA profile registration and added TCP port number IANA=0A=
   registration.=0A=
=0A=
   Reordered some sections to improve the flow of the document.=0A=
=0A=
   Changed IDXP DTD identifier to be more IETF-like and removed URLs=0A=
   from ENTITY declarations.=0A=
=0A=
   Changed IDXP profile URI to fall under the "http://iana.org/beep/=0A=
   transient" namespace.=0A=
=0A=
   Modified Section 1.3 to reference the requirements language =
specified=0A=
   by [2].=0A=
=0A=
   Eliminated the use of the "endpoint" terminology, in favor of =
"peer".=0A=
=0A=
   Modified figures to make them more understandable.=0A=
=0A=
   Modified Sections 2, 3, and 4 to use the requirements language=0A=
   specified by [2].=0A=
=0A=
   Indicated that the RFC Editor should remove Appendix B and its=0A=
   corresponding TOC reference prior to publication.=0A=
=0A=
   Fixed several typos.=0A=
=0A=
B.4 Significant Changes Since beep-idxp-01=0A=
=0A=
   Added new MUST and SHOULD language for use of TLS and TUNNEL=0A=
   profiles.=0A=
=0A=
   Modified the "IDXP-Greeting" element to include an "Options" sub-=0A=
   element.=0A=
=0A=
   Changed IDXP profile URI.=0A=
=0A=
B.5 Significant Changes Since beep-idxp-00=0A=
=0A=
   Added Section 5, describing how IDXP fulfills the communication=0A=
   protocol requirements of the IDWG.=0A=
=0A=
   Moved IDXP profile registration to Appendix A.=0A=
=0A=
   Clarified the role that underlying BEEP security profiles must =
play.=0A=
=0A=
   Clarified how IDMEF messages fit into IDXP.=0A=
=0A=
=0A=
=0A=
Feinstein, et al.       Expires December 16, 2002              [Page =
36]=0A=
=0C=0A=
Internet-Draft                  The IDXP                       June =
2002=0A=
=0A=
=0A=
   Clarified how the IDXP profile channels and BEEP sessions =
interact.=0A=
=0A=
   Made terminology clarifications and changes for overall =
consistency.=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Feinstein, et al.       Expires December 16, 2002              [Page =
37]=0A=
=0C=0A=
Internet-Draft                  The IDXP                       June =
2002=0A=
=0A=
=0A=
Appendix C. Acknowledgements=0A=
=0A=
   The authors gratefully acknowledge the contributions of Darren =
New,=0A=
   Marshall T.  Rose, Roy Pollock, Tim Buchheim, Mike Erlinger, and =
Paul=0A=
   Osterwald.=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Feinstein, et al.       Expires December 16, 2002              [Page =
38]=0A=
=0C=0A=
Internet-Draft                  The IDXP                       June =
2002=0A=
=0A=
=0A=
Full Copyright Statement=0A=
=0A=
   Copyright (C) The Internet Society (2002).  All Rights Reserved.=0A=
=0A=
   This document and translations of it may be copied and furnished =
to=0A=
   others, and derivative works that comment on or otherwise explain =
it=0A=
   or assist in its implementation may be prepared, copied, =
published=0A=
   and distributed, in whole or in part, without restriction of any=0A=
   kind, provided that the above copyright notice and this paragraph =
are=0A=
   included on all such copies and derivative works.  However, this=0A=
   document itself may not be modified in any way, such as by =
removing=0A=
   the copyright notice or references to the Internet Society or =
other=0A=
   Internet organizations, except as needed for the purpose of=0A=
   developing Internet standards in which case the procedures for=0A=
   copyrights defined in the Internet Standards process must be=0A=
   followed, or as required to translate it into languages other =
than=0A=
   English.=0A=
=0A=
   The limited permissions granted above are perpetual and will not =
be=0A=
   revoked by the Internet Society or its successors or assigns.=0A=
=0A=
   This document and the information contained herein is provided on =
an=0A=
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET =
ENGINEERING=0A=
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, =
INCLUDING=0A=
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION=0A=
   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF=0A=
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.=0A=
=0A=
Acknowledgement=0A=
=0A=
   Funding for the RFC Editor function is currently provided by the=0A=
   Internet Society.=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Feinstein, et al.       Expires December 16, 2002              [Page =
39]=0A=
=0C=0A=
=0A=

------_=_NextPart_000_01C21632.D6E39490
Content-Type: application/octet-stream;
	name="PGPexch.rtf.asc"
Content-Disposition: attachment;
	filename="PGPexch.rtf.asc"

-----BEGIN PGP MESSAGE-----
Version: PGP 7.0.4

owGdUr+P0zAULodOSEggsfFreNPdEkWO0yTVIQ4VtVcYqE5Xfg2WDjexW0PiBNtt
7lR1Y4AdiQFOYmBBgv8ECTHegsQICxsLC05TVbfAgIcn2+/7nt/3Pb9o3Di9fur6
+SD7PUu/b1+dv76w9kw13n592b/46OH7Xrb57vYnZ2Pv15H+0ji6FBzL7Q9nflz+
2Ttev7L/6vmb/rePa59No1ozogz3CJVaLEJcjDwcYJIwzlEVUypHHvL9GeG5NGaY
2g0iXJdCa8LjMVWaGQRtJWh6bW6T3ipZqKf4BOQ+UwmVdAHCfwMt68zPnSVTwcon
QiZNMok9UlCV1C9jBLeYYiAMCO0AV0yPIecczJjBQZZixWMo7K12Xbfi2Vp1zIeP
qTHFmGxi9I/DipKQVPghIkNSqNyw2Fh1cJNJ2GFCamMDGaJKTCoks6iFdi8AgEHO
TUltkx02ZWleZEwa6MqRxTHlwB5sQGfJQhb+YAvCqOUGrcCNWmEAB2GEQ9jZgihC
btgM3JbveXCnRkURdpseDhd8S275CENnIss8Tw5hN3UdGEyEYeBj5EDb2Aka6kCv
DT7yAwRlWbqjiVVne3LjPKv17v/PqjTbedSd9OAetK20DnShD3dreUvjUG3nysba
pa40TBVKaAYDFk+UMIdAZQK7SkxpbLWofKRopiuXV4WWf+DkYO1vafwB
=bMXU
-----END PGP MESSAGE-----

------_=_NextPart_000_01C21632.D6E39490--



From idwg-public-request@semper.org  Wed Jun 19 07:30:19 2002
Received: from www.opencard.org (www.opencard.org [195.212.119.145])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13895
	for <idwg-archive@odin.ietf.org>; Wed, 19 Jun 2002 07:30:18 -0400 (EDT)
Received: by www.opencard.org (Postfix, from userid 503)
	id 2B767344E1; Wed, 19 Jun 2002 13:31:33 +0200 (CEST)
Old-Return-Path: <nsyracus@cnri.reston.va.us>
Delivered-To: semper-idwg-public@opencard.org
Message-Id: <200206191128.HAA13709@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce:;;IETF-Announce:;;;, @zurich.ibm.com;;;
Cc: idwg-public@zurich.ibm.com
From: Internet-Drafts@ietf.org
Reply-To: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-idwg-beep-idxp-05.txt
Date: Wed, 19 Jun 2002 07:28:34 -0400
Sender: nsyracus@cnri.reston.va.us
Resent-Message-ID: <N71b9B.A.2QE.VuGE9@www.opencard.org>
Resent-From: idwg-public@semper.org
X-Mailing-List: <idwg-public@semper.org> archive/latest/522
X-Loop: idwg-public@semper.org
Precedence: list
Resent-Sender: idwg-public-request@semper.org
Resent-Date: Wed, 19 Jun 2002 13:31:33 +0200 (CEST)

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Intrusion Detection Exchange Format Working Group of the IETF.

	Title		: The Intrusion Detection Exchange Protocol (IDXP)
	Author(s)	: B. Feinstein, G. Matthews, J. White
	Filename	: draft-ietf-idwg-beep-idxp-05.txt
	Pages		: 39
	Date		: 18-Jun-02
	
This memo describes the Intrusion Detection Exchange Protocol (IDXP),
an application-level protocol for exchanging data between intrusion
detection entities.  IDXP supports mutual-authentication, integrity,
and confidentiality over a connection-oriented protocol.  The
protocol provides for the exchange of IDMEF messages, unstructured
text, and binary data.  The IDMEF message elements are described in
the Intrusion Detection Message Exchange Format (IDMEF) [2], a
companion document of the Intrusion Detection Exchange Format (IDWG)
working group of the IETF.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idwg-beep-idxp-05.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-idwg-beep-idxp-05.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-idwg-beep-idxp-05.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:	<20020618132255.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-idwg-beep-idxp-05.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-idwg-beep-idxp-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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

--OtherAccess--

--NextPart--




From idwg-public-request@semper.org  Fri Jun 21 12:17:28 2002
Received: from www.opencard.org (www.opencard.org [195.212.119.145])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20329
	for <idwg-archive@odin.ietf.org>; Fri, 21 Jun 2002 12:17:28 -0400 (EDT)
Received: by www.opencard.org (Postfix, from userid 503)
	id AA3BC3478A; Fri, 21 Jun 2002 18:18:54 +0200 (CEST)
Old-Return-Path: <mike@cs.hmc.edu>
Delivered-To: semper-idwg-public@opencard.org
Date: Fri, 21 Jun 2002 09:17:17 -0700
From: Mike Erlinger <mike@cs.hmc.edu>
To: intrusion detection wg <idwg-public@zurich.ibm.com>
Cc: Mike Erlinger <mike@cs.hmc.edu>, start@cs.hmc.edu
Subject: Working Group Status
Message-Id: <20020621161717.GA5397@cs.hmc.edu>
Reply-To: mike@cs.hmc.edu
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.27i
Resent-Message-ID: <dlZHOB.A.-YE.tH1E9@www.opencard.org>
Resent-From: idwg-public@semper.org
X-Mailing-List: <idwg-public@semper.org> archive/latest/523
X-Loop: idwg-public@semper.org
Precedence: list
Resent-Sender: idwg-public-request@semper.org
Resent-Date: Fri, 21 Jun 2002 18:18:54 +0200 (CEST)

Documents:

    All 4 of our documents have been submitted to the IESG.  Steve
    Bellovin, the co-AD, has been reviewing them with requests that
    various editorial changes be made.  

    Also, a message from Glenn Mansfield sent in April to the IESG never
    made it to the IDWG mailing list.  The result being that Glenn's
    comments were never reviewed by the working group.  

    The result is 3 new IDs:
      draft-ietf-idwg-idmef-xml-07.txt, sent to ID person today, 21 June
      draft-ietf-idwg-beep-idxp-05.txt, in the ID repository
      draft-ietf-idwg-requirements-07.txt  which will be posted to the ID
                                          person sometime this weekend.

    Please check out the new drafts and post any comments to the working
    group.

54th IETF - Yokohama, Japan

    The IDWG will NOT be meeting at the 54th IETF.   So far all the changes
    requested by the IESG are easily handled via email, and we have complete
    all aspects of our charter.

mike


-- 
Mike Erlinger, Professor and Chair Computer Science
www:      http://www.cs.hmc.edu/~mike
email:    mike@cs.hmc.edu
smail:    Computer Science Dept., Harvey Mudd College,
          301 E. 12th Street, Claremont, CA, 91711 
          909-621-8912,   FAX: 909-607-8364



From idwg-public-request@semper.org  Fri Jun 21 17:28:15 2002
Received: from www.opencard.org (www.opencard.org [195.212.119.145])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01908
	for <idwg-archive@odin.ietf.org>; Fri, 21 Jun 2002 17:27:44 -0400 (EDT)
Received: by www.opencard.org (Postfix, from userid 503)
	id 3EBE63478B; Fri, 21 Jun 2002 23:28:36 +0200 (CEST)
Old-Return-Path: <rij@zurich.ibm.com>
Delivered-To: semper-idwg-public@opencard.org
Date: Fri, 21 Jun 2002 23:26:45 +0200 (CEST)
From: James Riordan <rij@zurich.ibm.com>
To: idwg-public@semper.org
Subject: About the Intrusion Specification Language scope (fwd)
Message-Id: <Pine.LNX.4.44.0206212326130.25299-100000@elba.zurich.ibm.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Resent-Message-ID: <xWbueB.A.gGF.Eq5E9@www.opencard.org>
Resent-From: idwg-public@semper.org
X-Mailing-List: <idwg-public@semper.org> archive/latest/524
X-Loop: idwg-public@semper.org
Precedence: list
Resent-Sender: idwg-public-request@semper.org
Resent-Date: Fri, 21 Jun 2002 23:28:36 +0200 (CEST)


---------- Forwarded message ----------
Date: Fri, 21 Jun 2002 16:51:04 +0200 (CEST)
From: George B. Magklaras <g.magklaras@videonetworks.com>
To: idwg-public@zurich.ibm.com
Subject: About the Intrusion Specification Language scope 

Hello,

I am a software engineer by profession and a part time researcher on 
Intrusion Detection Systems/ Insider IT misuse 
(http://ted.see.plym.ac.uk/nrg/scripts/showcurrentphd.asp?projectid=6).

I have been larking in this list for a long time now, watching the IDMEF 
proposals evolve. After reading carefully the relevant Internet Draft 
documents and considering the target work output of the IDWG, I have one 
fundamental question in relation to the group's target no. 2:

'2. A common intrusion language specification, which describes data 
formats that satisfy the requirements.'

I do understand that it is important to have a standard to facilitate 
data exchange amongst various IDS framework components and I agree that 
the inclusion of the IDMEF model, its association with XML and its 
implementation by Stuart Staniford in Silicon Defense address the listed 
requirements. However, (and always in my -probably restricted- view) I 
do not understand how the current IDWG's efforts address the fundamental 
problem of devising a standard way for describing the intrusion activity 
itself. What I am really talking talking about is more along the lines 
of the older 'Common Intrusion Specification Language (CISL)', (with 
reference to the last document revised on  11/06/1999 found in 
 http://www.isi.edu/gost/cidf/drafts/language.txt ). My understanding is 
that what originally constituted the Common Intrusion Detection 
Framework (CIDF) evolved (in terms of improving and expanding the 
message exchange format types and mechanisms) into the IDMEF and its 
associated tools. On the other hand, further research 
activities/comments  that concern the streamlining of the Semantic 
IDentifier expressions (SIDs), the tools that provide the foundations 
for expressing a series of intrusive activities using a semantic schema 
seem to be absent from the  IDWG documentation. The word language 
specification for me includes both the data format specification as well 
as the syntax. IDMEF defines extensively the first area whereas the 
latter issues seem to be addressed only by CISL.

If my thoughts are true, where does the current development of the CISL 
stand? Is the project still active with people trying to further 
refine/expand its SID base? Is the IDWG currently involved in this area 
and if yes, could you point to any documents that contain the latest 
advances/references.

On the other hand, if I have misunderstood the scope of the IDWG work in 
relation to the syntax features of an Intrusion Specification Language, 
I would very much appreciate your comments.

Thank you in anticipation, 

-- 
---
George B. Magklaras

Internet Consultant
Internet Services Group (ISG)
Video Networks Ltd. (UK)
Tel: +44 (0)1707 362500
Internal Extension: 2580





From idwg-public-request@semper.org  Sun Jun 23 13:39:53 2002
Received: from www.opencard.org (www.opencard.org [195.212.119.145])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01866
	for <idwg-archive@odin.ietf.org>; Sun, 23 Jun 2002 13:39:50 -0400 (EDT)
Received: by www.opencard.org (Postfix, from userid 503)
	id 835A83478A; Sun, 23 Jun 2002 19:40:13 +0200 (CEST)
Old-Return-Path: <mike@cs.hmc.edu>
Delivered-To: semper-idwg-public@opencard.org
Date: Sun, 23 Jun 2002 10:38:34 -0700
From: Mike Erlinger <mike@cs.hmc.edu>
To: intrusion detection wg <idwg-public@zurich.ibm.com>
Cc: Mike Erlinger <mike@cs.hmc.edu>,
        Stuart Staniford <stuart@SiliconDefense.com>
Subject: New Requirements ID
Message-Id: <20020623173834.GA2418@cs.hmc.edu>
Reply-To: mike@cs.hmc.edu
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="fdj2RfSjLxBAspz7"
Content-Disposition: inline
User-Agent: Mutt/1.3.27i
Resent-Message-ID: <HYvnGD.A.2pC.7fgF9@www.opencard.org>
Resent-From: idwg-public@semper.org
X-Mailing-List: <idwg-public@semper.org> archive/latest/525
X-Loop: idwg-public@semper.org
Precedence: list
Resent-Sender: idwg-public-request@semper.org
Resent-Date: Sun, 23 Jun 2002 19:40:13 +0200 (CEST)


--fdj2RfSjLxBAspz7
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

A new draft of the Requirements ID has been sent to the ID person
and is attached.  This version fixes a couple of typo issues, namely
a bad link in 2.3 and the failure of the author's address info to
show up in the ID.

mike



-- 
Mike Erlinger, Professor and Chair Computer Science
www:      http://www.cs.hmc.edu/~mike
email:    mike@cs.hmc.edu
smail:    Computer Science Dept., Harvey Mudd College,
          301 E. 12th Street, Claremont, CA, 91711 
          909-621-8912,   FAX: 909-607-8364

--fdj2RfSjLxBAspz7
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="draft-ietf-idwg-requirements-07.txt"




Intrusion Detection Working Group                                M. Wood
Internet-Draft                            Internet Security Systems, Inc
Expires: December 22, 2002                                   M. Erlinger
                                                     Harvey Mudd College
                                                           June 23, 2002


           Intrusion Detection Message Exchange Requirements
                    draft-ietf-idwg-requirements-07

Status of this Memo

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

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at http://
   www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on December 22, 2002.

Copyright Notice

   Copyright (C) The Internet Society (2002).  All Rights Reserved.

Abstract

   The purpose of the Intrusion Detection Exchange Format Working Group
   (IDWG) is to define data formats and exchange procedures for sharing
   information of interest to intrusion detection and response systems,
   and to the management systems which may need to interact with them.
   This Internet-Draft describes the high-level requirements for such a
   communication mechanism, including the rationale for those
   requirements where clarification is needed.  Scenarios are used to
   illustrate some requirements.





Wood & Erlinger         Expires December 22, 2002               [Page 1]


Internet-Draft                Requirements                     June 2002


Table of Contents

   1.     Conventions Used in This Document  . . . . . . . . . . . .   5
   2.     Introduction . . . . . . . . . . . . . . . . . . . . . . .   6
   2.1    Rationale for IDMEF  . . . . . . . . . . . . . . . . . . .   6
   2.2    Intrusion Detection Terms  . . . . . . . . . . . . . . . .   7
   2.2.1  Activity:  . . . . . . . . . . . . . . . . . . . . . . . .   7
   2.2.2  Administrator: . . . . . . . . . . . . . . . . . . . . . .   7
   2.2.3  Alert: . . . . . . . . . . . . . . . . . . . . . . . . . .   7
   2.2.4  Analyzer:  . . . . . . . . . . . . . . . . . . . . . . . .   7
   2.2.5  Data Source: . . . . . . . . . . . . . . . . . . . . . . .   8
   2.2.6  Event: . . . . . . . . . . . . . . . . . . . . . . . . . .   8
   2.2.7  IDS: . . . . . . . . . . . . . . . . . . . . . . . . . . .   8
   2.2.8  Manager  . . . . . . . . . . . . . . . . . . . . . . . . .   8
   2.2.9  Notification:  . . . . . . . . . . . . . . . . . . . . . .   8
   2.2.10 Operator:  . . . . . . . . . . . . . . . . . . . . . . . .   8
   2.2.11 Response:  . . . . . . . . . . . . . . . . . . . . . . . .   8
   2.2.12 Sensor:  . . . . . . . . . . . . . . . . . . . . . . . . .   9
   2.2.13 Signature: . . . . . . . . . . . . . . . . . . . . . . . .   9
   2.2.14 Security Policy: . . . . . . . . . . . . . . . . . . . . .   9
   2.3    Architectural Assumptions  . . . . . . . . . . . . . . . .  10
   2.4    Organization of This Document  . . . . . . . . . . . . . .  11
   2.5    Document Impact on IDMEF Designs . . . . . . . . . . . . .  12
   3.     General Requirements . . . . . . . . . . . . . . . . . . .  13
   3.1     . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  13
   3.1.1  Rationale: . . . . . . . . . . . . . . . . . . . . . . . .  13
   3.2     . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  13
   3.2.1  Rationale: . . . . . . . . . . . . . . . . . . . . . . . .  13
   4.     Message Format Requirements  . . . . . . . . . . . . . . .  14
   4.1     . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  14
   4.1.1  Rationale: . . . . . . . . . . . . . . . . . . . . . . . .  14
   4.1.2  Scenario:  . . . . . . . . . . . . . . . . . . . . . . . .  14
   4.2     . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  14
   4.2.1  Rationale: . . . . . . . . . . . . . . . . . . . . . . . .  14
   4.2.2  Scenario:  . . . . . . . . . . . . . . . . . . . . . . . .  14
   5.     IDMEF Communications Protocol (IDP) Requirements . . . . .  15
   5.1     . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  15
   5.1.1  Rationale: . . . . . . . . . . . . . . . . . . . . . . . .  15
   5.2     . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  15
   5.2.1  Rationale: . . . . . . . . . . . . . . . . . . . . . . . .  15
   5.2.2  Scenario:  . . . . . . . . . . . . . . . . . . . . . . . .  15
   5.3     . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  16
   5.3.1  Rationale: . . . . . . . . . . . . . . . . . . . . . . . .  16
   5.4     . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  16
   5.4.1  Rationale: . . . . . . . . . . . . . . . . . . . . . . . .  16
   5.5     . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  16
   5.5.1  Rationale: . . . . . . . . . . . . . . . . . . . . . . . .  16
   5.6     . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  17



Wood & Erlinger         Expires December 22, 2002               [Page 2]


Internet-Draft                Requirements                     June 2002


   5.6.1  Rationale: . . . . . . . . . . . . . . . . . . . . . . . .  17
   5.7     . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  17
   5.7.1  Rationale: . . . . . . . . . . . . . . . . . . . . . . . .  17
   5.7.2  Scenario:  . . . . . . . . . . . . . . . . . . . . . . . .  17
   5.8     . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  17
   5.8.1  Rationale: . . . . . . . . . . . . . . . . . . . . . . . .  17
   5.8.2  Scenario:  . . . . . . . . . . . . . . . . . . . . . . . .  18
   6.     Message Content Requirements . . . . . . . . . . . . . . .  19
   6.1     . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  19
   6.1.1  Rationale: . . . . . . . . . . . . . . . . . . . . . . . .  19
   6.2     . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  19
   6.2.1  Rationale: . . . . . . . . . . . . . . . . . . . . . . . .  19
   6.2.2  Scenario:  . . . . . . . . . . . . . . . . . . . . . . . .  19
   6.3     . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  20
   6.3.1  Rationale: . . . . . . . . . . . . . . . . . . . . . . . .  20
   6.3.2  Scenario:  . . . . . . . . . . . . . . . . . . . . . . . .  20
   6.4     . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  20
   6.4.1  Rationale: . . . . . . . . . . . . . . . . . . . . . . . .  20
   6.5     . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  20
   6.5.1  Rationale: . . . . . . . . . . . . . . . . . . . . . . . .  20
   6.6     . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  21
   6.6.1  Rationale: . . . . . . . . . . . . . . . . . . . . . . . .  21
   6.6.2  Scenario:  . . . . . . . . . . . . . . . . . . . . . . . .  21
   6.7     . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  21
   6.7.1  Rationale: . . . . . . . . . . . . . . . . . . . . . . . .  21
   6.8     . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  21
   6.8.1  Rationale: . . . . . . . . . . . . . . . . . . . . . . . .  21
   6.9     . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  22
   6.9.1  Rationale: . . . . . . . . . . . . . . . . . . . . . . . .  22
   6.9.2  Scenario:  . . . . . . . . . . . . . . . . . . . . . . . .  22
   6.10    . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  22
   6.10.1 Rationale: . . . . . . . . . . . . . . . . . . . . . . . .  22
   6.10.2 Scenario:  . . . . . . . . . . . . . . . . . . . . . . . .  22
   6.11    . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  22
   6.11.1 Rationale: . . . . . . . . . . . . . . . . . . . . . . . .  23
   6.11.2 Scenario:  . . . . . . . . . . . . . . . . . . . . . . . .  23
   6.12    . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  23
   6.12.1 Rationale: . . . . . . . . . . . . . . . . . . . . . . . .  23
   6.12.2 Scenario:  . . . . . . . . . . . . . . . . . . . . . . . .  23
   6.13    . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  23
   6.13.1 Rationale: . . . . . . . . . . . . . . . . . . . . . . . .  24
   6.13.2 Scenario:  . . . . . . . . . . . . . . . . . . . . . . . .  24
   6.14    . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  24
   6.14.1 Rationale: . . . . . . . . . . . . . . . . . . . . . . . .  24
   6.14.2 Scenario:  . . . . . . . . . . . . . . . . . . . . . . . .  24
   6.15    . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  24
   6.15.1 Rationale: . . . . . . . . . . . . . . . . . . . . . . . .  25
   6.16    . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  25



Wood & Erlinger         Expires December 22, 2002               [Page 3]


Internet-Draft                Requirements                     June 2002


   6.16.1 Rationale: . . . . . . . . . . . . . . . . . . . . . . . .  25
   6.17    . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  25
   6.17.1 Rationale: . . . . . . . . . . . . . . . . . . . . . . . .  25
   6.18    . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  25
   6.18.1 Rationale: . . . . . . . . . . . . . . . . . . . . . . . .  25
   6.18.2 Scenario:  . . . . . . . . . . . . . . . . . . . . . . . .  26
   6.19    . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  26
   6.19.1 Rationale: . . . . . . . . . . . . . . . . . . . . . . . .  26
          Authors' Addresses . . . . . . . . . . . . . . . . . . . .  26
   A.     Acknowledgements . . . . . . . . . . . . . . . . . . . . .  27
          Full Copyright Statement . . . . . . . . . . . . . . . . .  28








































Wood & Erlinger         Expires December 22, 2002               [Page 4]


Internet-Draft                Requirements                     June 2002


1. Conventions Used in This Document

   This is not an IETF standards track document and thus the keywords
   MUST, MUST NOT, SHOULD, and MAY are NOT as in RFC 2119, but rather:

   o  MUST: This word, or the terms "REQUIRED" or "SHALL", means that
      the described behavior or characteristic is an absolute
      requirement for a proposed IDWG specification.

   o  MUST NOT: This phrase, or the phrase "SHALL NOT", means that the
      described behavior or characteristic is an absolute prohibition of
      a proposed IDWG specification.

   o  SHOULD: This word, or the adjective "RECOMMENDED", means that
      there may exist valid reasons in particular circumstances for a
      proposed IDWG specification to ignore described behavior or
      characteristics.

   o  MAY: This word, or the adjective "OPTIONAL", means that described
      behavior or characteristics are truly optional for a proposed IDWG
      specification.  One proposed specification may choose to include
      the described behavior or characteristic while another proposed
      specification may omit the same behavior or characteristic.




























Wood & Erlinger         Expires December 22, 2002               [Page 5]


Internet-Draft                Requirements                     June 2002


2. Introduction

   This document defines requirements for the Intrusion Detection
   Message Exchange Format (IDMEF), which is the intended work product
   of the Intrusion Detection Exchange Format Working Group (IDWG).
   IDMEF is planned to be a standard format which automated Intrusion
   Detection Systems (IDS) can use for reporting what they have deemed
   to be suspicious or of interest.  This document also specifies
   requirements for a communication protocol for communicating IDMEF.
   As chartered IDWG, has the responsibility to first evaluate existing
   communication protocols before choosing to specify a new one.  Thus
   the requirements in this document can be used to evaluate existing
   communication protocols.  If IDWG determines that a new communication
   protocol is necessary, the requirements in this document can be used
   to evaluate proposed solutions.

2.1 Rationale for IDMEF

   The reasons such a format should be useful are as follows:

   1.  A number of commercial and free Intrusion Detection Systems are
       available and more are becoming available all the time.  Some
       products are aimed at detecting intrusions on the network, others
       are aimed at host operating systems, while still others are aimed
       at applications.  Even within a given category, the products have
       very different strengths and weaknesses.  Hence it is likely that
       users will deploy more than a single product, and users will want
       to observe the output of these products from one or more
       manager(s).  A standard format for reporting will simplify this
       task greatly.

   2.  Intrusions frequently involve multiple organizations as victims,
       or multiple sites within the same organization.  Typically, those
       sites will use different IDSs.  It would be very helpful to
       correlate such distributed intrusions across multiple sites and
       administrative domains.  Having reports from all sites in a
       common format would facilitate this task.

   3.  The existence of a common format should allow components from
       different IDSs to be integrated more readily.  Thus, Intrusion
       Detection (ID) research should migrate into commercial products
       more easily.

   4.  In addition to enabling communication from an ID analyzer to an
       ID manager, the IDMEF notification system may also enable
       communication between a variety of IDS components.  However, for
       the remainder of this document, we refer to the communication as
       going from an analyzer to a manager.



Wood & Erlinger         Expires December 22, 2002               [Page 6]


Internet-Draft                Requirements                     June 2002


   All of these reasons suggest that a common format for reporting
   anything deemed suspicious should help the IDS market to grow and
   innovate more successfully, and should result in IDS users obtaining
   better results from deployment of ID systems.

2.2 Intrusion Detection Terms

   In order to make the rest of the requirements clearer, we define some
   terms about typical IDSs.  These terms are presented in alphabetical
   order.  The diagram at the end of this section illustrates the
   relationships of some of the terms defined herein.

2.2.1 Activity:

   Elements of the data source or occurrences within the data source
   that are identified by the sensor or analyzer as being of interest to
   the operator.  Examples of this include (but are not limited to)
   network session showing unexpected telnet activity, operating system
   log file entries showing a user attempting to access files to which
   he is not authorized to have access, application log files showing
   persistent login failures, etc.

   Activity can range from extremely serious occurrences (such as an
   unequivocally malicious attack) to less serious occurrences (such as
   unusual user activity that's worth a further look) to neutral
   activity (such as user login).

2.2.2 Administrator:

   The human with overall responsibility for setting the security policy
   of the organization, and, thus, for decisions about deploying and
   configuring the IDS.  This may or may not be the same person as the
   operator of the IDS.  In some organizations, the administrator is
   associated with the network or systems administration groups.  In
   other organizations, it's an independent position.

2.2.3 Alert:

   A message from an analyzer to a manager that an event of interest has
   been detected.  An alert typically contains information about the
   unusual activity that was detected, as well as the specifics of the
   occurrence.

2.2.4 Analyzer:

   The ID component or process that analyzes the data collected by the
   sensor for signs of unauthorized or undesired activity or for events
   that might be of interest to the security administrator.  In many



Wood & Erlinger         Expires December 22, 2002               [Page 7]


Internet-Draft                Requirements                     June 2002


   existing IDSs, the sensor and the analyzer are part of the same
   component.  In this document, the term analyzer is used generically
   to refer to the sender of the IDMEF message.

2.2.5 Data Source:

   The raw information that an intrusion detection system uses to detect
   unauthorized or undesired activity.  Common data sources include (but
   are not limited to) raw network packets, operating system audit logs,
   application audit logs, and system-generated checksum data.

2.2.6 Event:

   The occurrence in the data source that is detected by the sensor and
   which may result in an IDMEF alert being transmitted.  For example,
   'N' failed logins in 'T' seconds might indicate a brute-force login
   attack.

2.2.7 IDS:

   Intrusion detection system.  Some combination of one or more of the
   following components: sensor, analyzer, manager.

2.2.8 Manager

   The ID component or process from which the operator manages the
   various components of the ID system.  Management functions typically
   include (but are not limited to) sensor configuration, analyzer
   configuration, event notification management, data consolidation, and
   reporting.

2.2.9 Notification:

   The method by which the IDS manager makes the operator aware of the
   alert occurrence and thus the event.  In many IDSs, this is done via
   the display of a colored icon on the IDS manager screen, the
   transmission of an e-mail or pager message, or the transmission of an
   SNMP trap, although other notification techniques are also used.

2.2.10 Operator:

   The human that is the primary user of the IDS manager.  The operator
   often monitors the output of the ID system and initiates or
   recommends further action.

2.2.11 Response:

   The actions taken in response to an event.  Responses may be



Wood & Erlinger         Expires December 22, 2002               [Page 8]


Internet-Draft                Requirements                     June 2002


   undertaken automatically by some entity in the IDS architecture or
   may be initiated by a human.  Sending a notification to the operator
   is a very common response.  Other responses include (but are not
   limited to) logging the activity, recording the raw data (from the
   data source) that characterized the event, terminating a network,
   user, or application session, or altering network or system access
   controls.

2.2.12 Sensor:

   The ID component that collects data from the data source.  The
   frequency of data collection will vary across IDS offerings.  The
   sensor is setup to forward events to the analyzer.

2.2.13 Signature:

   A rule used by the analyzer to identify interesting activity to the
   security administrator.  Signatures represent one of the mechanisms
   (though not necessarily the only mechanism) by which IDSs detect
   intrusions.

2.2.14 Security Policy:

   The predefined, formally documented statement which defines what
   activities are allowed to take place on an organization's network or
   on particular hosts to support the organization's requirements.  This
   includes, but is not limited to, which hosts are to be denied
   external network access.























Wood & Erlinger         Expires December 22, 2002               [Page 9]


Internet-Draft                Requirements                     June 2002


    ________
   |        |                   --------
   | Data   |_________ ________|        |  __________
   | Source |     Activity     |Sensor  | |          |
   |________|         |        |________| | Operator |_______
                      |            |      |__________|       |
                     \|/         Event         A             |
                 _____V___         |          /|\            |
                |         |        |            \            |
                | Sensor  |__      |         Notification    |
                |_________| Event  |              \         \|/
                      A      |     V_________       \         V
                     /|\     |    |         |       \     Response
                      |       --->| Analyzer|__      |       A
                      |           |         | Alert  |      /|\
                      |           |_________|  |     |       |
                      |                A       |     |       |
                      |               /|\     \|/    |       |
                      |________________|   ____V___  |       |
                          |               |        |_|       |
                          |               | Manager|_________|
                          |               |________|
                          |                  A
                        Security            /|\
        _______________   |  Policy__________|
       |               |  |
       | Administrator |__|
       |_______________|



   The diagram above illustrates the terms above and their
   relationships.  Not every IDS will have all of these separate
   components exactly as shown.  Some IDSs will combine these components
   into a single module; some will have multiple instances of these
   modules.

2.3 Architectural Assumptions

   In this document, as defined in the terms above, we assume that an
   analyzer determines somehow that a suspicious event has been seen by
   a sensor, and sends an alert to a manager.  The format of that alert
   and the method of communicating it are what IDMEF proposes to
   standardize.

   For the purposes of this document, we assume that the analyzer and
   manager are separate components, and that they are communicating
   pairwise across a TCP/IP network.  No other form of communication



Wood & Erlinger         Expires December 22, 2002              [Page 10]


Internet-Draft                Requirements                     June 2002


   between these entities is contemplated in this document, and no other
   use of IDMEF alerts is considered.  We refer to the communication
   protocol that communicates IDMEF as the IDMEF Communication Protocol
   (IDP).

   The Trust Model is not specified as a requirement, but is rather left
   to the choice of the IDMEF communications protocol, i.e., a design
   decision.  What is specified are individual security related
   requirements, Section 5.

   We try to make no further architectural assumptions than those just
   stated.  For example, the following points should not matter:

   o  Whether the sensor and the analyzer are integrated or separate.

   o  Whether the analyzer and manager are isolated, or embedded in some
      large hierarchy or distributed mesh of components.

   o  Whether the manager actually notifies a human, takes action
      automatically, or just analyzes incoming alerts and correlates
      them.

   o  Whether a component might act as an analyzer with respect to one
      component, while also acting as a manager with respect to another.


2.4 Organization of This Document

   Besides this requirements document, the IDWG should produce two other
   documents.  The first should describe a data format or language for
   exchanging information about suspicious events.  In this, the
   requirements document, we refer to that document as the "data-format
   specification".  The second document to be produced should identify
   existing IETF protocols that are best used for conveying the data so
   formatted, and explain how to package this data in those existing
   formats or the document should specify a new protocol.  We refer to
   this as the IDP  (IDMEF Communication Protocol).

   Accordingly, the requirements here are partitioned into four sections

   o  The first of these contains general requirements that apply to all
      aspects of the IDMEF specification Section 3.

   o  The second section describes requirements on the formatting of
      IDMEF messages Section 4.

   o  The third section outlines requirements on the communications
      mechanism, IDP, used to move IDMEF messages from the analyzer to



Wood & Erlinger         Expires December 22, 2002              [Page 11]


Internet-Draft                Requirements                     June 2002


      the manager Section 5.

   o  The final section contains requirements on the content and
      semantics of the IDMEF messages Section 6 .

   For each requirement, we attempt to state the requirement as clearly
   as possible without imposing an idea of what a design solution should
   be.  Then we give the rationale for why this requirement is
   important, and state whether this should be an essential feature of
   the specification, or is beneficial but could be lacking if it is
   difficult to fulfill.  Finally, where it seems necessary, we give an
   illustrative scenario.  In some cases, we include possible design
   solutions in the scenario.  These are purely illustrative.

2.5 Document Impact on IDMEF Designs

   It is expected that proposed IDMEF designs will, at a minimum,
   satisfy the requirements expressed in this document.  However, this
   document will be used only as one of many criteria in the evaluation
   of various IDMEF designs and proposed communication protocols.  It is
   recognized that the working group may use additional metrics to
   evaluate competing IDMEF designs and/or communication protocols.





























Wood & Erlinger         Expires December 22, 2002              [Page 12]


Internet-Draft                Requirements                     June 2002


3. General Requirements

3.1

   The IDMEF SHALL reference and use previously published RFCs where
   possible.

3.1.1 Rationale:

   The IETF has already completed a great deal of research and work into
   the areas of networks and security.  In the interest of time, it is
   smart to use already defined and accepted standards.

3.2

   The IDMEF specification MUST take into account that IDMEF should be
   able to operate in environments that contain IPv4 and IPv6
   implementations.

3.2.1 Rationale:

   Since pure IPv4, hybrid IPv6/IPv4, and pure IPv6 environments are
   expected to exist within the time frame of IDMEF implementations, the
   IDMEF specification MUST support IPv6 and IPv4 environments.



























Wood & Erlinger         Expires December 22, 2002              [Page 13]


Internet-Draft                Requirements                     June 2002


4. Message Format Requirements

   The IDMEF message format is intended to be independent of the IDMEF
   communications protocol (IDP).  It should be possible to use a
   completely different transport mechanism without changing the IDMEF
   format.  The goal behind this requirement is to ensure a clean
   separation between semantics and communication mechanisms.  Obviously
   the IDMEF communication protocol is recommended.

4.1

   IDMEF message formats SHALL support full internationalization and
   localization.

4.1.1 Rationale:

   Since network security and intrusion detection are areas that cross
   geographic, political, and cultural boundaries, the IDMEF messages
   MUST be formatted such that they can be presented to an operator in a
   local language and adhering to local presentation customs.

4.1.2 Scenario:

   An IDMEF specification might include numeric event identifiers.  An
   IDMEF implementation might translate these numeric event identifiers
   into local language descriptions.  In cases where the messages
   contain strings, the information might be represented using the ISO/
   IEC IS 10646-1 character set and encoded using the UTF-8
   transformation format to facilitate internationalization.

4.2

   The format of IDMEF messages MUST support filtering and/or
   aggregation of data by the manager.

4.2.1 Rationale:

   Since it is anticipated that some managers might want to perform
   filtering and/or data aggregation functions on IDMEF messages, the
   IDMEF messages MUST be structured to facilitate these operations.

4.2.2 Scenario:

   An IDMEF specification proposal might recommend fixed format messages
   with strong numerical semantics.  This would lend itself to high-
   performance filtering and aggregation by the receiving station.





Wood & Erlinger         Expires December 22, 2002              [Page 14]


Internet-Draft                Requirements                     June 2002


5. IDMEF Communications Protocol (IDP) Requirements

5.1

   The IDP MUST support reliable transmission of messages.

5.1.1 Rationale:

   IDS managers often rely on receipt of data from IDS analyzers to do
   their jobs effectively.  Since IDS managers will rely on IDMEF
   messages for this purpose, it is important that IDP deliver IDMEF
   messages reliably.

5.2

   The IDP MUST support transmission of messages between ID components
   across firewall boundaries without compromising security.

5.2.1 Rationale:

   Since it is expected that firewalls will often be deployed between
   IDMEF capable analyzers and their corresponding managers, the ability
   to relay messages via proxy or other suitable mechanism across
   firewalls is necessary.  Setting up this communication MUST NOT
   require changes to the intervening firewall(s) that weaken the
   security of the protected network(s).  Nor SHOULD this be achieved by
   mixing IDMEF messages with other kinds of traffic (e.g., by
   overloading the HTTP POST method) since that would make it difficult
   for an organization to apply separate policies to IDMEF traffic and
   other kinds of traffic.

5.2.2 Scenario:

   One possible design is the use of TCP to convey IDMEF messages.  The
   general goal in this case is to avoid opening dangerous inbound
   "holes" in the firewall.  When the manager is inside the firewall and
   the analyzers are outside the firewall, this is often achieved by
   having the manager initiate an outbound connection to each analyzer.
   However, it is also possible to place the manager outside the
   firewall and the analyzers on the inside; this can occur when a
   third-party vendor (such as an ISP) is providing monitoring services
   to a user.  In this case, the outbound connections would be initiated
   by each analyzer to the manager.  A mechanism that permits either the
   manager or the analyzer to initiate connections would provide maximum
   flexibility in manager and analyzer deployment.






Wood & Erlinger         Expires December 22, 2002              [Page 15]


Internet-Draft                Requirements                     June 2002


5.3

   The IDP MUST support mutual authentication of the analyzer and the
   manager to each other.  Application-layer authentication is required
   irrespective of the underlying transport layer.

5.3.1 Rationale:

   Since the alert messages are used by a manager to direct responses or
   further investigation related to the security of an enterprise
   network, it is important that the receiver have confidence in the
   identity of the sender and that the sender have confidence in the
   identity of the receiver.  This is peer-to-peer authentication of
   each party to the other.  It MUST NOT be limited to authentication of
   the underlying communications mechanism, for example, because of the
   risk that this authentication process might be subverted or
   misconfigured.

5.4

   The IDP MUST support confidentiality of the message content during
   message exchange.  The selected design MUST be capable of supporting
   a variety of encryption algorithms and MUST be adaptable to a wide
   variety of environments.

5.4.1 Rationale:

   IDMEF messages potentially contain extremely sensitive information
   (such as passwords) and would be of great interest to an intruder.
   Since it is likely some of these messages will be transmitted across
   uncontrolled network segments, it is important that the content be
   shielded.  Furthermore, since the legal environment for encryption
   technologies is extremely varied and changes often, it is important
   that the design selected be capable of supporting a number of
   different encryption options and be adaptable by the user to a
   variety of environments.

5.5

   The IDP MUST ensure the integrity of the message content.  The
   selected design MUST be capable of supporting a variety of integrity
   mechanisms and MUST be adaptable to a wide variety of environments.

5.5.1 Rationale:

   IDMEF messages are used by the manager to direct action related to
   the security of the protected enterprise network.  It is vital for
   the manager to be certain that the content of the message has not



Wood & Erlinger         Expires December 22, 2002              [Page 16]


Internet-Draft                Requirements                     June 2002


   been changed after transmission.

5.6

   The IDP SHOULD be able to ensure non-repudiation of the origin of
   IDMEF messages.

5.6.1 Rationale:

   Given that sensitive security information is being exchanged via the
   IDMEF, it is important that the humans operating the system are able
   to associate messages with the originating IDMEF entity.

5.7

   The IDP SHOULD resist protocol denial of service attacks.

5.7.1 Rationale:

   A common way to defeat secure communications systems is through
   resource exhaustion.  While this does not corrupt valid messages, it
   can prevent any communication at all.  It is desirable that IDP
   resist such denial of service attacks.

5.7.2 Scenario:

   An attacker penetrates a network being defended by an IDS.  Although
   the attacker is not certain that an IDS is present, he is certain
   that application-level encrypted traffic (i.e., IDMEF traffic) is
   being exchanged between components on the network being attacked.  He
   decides to mask his presence and disrupt the encrypted communications
   by initiating one or more flood events.  If the IDP can resist such
   an attack, the probability that the attacker will be stopped
   increases.

5.8

   The IDP SHOULD resist malicious duplication of messages.

5.8.1 Rationale:

   A common way to impair the performance of secure communications
   mechanisms is to duplicate the messages being sent, even though the
   attacker might not understand them, in an attempt to confuse the
   receiver.  It is desirable that the IDP resist such message
   duplication.





Wood & Erlinger         Expires December 22, 2002              [Page 17]


Internet-Draft                Requirements                     June 2002


5.8.2 Scenario:

   An attacker penetrates a network being defended by an IDS.  The
   attacker suspects that an IDS is present and quickly identifies the
   encrypted traffic flowing between system components as being a
   possible threat.  Even though she cannot read this traffic, she
   copies the messages and directs multiple copies at the receiver in an
   attempt to confuse it.  If the IDP resists such message duplication,
   the probability that the attacker will be stopped increases.










































Wood & Erlinger         Expires December 22, 2002              [Page 18]


Internet-Draft                Requirements                     June 2002


6. Message Content Requirements

6.1

   There are many different types of IDSs, such as those based on:
   signatures, anomalies, correlation, network monitoring, host
   monitoring, or application monitoring.  The IDMEF design MUST strive
   to accommodate these diverse approaches by concentrating on conveying
   *what* an IDS has detected, rather than *how* it detected it.

6.1.1 Rationale:

   Rationale: There are many types of IDSs that analyze a variety of
   data sources.  Some are profile based and operate on log files,
   attack signatures etc.  Others are anomaly based and define normal
   behavior and detect deviations from the established baseline.  Each
   of these IDSs reports different data that, in part, depends on their
   intrusion detection methodology.  All MUST be supported by this
   standard.

6.2

   The content of IDMEF messages MUST contain the identified name of the
   event (event identity) if it is known.  This name MUST be drawn from
   a standardized list of events (if available) or will be an
   implementation-specific name if the event identity has not yet been
   standardized.  It is not known how this standardized list will be
   defined or updated.  Requirements on the creation of this list are
   beyond our efforts.  Other groups within the security arena are
   investigating the creation of such lists.

6.2.1 Rationale:

   Given that this document presents requirements on standardizing ID
   message formats so that an ID manager is able to receive alerts from
   analyzers from multiple implementations, it is important that the
   manager understand the semantics of the reported events.  There is,
   therefore, a need to identify known events and store information
   concerning their methods and possible fixes to these events.  Some
   events are well known and this recognition can help the operator.

6.2.2 Scenario:

   Intruder launches an attack that is detected by two different
   analyzers from two distinct implementations.  Both report the same
   event identity to the ID manager, even though the algorithms used to
   detect the attack by each analyzer might have been different.




Wood & Erlinger         Expires December 22, 2002              [Page 19]


Internet-Draft                Requirements                     June 2002


6.3

   The IDMEF message design MUST include information, which the sender
   should provide, that allows a receiver to locate background
   information on the kind of event that is being reported in the alert.

6.3.1 Rationale:

   This information is used by administrators to report and fix
   problems.

6.3.2 Scenario:

   Attacker performs a well-known attack.  A reference to a URL to
   background information on the attack is included in the IDMEF
   message.  The operator uses this information to initiate repairs on
   the vulnerable system.

6.4

   The IDMEF message MUST be able to reference additional detailed data
   related to this specific underlying event.  It is OPTIONAL for
   implementations to use this field.  No requirements are placed on the
   format or content of this field.  It is expected that this will be
   defined and described by the implementor.

6.4.1 Rationale:

   Operators might want more information on specifics of an event.  This
   field, if filled in by the analyzer, MAY point to additional or more
   detailed information about the event.

6.5

   The IDMEF message MUST contain the identity of the source of the
   event and target component identifier if it is known.  In the case of
   a network-based event, this will be the source and destination IP
   address of the session used to launch the event.  Note that the
   identity of source and target will vary for other types of events,
   such as those launched/detected at the operating system or
   application level.

6.5.1 Rationale:

   This will allow the operator to identify the source and target of the
   event.





Wood & Erlinger         Expires December 22, 2002              [Page 20]


Internet-Draft                Requirements                     June 2002


6.6

   The IDMEF message MUST support the representation of different types
   of device addresses.

6.6.1 Rationale:

   A Device is a uniquely addressable element on the network.  (i.e.,
   not limited to computers or networks nor a specific level of the
   network protocol hierarchy).  Additionally, devices involved in an
   intrusion event might use addresses that are not IP-centric.

6.6.2 Scenario:

   The IDS recognizes an intrusion on a particular device and includes
   both the IP address and the MAC address of the device in the IDMEF
   message.  In another situation, the IDS recognizes an intrusion on a
   device which has only a MAC address and includes only that address in
   the IDMEF message.  Another situation involves analyzers in an ATM
   switch fabric which use E.164 address formats.

6.7

   The IDMEF message MUST contain an indication of the possible impact
   of this event on the target.  The IDMEF design document MUST define
   the scope of this value.

6.7.1 Rationale:

   Information concerning the possible impact of the event on the target
   system provides an indication of what the intruder is attempting to
   do and is critical data for the operator to perform damage
   assessment.  Not all systems will be able to determine this, but it
   is important data to transmit for those systems that can.  This
   requirement places no requirements on the list itself (e.g.,
   properties of the list, maintenance, etc.), rather the requirement
   only specifies that the IDMEF must contain a field for specifying the
   impact and that the IDMEF must define the scope of such values.

6.8

   The IDMEF message MUST provide information about the automatic
   actions taken by the analyzer in response to the event (if any).

6.8.1 Rationale:

   It is very important for the operator to know if there was an
   automated response and what that response was.  This will help



Wood & Erlinger         Expires December 22, 2002              [Page 21]


Internet-Draft                Requirements                     June 2002


   determine what further action to take, if any.

6.9

   The IDMEF message MUST include information which would make it
   possible to later identify and locate the individual analyzer which
   reported the event.

6.9.1 Rationale:

   The identity of the detecting analyzer often proves to be a valuable
   piece of data to have in determining how to respond to a particular
   event.

6.9.2 Scenario:

   Scenario: One interesting scenario involves the progress of an
   intrusion event throughout a network.  If the same event is detected
   and reported by multiple analyzers, the identity of the analyzer (in
   the case of a network-based analyzer) might provide some indication
   of the network location of the target systems and might warrant a
   specific type of response.  This might be implemented as an IP
   address.

6.10

   The IDMEF message MUST be able to contain the identity of the
   implementor and the analyzer that detected the event.

6.10.1 Rationale:

   Rationale: Users might run multiple IDSs to protect their enterprise.
   This data will help the systems administrator determine which
   implementor and analyzer detected the event.

6.10.2 Scenario:

   Analyzer X from implementor Y detects a potential intrusion.  A
   message is sent reporting that it found a potential break-in with X
   and Y specified.  The operator is therefore able to include the known
   capabilities or weaknesses of analyzer X in his decision regarding
   further action.

6.11

   The IDMEF message MUST be able to state the degree of confidence of
   the report.  The completion of this field by an analyzer is OPTIONAL,
   as this data might not be available at all analyzers.



Wood & Erlinger         Expires December 22, 2002              [Page 22]


Internet-Draft                Requirements                     June 2002


6.11.1 Rationale:

   Many IDSs contain thresholds to determine whether or not to generate
   an alert.  This might influence the degree of confidence one has in
   the report or perhaps would indicate the likelihood of the report
   being a false alarm.

6.11.2 Scenario:

   The alarm threshold monitor is set at a low level to indicate that an
   organization wants reports on any suspicious activity, regardless of
   the probability of a real attack.  The degree of confidence measure
   is used to indicate if this is a low probability or high probability
   event.

6.12

   The IDMEF message MUST be uniquely identifiable in that it can be
   distinguished from other IDMEF messages.

6.12.1 Rationale:

   An IDMEF message might be sent by multiple geographically-distributed
   analyzers at different times.  A unique identifier will allow an
   IDMEF message to be identified efficiently for data reduction and
   correlation purposes.

6.12.2 Scenario:

   The unique identifier might consist of a unique originator identifier
   (e.g.  IPv4 or IPv6 address) concatenated with a unique sequence
   number generated by the originator.  In a typical IDS deployment, a
   low-level event analyzer will log the raw sensor information into,
   e.g., a database while analyzing and reporting results to higher
   levels.  In this case, the unique raw message identifier can be
   included in the result message as supporting evidence.  Higher level
   analyzers can later use this identifier to retrieve the raw message
   from the database if necessary.

6.13

   The IDMEF MUST support reporting alert creation date and time in each
   event, where the creation date and time refer to the date and time
   that the analyzer decided to create an alert.  The IDMEF MAY support
   additional dates and times, such as the date and time the event
   reference by the alert began.





Wood & Erlinger         Expires December 22, 2002              [Page 23]


Internet-Draft                Requirements                     June 2002


6.13.1 Rationale:

   Time is important from both a reporting and correlation point of
   view.  Event onset time might differ from the alert creation time
   because it might take some time for the sensor to accumulate
   information about a monitored activity before generating the event,
   and additional time for the analyzer to receive the event and create
   an alert.  The event onset time is therefore more representative of
   the actual time that the reported activity began than is the alert
   creation time.

6.13.2 Scenario:

   If an event is reported in the quiet hours of the night, the operator
   might assign a higher priority to it than she would to the same event
   reported in the busy hours of the day.  Furthermore, an event (like a
   lengthy port scan) may take place over a long period of time and it
   would be useful for the analyzer to report the time of the alert as
   well as the time the event began.

6.14

   Time SHALL be reported such that events from multiple analyzers in
   different time zones can be received by the same manager and that the
   local time at the analyzer can be inferred.

6.14.1 Rationale:

   For event correlation purposes, it is important that the manager be
   able to normalize the time information reported in the IDMEF alerts.

6.14.2 Scenario:

   A distributed ID system has analyzers located in multiple timezones,
   all reporting to a single manager.  An intrusion occurs that spans
   multiple timezones as well as multiple analyzers.  The central
   manager requires sufficient information to normalize these alerts and
   determine that all were reported near the same "time" and that they
   are part of the same attack.

6.15

   The format for reporting the date MUST be compliant with all current
   standards for Year 2000 rollover, and it MUST have sufficient
   capability to continue reporting date values past the year 2038.






Wood & Erlinger         Expires December 22, 2002              [Page 24]


Internet-Draft                Requirements                     June 2002


6.15.1 Rationale:

   It is desirable that the IDMEF have a long lifetime and that
   implementations be suitable for use in a variety of environments.
   Therefore, characteristics that limit the lifespan of the IDMEF (such
   as 2038 date representation limitation) MUST be avoided.

6.16

   Time granularity and time accuracy in event messages SHALL NOT be
   specified by the IDMEF.

6.16.1 Rationale:

   The IDMEF cannot assume a certain clock granularity on sensing
   elements, and so cannot impose any requirements on the granularity of
   the event timestamps.  Nor can the IDMEF assume that the clocks being
   used to timestamp the events have a specified accuracy.

6.17

   The IDMEF message MUST support an extension mechanism used by
   implementors to define implementation-specific data.  The use of this
   mechanism by the implementor is OPTIONAL.  This data contains
   implementation-specific information determined by each implementor.
   The implementor MUST indicate how to interpret these extensions,
   although there are no specific requirements placed on how
   implementors describe their implementation-specific extensions.

6.17.1 Rationale:

   Implementors might wish to supply extra data such as the version
   number of their product or other data that they believe provides
   value added due to the specific nature of their product.
   Implementors may publish a document or web site describing their
   extensions; they might also use an in-band extension mechanism that
   is self-describing.

6.18

   The semantics of the IDMEF message MUST be well defined.

6.18.1 Rationale:

   Good semantics are key to understanding what the message is trying to
   convey so there are no errors.  Operators will decide what action to
   take based on these messages, so it is important that they can
   interpret them correctly.



Wood & Erlinger         Expires December 22, 2002              [Page 25]


Internet-Draft                Requirements                     June 2002


6.18.2 Scenario:

   Without this requirement, the operator receives an IDMEF message and
   interprets it one way.  The implementor who constructed the message
   intended it to have a different meaning from the operator's
   interpretation.  The resulting corrective action is, therefore,
   incorrect.

6.19

   The IDMEF itself MUST be extensible.  As new ID technologies emerge
   and as new information about events becomes available, the IDMEF
   message format MUST be able to include this new information.

6.19.1 Rationale:

   As intrusion detection technology continues to evolve, it is likely
   that additional information relating to detected events will become
   available.  The IDMEF message format MUST be able to be extended by a
   specific implementation to encompass this new information.


Authors' Addresses

   Mark Wood
   Internet Security Systems, Inc
   6303 Barfield Road
   Atlanta, GA  30328
   US

   EMail: mark1@iss.net


   Michael A. Erlinger
   Harvey Mudd College
   Computer Science Dept
   301 East 12th Street
   Claremont, CA  91711
   US

   EMail: mike@cs.hmc.edu
   URI:   http://www.cs.hmc.edu/









Wood & Erlinger         Expires December 22, 2002              [Page 26]


Internet-Draft                Requirements                     June 2002


Appendix A. Acknowledgements

   The following individuals contributed substantially to this document
   and should be recognized for their efforts.  This document would not
   exist without their help:

      Mark Crosbie, Hewlett-Packard

      David Curry, IBM Emergency Response Services

      David Donahoo, Air Force Information Warfare Center

      Mike Erlinger, Harvey Mudd College

      Fengmin Gong, Microcomputing Center of North Carolina

      Dipankar Gupta, Hewlett-Packard

      Glenn Mansfield, Cyber Solutions, Inc.

      Jed Pickel, CERT Coordination Center

      Stuart Staniford-Chen, Silicon Defense

      Maureen Stillman, Nokia IP Telephony


























Wood & Erlinger         Expires December 22, 2002              [Page 27]


Internet-Draft                Requirements                     June 2002


Full Copyright Statement

   Copyright (C) The Internet Society (2002).  All Rights Reserved.

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Acknowledgement

   Funding for the RFC Editor function is currently provided by the
   Internet Society.



















Wood & Erlinger         Expires December 22, 2002              [Page 28]



--fdj2RfSjLxBAspz7--



From idwg-public-request@semper.org  Mon Jun 24 07:49:44 2002
Received: from www.opencard.org (www.opencard.org [195.212.119.145])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA00905
	for <idwg-archive@odin.ietf.org>; Mon, 24 Jun 2002 07:49:43 -0400 (EDT)
Received: by www.opencard.org (Postfix, from userid 503)
	id 7061A3478F; Mon, 24 Jun 2002 13:51:16 +0200 (CEST)
Old-Return-Path: <nsyracus@cnri.reston.va.us>
Delivered-To: semper-idwg-public@opencard.org
Message-Id: <200206241148.HAA00658@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce:;;IETF-Announce:;;;, @zurich.ibm.com;;;
Cc: idwg-public@zurich.ibm.com
From: Internet-Drafts@ietf.org
Reply-To: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-idwg-idmef-xml-07.txt
Date: Mon, 24 Jun 2002 07:48:33 -0400
Sender: nsyracus@cnri.reston.va.us
Resent-Message-ID: <eEPNDC.A.oYE.zewF9@www.opencard.org>
Resent-From: idwg-public@semper.org
X-Mailing-List: <idwg-public@semper.org> archive/latest/526
X-Loop: idwg-public@semper.org
Precedence: list
Resent-Sender: idwg-public-request@semper.org
Resent-Date: Mon, 24 Jun 2002 13:51:16 +0200 (CEST)

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Intrusion Detection Exchange Format Working Group of the IETF.

	Title		: Intrusion Detection Message Exchange Format Data Model
                          and Extensible Markup Language (XML) Document Type 
                          Definition
	Author(s)	: D. Curry, H. Debar
	Filename	: draft-ietf-idwg-idmef-xml-07.txt
	Pages		: 108
	Date		: 21-Jun-02
	
The purpose of the Intrusion Detection Message Exchange Format
(IDMEF) is to define data formats and exchange procedures for sharing
information of interest to intrusion detection and response systems,
and to the management systems which may need to interact with them.
This Internet-Draft describes a data model to represent information
exported by intrusion detection systems, and explains the rationale
for using this model.  An implementation of the data model in the
Extensible Markup Language (XML) is presented, an XML Document Type
Definition is developed, and examples are provided.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idwg-idmef-xml-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-idwg-idmef-xml-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-idwg-idmef-xml-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:	<20020621122028.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-idwg-idmef-xml-07.txt

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

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

--OtherAccess--

--NextPart--




From idwg-public-request@semper.org  Tue Jun 25 07:02:41 2002
Received: from www.opencard.org (www.opencard.org [195.212.119.145])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA29443
	for <idwg-archive@odin.ietf.org>; Tue, 25 Jun 2002 07:02:41 -0400 (EDT)
Received: by www.opencard.org (Postfix, from userid 503)
	id AD10B3478E; Tue, 25 Jun 2002 13:04:01 +0200 (CEST)
Old-Return-Path: <nsyracus@cnri.reston.va.us>
Delivered-To: semper-idwg-public@opencard.org
Message-Id: <200206251101.HAA29152@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce:;;IETF-Announce:;;;, @zurich.ibm.com;;;
Cc: idwg-public@zurich.ibm.com
From: Internet-Drafts@ietf.org
Reply-To: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-nalawade-bgp-inform-00.txt
Date: Tue, 25 Jun 2002 07:01:32 -0400
Sender: nsyracus@cnri.reston.va.us
Resent-Message-ID: <dgHAlB.A.5BH.h4EG9@www.opencard.org>
Resent-From: idwg-public@semper.org
X-Mailing-List: <idwg-public@semper.org> archive/latest/527
X-Loop: idwg-public@semper.org
Precedence: list
Resent-Sender: idwg-public-request@semper.org
Resent-Date: Tue, 25 Jun 2002 13:04:01 +0200 (CEST)

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: BGPv4 INFORM message
	Author(s)	: G. Nalawade et al.
	Filename	: draft-nalawade-bgp-inform-00.txt
	Pages		: 10
	Date		: 24-Jun-02
	
This document defines a new message type, the BGP INFORM
message that communicates Informational data and operational
warnings without resetting the peering session.

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

--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:	<20020624143644.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-nalawade-bgp-inform-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-nalawade-bgp-inform-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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

--OtherAccess--

--NextPart--




From idwg-public-request@semper.org  Wed Jun 26 06:45:11 2002
Received: from www.opencard.org (www.opencard.org [195.212.119.145])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11202
	for <idwg-archive@odin.ietf.org>; Wed, 26 Jun 2002 06:45:10 -0400 (EDT)
Received: by www.opencard.org (Postfix, from userid 503)
	id 9003934793; Wed, 26 Jun 2002 12:46:41 +0200 (CEST)
Old-Return-Path: <nsyracus@cnri.reston.va.us>
Delivered-To: semper-idwg-public@opencard.org
Message-Id: <200206261044.GAA11122@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce:;;IETF-Announce:;;;, @zurich.ibm.com;;;
Cc: idwg-public@zurich.ibm.com
From: Internet-Drafts@ietf.org
Reply-To: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-idwg-requirements-07.txt
Date: Wed, 26 Jun 2002 06:44:07 -0400
Sender: nsyracus@cnri.reston.va.us
Resent-Message-ID: <BxkT_C.A.rnE.QuZG9@www.opencard.org>
Resent-From: idwg-public@semper.org
X-Mailing-List: <idwg-public@semper.org> archive/latest/528
X-Loop: idwg-public@semper.org
Precedence: list
Resent-Sender: idwg-public-request@semper.org
Resent-Date: Wed, 26 Jun 2002 12:46:41 +0200 (CEST)

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Intrusion Detection Exchange Format Working Group of the IETF.

	Title		: Intrusion Detection Mesage Exchange Requirements
	Author(s)	: M. Wood, M. Erlinger
	Filename	: draft-ietf-idwg-requirements-07.txt
	Pages		: 28
	Date		: 25-Jun-02
	
The purpose of the Intrusion Detection Exchange Format Working Group
(IDWG) is to define data formats and exchange procedures for sharing
information of interest to intrusion detection and response systems,
and to the management systems which may need to interact with them.
This Internet-Draft describes the high-level requirements for such a
communication mechanism, including the rationale for those
requirements where clarification is needed.  Scenarios are used to
illustrate some requirements.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idwg-requirements-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-idwg-requirements-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-idwg-requirements-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:	<20020625142310.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-idwg-requirements-07.txt

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

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

--OtherAccess--

--NextPart--




