Re: [spring] WG Adoption call - draft-srcompdt-spring-compression-requirement - draft-srcompdt-spring-compression-analysis

Tony Li <> Fri, 10 September 2021 19:28 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 8BE1C3A16E1 for <>; Fri, 10 Sep 2021 12:28:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.996
X-Spam-Status: No, score=-1.996 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, MIME_QP_LONG_LINE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id v1GfUoW1sAcy for <>; Fri, 10 Sep 2021 12:28:13 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::1032]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 1D4E03A16DD for <>; Fri, 10 Sep 2021 12:28:13 -0700 (PDT)
Received: by with SMTP id u13-20020a17090abb0db0290177e1d9b3f7so2227164pjr.1 for <>; Fri, 10 Sep 2021 12:28:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=eijKMI/GYNJPZsxwbQIUCzL/oY9+8/jKLIzRfQwZRTI=; b=gIcb9QMLc1ykWyeQwfY0dsfDsJ0rXqwH5NDtzWKclqikkArkU0203N8rZ2UcKtHku2 Pbx8vWdcS/+ZJtlFcB8NgCINzwDeBe8+e/KIWYegW1EscspSKFMvCcpz67Y87X7rrtLY eUjGJZcvnQcUsUjSH2dm/YrakPyo+xJ+AYWZ4SdkesksRt+WBXdzidL3S1QRpPQpLOj+ cKttmBuMC5+wKxjKTHC7xbOg/OW7eR+o5Fkvwp2N/9qLrhOaTkeOygDkcexO7N6cO4Xe U1gQ4O3JNb9UtG+R1t5U0CNOMmO1Cw9Ktvyos6MGxdEg2I3fmCkoDBtaiKWcas2e0YA1 j+Qw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=eijKMI/GYNJPZsxwbQIUCzL/oY9+8/jKLIzRfQwZRTI=; b=2hKXu6QkG5Z1P2PxERWPZyb8Ar6tl4/OfHGCc1/2ZZ3TsjjMW5sQ1DjjqShcgHFJSb lAQ4jE2Nq26/VWMCNsz1MuxFw/JZBKvZ1QUXG+t2yhd/g7v7jexfT8vMVO09vXBIUJWq wqEgaWDLpVhQSGsuCplNKm+a22VIcCMkQ/8cxXzEoOi7Y5ncktisv6LStdEYZjB0PkOd PsU60PAcEfwMtlQ+HJm4DP/AwdrUadEW6EErwbC/fgweGwL3etmlPPQLkpdwPf/XBb+0 YzzbNPTtJ+RJDLdjxL4UAQTWVcJo13GKPIrri9JXPDU+OFYCVXRnTAGY3ZJrPWhh1kys yTBA==
X-Gm-Message-State: AOAM533wunZ0g//aPBMwHTWPCdYVZVcRiY6Dt7YOXvgxckta2HoC5FAU ewYOpw+RHocdxBiAPVpDs9I=
X-Google-Smtp-Source: ABdhPJxfaCt7zLNtVm7r5VRSELVNGqNQM27dlRRpkOjXGQIrKEQyF+7fE5UtjZepugsLeXjBE/olfA==
X-Received: by 2002:a17:90a:e547:: with SMTP id ei7mr11462298pjb.177.1631302091223; Fri, 10 Sep 2021 12:28:11 -0700 (PDT)
Received: from ([]) by with ESMTPSA id g12sm5127652pja.28.2021. (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 10 Sep 2021 12:28:10 -0700 (PDT)
Content-Type: multipart/alternative; boundary=Apple-Mail-538D2709-4CAA-4364-844E-5F3F1E10220D
Content-Transfer-Encoding: 7bit
From: Tony Li <>
Mime-Version: 1.0 (1.0)
Date: Fri, 10 Sep 2021 12:28:09 -0700
Message-Id: <>
References: <>
In-Reply-To: <>
To: Ron Bonica <>
X-Mailer: iPhone Mail (18G82)
Archived-At: <>
Subject: Re: [spring] WG Adoption call - draft-srcompdt-spring-compression-requirement - draft-srcompdt-spring-compression-analysis
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 10 Sep 2021 19:28:20 -0000

I support adoption.


Sent from my iPhone

> On Sep 10, 2021, at 12:16 PM, Ron Bonica <> 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 <> On Behalf Of
> Sent: Tuesday, September 7, 2021 9:13 AM
> To:
> 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:
> 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