Re: [mpls] AD review of draft-ietf-mpls-tp-identifiers

George Swallow <swallow@cisco.com> Thu, 07 July 2011 19:15 UTC

Return-Path: <swallow@cisco.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBC6C1F0CD6 for <mpls@ietfa.amsl.com>; Thu, 7 Jul 2011 12:15:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.445
X-Spam-Level:
X-Spam-Status: No, score=-97.445 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DATE_IN_PAST_96_XX=1.69, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_NUMERIC_HELO=2.067, 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 gopn7HDE2D5Q for <mpls@ietfa.amsl.com>; Thu, 7 Jul 2011 12:15:57 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id E4D4F1F0CD4 for <mpls@ietf.org>; Thu, 7 Jul 2011 12:15:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=swallow@cisco.com; l=4934; q=dns/txt; s=iport; t=1310066157; x=1311275757; h=date:subject:from:to:cc:message-id:in-reply-to: mime-version; bh=IVZRFVWAu+qoJNR1tUgAhEBG4eGjeJLuVIvKQbnVauM=; b=MQemeV2eoRKEIhCqpZAVaaF2jkmctNSddQvn+apRtyGzlJkPVaHMJGmG BdiHf3uslmHag6WQOi7V1IsLZr/6ObeQQxbybW3VikvaVUAPbD7lCj0ia x/Z/QuStnuFA5WM6W3Om1pOgiAXmYppPO8WGc2sRBvyQWHjh/vC505gVS I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhEMAKUEFk6tJV2c/2dsb2JhbABTMIIhpABjAneIe6RanXCGOASSRoUGh0OEFA
X-IronPort-AV: E=Sophos;i="4.65,494,1304294400"; d="scan'208,217";a="783109"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-9.cisco.com with ESMTP; 07 Jul 2011 19:15:56 +0000
Received: from xbh-rcd-101.cisco.com (xbh-rcd-101.cisco.com [72.163.62.138]) by rcdn-core-5.cisco.com (8.14.3/8.14.3) with ESMTP id p67JFu1I007636; Thu, 7 Jul 2011 19:15:56 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); Thu, 7 Jul 2011 14:15:55 -0500
Received: from 161.44.113.58 ([161.44.113.58]) by XMB-RCD-106.cisco.com ([72.163.62.148]) with Microsoft Exchange Server HTTP-DAV ; Thu, 7 Jul 2011 19:15:56 +0000
User-Agent: Microsoft-Entourage/12.29.0.110113
Date: Fri, 01 Jul 2011 14:27:16 -0400
From: George Swallow <swallow@cisco.com>
To: Adrian Farrel <adrian@olddog.co.uk>, draft-ietf-mpls-tp-identifiers@tools.ietf.org
Message-ID: <CA3389C4.11107%swallow@cisco.com>
Thread-Topic: [mpls] AD review of draft-ietf-mpls-tp-identifiers
Thread-Index: Acw1Epl1e9a+4No9S6KI0ZM/JsUxMgDCed0t
In-Reply-To: <066b01cc3512$9f0721f0$dd1565d0$@olddog.co.uk>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3392896555_159740833"
X-OriginalArrivalTime: 07 Jul 2011 19:15:55.0869 (UTC) FILETIME=[4BC5C0D0:01CC3CDA]
Cc: mpls@ietf.org, mpls-chairs@tools.ietf.org
Subject: Re: [mpls] AD review of draft-ietf-mpls-tp-identifiers
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 07 Jul 2011 19:15:58 -0000

Adrian -


On 6/27/11 5:38 PM, "Adrian Farrel" <adrian@olddog.co.uk> wrote:

> Hi,
> 
> I have done my AD review of this document. In view of the fact that my
> comments
> are quite small, could you please handle them as part of the IETF last call
> which I will start forthwith.
> 
> Thanks,
> Adrian
> 
> ---
>   
> You seem to be missing a section on MEP_IDs for MPLS_TP Sections.
> Insert before 7.2.1?
> 
Added the following section:

7.2.1.  MPLS-TP Section MEP_IDs

   IP compatible MEP_IDs for MPLS-TP are simply the IF_IDs of each end
   of the section.  For example, for a section whose MEG_ID is

      A1-IF_ID::Z9-IF_ID

   the Section MEP_ID at A1 would be

      A1-IF_ID

   and the Section MEP_ID at Z9 would be

      Z9-IF_ID.

   Where the Section MEP_ID needs to be globally unique, this is
   accomplished by using globally unique Node_IDs as defined above.
   Thus a globally unique Section MEP_ID becomes

      Global_ID::IF_ID.

> 
> ---
> 
> Nits
> 
> 1.3
> 
> OLD
> The notation does define a preferred ordering of the fields.
> NEW
> The notation defines a preferred ordering of the fields.
> END
> 
Done.
> 
> OLD
>  Z9 is used to indicated the
> NEW
>  Z9 is used to indicate the
> END
> 
Done.

...George
> 
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>