Bruno,
Thanks. This clears up the confusion.
I support adoption.
Ron
Juniper Business Use Only
From: [email protected] <[email protected]>
Sent: Monday, September 13, 2021 5:50 AM
To: Ron Bonica <[email protected]>
Cc: [email protected]
Subject: RE: WG Adoption call - draft-srcompdt-spring-compression-requirement -
draft-srcompdt-spring-compression-analysis
[External Email. Be cautious of content]
Ron,
It looks to me that you are quite well aware of the whole IETF process; but if
not [1] may be a good starting pointer.
This WG adoption call is not expected to be any different than other WG
adoption calls.
You are right that WG adoption of a document means that the WG own the document
and so its content. But WG adoption of a document only make sense if the wg
believe that the document is a good starting point: we are not adopting the
title but the whole document.
Your below email is not crystal clear to me with regards to whether or not you
have a concern with the document.
If you have specific concern(s) on the document or some part/sentences in the
document, could you please state those concerns on the mailing list?
>From the informational document that you have cited, below are two questions
>which seem related to your email. If you wish to, you are also welcome to
>voice your opinion on these two points.
* Does the document provide an acceptable platform for continued effort by
the working group?
* What are the process or technical objections to adoption of the draft?
> If so, I support adoption of this draft.
Which one?
[1]
https://www.ietf.org/standards/process/<https://urldefense.com/v3/__https:/www.ietf.org/standards/process/__;!!NEt6yMaO-gk!XORaRAzP4eTP5TQKr2ujYE5WK4Cy0_jornjNH4rmA6EVd5o35UD5BZnRhn-sVLRh$>
--Bruno
From: Ron Bonica [mailto:[email protected]]
Sent: Friday, September 10, 2021 9:16 PM
To: DECRAENE Bruno INNOV/NET
<[email protected]<mailto:[email protected]>>;
[email protected]<mailto:[email protected]>
Subject: RE: WG Adoption call - draft-srcompdt-spring-compression-requirement -
draft-srcompdt-spring-compression-analysis
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]<mailto:[email protected]>> On
Behalf Of [email protected]<mailto:[email protected]>
Sent: Tuesday, September 7, 2021 9:13 AM
To: [email protected]<mailto:[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://urldefense.com/v3/__https:/datatracker.ietf.org/doc/html/draft-srcompdt-spring-compression-requirement__;!!NEt6yMaO-gk!T1i99K3HoodKT8vePZSAAOBS5cz0a3fTWlQEk5xTiZa05lP82zMKOvwMhUozCY2f$>
https://datatracker.ietf.org/doc/html/draft-srcompdt-spring-compression-analysis<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/html/draft-srcompdt-spring-compression-analysis__;!!NEt6yMaO-gk!T1i99K3HoodKT8vePZSAAOBS5cz0a3fTWlQEk5xTiZa05lP82zMKOvwMhc0iIRXo$>
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.
_________________________________________________________________________________________________________________________
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
