Guy Harris <[email protected]> wrote: > One of the other daemons is journald, which is a syslogd replacement:
>
https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html
> The "systemd" block in pcapng is called the "systemd Journal Export
> Block"; it doesn't cover systemd as a whole, it just covers the format
> that journald uses to export entries from its log file. The
> description of the export block points to the description of the export
> format:
So to be clear, the "systemd" block is about log file entries which are
partially binary.
I think that it deserves a document on it's own, regardless of what you might
think about systemd.
> Do any of those RFCs point to an external specification for most of the
> information about the item being discussed, similarly to what's the
> case for the systemd Journal Export Block?
> Are there any registries that have "less than an RFC and more than a
> mailto: URL", i.e. that say more than just "ask this person, hopefully
> they're still around, still have that email address, and still remember
> what this entry in the registry was all about"?
Yes, this is called First Come, First Served.
It usually has an Designated Expert that IANA consults.
We haven't proposed any policy yet in section 11.1 of tuexen-opsawg-pcapng,
except for defining that 0x8000_0000 to 0xffff_ffff are for local use.
(IANA speak is: "PRIVATE USE")
We should probably reserve the first 64K for IETF Action (i.e. standards
track), 64K to 0x0fff_ffff for Specification Required (not necessarily an
RFC) and make the 0x1000_0000 to 0x7fff_ffff as FCFS.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] [email protected] http://www.sandelman.ca/ | ruby on rails [
signature.asc
Description: PGP signature
_______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
