There is a reasonable good foundation for this document giving it is coalesced 
from parts of several relevant WG documents. I will launch the adoption call 
soon. 


Sheng JIANG



>Dear Sheng,



>



>On behalf of the co-authors, i would hereby like to ask for adoption of



>draft-eckert-anima-brski-discovery.



>



>The draft is not about new, not-yet-adopted work, but instead it is coalescing



>discovery options that we originally had started to write into different BRSKI 
>variation



>documents:



>



>    draft-ietf-anima-brski-prm



>    draft-ietf-anima-brski-ae



>    draft-ietf-anima-brski-constrained-voucher



>    draft-ietf-anima-brski-constrained-proxy



>



>During the work on the discovery text for those drafts in the past year, it 
>became



>obvious that there was a lot of overlap and more text than woudl reasonably 
>make sense



>in every individual variation when it had to be duplicated across so many 
>drafts.



>



>We already have precedence of moving out text from one adopted ANIMA RFC into 
>another



>and adopting the second without another adoption call 
>(draft-ietf-anima-brski-async-enroll-03 ->



>draft-ietf-anima-brski-prm-00), and i think the same process would equally be 
>appropriate here,



>but if you think we need an adoption call, then i would like to ask for one on 
>behalf of



>the co-authors.



>



>Also, i think we had good discussion about the document during IETF118, in our



>side meetings and on the mailing list:



>



>https://mailarchive.ietf.org/arch/search/?q=%22draft-eckert-anima-brski-discovery%22



>



>Thank you!



>    Toerless



>



>_______________________________________________



>Anima mailing list



>[email protected]



>https://www.ietf.org/mailman/listinfo/anima



>


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

Reply via email to