Re: [mpls] "opertor" in draft-ietf-mpls-tp-psc-itu
"Ryoo, Jeong-dong" <ryoo@etri.re.kr> Mon, 02 December 2013 01:42 UTC
Return-Path: <ryoo@etri.re.kr>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEF791ADF72 for <mpls@ietfa.amsl.com>; Sun, 1 Dec 2013 17:42:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.901
X-Spam-Level:
X-Spam-Status: No, score=-101.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 EWsYnPrj9J2H for <mpls@ietfa.amsl.com>; Sun, 1 Dec 2013 17:42:20 -0800 (PST)
Received: from smtpeg.etri.re.kr (smtpeg2.etri.re.kr [129.254.27.142]) by ietfa.amsl.com (Postfix) with ESMTP id 5D3781ADF60 for <mpls@ietf.org>; Sun, 1 Dec 2013 17:42:20 -0800 (PST)
Received: from SMTP3.etri.info (129.254.28.73) by SMTPEG2.etri.info (129.254.27.142) with Microsoft SMTP Server (TLS) id 14.1.355.2; Mon, 2 Dec 2013 10:42:13 +0900
Received: from SMTP2.etri.info ([169.254.2.161]) by SMTP3.etri.info ([169.254.157.203]) with mapi id 14.01.0355.002; Mon, 2 Dec 2013 10:42:07 +0900
From: "Ryoo, Jeong-dong" <ryoo@etri.re.kr>
To: Loa Andersson <loa@pi.nu>, "mpls@ietf.org" <mpls@ietf.org>, "draft-ietf-mpls-tp-psc-itu@tools.ietf.org" <draft-ietf-mpls-tp-psc-itu@tools.ietf.org>, "mpls-chairs@tools.ietf.org" <mpls-chairs@tools.ietf.org>
Thread-Topic: [mpls] "opertor" in draft-ietf-mpls-tp-psc-itu
Thread-Index: AQHO7MG5MoNo5Ie5+EqGd7NBQarCh5pAI/6+
Date: Mon, 02 Dec 2013 01:42:06 +0000
Message-ID: <5B4A6CBE3924BB41A3BEE462A8E0B75A286AB368@SMTP2.etri.info>
References: <52982260.2020304@pi.nu>
In-Reply-To: <52982260.2020304@pi.nu>
Accept-Language: ko-KR, en-US
Content-Language: ko-KR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-new-displayname: UnlvbywgSmVvbmctZG9uZw==
x-originating-ip: [129.254.28.46]
Content-Type: multipart/alternative; boundary="_000_5B4A6CBE3924BB41A3BEE462A8E0B75A286AB368SMTP2etriinfo_"
MIME-Version: 1.0
Subject: Re: [mpls] "opertor" in draft-ietf-mpls-tp-psc-itu
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Dec 2013 01:42:24 -0000
Loa, thanks for the comments, While I agree with your points, I don't think this document defines the network operation procedures for MPLS-TP networks. Therefore, I would like to propose to change the last sentence of your suggested new text as follows: "For transport network operators accustomed to the operational procedures for Optical and Ethernet transport networks this document defines the protocol operations and mechanisms that result in the same network operation procedures for MPLS-TP networks." The other sentences are ok with me. Best regards, Jeong-dong ________________________________ From : "Loa Andersson" <loa@pi.nu> Sent : 2013-11-29 14:13:21 ( +09:00 ) To : mpls@ietf.org <mpls@ietf.org>, draft-ietf-mpls-tp-psc-itu@tools.ietf.org <draft-ietf-mpls-tp-psc-itu@tools.ietf.org>, mpls-chairs@tools.ietf.org <mpls-chairs@tools.ietf.org> Cc : Subject : [mpls] "opertor" in draft-ietf-mpls-tp-psc-itu Authors/Editors, Section 4.1 of draft-ietf-mpls-tp-psc-itu-00 uses the term "network operator" in a way that makes the reader think that this is true for every network operator. "..., for network operators it is important that the MPLS-TP protection switching preserves the network operation behavior to which network operators have become accustomed." Admittedly "transport network operators" are a sufficiently large group, but far from the only once that think of themselves as "network operators", likely the majority of "network operators" are not for their operational activities interested or even aware of the commands described in this document. My experience is also that the IETF should not tell "network operators" what is important for them. Suggested new text (from the beginning of the paragraph): "Transport network operators run networks based on different technologies, e.g. optical transport networks, Etherent transport networks and MPLS-TP networks. Commonality between operational procedures are important. For transport network operators accustomed to the operational procedures for Optical and Ethernet transport networks this document defines the same procedures for MPLS-TP networks." /Loa -- Loa Andersson email: loa@mail01.huawei.com Senior MPLS Expert loa@pi.nu Huawei Technologies (consultant) phone: +46 739 81 21 64 _______________________________________________ mpls mailing list mpls@ietf.org https://www.ietf.org/mailman/listinfo/mpls
- [mpls] "opertor" in draft-ietf-mpls-tp-psc-itu Loa Andersson
- Re: [mpls] "opertor" in draft-ietf-mpls-tp-psc-itu Ryoo, Jeong-dong
- Re: [mpls] "opertor" in draft-ietf-mpls-tp-psc-itu Loa Andersson
- Re: [mpls] "opertor" in draft-ietf-mpls-tp-psc-itu Ryoo, Jeong-dong