Hi Alvaro,
Thank you. 
The co-authors will submit the draft 
(draft-ietf-spring-dhc-distribute-srv6-locator-by-dhcp-00) during the upcoming 
submission window at IETF 118.

Best regards,

Weiqiang

From: Alvaro Retana
Date: 2023-10-27 00:28
To: spring
CC: draft-cheng-spring-distribute-srv6-locator-by-dhcp; spring-cha...@ietf.org
Subject: Re: [spring] spring WG Adoption Call for 
draft-cheng-dhc-distribute-srv6-locator-by-dhcp
Hi!

This messages closed the adoption call for this draft.  There has been 
sufficient support and the authors have addressed the concerns what were 
brought up successfully. The document is adopted.

Authors: Please submit a replacement draft 
(draft-ietf-spring-dhc-distribute-srv6-locator-by-dhcp).  The submission window 
should open again during IETF 118.

Thanks!

Alvaro. 

On July 5, 2023 at 8:00:03 AM, Alvaro Retana (aretana.i...@gmail.com) wrote:

Dear WG: 

This message starts a two-week adoption call for 
draft-cheng-dhc-distribute-srv6-locator-by-dhcp, ending on July/19.  It 
"describes the method of assigning locators to SRv6 Endpoints through DHCPv6".  
 

   
https://datatracker.ietf.org/doc/draft-cheng-spring-distribute-srv6-locator-by-dhcp/
  


Please review the draft and consider whether you support its adoption by the 
WG.  Please share any thoughts with the list to indicate support or opposition 
-- this is not a vote.   

If you are willing to provide a more in-depth review, please state it 
explicitly to give the chairs an indication of the energy level in the working 
group willing to work on the document. 

WG adoption is the start of the process.  The fundamental question is whether 
you agree the proposal is worth the WG's time to work on and whether this draft 
represents a good starting point.  The chairs are particularly interested in 
hearing the opinion of people who are not authors of the document. 

Thanks! 

Alvaro (for the Chairs)
_______________________________________________
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

Reply via email to