Randy,
The registry we are creating contains (along with the OID and a
descriptive name) a specification pointer so that an implementer looking
at the registry can find the spec for the signed object in question.
I'm willing to add a reference to ghostbusters in the signed-object
draft, but my concern is that adding a reference to ghostbusters might
delay publication of the signed object draft. (As signed objects is in
IESG review and is now very close to publication.)
If we did not add a reference to ghostbusters in the signed-object
draft, then the way forward would be for ghostbusters to contain a very
short IANA considerations section that says: "Please add the following
triple to the signed object registry specified in [reference to signed
object]. <insert triple here>"
If the working group chairs could provide advice on the best way to
proceed forward (either adding a reference to ghostbusters in the
signed-object draft, or else adding an IANA considerations section to
ghostbusters) I would appreciate it.
- Matt Lepinski
On 5/11/2011 12:30 AM, Randy Bush wrote:
The signed-object registry will be initially populated with the ROA and
manifest OIDs; the -roa-format and -manifests docs can move forward
without modification.
ghostbusters too, please
1.2.840.113549.1.9.16.1.35
randy
_______________________________________________
sidr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sidr
_______________________________________________
sidr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sidr