[Cats] Use of the CATS WG Github

Adrian Farrel <adrian@olddog.co.uk> Thu, 12 October 2023 02:46 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: cats@ietfa.amsl.com
Delivered-To: cats@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA967C151073; Wed, 11 Oct 2023 19:46:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.104
X-Spam-Level:
X-Spam-Status: No, score=-7.104 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=olddog.co.uk
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AO_fuwoN-qqu; Wed, 11 Oct 2023 19:46:23 -0700 (PDT)
Received: from mta6.iomartmail.com (mta6.iomartmail.com [62.128.193.156]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 810A7C14CE39; Wed, 11 Oct 2023 19:46:21 -0700 (PDT)
Received: from vs3.iomartmail.com (vs3.iomartmail.com [10.12.10.124]) by mta6.iomartmail.com (8.14.7/8.14.7) with ESMTP id 39C2k7uQ007272; Thu, 12 Oct 2023 03:46:07 +0100
Received: from vs3.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 7E0CF4604B; Thu, 12 Oct 2023 03:46:07 +0100 (BST)
Received: from vs3.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 5E4424604A; Thu, 12 Oct 2023 03:46:07 +0100 (BST)
Received: from asmtp1.iomartmail.com (unknown [10.12.10.248]) by vs3.iomartmail.com (Postfix) with ESMTPS; Thu, 12 Oct 2023 03:46:07 +0100 (BST)
Received: from LAPTOPK7AS653V (ecs-139-159-170-12.compute.hwclouds-dns.com [139.159.170.12]) (authenticated bits=0) by asmtp1.iomartmail.com (8.14.7/8.14.7) with ESMTP id 39C2k3Qk032094 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 12 Oct 2023 03:46:05 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Qing An' <anqing.aq@alibaba-inc.com>, 'Peng Liu' <liupengyjy@chinamobile.com>, 'cats' <cats@ietf.org>
Cc: cats-chairs@ietf.org
References: <2023101119425249105113@chinamobile.com> <469b5b82-5dc5-4dfa-8d9f-9f166b7c5ba7.anqing.aq@alibaba-inc.com>
In-Reply-To: <469b5b82-5dc5-4dfa-8d9f-9f166b7c5ba7.anqing.aq@alibaba-inc.com>
Date: Thu, 12 Oct 2023 03:46:02 +0100
Organization: Old Dog Consulting
Message-ID: <055301d9fcb6$3f4defe0$bde9cfa0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0554_01D9FCBE.A1134240"
X-Mailer: Microsoft Outlook 16.0
Content-Language: en-gb
Thread-Index: Adn8tje7ztCkRBQCSHWHMqasEKcYmA==
X-Originating-IP: 139.159.170.12
X-Thinkmail-Auth: adrian@olddog.co.uk
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=olddog.co.uk; h=reply-to :from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type; s=20221128; bh=x7HGn1tmc4boPdLjbMw7K te2y/9m4cF2e6WVnb9JvEk=; b=bpuGlvbi9Y1zP+EAhgnPCEJ8cG8RUeML/QCWu bBrtZp8fgrUVtmo6Y3JAcO5TSl3y8uhaVpSxZrKYYEkyWhP+3ZZqq2XOpv6pn5CH tEdCOKxdgey5mMCOoovAZHQ5vygQEKCcefLBLHDE0YGQWKwUfHnmPqcP2+VzqX1V kn6zpDUvHXEohy28jzZMZUqP3ZQJeRh0NetW1E5Nlckqa2yz5sSTRmko2plNXIw+ AnXnvmYJEkZqDMomx/3v9O7dFH2O6Xv9rwuWdOafubbzxuDFJREs+tL12GLgWHFX WVgUXVkauYqYqeDHv36/DTtJZlm3Sf0t/ysYaT1cfaio9dBfQ==
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.1.0.2090-9.0.0.1002-27930.004
X-TM-AS-Result: No--24.390-10.0-31-10
X-imss-scan-details: No--24.390-10.0-31-10
X-TMASE-Version: IMSVA-9.1.0.2090-9.0.1002-27930.004
X-TMASE-Result: 10--24.390400-10.000000
X-TMASE-MatchedRID: /hyYWLkd2Sjv4tNJ1H3OMGoP/44lroeDxqwmEOBVKeoXR19nmRX2X4fq baIWKx3QtasxpUmh4e4YXmnq7byLOSqQO0zIUpynvHKClHGjjr0iSMnphO25Rd7p0Ru8jKvFhUP RMlWCwoTY6l6Q0ccySrcm79m33DGjmmJTaSCgYAvDguUBa3ISJX5Lmbb/xUuawfFIH9Seo2i6PD 0Fdea44JyYyq3dyMume0HF0ouRBVjsrfmvTLX/nv3vrjdfNHuX+VJ6lZyB0s9QbtDzBpEFfjLjZ 4rHWudrYK8+BIRGUQhzZV9mDJK6WsgLggM+entsE7sLdRVaGmffVqwz+CynaZ0oD5Lw3bToEqSm Dx1CZ0qQiUqgvBUFUDwNakGbUKNlOY0uFdPXUM5SAphtkUXoaEhMRy+qNwXgt2pskOlEt2qM1cD jR5aQuh40pxVe/+IJxU/SELf9UQ8/sDqabNSyQIDcpVWyPxAMxoZTHZ+XCFGWyPi+tKraPCSxSJ zWHcFlYI1t3hSgQLVRgM2MVcov06AuExYkDrItQfSOYOlxKYuSiza26cvwNNkY+KIbxMxzVIVGp QSjDhuWxW4Piwz4HrQzXfXZKQZFRS5eRZNKL9HcFkTd9CjuT/es4f8X5NWomCNknSXswf8PY7Ec 0tWek6lf6vShYFTIp0ZR6M3LqXqCcRgQIkcreCi1gp0ZxaqKKBRhpIHr/bKsp+jIDIe/maDmkLz tB9AW4vM1YF6AJbbVZ0g740lL+QSz8fXAzKymnT1cnsZohTCw7M6dyuYKgwKmARN5PTKc
X-TMASE-SNAP-Result: 1.821001.0001-0-1-22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/cats/BgapJulL4PGE_72iuZ1tt58RGS8>
Subject: [Cats] Use of the CATS WG Github
X-BeenThere: cats@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Computing-Aware Traffic Steering \(CATS\)" <cats.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cats>, <mailto:cats-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cats/>
List-Post: <mailto:cats@ietf.org>
List-Help: <mailto:cats-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cats>, <mailto:cats-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Oct 2023 02:46:28 -0000

To be clear for Qing An’s question and *everybody*

 

The repo is a tool that you are allowed to use but not required to use. It is MAY, not SHOULD or MUST.

It is a choice for the document authors and a personal choice depending on how they like to work.

 

[Hint: You will NEVER see me using Git for any I-D that I edit. I passionately hate it as a tool. :-) ]

 

