Re: TransportDomain. Was: Re: [Syslog] Submission ofdraft-ietf-syslog-device-mib-12.txt

["tom.petch" <cfinss@dial.pipex.com>]

----- Original Message -----
From: "Juergen Schoenwaelder" <j.schoenwaelder@iu-bremen.de>
To: "tom.petch" <cfinss@dial.pipex.com>
Cc: "Glenn M. Keeni" <glenn@cysols.com>; <syslog@ietf.org>
Sent: Wednesday, December 27, 2006 12:40 PM
Subject: Re: TransportDomain. Was: Re: [Syslog] Submission
ofdraft-ietf-syslog-device-mib-12.txt

> On Sun, Dec 24, 2006 at 08:08:12PM +0100, tom.petch wrote:
> >
> > My sense is that your analysis of the protocols is
> >   syslog
> >   encapsulation
> >   transport
> > somewhat RFC3411-like so we might have an enumeration for
> > encapsulation, one (or more) for transport and problem solved.  I am
> > saying that the structure (architecture/layers) is not like that (no
> > dbh:-), that we have 'tls/tcp/IANA port' all tied up in a bundle
> > together, take it or leave it.
>
> I tried to clarify in a constructive way the purpose of InetAddress
> and friends and TransportAddress and friends. You seem to suggest to
> use some syslog specific SyslogDomain/SyslogAddress (but you don't
> spell things out so you leave me guessing).
>
You did indeed clarify the purpose of InetAddress and TransportAddress and that
leaves me thinking that they do not fit very well here:-(  Rather we have a
choice of
 RFC3164 over UDP
-protocol over UDP
-protocol over TLS/TCP
RFC3195 over BEEP
(some of which can be signed) to enumerate

Tom Petch

> > Were we ever to do anything different in future, most likely it
> > would be a another package, perhaps SSH/TCP/different IANA port or
> > TCP per se, so the decomposition you imply does not make sense to
> > me.
>
> There is a transport endpoint involved in SSH/TCP and some sort of
> encapsulation - so I do not really see what breaks.
>
> /js
>
> --
> Juergen Schoenwaelder {International|Jacobs} University Bremen
> <http://www.eecs.iu-bremen.de/> P.O. Box 750 561, 28725 Bremen, Germany