[arch-d] 答复: ETSI Liaison Work

Lizhenbin <lizhenbin@huawei.com> Mon, 29 June 2020 08:30 UTC

Return-Path: <lizhenbin@huawei.com>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D789A3A0C87 for <architecture-discuss@ietfa.amsl.com>; Mon, 29 Jun 2020 01:30:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
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 TRGmDgWqud8q for <architecture-discuss@ietfa.amsl.com>; Mon, 29 Jun 2020 01:30:28 -0700 (PDT)
Received: from huawei.com (szxga01-in.huawei.com [45.249.212.187]) (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 4173C3A0C8A for <architecture-discuss@iab.org>; Mon, 29 Jun 2020 01:30:28 -0700 (PDT)
Received: from DGGEMM401-HUB.china.huawei.com (unknown [172.30.72.54]) by Forcepoint Email with ESMTP id 21B233E12FEDB63D329E; Mon, 29 Jun 2020 16:30:23 +0800 (CST)
Received: from DGGEMM512-MBS.china.huawei.com ([169.254.4.204]) by DGGEMM401-HUB.china.huawei.com ([10.3.20.209]) with mapi id 14.03.0487.000; Mon, 29 Jun 2020 16:30:21 +0800
From: Lizhenbin <lizhenbin@huawei.com>
To: Guntur Wiseno Putra <gsenopu@gmail.com>, Rob Sayre <sayrer@gmail.com>
CC: "architecture-discuss@iab.org" <architecture-discuss@iab.org>, Paul Hoffman <paul.hoffman@vpnc.org>, IETF discussion list <ietf@ietf.org>
Thread-Topic: [arch-d] ETSI Liaison Work
Thread-Index: AQHWTRGjUXGewUz24UmVNs9y8X6LVKjtnUmAgABhnQCAAG+xgIAA1V7Q
Date: Mon, 29 Jun 2020 08:30:21 +0000
Message-ID: <5A5B4DE12C0DAC44AF501CD9A2B01A8D937A0E42@dggemm512-mbs.china.huawei.com>
References: <CAChr6SwT2MV-wg5ZA25_Z-iPReX6YZKzPUifBk+-G7js8iFgtw@mail.gmail.com> <9407069F-19E1-4AC1-BE4D-B7D6F62CC34F@vpnc.org> <CAChr6Swcn-y9UevzVB_TgTaPO4PU5Y_hXUBy6i=P9++3c18Vvw@mail.gmail.com>, <CAKi_AEvu4ESKogckHz12n_UQweMHiFuQVKKApi4+_Yy71wTGYA@mail.gmail.com>
In-Reply-To: <CAKi_AEvu4ESKogckHz12n_UQweMHiFuQVKKApi4+_Yy71wTGYA@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.153.180.83]
Content-Type: multipart/alternative; boundary="_000_5A5B4DE12C0DAC44AF501CD9A2B01A8D937A0E42dggemm512mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/sgM_cFwAmxgT34LKTsS5dhKd2Y8>
Subject: [arch-d] 答复: ETSI Liaison Work
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Jun 2020 08:30:30 -0000

Hi Guntur,

It is very helpful. Thanks very much.

I will go through these liaison and go on to summarize the need for the ETSI Liaison work.





Best Regards,

Zhenbin (Robin)









________________________________
发件人: Architecture-discuss [architecture-discuss-bounces@ietf.org] 代表 Guntur Wiseno Putra [gsenopu@gmail.com]
发送时间: 2020年6月29日 11:43
收件人: Rob Sayre
抄送: architecture-discuss@iab.org; Paul Hoffman; IETF discussion list
主题: Re: [arch-d] ETSI Liaison Work

Dear Rob &
architecture-discuss,


Adding a collection of references on "ETSI" having not been mentioned so far in this thread:

(By the help of the search engine available at "liaison statements" for "ETSI":)
Total Statements: 94


https://datatracker.ietf.org/liaison/posted/?text=ETSI&source=&destination=&start_date=&end_date=


Regard,
Guntur Wiseno Putra

Pada Senin, 29 Juni 2020, Rob Sayre <sayrer@gmail.com<mailto:sayrer@gmail.com>> menulis:
On Sun, Jun 28, 2020 at 8:14 AM Paul Hoffman <paul.hoffman@vpnc.org<mailto:paul.hoffman@vpnc.org>> wrote:

Although there are always layer 8 and 9 reasons for having, or not
having, liaison agreements, ...

Yes. This is the substance of my question.

thanks,
Rob

PS - I used the word "reviewed", but I should have written "read and commented", since no one asked me to do anything. :)