Thanks to all who responded to the Call for Adoption. Five people
indicated support during the extended call period with two being the
authors. There was 1 additional indication of support during the
original call for support. There were no objections.
This document is adopted by the workin
Hi,
I support adoption of this document and will continue to contribute to it.
G.
> On 10 Feb 2021, at 19:33, James Galvin wrote:
>
> The Chairs would like to extend this CALL FOR ADOPTION because we’d like to
> separate out an issue that has come up in the discussion of this adoption.
> We
Hi all,
+1 for adoption.
Best,
Maurizio
> Il giorno 10 feb 2021, alle ore 20:33, James Galvin ha
> scritto:
>
> The Chairs would like to extend this CALL FOR ADOPTION because we’d like to
> separate out an issue that has come up in the discussion of this adoption.
> We are hoping that thi
Hi.
+1 for adoption.
Jasdip
On 2/10/21, 2:33 PM, "regext on behalf of James Galvin"
wrote:
The Chairs would like to extend this CALL FOR ADOPTION because we’d
like to separate out an issue that has come up in the discussion of this
adoption. We are hoping that this clarity wil
Hi,
I support adoption of this draft for the purpose stated by WG Chairs and
am willing to go on working on it.
Mario
Il 10/02/2021 20:33, James Galvin ha scritto:
The Chairs would like to extend this CALL FOR ADOPTION because we’d
like to separate out an issue that has come up in the discus
The Chairs would like to extend this CALL FOR ADOPTION because we’d
like to separate out an issue that has come up in the discussion of this
adoption. We are hoping that this clarity will address the concern that
has been raised.
This document actually covers two distinct issues.
1. A specif
