Changes between Version 4 and Version 5 of AaronHelsinger/GAPI_AM_API_DRAFT2

Timestamp:

04/04/12 11:03:21 (12 years ago)

Author:

Aaron Helsinger

Comment:

--

AaronHelsinger/GAPI_AM_API_DRAFT2

@@ -54 +54 @@
  - '''ADOPTED''' with changes: Change Set I2: !SliversStatus return includes SSH logins/key for nodes that support SSH access
  - '''ADOPTED''': Change Set I3: !CreateSlivers return becomes a struct, adds sliver expiration
- - '''ADOPTED''': wiki:AaronHelsinger/GAPI_AM_API_DRAFT2#Adopted:ChangeSetK:Standardizecertificatesandcredentials Change Set K]: Standardize certificate contents, etc
+ - '''ADOPTED''': [wiki:AaronHelsinger/GAPI_AM_API_DRAFT2#Adopted:ChangeSetK:Standardizecertificatesandcredentials Change Set K]: Standardize certificate contents, etc
   - Include a real serial number, holder email, holder uuid, and optionally authority URL in certificates
   - Define slice ID as the UUID plus URN in slice certificates
@@ -313 +313 @@
 
  - An AM must pick credentials out of the list that it understands and be robust to receiving credentials it does not understand.
-  - Current slice and user credentials will be recognizable for following the schema defined in [#ChangeSetK:Standardizecertificatesandcredentials Change Set K].
+  - Current slice and user credentials will be recognizable for following the schema defined in [#Adopted:ChangeSetK:Standardizecertificatesandcredentials Change Set K].
  - AMs are required to continue to accept current-format credentials.
   - In particular, a single standard slice credential remains sufficient for most authorization policies.