Three points of reference for you all:

 

1.	Any repo held outside the IETF, is not an IETF repo. (Obvious, huh?). It has no authority. It is just a tool you use. 
2.	When (if) we adopt an I-D into the WG, we could realistically move it to the IETF repo, but that is not a requirement.
3.	Please be sure to keep the WG involved in discussions and decisions made via Git. The hints are:

a.	Discussions and decisions about WG I-Ds MUST be made on the mailing list
b.	If you want people to help with / discuss your individual I-Ds you SHOULD keep them informed via the mailing list
c.	You SHOULD post regular updates to your I-Ds. Don’t just keep updating the text in Git without checkpointing via a new revision in the Datatracker. New revisions of the draft do not need to have major changes. An I-D does not need to be complete.
d.	Please do not set up your repo to spam the mailing list with emails that report all of the changes.

 

Thanks for moving the work forward: I am looking forward to seeing some updated drafts SOON [1]

 

Best,

Adrian

 

[1] https://datatracker.ietf.org/doc/draft-farrel-soon/

 

 

From: Cats <cats-bounces@ietf.org> On Behalf Of Qing An
Sent: 12 October 2023 03:17
To: Peng Liu <liupengyjy@chinamobile.com>; cats <cats@ietf.org>
Cc: cats-chairs@ietf.org
Subject: Re: [Cats] CATS WG Github

 

Thanks Peng. That's really helpful.

 

As for the Use Case of Computing-Aware AI large model discussed previously (https://datatracker.ietf.org/doc/draft-an-cats-usecase-ai/), should I make a pull request in the repo? 

 

Regards,

Qing An

 

 

------------------------------------------------------------------

From:Peng Liu <liupengyjy@chinamobile.com <mailto:liupengyjy@chinamobile.com> >

Send Time:2023年10月11日(星期三) 19:41

To:cats <cats@ietf.org <mailto:cats@ietf.org> >

Cc:cats-chairs@ietf.org <cats-chairs@ietf.org <mailto:cats-chairs@ietf.org> >

Subject:[Cats] CATS WG Github

 

Hi All, 

 

We have the WG github for the WG documents: https://github.com/cats-wg. 

 

The repositories for the draft-ietf-cats-usecases-requirements is: https://github.com/cats-wg/draft-ietf-cats-usecases-requirements.

 

Authors of the document can use it to refine the draft, we also encourage people to comments on it and sync the updates to the mailinglist. Thanks.

 

Regards,

Peng 


  _____  


liupengyjy@chinamobile.com <mailto:liupengyjy@chinamobile.com>