> Hi, please be aware that the YANG components of this will be moved to
> rfc8366bis.   They are already in the rfc8366bis-05, but I don't yet feel 
> that we have *WG* Consensus to do this.In general, I don't have preference 
whether this document of rfc8366bis defines YANG components. The major 
differency would be rfc8366bis would depend on the brski-prm document. That 
could means rfc8366bis could not  be published as RFC until brshi-prm 
published. I think an independent rfc8366bis could move faster. However, as I 
said, I don't have personal preference. I am fine either way。 I would leave 
this to authors‘’ choice.Regards,Sheng 
 
------------------ Original ------------------
From: &nbsp;"Michael&nbsp;Richardson"<[email protected]&gt;;
Date: &nbsp;Thu, Feb 2, 2023 03:34 AM
To: &nbsp;"Sheng Jiang"<[email protected]&gt;; 
Cc: &nbsp;"anima"<[email protected]&gt;; "Toerless Eckert"<[email protected]&gt;; 
"anima-chairs"<[email protected]&gt;; 
"draft-ietf-anima-brski-prm"<[email protected]&gt;; 
"ietf"<[email protected]&gt;; 
Subject: &nbsp;Re: WGLC for draft-ietf-anima-brski-prm-06, ends Feb. 15th, 2023

&nbsp;


Sheng Jiang <[email protected]&gt; wrote:
&nbsp;&nbsp;&nbsp; &gt; This message starts the two-week (*) ANIMA Working 
Group Last Call to
&nbsp;&nbsp;&nbsp; &gt; advance draft-ietf-anima-brski-prm-06, which specifies 
enhancements to
&nbsp;&nbsp;&nbsp; &gt; BRSKI (RFC8995) to facilitate bootstrapping in domains 
featuring no or
&nbsp;&nbsp;&nbsp; &gt; only time limited connectivity between 
a&amp;nbsp;pledge and the domain

Hi, please be aware that the YANG components of this will be moved to
rfc8366bis.&nbsp;&nbsp; They are already in the rfc8366bis-05, but I don't yet 
feel
that we have *WG* Consensus to do this.

Toerless has asked me to regurgitate the entire discussion, again, which I
think that I won't do.

&nbsp;&nbsp;&nbsp; &gt; If you do not feel this document should advance, please 
state
&nbsp;&nbsp;&nbsp; &gt; your reasons why

So, as much as I'd like it to advance, I don't think it can advance until we
agree what to do with the YANG.


--
Michael Richardson <[email protected]&gt;, Sandelman Software Works
&nbsp;-= IPv6 IoT consulting =-
_______________________________________________
Anima mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/anima

Reply via email to