Brian E Carpenter <[email protected]> wrote: > This looks like all good stuff to me and I don't have much to say.
>> The domain is embodied by the Registrar component.
> I think that's a step too far, because the Registrar doesn't
> do anything to establish the domain boundary and which nodes
> are at the edges of the domain. So I think it's better to say
> "The Registrar component embodies the identity, membership and
> trust anchor of the domain."
Thank you.
> [The identity being the DomainID, and the membership being the
> set of currently enrolled pledges. The registrar is the trust
> anchor because it either contains or interfaces with the CA.]
>> This document, while a Best Current Practices, makes use of BCP14
>> language to indicate which practices are mandatory, and which ones
>> are just recommendations.
> Did you mean to write "while *not* a BCP"? In any case you've
> tagged the draft for the standards track, which seems wrong.
I meant to mark it as BCP (fixing), or perhaps it would informational.
I'm not really sure if makes sense to publish it in any rush.
Perhaps it belongs in a book or white paper.
--
Michael Richardson <[email protected]>, Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
_______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima
