From: Paul Moore <paul.moore@hp.com>
To: linux-audit@redhat.com
Cc: Joy Latten <latten@us.ibm.com>
Subject: Re: RFC4303 (IPsec/ESP) auditing requirements
Date: Wed, 5 Dec 2007 15:46:13 -0500 [thread overview]
Message-ID: <200712051546.13686.paul.moore@hp.com> (raw)
In-Reply-To: <200712051445.13051.paul.moore@hp.com>
On Wednesday 05 December 2007 2:45:12 pm Paul Moore wrote:
> Hello all,
>
> I'm looking at RFC4303 at some of the auditing requirements and one of the
> gaps between what the specification requires and what we currently provide
> involves the SA's sequence number and the IPv6 flow ID. According the list
> of existing audit fields[1] there doesn't appear to any fields which are a
> good match. With that in mind I'd like to propose two new fields:
>
> * seqno - sequence number
> * flowid - flow id
Scratch the 'flowid' name, the more I look at things we should probably go
with 'flowlbl'.
> Any comments, objections, suggestions?
>
> [1] http://people.redhat.com/sgrubb/audit/audit-parse.txt
--
paul moore
linux security @ hp
next prev parent reply other threads:[~2007-12-05 20:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-05 19:45 RFC4303 (IPsec/ESP) auditing requirements Paul Moore
2007-12-05 20:46 ` Paul Moore [this message]
2007-12-06 18:25 ` Valdis.Kletnieks
2007-12-06 18:46 ` Paul Moore
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200712051546.13686.paul.moore@hp.com \
--to=paul.moore@hp.com \
--cc=latten@us.ibm.com \
--cc=linux-audit@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox