You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Scribing Template --Thursday, Oct 4, 2012 at 2:15pm -- Salon 6

TOPIC

Use of attribute options in LDAP to express 'metadata' about directory attributes

CONVENER: Benn Oshrin

SCRIBE: Chris Phillips

# of ATTENDEES: ~12?

MAIN ISSUES DISCUSSED 

RFC4512 and RFC4520 describe a way to decorate LDAP directory attributes with metadata about a given attribute.

Is there a way that this can be used to better explain/describe the value(s) contained within a given attribute and in turn, but used as the origin for other things in other areas (e.g. SAML representation of an object, JSON schema etc)

Comments:

# Don't do anything that breaks anything
# Design would be generic and re-usable and not just within higher ed in some cases.
# multivalued attributes will have a unique for each value within the attribute and it can be different.

Some examples are:

CN:lang-en:somevalue

CN:x-preferred:anothervalue

In order to define an 'option' label, an RFC needs to be written, an OID requested from IANA, and a Best Current Practice (BCP) needs to be done

-

ACTIVITIES GOING FORWARD / NEXT STEPS

Enumerate the option lables we would want to sponsor for RFC definition

Determine how we should encode them

Publish an initial one (Lang makes a lot of sense), and work on the next most important ones.

Repeat until done.

If slides are used in the session, please ask presenters to convert their slides to PDF and email them to acamp-info@incommon.org

Thank you!

  • No labels