Re: [alto] GitHub Use for IETF Working Groups

Qin Wu <> Mon, 22 March 2021 11:25 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id AF5CC3A11AF for <>; Mon, 22 Mar 2021 04:25:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Scv3mzLbgFre for <>; Mon, 22 Mar 2021 04:25:13 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 53E9E3A11AD for <>; Mon, 22 Mar 2021 04:25:13 -0700 (PDT)
Received: from (unknown []) by (SkyGuard) with ESMTP id 4F3sPw4t7Sz682Zn; Mon, 22 Mar 2021 19:16:20 +0800 (CST)
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Mon, 22 Mar 2021 12:25:00 +0100
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.2106.2 via Frontend Transport; Mon, 22 Mar 2021 12:25:00 +0100
Received: from ([]) by ([]) with mapi id 14.03.0513.000; Mon, 22 Mar 2021 19:24:58 +0800
From: Qin Wu <>
To: Jensen Zhang <>
CC: "" <>, IETF ALTO <>
Thread-Topic: [alto] GitHub Use for IETF Working Groups
Thread-Index: AdcfDc7J1TwalbfDT0G1wk+I0iP9Hw==
Date: Mon, 22 Mar 2021 11:24:57 +0000
Message-ID: <>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABAADE78FCBdggeml511mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
Subject: Re: [alto] GitHub Use for IETF Working Groups
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 22 Mar 2021 11:25:19 -0000

Both works for me. You can send me your github username offline to me if you want to add you as collaborators.

发件人: Jensen Zhang []
发送时间: 2021年3月22日 19:17
收件人: Qin Wu <>
抄送:; IETF ALTO <>
主题: Re: [alto] GitHub Use for IETF Working Groups

Hi Qin,

It looks nice. Shall we send pull requests or you add us as collaborators of each repo?


On Mon, Mar 22, 2021 at 7:09 PM Qin Wu <<>> wrote:
Excellent, Kai, can you move path vector document into<>
which will be monitored by ietf secretariat and our Ads.
You can see the entry point to ALTO github organization.
发件人:<> [<>]
发送时间: 2021年3月22日 18:31
收件人: Qin Wu <<>>
抄送: IETF ALTO <<>>
主题: Re: [alto] GitHub Use for IETF Working Groups

Hi Qin,

Thanks for the email and I would like to second the suggestion.

We are already using github for the Path Vector document:


2021-03-20 10:47:21"Qin Wu" <<>>wrote:


I think it is a good practice to use Github to keep track of any open issues on chartered items.

For all the document authors, I recommend to move your WG drafts to the github,

The following is the guideline to tell you how to upload your drafts


> 发件人: WGChairs [] 代表 IETF Secretariat

> 发送时间: 2021年3月10日 4:11

> 收件人: Working Group Chairs <<>>

> 主题: GitHub Use for IETF Working Groups


> To the WG Chairs,


> Many IETF working groups are now using GitHub. RFC 8875 [1] and 8874

> [2] detail IETF Working Group GitHub administration. Per the RFCs, the

> WG Chairs must add the IETF Secretariat (@ietf-secretariat) and the

> WG's Area Directors as owners of the WG GitHub organization.

> Instructions for how to create your WG GitHub, as well as how to add

> the appropriate owners, can be found on the WG Chairs page [3].


> If you already have a GitHub organization for your working group,

> please verify that the IETF Secretariat (GitHub user ID: @ietf-

> secretariat) is an owner. In addition, please make sure that the WG

> GitHub is included within the “Additional Resources” section of the

> the WG’s Datatracker page (e.g.,

> In addition to making it

> easier for people to find, linking your GitHub from within the

> Datatracker also ensures that the GitHub data will be backed up by the



> If your working group does not yet have a GitHub Organization and you

> would like us to set one up for you, please send email to

><> with the subject line "GitHub Organization Request

> for WGACRONYM." Please include the GitHub ID for each WG Chair and WG

> Secretary.


> If you have any questions, please let us know!


> Best regards,


> The IETF Secretariat



> [1]

> [2]

> [3]

alto mailing list<>