[L2sm] 答复: Opinions on issue tracker for L2SM please
顾 戎 <gurong_cmcc@outlook.com> Tue, 22 November 2016 03:35 UTC
Return-Path: <gurong_cmcc@outlook.com>
X-Original-To: l2sm@ietfa.amsl.com
Delivered-To: l2sm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC45712946E for <l2sm@ietfa.amsl.com>; Mon, 21 Nov 2016 19:35:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.019
X-Spam-Level:
X-Spam-Status: No, score=-2.019 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=outlook.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aVTUhnypGzLQ for <l2sm@ietfa.amsl.com>; Mon, 21 Nov 2016 19:35:56 -0800 (PST)
Received: from BAY004-OMC4S9.hotmail.com (bay004-omc4s9.hotmail.com [65.54.190.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 54CD7129429 for <l2sm@ietf.org>; Mon, 21 Nov 2016 19:35:56 -0800 (PST)
Received: from APC01-HK2-obe.outbound.protection.outlook.com ([65.54.190.199]) by BAY004-OMC4S9.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Mon, 21 Nov 2016 19:35:56 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=yCpO9jQOgUV23wjyx1ZVFgkUTXpEJbcIqbNVcr6KdDs=; b=awJ+befx2p+k43idztUckFojR8y+LH7O4kal4RkZIMr5/3NUgQlLsBtZKIjJQXw8AnESjw3yotyy8bzRuLYJLMo62u32KbAUybd+TqExqSv4o+3h3f7QRxS8Cgrg/j0auj555ERn/h763eE0BK+mKqexl2IM6snXPSCcp4p/phQkdSYZKMl1Vlv1bcVTDKP0bw8lXyOWeobZfepH+eKlf3oHXiJvwaHqculQ/rzrEqSs9N8uuoY74Hi8QOcOaVg9a0lX7zO1NKT48ddY6tlHiOKYuB9RzxEGJiJUGbixJaXzf9IrEQCNcqNT1paSCm55fUAiLtO8meX5QnZp4wcv4Q==
Received: from HK2APC01FT020.eop-APC01.prod.protection.outlook.com (10.152.248.54) by HK2APC01HT032.eop-APC01.prod.protection.outlook.com (10.152.249.30) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.721.5; Tue, 22 Nov 2016 03:35:46 +0000
Received: from KL1PR0201MB1656.apcprd02.prod.outlook.com (10.152.248.57) by HK2APC01FT020.mail.protection.outlook.com (10.152.248.186) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.721.5 via Frontend Transport; Tue, 22 Nov 2016 03:35:46 +0000
Received: from KL1PR0201MB1656.apcprd02.prod.outlook.com ([10.167.58.150]) by KL1PR0201MB1656.apcprd02.prod.outlook.com ([10.167.58.150]) with mapi id 15.01.0734.012; Tue, 22 Nov 2016 03:35:46 +0000
From: 顾 戎 <gurong_cmcc@outlook.com>
To: "l2sm@ietf.org" <l2sm@ietf.org>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>
Thread-Topic: [L2sm] Opinions on issue tracker for L2SM please
Thread-Index: AdJBOhBIlyfjMEmNRC2INN5CcvGuTQDNz7Qp
Date: Tue, 22 Nov 2016 03:35:45 +0000
Message-ID: <KL1PR0201MB1656B5F2B1CD3FF9F523E39B8BB40@KL1PR0201MB1656.apcprd02.prod.outlook.com>
References: <0d6801d2413a$2fa6e0e0$8ef4a2a0$@olddog.co.uk>
In-Reply-To: <0d6801d2413a$2fa6e0e0$8ef4a2a0$@olddog.co.uk>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=outlook.com;
x-incomingtopheadermarker: OriginalChecksum:; UpperCasedChecksum:; SizeAsReceived:7471; Count:38
x-tmn: [EIkb92wj05MGDQY1AxIbIunqhoHB2Cen+Eb+uwWZX/0=]
x-incomingheadercount: 38
x-eopattributedmessage: 0
x-microsoft-exchange-diagnostics: 1; HK2APC01HT032; 5:U9sxzyGB6iO5ponw6ies1vLrjGxDyx9SF9TLfIR47TcWUSzqp1PxJUrVwT8lBLNbnXiKmioTQ1BOCAtOujJq2k5m/gHn2LJHa0OlNhwiqoHk1fr+vZvkAJwJCJyDALnobYpRkrMFtS0B/67vUfdNRw==; 24:0F6I30rUdJZmskj/TvxXGQWoCIuPPU2en5pbuQstXwXA66Mw2Mt8FM2CTfKTakbyJijixOtSJLMdtuDPlSvQNdf/MlYCxBVZuGi0rSe0M5w=; 7:uIRnXQf40c2LbfMj+CgoiRcXQsL6+inKWlIFd0qDzKTdGGFpCHPMjlsAZsIvjST+8XzM8Q5orJl/U5vusp2HPN4baICihw+WwXAzZBTj6AVznzP2ABXOqkhyF3ycU/pZdw4TJA2T4UtaMDgK9fKcka+Uq8kOrBnf5tavPBflfiSZeOXd6MJuU/QpRdNXmkMKXOUH/vMkNAJkWHKGva3LQ7WCflG+9ytInd5Fe0T4JJOoKDFG+sg3nW96dmokmOTGT1tU5t/kkqio+g2w2Xx8QWN6MzmrSfxvtNdohjpdkIFFqgY5/uiWcp++2hZG5AzVGf7pxT2+029bUVtEAEpXZ/vIB3Aw0M6QmawAstURfiQ=
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(10019020)(98900003); DIR:OUT; SFP:1102; SCL:1; SRVR:HK2APC01HT032; H:KL1PR0201MB1656.apcprd02.prod.outlook.com; FPR:; SPF:None; LANG:en;
x-ms-office365-filtering-correlation-id: 42ff562a-1730-44aa-253d-08d41288a51d
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(1601124038)(1603103113)(1603101340)(1601125047); SRVR:HK2APC01HT032;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(432015012)(82015046); SRVR:HK2APC01HT032; BCL:0; PCL:0; RULEID:; SRVR:HK2APC01HT032;
x-forefront-prvs: 0134AD334F
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_KL1PR0201MB1656B5F2B1CD3FF9F523E39B8BB40KL1PR0201MB1656_"
MIME-Version: 1.0
X-OriginatorOrg: outlook.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Nov 2016 03:35:45.9474 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HK2APC01HT032
X-OriginalArrivalTime: 22 Nov 2016 03:35:56.0021 (UTC) FILETIME=[888EAA50:01D24471]
Archived-At: <https://mailarchive.ietf.org/arch/msg/l2sm/NBhhGWlFHwYupXF9pfSkhuhEQ1s>
Subject: [L2sm] 答复: Opinions on issue tracker for L2SM please
X-BeenThere: l2sm@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "The Layer Two Virtual Private Network Service Model \(L2SM\)" <l2sm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2sm>, <mailto:l2sm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/l2sm/>
List-Post: <mailto:l2sm@ietf.org>
List-Help: <mailto:l2sm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2sm>, <mailto:l2sm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Nov 2016 03:35:58 -0000
Hi, I prefer to use IETF tool to track L2SM open issue since L2SM has been formed and it would be great to make discussion and open issue transparent to everybody who are interested and want to provide input. Gu Rong gurong@chinamobile.com gurong_cmcc@outlook.com ________________________________ 发件人: L2sm <l2sm-bounces@ietf.org> 代表 Adrian Farrel <adrian@olddog.co.uk> 发送时间: 2016年11月18日 1:22 收件人: l2sm@ietf.org 主题: [L2sm] Opinions on issue tracker for L2SM please Hi, During the development of the current draft, the authors used issues tracked in github using an old (and possibly inappropriate user ID) at https://github.com/alreadytiredofnomcom/L2SMissues/issues This worked "somewhat" depending on which authors had access to github. We have a three-way choice, IMHO: 1. just continue that issue tracker in github 2. stay in github but move to a better account 3. move issue tracking into the IETF using IETF tools Does anyone have an opinion? Thanks, Adrian _______________________________________________ L2sm mailing list L2sm@ietf.org https://www.ietf.org/mailman/listinfo/l2sm