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

["Glenn M. Keeni" <glenn@cysols.com>]

Juergen,
Juergen Schoenwaelder wrote:
> On Thu, Dec 21, 2006 at 02:49:53PM +0900, Glenn M. Keeni wrote:
>
> >    Attached please find the updated ID
> >          draft-ietf-syslog-device-mib-12.txt
>
> The combination of 
>
>   syslogEntityControlBindAddrType	InetAddressType
>   syslogEntityControlBindAddr		InetAddress
>   syslogEntityControlTransportDomain	TransportDomain
>   syslogEntityControlService		SyslogService
>
> looks a bit crazy to me. 
I seemed to have missed something here. It will help if you can tell
me where I am going wrong in the following:
> - Why have both InetAddressType and TransportDomain?
We will not have this.
> - Why not simply use (InetAddressType,InetAddress,InetPortNumber) or
>   (TansportAddressType,TransportAddress)?
We got started with InetAddressType,InetAddress,InetPortNumber. But
then we realized that we will have problems representing transport
over TLS etc.
We can not use TransportAddressType,TransportAddress as there is no
transport type specified for
    (syslog) Transport over TLS
> - What is the value of saying the service name is "xyz", which has
>   only local significance?
Is this referring to syslogEntityControlService?
We will probably not need this.
> - How do I find out which encapsulations are supported (plain, beep,
>   tls, ...)?
That is the problem we are trying to solve.
Can that be done by defining appropriate domains for
    syslog transport over TLS
    syslog transport over beep etc. ?

Glenn



_______________________________________________
Syslog mailing list
Syslog@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/syslog