Hi, As we are currently in the process of RFC8366bis I have a question regarding the assertions.
Currently we have different types of assertions defined (https://www.ietf.org/archive/id/draft-ietf-anima-rfc8366bis-12.html#name-yang-module): - logged - verified - proximity - agent-proximity Logged and verified relates to actions which can be performed on the MASA side related to ownership verification, while proximity and agent-proximity provide information about the onboarding situation n the deployment domain. I was wondering if we address different assertions in one value based on the following use case: * A pledge (product) is sold via a distributor. The MASA has no information about the final customer. * If the pledge is onboarded, it creates a Voucher-request asking for a proximity assertion * The registrar provides the registrar voucher request including the pledge voucher request to the MASA * Based on the contained information, the MASA can verify proximity, but still may not know the customer (domain). * The MASA could react with the assertion "proximity". But given that the MASA has no information about the end customer it may also react with "logged" With this, are we addressing two different statements in one enumeration? Or did I misinterpret the enum? Best regards Steffen -- Steffen Fries
_______________________________________________ Anima mailing list -- [email protected] To unsubscribe send an email to [email protected]
