Re: Working Group Last Call on draft-ietf-ccamp-gmpls-addressing-06.txt
"Adrian Farrel" <adrian@olddog.co.uk> Thu, 26 April 2007 16:33 UTC
Return-path: <owner-ccamp@ops.ietf.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hh6uQ-0001Ys-Pb for ccamp-archive@ietf.org; Thu, 26 Apr 2007 12:33:30 -0400
Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hh6uN-0002Ou-M7 for ccamp-archive@ietf.org; Thu, 26 Apr 2007 12:33:30 -0400
Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD)) (envelope-from <owner-ccamp@ops.ietf.org>) id 1Hh6nZ-000EfA-Qm for ccamp-data@psg.com; Thu, 26 Apr 2007 16:26:25 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com
X-Spam-Level:
X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00, FORGED_RCVD_HELO autolearn=ham version=3.1.7
Received: from [212.23.8.67] (helo=fizeau.zen.co.uk) by psg.com with esmtp (Exim 4.63 (FreeBSD)) (envelope-from <adrian@olddog.co.uk>) id 1Hh6nV-000Eeq-Qw for ccamp@ops.ietf.org; Thu, 26 Apr 2007 16:26:24 +0000
Received: from [212.23.3.140] (helo=pythagoras.zen.co.uk) by fizeau.zen.co.uk with esmtp (Exim 4.50) id 1Hh6nU-0003B6-SJ for ccamp@ops.ietf.org; Thu, 26 Apr 2007 16:26:20 +0000
Received: from [88.96.235.142] (helo=cortex.aria-networks.com) by pythagoras.zen.co.uk with esmtp (Exim 4.50) id 1Hh6nT-0007hg-CR for ccamp@ops.ietf.org; Thu, 26 Apr 2007 16:26:19 +0000
Received: from your029b8cecfe ([217.158.132.42] RDNS failed) by cortex.aria-networks.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 26 Apr 2007 17:26:17 +0100
Message-ID: <125a01c7881f$98485770$6f849ed9@your029b8cecfe>
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
From: Adrian Farrel <adrian@olddog.co.uk>
To: MEURIC Julien RD-CORE-LAN <julien.meuric@orange-ftgroup.com>, ccamp@ops.ietf.org
References: <E1HeGAE-0002ES-HN@stiedprstage1.ietf.org> <099001c784f7$696d2e60$6f849ed9@your029b8cecfe> <7DBAFEC6A76F3E42817DF1EBE64CB026047FC600@FTRDMEL2.rd.francetelecom.fr>
Subject: Re: Working Group Last Call on draft-ietf-ccamp-gmpls-addressing-06.txt
Date: Thu, 26 Apr 2007 17:25:58 +0100
Organization: Old Dog Consulting
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="original"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-OriginalArrivalTime: 26 Apr 2007 16:26:18.0263 (UTC) FILETIME=[9E2F9270:01C7881F]
X-Originating-Pythagoras-IP: [88.96.235.142]
Sender: owner-ccamp@ops.ietf.org
Precedence: bulk
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Good comments. Thanks. > In the abstract and the introduction, the phrase "facilitate > better interworking" reads weird to me. I'm not a native > English speaker, but wouldn't "facilitate interworking" be > more appropriate? OK > About the IGP terminology, in OSPF and IS-IS RFCs, > "OSPF-TE" and "IS-IS-TE" terms are reserved for > MPLS-TE extensions (RFC 3630 and 3784) while > GMPLS ones (RFC 4203 and 4205) are rather named > "GMPLS OSPF" and "GMPLS IS-IS". I believe the ID > should follow this terminology more closely. No objection. > In section 5.1.1: > "An unnumbered TE > link end network-wide identifier is comprised of a TE Router ID > associated with the link local end, followed by the link local > identifier" > > The intent on (TE Router ID, link local ID) is clear to anyone > familiar with the context, but I also feel -- due to my mother > tongue? -- that this might also be misread as (TE Router ID, > link local end, link local ID), which does not make any sense. > However, considering this is a clarification document, maybe > replacing "associated with" by "corresponding to" or just > recalling it's a pair would do the trick. Try... An unnumbered TE link end network-wide identifier is comprised of two elements: - a TE Router ID that is associated with the link local end - the link local identifier. > In section 6.1.2: > "If the interface was intended to be used as an outgoing > interface, the path will be broken an may be impossible to > resolve." > > s/an/and/ OK > "The path will be broken" looks like a postulate and needs a > clarification. Yes, the sentence and the path are broken :-) Try... If the interface was intended to be used as an outgoing interface, the computed path may be unsatisfactory and the explicit route in the ERO may be impossible to resolve. >"This a loose hop that identifies an interface should always > identify the incoming TE link in the data plane." > > Something's missing or "This" should be removed. s/This/Thus,/ Cheers, Adrian
- I-D ACTION:draft-ietf-ccamp-gmpls-addressing-06.t… Internet-Drafts
- Working Group Last Call on draft-ietf-ccamp-gmpls… Adrian Farrel
- RE: Working Group Last Call on draft-ietf-ccamp-g… MEURIC Julien RD-CORE-LAN
- Re: Working Group Last Call on draft-ietf-ccamp-g… Adrian Farrel
- Re: Working Group Last Call on draft-ietf-ccamp-g… Adrian Farrel