Re: R: [mpls] Last Call: <draft-ietf-mpls-tp-identifiers-06.txt> (MPLS-TP Identifiers) to Proposed Standard

George Swallow <swallow@cisco.com> Fri, 08 July 2011 13:39 UTC

Return-Path: <swallow@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A059F21F8A9D; Fri, 8 Jul 2011 06:39:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.901
X-Spam-Level:
X-Spam-Status: No, score=-104.901 tagged_above=-999 required=5 tests=[AWL=-2.301, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5sg7HY5rTjS2; Fri, 8 Jul 2011 06:39:48 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id A114721F86D6; Fri, 8 Jul 2011 06:39:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=swallow@cisco.com; l=4678; q=dns/txt; s=iport; t=1310132388; x=1311341988; h=date:subject:from:to:cc:message-id:in-reply-to: mime-version:content-transfer-encoding; bh=OUwE7mFBnkEf9TjCfHl/rZzCLnlztl7CAqGYuq5JNkQ=; b=UIxNjv8jKy4YS89Sw29wXknLdYIXF6IfyustRYdJXgGshgv2G8lH9f5x QcsHAh1hfvuwsWGKbUNE2ZeCuiGINQW8t21s0uXv7NZv+oU1mhiIXcom9 +t3SHXCIfQxA1kdj7tPyok0Ri9OPJ26h6WML5kBEVmgcgVUIOdgKdIM2p s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAKkHF06tJXG8/2dsb2JhbABMBqdFd4h7pHCdfgKDOoJ8BIcdiy+FBota
X-IronPort-AV: E=Sophos;i="4.65,499,1304294400"; d="scan'208";a="1042446"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-3.cisco.com with ESMTP; 08 Jul 2011 13:39:48 +0000
Received: from xbh-rcd-101.cisco.com (xbh-rcd-101.cisco.com [72.163.62.138]) by rcdn-core2-1.cisco.com (8.14.3/8.14.3) with ESMTP id p68DdlSB007050; Fri, 8 Jul 2011 13:39:48 GMT
Received: from xmb-rcd-106.cisco.com ([72.163.62.148]) by xbh-rcd-101.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 8 Jul 2011 08:39:47 -0500
Received: from 10.86.244.217 ([10.86.244.217]) by XMB-RCD-106.cisco.com ([72.163.62.148]) with Microsoft Exchange Server HTTP-DAV ; Fri, 8 Jul 2011 13:39:47 +0000
User-Agent: Microsoft-Entourage/12.29.0.110113
Date: Fri, 08 Jul 2011 09:39:46 -0400
Subject: Re: R: [mpls] Last Call: <draft-ietf-mpls-tp-identifiers-06.txt> (MPLS-TP Identifiers) to Proposed Standard
From: George Swallow <swallow@cisco.com>
To: D'Alessandro Alessandro Gerardo <alessandro.dalessandro@telecomitalia.it>, "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <CA3C80E2.11826%swallow@cisco.com>
Thread-Topic: R: [mpls] Last Call: <draft-ietf-mpls-tp-identifiers-06.txt> (MPLS-TP Identifiers) to Proposed Standard
Thread-Index: Acw1F+fy2cc2fqAsQjWUdW71y7nF9QGmM/rQAHDyCYo=
In-Reply-To: <A1F769BC58A8B146B2EEA818EAE052A2096B4DAB82@GRFMBX702RM001.griffon.local>
Mime-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
X-OriginalArrivalTime: 08 Jul 2011 13:39:47.0561 (UTC) FILETIME=[80EFED90:01CC3D74]
Cc: "mpls@ietf.org" <mpls@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jul 2011 13:39:49 -0000

Alessandro -

Thanks for the comments.  Will incorporate in next rev.

...George


On 7/6/11 4:16 AM, "D'Alessandro Alessandro Gerardo"
<alessandro.dalessandro@telecomitalia.it> wrote:

> Dear all,
> I have the following comments:
> 
> Sect 7: " A maintenance point is either a Maintenance
> Entity Group End-point (MEP) or a Maintenance Entity Group
> Intermediate Point (MIP). Maintenance points are uniquely associated
> with a MEG."
>> This is true for MEP. MIP, as currently defined, are not uniquely associated
>> with a MEG.
> 
> Sec 7.4 " At a cross-connect point, in order to automatically generate MIP_IDs
> for MPLS-TP, we simply use the IF_IDs of the two interfaces which are
> cross-connected"
>> the above given definition refers to "intermediate node". It should be
>> extended to cover also the case of "end nodes" because MIPs could be located
>> in such nodes when per-interface MEPs model is applied (e.g.
>> draft-ietf-mpls-tp-oam-framework and Yoshinori's contributions)
>> a reference to sect 4, where IF_ID are defined, should be added
> 
> Best regards,
> Alessandro
> ------------------------------------------------------------------
> Telecom Italia
> Alessandro D'Alessandro
> Transport Innovation
> Via Reiss Romoli, 274 - 10148 Torino
> phone:  +39 011 228 5887
> mobile: +39 335 766 9607
> fax: +39 06 418 639 07
> 
> 
> -----Messaggio originale-----
> Da: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] Per conto di The IESG
> Inviato: martedì 28 giugno 2011 00:16
> A: IETF-Announce
> Cc: mpls@ietf.org
> Oggetto: [mpls] Last Call: <draft-ietf-mpls-tp-identifiers-06.txt> (MPLS-TP
> Identifiers) to Proposed Standard
> 
> 
> The IESG has received a request from the Multiprotocol Label Switching WG
> (mpls) to consider the following document:
> - 'MPLS-TP Identifiers'
>   <draft-ietf-mpls-tp-identifiers-06.txt> as a Proposed Standard
> 
> The IESG plans to make a decision in the next few weeks, and solicits final
> comments on this action. Please send substantive comments to the ietf@ietf.org
> mailing lists by 2011-07-11. Exceptionally, comments may be sent to
> iesg@ietf.org instead. In either case, please retain the beginning of the
> Subject line to allow automated sorting.
> 
> Abstract
> 
>    This document specifies an initial set of identifiers to be used in
>    the Transport Profile of Multiprotocol Label Switching (MPLS-TP).
>    The MPLS-TP requirements (RFC 5654) require that the elements and
>    objects in an MPLS-TP environment are able to be configured and
>    managed without a control plane.  In such an environment many
>    conventions for defining identifiers are possible.  This document
>    defines identifiers for MPLS-TP management and OAM functions suitable
>    to IP/MPLS conventions.
> 
>    This document is a product of a joint Internet Engineering Task Force
>    (IETF) / International Telecommunication Union Telecommunication
>    Standardization Sector (ITU-T) effort to include an MPLS Transport
>    Profile within the IETF MPLS and Pseudowire Emulation Edge-to-Edge
>    (PWE3) architectures to support the capabilities and functionalities
>    of a packet transport network as defined by the ITU-T.
> 
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-identifiers/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-identifiers/
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> 
> 
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> 
> Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle
> persone indicate. La diffusione, copia o qualsiasi altra azione derivante
> dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora
> abbiate ricevuto questo documento per errore siete cortesemente pregati di
> darne immediata comunicazione al mittente e di provvedere alla sua
> distruzione, Grazie.
> 
> This e-mail and any attachments is confidential and may contain privileged
> information intended for the addressee(s) only. Dissemination, copying,
> printing or use by anybody else is unauthorised. If you are not the intended
> recipient, please delete this message and any attachments and advise the
> sender by return e-mail, Thanks.
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf