[Dime] Comments on section 2 of new version draft-ietf-dime-erp-01
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Dime] Comments on section 2 of new version draft-ietf-dime-erp-01



2.  Terminology
 
   This document uses terminology defined in [RFC3748], [RFC5295],
   [RFC5296], and [RFC4072].
 
   "Root key" (RK) or "bootstrapping material" refer to the rRK or rDSRK
   derived from an EMSK, depending on the location of the ER server in
   home or foreign domain.
 
   We note in this document ERP/DER a Diameter-EAP-Request command with
   the Application Id set to Diameter ERP application.  On the same
   model, we use ERP/DEA, EAP/DER and EAP/DEA.
  
   [Qin]: what does the same model mean? how about saying:
   "
   We note in this document ERP/DER *refer to* a Diameter-EAP-Request Command with the
   Application Id set to Diameter ERP application. *Similarly*, we use ERP/DEA, EAP/DER
   and EAP/DEA
   "
   [Qin] I am wondering how EAP/DER and ERP/DER can be used in the same one roundtrip exhange
   between the authenticator, ER server and home EAP server. In my understanding, when to use ERP/DER
   and when to use EAP/DER depends on the deployment scenario and bootstrapping mode. e.g., in implicit
   bootstrapping mode, we use EAP/DER, in explicit bootstraping mode, we use ERP/DER?
   another example when home EAP server does not support ERP and ER server support EAP, in this case,
   EAP/DER and EAP/DEA can be used between ER server with EAP proxy function support and home EAP server.
   Am I right?
 

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.