[Ace] AIF as discussed today (Re: I-D Action: draft-bormann-core-ace-aif-08.txt)
I went ahead and quickly implemented what we had discussed today. https://www.ietf.org/id/draft-bormann-core-ace-aif-08.html Lots more editing to do, but the gist of what I was trying to say should be there. Comments welcome! Grüße, Carsten > On 2020-06-23, at 00:12, internet-dra...@ietf.org wrote: > > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > This draft is a work item of the Authentication and Authorization for > Constrained Environments WG of the IETF. > >Title : An Authorization Information Format (AIF) for ACE >Author : Carsten Bormann > Filename: draft-bormann-core-ace-aif-08.txt > Pages : 9 > Date: 2020-06-22 > > Abstract: > Constrained Devices as they are used in the "Internet of Things" need > security. One important element of this security is that devices in > the Internet of Things need to be able to decide which operations > requested of them should be considered authorized, need to ascertain > that the authorization to request the operation does apply to the > actual requester, and need to ascertain that other devices they place > requests on are the ones they intended. > > To transfer detailed authorization information from an authorization > manager (such as an ACE-OAuth Authorization Server) to a device, a > representation format is needed. This document provides a suggestion > for such a format, the Authorization Information Format (AIF). AIF > is defined both as a general structure that can be used for many > different applications and as a specific refinement that describes > REST resources and the permissions on them. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-bormann-core-ace-aif/ > > There are also htmlized versions available at: > https://tools.ietf.org/html/draft-bormann-core-ace-aif-08 > https://datatracker.ietf.org/doc/html/draft-bormann-core-ace-aif-08 > > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=draft-bormann-core-ace-aif-08 > > > Please note that it may take a couple of minutes from the time of submission > until the htmlized version and diff are available at tools.ietf.org. > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > > ___ > I-D-Announce mailing list > i-d-annou...@ietf.org > https://www.ietf.org/mailman/listinfo/i-d-announce > Internet-Draft directories: http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt ___ Ace mailing list Ace@ietf.org https://www.ietf.org/mailman/listinfo/ace
[Ace] I-D Action: draft-bormann-core-ace-aif-08.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Authentication and Authorization for Constrained Environments WG of the IETF. Title : An Authorization Information Format (AIF) for ACE Author : Carsten Bormann Filename: draft-bormann-core-ace-aif-08.txt Pages : 9 Date: 2020-06-22 Abstract: Constrained Devices as they are used in the "Internet of Things" need security. One important element of this security is that devices in the Internet of Things need to be able to decide which operations requested of them should be considered authorized, need to ascertain that the authorization to request the operation does apply to the actual requester, and need to ascertain that other devices they place requests on are the ones they intended. To transfer detailed authorization information from an authorization manager (such as an ACE-OAuth Authorization Server) to a device, a representation format is needed. This document provides a suggestion for such a format, the Authorization Information Format (AIF). AIF is defined both as a general structure that can be used for many different applications and as a specific refinement that describes REST resources and the permissions on them. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-bormann-core-ace-aif/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-bormann-core-ace-aif-08 https://datatracker.ietf.org/doc/html/draft-bormann-core-ace-aif-08 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-bormann-core-ace-aif-08 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ ___ Ace mailing list Ace@ietf.org https://www.ietf.org/mailman/listinfo/ace
[Ace] The ACE WG has placed draft-bormann-core-ace-aif in state "Candidate for WG Adoption"
The ACE WG has placed draft-bormann-core-ace-aif in state Candidate for WG Adoption (entered by Jim Schaad) The document is available at https://datatracker.ietf.org/doc/draft-bormann-core-ace-aif/ ___ Ace mailing list Ace@ietf.org https://www.ietf.org/mailman/listinfo/ace
[Ace] The ACE WG has placed draft-tiloca-ace-oscore-gm-admin in state "Call For Adoption By WG Issued"
The ACE WG has placed draft-tiloca-ace-oscore-gm-admin in state Call For Adoption By WG Issued (entered by Jim Schaad) The document is available at https://datatracker.ietf.org/doc/draft-tiloca-ace-oscore-gm-admin/ ___ Ace mailing list Ace@ietf.org https://www.ietf.org/mailman/listinfo/ace
[Ace] Call for adoption draft-tiloca-ace-oscore-gm-admin
Hi, Following the interim meeting this morning, this email starts a call for adoption of "Admin Interface for the OSCORE Group Manager"[1]. Please state your opinion by July 6 2020 whether the WG should adopt or not this document. Yours, Jim and Daniel [1] https://datatracker.ietf.org/doc/draft-tiloca-ace-oscore-gm-admin/ -- Daniel Migault Ericsson ___ Ace mailing list Ace@ietf.org https://www.ietf.org/mailman/listinfo/ace
Re: [Ace] IANA considerations for authz-info RT
That corresponds to what I expected to see.
> -Original Message-
> From: Ace On Behalf Of Carsten Bormann
> Sent: Monday, June 22, 2020 8:56 AM
> To: ace@ietf.org
> Subject: [Ace] IANA considerations for authz-info RT
>
> Marco and I still have to do the bike shedding on the actual name (“ace.ai”
> below), but we can look at my proposed text already anyway:
>
> 8. IANA Considerations
>
> 8.NN. CoRE Resource Type registry
>
>IANA is requested to register a new Resource Type (rt=) Link Target
>Attribute in the "Resource Type (rt=) Link Target Attribute Values"
>subregistry under the "Constrained RESTful Environments (CoRE)
>Parameters" {{?IANA.core-parameters}} registry:
>
>rt="ace.ai". This resource type describes an ACE-OAuth authz-info
>endpoint resource.
>
>Specific ACE-OAuth profiles can use this common resource type for
>defining their profile-specific discovery processes.
>
> Have I captured the discussion today?
>
> Grüße, Carsten
>
> ___
> Ace mailing list
> Ace@ietf.org
> https://www.ietf.org/mailman/listinfo/ace
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace
[Ace] Minutes Posted
I have posted the minutes for the meeting today. If you want to make any change let me know. Jim ___ Ace mailing list Ace@ietf.org https://www.ietf.org/mailman/listinfo/ace
[Ace] AIF followup comment
Francesca, Cigdem, One of the things that you might want to consider as part of you problem with adapting to AIF is that the profile may want to re-define the bit string so that instead of using the CoAP request codes, you use your set of options allowing for a tighter encoding. Jim ___ Ace mailing list Ace@ietf.org https://www.ietf.org/mailman/listinfo/ace
[Ace] IANA considerations for authz-info RT
Marco and I still have to do the bike shedding on the actual name (“ace.ai”
below), but we can look at my proposed text already anyway:
8. IANA Considerations
8.NN. CoRE Resource Type registry
IANA is requested to register a new Resource Type (rt=) Link Target
Attribute in the "Resource Type (rt=) Link Target Attribute Values"
subregistry under the "Constrained RESTful Environments (CoRE)
Parameters" {{?IANA.core-parameters}} registry:
rt="ace.ai". This resource type describes an ACE-OAuth authz-info
endpoint resource.
Specific ACE-OAuth profiles can use this common resource type for
defining their profile-specific discovery processes.
Have I captured the discussion today?
Grüße, Carsten
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace
