search

anima-wg / anima-brski-prm

ANIMA BRSKI Pledge in Responder Mode
Other
0 stars 6 forks source link

Necessity for new registrar enrollment endpoint #92

Closed stfries closed 1 year ago

stfries commented 1 year ago

Comment from Toerless to section 6.2.6

a) Is it really necessary to create a new endpoint ? I don't think it is, because the Media-Type of the request will indicate the new encoding, so why should we not be able to reuse the existing endpoint given how the semantic stays the say, just the encoding changes. Right ?

b) If it is necessary to create a new endpoint, should this be in /brski/ ? I think it would be more logical to put it under /est/. This enrollment request formatting would work perfectly well without BRSKI upfront.

stfries commented 1 year ago

We actually struggled here and were first tempted to exactly do as proposed under your point a) We restraint to not have the processing implicit based on the Content-Type but via an explicit endpoint. This would allow to use this endpoint also for other protocols not just EST. This was also the reason to put it under BRSKI and not EST naming to avoid confusion with the EST specified simpleenroll endpoint.

Proposal to leave it for clarity in the usage of already defined EST endpoints

stfries commented 1 year ago

Design Team May 09: leave as is, also easier to mix it with existing EST servers. Can be closed