On 28/10/2009, at 11:30 AM, Randy Bush wrote:

Sandy, with your WG chair hat on, could you please issue a WG Last
Call on the following document:
draft-ietf-sidr-rescerts-provisioning-05.txt

still reading, but ...

naming of actors in this document still assumes that ISPs are the
children.  children might be RIRs (parent IANA), or end sites (parent
ISPs or owning non-end user sites (e.g. business subsidiaries or govt
structures)).

again, i suggest something like 'parent' and 'child', though i am not
strongly attached to those words.

randy

I don't see the acronym RIR anywhere in the document. There is one reference to regional internet registry policy documents.

It does talk about LIR, and IR, and ISP. I would have thought that IANA, the RIRs and LIRs are conceptually at least one of LIR and IR in this context.

So, are you just saying you want these specific terms replaced by more neutral 'parent' and 'child' (or likewise, similar, roget-thesaurus- time) terms?

section 1.1 terminology seems to me to be quite good actually:

1.1 Terminology

  (elided)

   Additional terms used in this document are:

"IR" an abbreviation of "Internet Registry", using in the context of
      this document as an entity undertaking the role of resource
      issuer.  An IR is a Certificate Authority, and can issue Resource
      Certificates.

   "ISP"  an abbreviation of "Internet Service Provider", using in the
      context of this document as an entity undertaking the role of
      resource recipient who is the subject of a Resource Certificate.
      An ISP may be issued with a CA-enabled certificate, allowing the
      entity to also assume the role of an IR.

   "resource class"  a resource class refers to a collection of
      resources that can be certified in a single resource certificate
      by an issuer.

   "server"  in the context of this client/server protocol
      specification, the IR assumes the role of the "server."

   "client"  in the context of this client/server protocol
      specification, the ISP assumes the role of the "client."

So, contextually, an entity is referred to as a client when it faces up, which is broadly speaking what most ISPs will do *in the context of their own routing announcements* at least.

When they operate as agents issuing certificates, they are in the role of an IR. -And that is what the "ISP" terminology section says: "An ISP may be issued with a CA-enabled certificate, allowing the entity to also assume the role of an IR."

I'm not an author of this draft btw.

-george


_______________________________________________
sidr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sidr

Reply via email to