I support adoption.

T

Sent from my iPhone

> On Sep 10, 2021, at 12:16 PM, Ron Bonica 
> <[email protected]> wrote:
> 
> 
> Bruno,
>  
> When a WG adopts a design team draft, I assume that the draft becomes subject 
> to the following guidelines from RFC7221:
>  
> “Once a working group adopts a draft, the document is owned by the working 
> group and can be changed however the working group decides, within the bounds 
> of IETF process and the working group charter.  Absent explicit agreement, 
> adopting a document does not automatically mean that the working group has 
> agreed to all of its content.  So a working group (or its charter) might 
> explicitly dictate the basis for retaining, removing, or modifying some or    
>    all of a draft's content, technical details, or the like. However, in the 
> absence of such constraints, it is worth having the adoption process include 
> a sub-process of gathering working group concerns about the existing draft 
> and flagging them explicitly.”
>  
> Do I have that right?
>  
> If so, I support adoption of this draft.
>  
>                                                                 Ron
>  
>  
> Juniper Business Use Only
> From: spring <[email protected]> On Behalf Of [email protected]
> Sent: Tuesday, September 7, 2021 9:13 AM
> To: [email protected]
> Subject: [spring] WG Adoption call - 
> draft-srcompdt-spring-compression-requirement - 
> draft-srcompdt-spring-compression-analysis
>  
> [External Email. Be cautious of content]
>  
> Dear WG,
>  
>  
> The Design Team has produced two documents:
> - A requirement document: draft-srcompdt-spring-compression-requirement
> - A solution analysis document: draft-srcompdt-spring-compression-analysis
>  
> Both have been presented to the WG and triggered some discussions but are 
> still individual documents.
> We believe it's now time for the WG to consider taking ownership of those two 
> documents.
> Note that, especially for those two documents, WG adoption does not 
> necessarily mean RFC publication in particular if it turns out that the 
> benefit of long term archive would not justify the WG and IESG effort to 
> finalize those two documents.
>  
>  
> This message starts a 2 week WG adoption call, ending September  20th 2021, 
> for:
> https://datatracker.ietf.org/doc/html/draft-srcompdt-spring-compression-requirement
> https://datatracker.ietf.org/doc/html/draft-srcompdt-spring-compression-analysis
>  
>  
> After review of the document(s) please indicate support (or not) for WG 
> adoption of the document(s) to the mailing list.
> Please also provide comments/reasons for your support (or lack thereof) as 
> this is a stronger way to indicate your (non) support as this is not a vote.
>  
> If you are willing to work on the document(s), please state this explicitly. 
> This gives the chairs an indication of the energy level of people in the 
> working group willing to work on the document.
>  
> Thanks!
>  
> Jim, Bruno & Joel
>  
> _________________________________________________________________________________________________________________________
>  
> Ce message et ses pieces jointes peuvent contenir des informations 
> confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu 
> ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
> electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou 
> falsifie. Merci.
>  
> This message and its attachments may contain confidential or privileged 
> information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete 
> this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been 
> modified, changed or falsified.
> Thank you.
> _______________________________________________
> spring mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/spring
_______________________________________________
spring mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/spring

Reply via email to