Re: [Idnet] Architecture and standard opportunities of IDN

Jérôme François <jerome.francois@inria.fr> Tue, 01 August 2017 16:28 UTC

Return-Path: <jerome.francois@inria.fr>
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 9AA6F131E9F for <idnet@ietfa.amsl.com>; Tue, 1 Aug 2017 09:28:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.921
X-Spam-Level:
X-Spam-Status: No, score=-6.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-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 IqOIor_7tqw3 for <idnet@ietfa.amsl.com>; Tue, 1 Aug 2017 09:28:04 -0700 (PDT)
Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) (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 BB524131E96 for <idnet@ietf.org>; Tue, 1 Aug 2017 09:28:03 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.41,306,1498514400"; d="scan'208";a="233428808"
Received: from static-176-183-206-74.ncc.abo.bbox.fr (HELO [192.168.1.27]) ([176.183.206.74]) by mail3-relais-sop.national.inria.fr with ESMTP/TLS/DHE-RSA-AES128-SHA; 01 Aug 2017 18:28:01 +0200
To: yanshen <yanshen@huawei.com>
References: <5D36713D8A4E7348A7E10DF7437A4B927CE3A673@NKGEML515-MBX.china.huawei.com> <20170727004512.GC18300@spectre> <ae317d90-f98f-acd3-00d7-463ff3a97782@inria.fr> <6AE399511121AB42A34ACEF7BF25B4D2979B8A@DGGEMM505-MBS.china.huawei.com>
Cc: "idnet@ietf.org" <idnet@ietf.org>
From: =?UTF-8?B?SsOpcsO0bWUgRnJhbsOnb2lz?= <jerome.francois@inria.fr>
Message-ID: <8ad08c34-2808-0341-8d6a-982c9f02ef17@inria.fr>
Date: Tue, 1 Aug 2017 18:28:00 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <6AE399511121AB42A34ACEF7BF25B4D2979B8A@DGGEMM505-MBS.china.huawei.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/idnet/-XZ8fQirgXUWqzqETXhbU0kms8Q>
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: Tue, 01 Aug 2017 16:28:06 -0000

Hi,

Le 31/07/2017 à 14:25, yanshen a écrit :
>> 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".
>
>>
So, listing "all" (the most used) data format (attributes and encoding)
should be a starting point

jerome