[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: sylsog in NETCONF notifications
- To: "Martin Bjorklund" <mbj@tail-f.com>
- Subject: RE: sylsog in NETCONF notifications
- From: "Hector Trevino \(htrevino\)" <htrevino@cisco.com>
- Date: Thu, 6 Jul 2006 13:35:50 -0700
- Authentication-results: sj-dkim-2.cisco.com; header.From=htrevino@cisco.com; dkim=pass ( sig from cisco.com verified; );
- Cc: <rgerhards@gmail.com>, <netconf@ops.ietf.org>
- Dkim-signature: a=rsa-sha1; q=dns; l=649; t=1152218151; x=1153082151; c=relaxed/simple; s=sjdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=htrevino@cisco.com; z=From:=22Hector=20Trevino=20\(htrevino\)=22=20<htrevino@cisco.com> |Subject:RE=3A=20sylsog=20in=20NETCONF=20notifications; X=v=3Dcisco.com=3B=20h=3Di1g4ON2xyWi8EvZT8FbxLj99TTk=3D; b=QJG6+vUrzl/WJ6NjX7AULqXbGp9QPp0dBk9oDBxc4VnL4I10sG5AJ/Ml8vX2G1/cA2AzQZB7 mWDieZ9GLItmGCCq3vNJZP1LK0OS7jYkpI4bxxHdr9CXgmK4nLHXM0Ul;
>
> The current draft specifies in B.1 a mapping from the syslog
> fields to something called NETCONF event fields. But these
> event fields are not defined anywhere. Is this part still
> correct, or are you saying that the syslog message is
> tunnelled "as-is"?
>
>
> /martin
>
The field descriptions got removed in a previous update. This needs to
be updated. The idea was that if we were to define the NETCONF
notification contents then we'd use the same definitions as syslog for
the fields listed in that table.
To your second question, yes the entire syslog message is tunneled as
is.
--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>