Re: [Dime] Comments on draft-ietf-dime-erp-03.txt

> Section 4 says:
>   When an ER server receives the ERP/DER message, it searches its local
>   database for a root key
> 
>   FFS:
>      and authorization state?

[Qin]: I guess we talk this before as one of open issue. Seems authorization attributes 
is missing, such as 
1.how the service type and Authorization-Lifetime is configured, 
2.how to verify the local ER server is authorized to advertise the domain name, 
3.how to authorize those users for ERP service.
On the other hand, we should decouple authorization with authentication.

> There seems to be some confusion here: an ER server will _never_ receive an
> ERP/DER message, since that is a _Diameter_ message, not an EAP message.
> Actually, the confusion starts in the Introduction: "a new Diameter ERP
> application to transport ERP messages between an ER authenticator and the ER
> server".  "Authenticator" is a technical term & refers to an EAP protocol
> entity, not a Diameter entity, so how can send Diameter messages?  Clearing
> up this confusion might go a long way toward making an acceptable
> specification.

[Qin]: Is it a big issue?

_______________________________________________
> DiME mailing list
> DiME@ietf.org
> https://www.ietf.org/mailman/listinfo/dime