All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Moore <paul.moore@hp.com>
To: James Morris <jmorris@namei.org>
Cc: Daniel J Walsh <dwalsh@redhat.com>,
	libvir-list@redhat.com,
	"Daniel P. Berrange" <berrange@redhat.com>,
	Daniel Veillard <veillard@redhat.com>,
	Stephen Smalley <sds@tycho.nsa.gov>,
	selinux@tycho.nsa.gov
Subject: Re: [RFC] sVirt v0.10 - initial prototype
Date: Tue, 28 Oct 2008 18:17:35 -0400	[thread overview]
Message-ID: <200810281817.35288.paul.moore@hp.com> (raw)
In-Reply-To: <alpine.LRH.1.10.0810290836010.25230@tundra.namei.org>

On Tuesday 28 October 2008 5:42:17 pm James Morris wrote:
> On Thu, 23 Oct 2008, Paul Moore wrote:
> > However, may I suggest that instead of representing the DOI as a
> > string we use a 32bit integer?  I know that may sound a bit odd,
> > but in the networking world most DOI values are represented as
> > integers and when security labels are involved they tend to be
> > 32bits.  I understand that using a plain integer is much more
> > abstract than a human readable string but it should make it easier
> > to leverage existing and future* DOI frameworks.
>
> I'd prefer to use string, which can be managed freely by the user,
> and be human-readable.  Unlike IP layer networking, we're not
> constrained by e.g. having to fit in the IP options, and can simply
> convey the DOI as-is.

True, we've got plenty of space to play with in the sVirt case as 
opposed to things like labeled networking and labeled NFS.  However, 
that wasn't really my concern.  It is likely that at some point in the 
future we will have some sort of standardized approach to dealing with 
DOIs and right now most of the DOIs in the labeled security space are 
32 bit integers; using a 32 bit value in sVirt has the potential to 
make life much easier down the road.  Granted, if strings are voted as 
the way forward and portability of labeled guests really takes off then 
I'm sure we'll find a way to deal with it; it would just be nice not to 
have to adapt things later on.

> This will also not prevent users from utilizing integers as the DOI
> if desired.

Also true.

> In the common non-DoD case, people should be able to configure the
> DOI as simply as editing a configuration file to set the DOI to a
> domain name or arbitrary realm name.

I don't think DoD/non-DoD has anything to do with it, it is more of a 
management issue and both groups have the same problem.  Is the 
convenience of being able to enter "guests-r-us.com" over "5" in the 
DOI field really worth the disconnect from the traditional 32 bit DOI 
integer?

> > *An informal group/list just formed to start discussing DOI
> > management issues such as DOI formats, negotiation and translation.
>
> URL ?

Viola, http://mail.opensolaris.org/mailman/listinfo/doi-discuss, there 
was one thread in the beginning that got some traffic but it has been 
pretty quiet since then.  I'm pretty sure archives are available at the 
link above.

-- 
paul moore
linux @ hp

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

  reply	other threads:[~2008-10-28 22:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-21  2:06 [RFC] sVirt v0.10 - initial prototype James Morris
2008-10-21 13:57 ` Daniel J Walsh
2008-10-21 16:22   ` Daniel P. Berrange
2008-10-21 17:50     ` Daniel J Walsh
2008-10-22  9:51       ` Daniel P. Berrange
2008-10-22  9:50     ` James Morris
2008-10-22 10:03       ` Daniel P. Berrange
2008-10-22 10:05         ` James Morris
2008-10-29 21:51     ` James Morris
2008-10-22  9:23   ` James Morris
2008-10-23 12:05     ` Paul Moore
2008-10-28 21:42       ` James Morris
2008-10-28 22:17         ` Paul Moore [this message]
2008-10-29 14:40           ` David P. Quigley
2008-10-21 17:17 ` Daniel P. Berrange
2008-10-22 10:01   ` James Morris
2008-10-30  9:40 ` [libvirt] " Atsushi SAKAI
2008-10-30 19:18   ` Daniel J Walsh

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=200810281817.35288.paul.moore@hp.com \
    --to=paul.moore@hp.com \
    --cc=berrange@redhat.com \
    --cc=dwalsh@redhat.com \
    --cc=jmorris@namei.org \
    --cc=libvir-list@redhat.com \
    --cc=sds@tycho.nsa.gov \
    --cc=selinux@tycho.nsa.gov \
    --cc=veillard@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.