Re: [Idnet] Architecture and standard opportunities of IDN

yanshen <yanshen@huawei.com> Mon, 31 July 2017 12:25 UTC

Return-Path: <yanshen@huawei.com>
X-Original-To: idnet@ietfa.amsl.com
Delivered-To: idnet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D33613219D for <idnet@ietfa.amsl.com>; Mon, 31 Jul 2017 05:25:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 ZGUlKovRtcbF for <idnet@ietfa.amsl.com>; Mon, 31 Jul 2017 05:25:57 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DAB9712741D for <idnet@ietf.org>; Mon, 31 Jul 2017 05:25:56 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml703-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DLQ14005; Mon, 31 Jul 2017 12:25:54 +0000 (GMT)
Received: from DGGEMM405-HUB.china.huawei.com (10.3.20.213) by lhreml703-cah.china.huawei.com (10.201.108.44) with Microsoft SMTP Server (TLS) id 14.3.301.0; Mon, 31 Jul 2017 13:25:38 +0100
Received: from DGGEMM505-MBS.china.huawei.com ([169.254.2.173]) by DGGEMM405-HUB.china.huawei.com ([10.3.20.213]) with mapi id 14.03.0301.000; Mon, 31 Jul 2017 20:25:05 +0800
From: yanshen <yanshen@huawei.com>
To: =?iso-8859-1?Q?J=E9r=F4me_Fran=E7ois?= <jerome.francois@inria.fr>
CC: "idnet@ietf.org" <idnet@ietf.org>
Thread-Topic: [Idnet] Architecture and standard opportunities of IDN
Thread-Index: AdMGA6fVfWTKGPKySXypIgnjpRC5HgAKuS0AAEYhhAAAqrM+EA==
Date: Mon, 31 Jul 2017 12:25:04 +0000
Message-ID: <6AE399511121AB42A34ACEF7BF25B4D2979B8A@DGGEMM505-MBS.china.huawei.com>
References: <5D36713D8A4E7348A7E10DF7437A4B927CE3A673@NKGEML515-MBX.china.huawei.com> <20170727004512.GC18300@spectre> <ae317d90-f98f-acd3-00d7-463ff3a97782@inria.fr>
In-Reply-To: <ae317d90-f98f-acd3-00d7-463ff3a97782@inria.fr>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.130.179.89]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090206.597F21D3.003C, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.2.173, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 189c22a679284c96377573e097c5cc14
Archived-At: <https://mailarchive.ietf.org/arch/msg/idnet/w6ZK6_4Bi6DBJGe-vO_EFduITig>
Subject: Re: [Idnet] Architecture and standard opportunities of IDN
X-BeenThere: idnet@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "The IDNet \(Intelligence-Defined Network\) " <idnet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idnet>, <mailto:idnet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idnet/>
List-Post: <mailto:idnet@ietf.org>
List-Help: <mailto:idnet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idnet>, <mailto:idnet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Jul 2017 12:25:59 -0000

Hi Jerome,

> -----Original Message-----
> From: IDNET [mailto:idnet-bounces@ietf.org] On Behalf Of Jér?me Fran?ois
> Sent: Friday, July 28, 2017 6:13 PM
> To: idnet@ietf.org
> Subject: Re: [Idnet] Architecture and standard opportunities of IDN
> 
> Hi,
> 
> Le 27/07/2017 à 02:45, Pedro Martinez-Julia a écrit :
> > Dear Sheng,
> >
> > First of all, and considering my recent experience with the Network
> > Slicing work, I think we have some aspects of our work that are
> > probably essential for the IETF and network technology in general:
> >
> > - As you mention and all of us know well, we need to standardize the
> >   data format, so it is a good opportunity to define some ontology and
> >   the corresponding YANG model that structures such data.
> Do you imagine kind of a transformation process in the architecture as data to be
> used can come with pre-existing various data formats ?

My two cents. I ever think about that. The proposed data format should be easily "re-constructed" via existing data formats. The new attributes in the new format should can be auto-filled. Like the transformation of "XML schema" to "YANG".

> > - We have also a good opportunity to define a "benchmarking framework"
> >   that can be used with whatever dataset we can gather in the future in
> >   order to validate some approach. This would be a combination of YANG
> >   model and work protocols (not network, but procedure protocols) that
> >   would be required to ensure the results are universally valid and can
> >   be contrasted to other results. This is essential in any discipline,
> >   as we can find in areas such as multimedia communications or computer
> >   vision, but the networking area does not have anything like it.
> Fully agree, this is essential for comparing results. This is well linked to datasets
> issues as well and in general with reproducible experiments.
> > - The definition of "wire protocols", interfaces, and the format of data
> >   exchanged (also as YANG models) that are easily identified in the IDN
> >   architecture figure that I think all of us support to some extent.
> >
> > - Of course, the IDN reference architecture (but this has been deeply
> >   discussed).
> >
> > As you can perceive, I am trying to be practical. This somehow
> > contrasts with my typical views, which are normally quite abstract,
> > but those work are quite obvious, are not defined elsewhere, and can
> > be a good starting point to form a WG in the future. For the moment,
> > we can address such work through other RG/WG (e.g. NMRG) so we can
> > begin the writing of some drafts-of-drafts for IETF 100. If you are
> > interested on doing it, please let me know and we can define some
> > schedule and some rough ToC for those documents. Thank you very much.
> >
> > Regards,
> > Pedro
> >
> > On Wed, Jul 26, 2017 at 11:38:09AM +0000, Sheng Jiang wrote:
> >> Hi, all,
> >>
> >> Please find the below figure that I shared in the IDN discussion meeting last
> week in Prague. This illustrates the IDN architecture in a very generic way. The
> on-site participants had the very similar understanding that the upper left box -
> the unified and selected data is should be the prior work towards standardization.
> Also, the participants shared the same opinion that the data structure may be
> various among use cases. So, we should keep discussing on use cases with the
> target to converge on one or two significant and specific use cases.
> >> [cid:image001.png@01D30643.900DB7F0]
> >>
> >> Regards,
> >>
> >> Sheng
> >
> >
> >> _______________________________________________
> >> IDNET mailing list
> >> IDNET@ietf.org
> >> https://www.ietf.org/mailman/listinfo/idnet
> >
> 
> 
> _______________________________________________
> IDNET mailing list
> IDNET@ietf.org
> https://www.ietf.org/mailman/listinfo/idnet