Re: [Teas-ns-dt] FW: New Version Notification for draft-nsdt-teas-ns-framework-00.txt

"Dongjie (Jimmy)" <jie.dong@huawei.com> Mon, 09 March 2020 23:32 UTC

Return-Path: <jie.dong@huawei.com>
X-Original-To: teas-ns-dt@ietfa.amsl.com
Delivered-To: teas-ns-dt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF8CA3A0955 for <teas-ns-dt@ietfa.amsl.com>; Mon, 9 Mar 2020 16:32:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.331
X-Spam-Level:
X-Spam-Status: No, score=-1.331 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, INVALID_MSGID=0.568, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 MJVnxKtfCodn for <teas-ns-dt@ietfa.amsl.com>; Mon, 9 Mar 2020 16:32:52 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 C1F133A0967 for <teas-ns-dt@ietf.org>; Mon, 9 Mar 2020 16:32:51 -0700 (PDT)
Received: from lhreml701-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id EC5E66180A8CB803B825; Mon, 9 Mar 2020 23:32:49 +0000 (GMT)
Received: from dggeme753-chm.china.huawei.com (10.3.19.99) by lhreml701-cah.china.huawei.com (10.201.108.42) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 9 Mar 2020 23:32:49 +0000
Received: from dggeme704-chm.china.huawei.com (10.1.199.100) by dggeme753-chm.china.huawei.com (10.3.19.99) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Tue, 10 Mar 2020 07:32:47 +0800
Received: from dggeme704-chm.china.huawei.com ([10.9.48.231]) by dggeme704-chm.china.huawei.com ([10.9.48.231]) with mapi id 15.01.1713.004; Tue, 10 Mar 2020 07:32:47 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: Eric Gray <eric.gray=40ericsson.com@dmarc.ietf.org>, teas-ns-dt <teas-ns-dt@ietf.org>
CC: Jari Arkko <jari.arkko@ericsson.com>
Thread-Topic: [Teas-ns-dt] FW: New Version Notification for draft-nsdt-teas-ns-framework-00.txt
Thread-Index: AQHV9kce+Pzh3j1hykSbHiVqw6RUJKhAoc8AgABHt/Q=
Importance: high
X-Priority: 1
Date: Mon, 9 Mar 2020 23:32:46 +0000
Message-ID: D293874A-0FFF-4EFE-BD6F-C7039E2A1260
References: <158378133219.5451.853090851556831969@ietfa.amsl.com>, <BN8PR15MB264440412887E166A3E804FA97FE0@BN8PR15MB2644.namprd15.prod.outlook.com>
In-Reply-To: <BN8PR15MB264440412887E166A3E804FA97FE0@BN8PR15MB2644.namprd15.prod.outlook.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_D293874A0FFF4EFEBD6FC7039E2A1260_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas-ns-dt/1Wejk-4dw7ayYtHeI0fLZtbecgM>
Subject: Re: [Teas-ns-dt] FW: New Version Notification for draft-nsdt-teas-ns-framework-00.txt
X-BeenThere: teas-ns-dt@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: TEAS Network Slicing Design Team <teas-ns-dt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas-ns-dt>, <mailto:teas-ns-dt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas-ns-dt/>
List-Post: <mailto:teas-ns-dt@ietf.org>
List-Help: <mailto:teas-ns-dt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas-ns-dt>, <mailto:teas-ns-dt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Mar 2020 23:32:54 -0000

Hi Eric,


Thanks for the submission, while the current version does not reflect our discussion about authorship on the last conference call or previous meetings. On last call both Jari and I suggested that we add a section of the list of all the authors/contributors who made contribution to the text in the draft, but I see several names are missing here (at least myself, xufeng and Jari...). If the number of authors exceed the limit of front page,  the tradition is only the editors are shown on front page.

If we really want to respect all the contributions made, could you update and add these names to the draft? Thanks.


Best regards,

Jie








发件人:Eric Gray <eric.gray=40ericsson.com@dmarc.ietf.org>
收件人:teas-ns-dt <teas-ns-dt@ietf.org>
抄 送:Jari Arkko <jari.arkko@ericsson.com>
时 间:2020-03-10 03:17:50
主 题:[Teas-ns-dt] FW: New Version Notification for draft-nsdt-teas-ns-framework-00.txt



-----Original Message-----
From: internet-drafts@ietf.org <internet-drafts@ietf.org>
Sent: Monday, March 9, 2020 3:16 PM
To: John Drake <jdrake@juniper.net>et>; Dhruv Dhody <dhruv.ietf@gmail.com>om>; Reza Rokui <reza.rokui@nokia.com>om>; Eric Gray <eric.gray@ericsson.com>om>; Eric Gray <eric.gray@ericsson.com>
Subject: New Version Notification for draft-nsdt-teas-ns-framework-00.txt
Importance: High


A new version of I-D, draft-nsdt-teas-ns-framework-00.txt
has been successfully submitted by Eric Gray and posted to the IETF repository.

Name:           draft-nsdt-teas-ns-framework
Revision:       00
Title:          Framework for Transport Network Slices
Document date:  2020-03-09
Group:          Individual Submission
Pages:          17
URL:            https://www.ietf.org/internet-drafts/draft-nsdt-teas-ns-framework-00.txt
Status:         https://datatracker.ietf.org/doc/draft-nsdt-teas-ns-framework/
Htmlized:       https://tools.ietf.org/html/draft-nsdt-teas-ns-framework-00
Htmlized:       https://datatracker.ietf.org/doc/html/draft-nsdt-teas-ns-framework


Abstract:
   This memo discusses setting up special-purpose transport connections
   using existing IETF technologies.  These connections are called
   transport slices for the purposes of this memo.  The memo discusses
   the general framework for this setup, the necessary system components
   and interfaces, and how abstract requests can be mapped to more
   specific technologies.  The memo also discusses related
   considerations with monitoring and security.

   This memo is intended for discussing interfaces and technologies.  It
   is not intended to be a new set of concrete interfaces or
   technologies.  Rather, it should be seen as an explanation of how
   some existing, concrete IETF VPN and traffic-engineering technologies
   can be used to create transport slices.  Note that there are is a
   rather large of these technologies, and new technologies or
   capabilities keep being added.  This memo is also not intended
   presume any particular technology choice.




Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat


--
Teas-ns-dt mailing list
Teas-ns-dt@ietf.org
https://www.ietf.org/mailman/listinfo/teas-ns-dt