MinimumLID

From LID Wiki

Minimum LID is the name of the minimum functionality that must be supported by a URL to be a LID URL.

See also: LID Relying Party Service, LID Services

Contents 1 Yadis Discovery 2 Protocol Query 3 Public Key 4 Notes

Yadis Discovery

The URL must support one of the valid methods for Yadis discovery, such as:

• the X-XRDS-Location HTTP header
• the equivalent http-equiv statement in HTML
• the direct return of the XRDS file from the URL when the appropriate MIME type is specified.

Protocol Query

Note: this form of the protocol query has been obsoleted due to Yadis.

LID?meta=lid

must return the version of LID(tm) supported by this URL. If the LID(tm) version is at least 2.0, it also must return the names and versions of all LID 2.0 Profiles supported by this URL. If the URL also supports the LID Relying Party Profile, it may take the identity of the LID Client performing the query into account.

The response format uses MIME type text/plain and has the following syntax:

protocol: http://lid.netmesh.org/
version: 2.0

profile: org.netmesh.lid.relying-party
version: 1.0,1.2,2.001

profile: some-other-profile
version: some-opaque-version-string

The response elements are separated by empty lines. There is exactly one element with the keyword protocol: http://lid.netmesh.org/, which represents LID(tm) itself. All subsequent elements are optional; they reflect LID 2.0 Profiles supported by this URL.

Each protocol and profile lists the version it supports, using the version keyword. In case multiple versions are supported, these version strings are separated by commas (without adding additional white space). Version strings must be treated as opaque strings as no assumption is being made about a particular versioning naming scheme. In particular, one must not assume that a version string that appears to be earlier (e.g. 1.3 vs. 2.2) indeed is earlier, or remains supported by the URL if not listed.

Each keyword-value pair is listed on a separate line. There is exactly one space between the colon and the value, and no space between keyword and colon. No assumptions must be made about the length of the lines.

In the future, additional keywords may be added to this response. Implementations are strongly advised not to assume that there will be only two lines per profile; the proper separator is the empty line between the different profiles.

Public Key

LID?lid-meta=gpg%20--export%20--armor

must return the public GPG key associated with the LID URL. (See also LID 2.0). By virtue of Yadis, the service URI for this query may be different than then LID URL itself.

Changed from meta to lid-meta in order to not overload the keyword meta too much that also might be used by non-LID technologies.

Notes

MinimumLID does not need to return any identity data other than the public keys of the required LID Credential Types.