Re: Comments on IDXP

> 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.