Re: [apps-discuss] Fwd: New Version Notification for draft-sinnema-xacml-media-type-02.txt

Erik Wilde <> Fri, 29 March 2013 01:27 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E81FF21F848B for <>; Thu, 28 Mar 2013 18:27:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id U5FH8LSk5PXi for <>; Thu, 28 Mar 2013 18:27:32 -0700 (PDT)
Received: from cm02fe.IST.Berkeley.EDU (cm02fe.IST.Berkeley.EDU []) by (Postfix) with ESMTP id 4B84A21F8488 for <>; Thu, 28 Mar 2013 18:27:32 -0700 (PDT)
Received: from ([] helo=dretpro.local) by with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.76) (auth (envelope-from <>) id 1ULO6L-0001th-7M; Thu, 28 Mar 2013 18:27:30 -0700
Message-ID: <>
Date: Thu, 28 Mar 2013 18:27:28 -0700
From: Erik Wilde <>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130216 Thunderbird/17.0.3
MIME-Version: 1.0
To: " application-layer protocols" <>
References: <> <> <>
In-Reply-To: <>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: Barry Leiba <>
Subject: Re: [apps-discuss] Fwd: New Version Notification for draft-sinnema-xacml-media-type-02.txt
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 29 Mar 2013 01:27:33 -0000

hello barry.

On 2013-03-28 6:36 , Barry Leiba wrote:
> As far as I can tell at a brief glance, this is only a media type
> registration, for something that's documented in an OASIS document.  Is
> that correct?

close (XACML is defined in various OASIS specs), but not 100% (there is 
no single OASIS document tying the various versions together). we do 
have things in there that are not specified anywhere else, which is why 
we chose to go the IETF route where we can publish and discuss drafts.

> If so, then you needn't even publish this as an RFC at all.  You can
> make the media type registration on behalf of OASIS directly to IANA,
> using the form on the media types IANA page, requesting a registration
> in the standards tree for an SDO.

that's good to know. for now, we would like to continue the route we 
have been preparing, if that is possible. our main goal was to have a 
way how we can make this work public and discuss it before we simply 
declare it registered.

> In any case, you should post a pointer to this I-D to
> < <>>, so the media types
> crowd can review it.

ok, i just did that. please let me know if anything speaks against 
keeping this on its current path. thanks and cheers,


erik wilde |  -  tel:+1-510-2061079 |
            | UC Berkeley  -  School of Information (ISchool) |
            | |