[mpls-tp] Use of term "interface" in MPLS-TP Identifiers and OAM Framework drafts
"BUSI, ITALO (ITALO)" <italo.busi@alcatel-lucent.com> Fri, 10 December 2010 08:58 UTC
Return-Path: <italo.busi@alcatel-lucent.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix)
with ESMTP id 777963A6C6E; Fri, 10 Dec 2010 00:58:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.703
X-Spam-Level:
X-Spam-Status: No, score=-5.703 tagged_above=-999 required=5 tests=[AWL=0.545,
BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com
[127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bu++t7xs8+SU;
Fri, 10 Dec 2010 00:58:41 -0800 (PST)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by
core3.amsl.com (Postfix) with ESMTP id 665443A6A96;
Fri, 10 Dec 2010 00:58:40 -0800 (PST)
Received: from FRMRSSXCHHUB04.dc-m.alcatel-lucent.com
(FRMRSSXCHHUB04.dc-m.alcatel-lucent.com [135.120.45.64]) by smail2.alcatel.fr
(8.14.3/8.14.3/ICT) with ESMTP id oBA9086F017041 (version=TLSv1/SSLv3
cipher=RC4-MD5 bits=128 verify=NOT); Fri, 10 Dec 2010 10:00:10 +0100
Received: from FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com ([135.120.45.43]) by
FRMRSSXCHHUB04.dc-m.alcatel-lucent.com ([135.120.45.64]) with mapi;
Fri, 10 Dec 2010 10:00:08 +0100
From: "BUSI, ITALO (ITALO)" <italo.busi@alcatel-lucent.com>
To: "mpls-tp@ietf.org" <mpls-tp@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>
Date: Fri, 10 Dec 2010 10:00:07 +0100
Thread-Topic: Use of term "interface" in MPLS-TP Identifiers and OAM Framework
drafts
Thread-Index: AcuYCIjDZUn6b3RvQm2LucvRj/p3XAAPYRew
Message-ID: <15740615FC9674499FBCE797B011623F16CD17E1@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com>
References: <AANLkTikBNsFZ=g-rQdPu9avPAoUdsNaiD==dxoRC6fq7@mail.gmail.com>
In-Reply-To: <AANLkTikBNsFZ=g-rQdPu9avPAoUdsNaiD==dxoRC6fq7@mail.gmail.com>
Accept-Language: it-IT, en-US
Content-Language: it-IT
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: it-IT, en-US
Content-Type: multipart/alternative;
boundary="_000_15740615FC9674499FBCE797B011623F16CD17E1FRMRSSXCHMBSB1d_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.80
Subject: [mpls-tp] Use of term "interface" in MPLS-TP Identifiers and OAM
Framework drafts
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>,
<mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>,
<mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Dec 2010 08:58:45 -0000
I see a lot of comments related to the term "interface" used within the OAM Framework draft in the context of the per-interface MIP definition and NO comments on the same term used within the Identifiers draft. I would like to clarify that the same term "interface" actually represents the same concept in both the MPLS-TP Identifiers and MPLS-TP OAM Framework drafts. I would therefore propose that the following definition is added to both drafts: " Interface: An interface is the attachment point to a server (sub-)layer e.g., MPLS-TP section or MPLS-TP tunnel. " This definition is taken from the text in section 4 of the Identifiers draft with the following proposed changes: 1) c/Access Point (AP)/attachment point/ as proposed by ITU-T 2) c/layer/(sub-)layer/ to align the definition with the outcome of past discussion: label stacking is a form of sub-layering with the MPLS and MPLS-TP layer network. I have a strong opinion that both the MPLS-TP Identifiers and the MPLS-TP OAM Framework must use the same term (and definition) to identify the same entity. I have a preference to keep the term "interface" on both drafts to speed up the work. Italo
- [mpls-tp] Looking for alternative term for per-in… Greg Mirsky
- [mpls-tp] 答复: Looking for alternative term for pe… wei.hongbo
- Re: [mpls-tp] 答复: Looking for alternative term fo… Alexander Vainshtein
- Re: [mpls-tp] Looking for alternative term for pe… wei.hongbo
- [mpls-tp] Use of term "interface" in MPLS-TP Iden… BUSI, ITALO (ITALO)
- Re: [mpls-tp] Use of term "interface" in MPLS-TP … Alexander Vainshtein
- [mpls-tp] R: Use of term "interface" in MPLS-TP I… BUSI, ITALO (ITALO)
- Re: [mpls-tp] [mpls] R: Use of term "interface" i… Adrian Farrel
- [mpls-tp] RE: 答复: Looking for alternative term fo… maarten vissers
- Re: [mpls-tp] [mpls] R: Use of term "interface" i… Alexander Vainshtein
- Re: [mpls-tp] [mpls] R: Use of term "interface" i… Greg Mirsky
- Re: [mpls-tp] [mpls] R: Use of term "interface" i… Adrian Farrel