Re: [CCAMP] [Technical Errata Reported] RFC4427 (1835)

Vishwas Manral <vishwas.ietf@gmail.com> Fri, 21 August 2009 22:25 UTC

Return-Path: <vishwas.ietf@gmail.com>
X-Original-To: ccamp@core3.amsl.com
Delivered-To: ccamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 12A213A69EA for <ccamp@core3.amsl.com>; Fri, 21 Aug 2009 15:25:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.484
X-Spam-Level:
X-Spam-Status: No, score=-2.484 tagged_above=-999 required=5 tests=[AWL=0.115, BAYES_00=-2.599]
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 Yt7eKqd8Js+G for <ccamp@core3.amsl.com>; Fri, 21 Aug 2009 15:25:15 -0700 (PDT)
Received: from mail-gx0-f217.google.com (mail-gx0-f217.google.com [209.85.217.217]) by core3.amsl.com (Postfix) with ESMTP id C66B03A6977 for <ccamp@ietf.org>; Fri, 21 Aug 2009 15:25:12 -0700 (PDT)
Received: by gxk17 with SMTP id 17so1453059gxk.19 for <ccamp@ietf.org>; Fri, 21 Aug 2009 15:25:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=Oc16dwbaCI5JwYHAtbJMTTcbyfG2U4wZ8fi3h3kQkTg=; b=no6hbVn1KrX/iVQtSeclPV3X8xcXBN430zP4iQBv/90Z4tpcrDcyaewV3CY4l91ZRl gn+pQFlXPAA5v2QvNqqOBcrlv67bMTZe0mE5ihxqJTYIM5UfqUQyb33QYzhbecVWQ+ho sqSwA805fGm5diT9fDi+o/PZR4AHGxRTkB7Yw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=D7IyQX4Q1bGozl2rXaYeF6ufCH2xL25tWO5zyq2is8wiO+EEcQ8hVhElSOxGtueyZ3 vVevZMEGISV8u7ZPuhGyX7WI/kmc4UKXZ20FVTGks+poUG5AABTVq0MIgbWEUBjqj+gH 2gUt+kif0kwCEZKIRMRJMertK3JWgMMsWEJAs=
MIME-Version: 1.0
Received: by 10.150.237.3 with SMTP id k3mr3244322ybh.70.1250893515549; Fri, 21 Aug 2009 15:25:15 -0700 (PDT)
In-Reply-To: <C0AC8FAB6849AB4FADACCC70A949E2F19058B1F1@EUSAACMS0701.eamcs.ericsson.se>
References: <200908202302.n7KN2xcC002305@boreas.isi.edu> <C0AC8FAB6849AB4FADACCC70A949E2F19055D84F@EUSAACMS0701.eamcs.ericsson.se> <77ead0ec0908210758v15c6828bsbfda4e6bec5c8d89@mail.gmail.com> <C0AC8FAB6849AB4FADACCC70A949E2F19058B1F1@EUSAACMS0701.eamcs.ericsson.se>
Date: Fri, 21 Aug 2009 15:25:15 -0700
Message-ID: <77ead0ec0908211525w7bbd0c09tdc5a3b20d9398300@mail.gmail.com>
From: Vishwas Manral <vishwas.ietf@gmail.com>
To: Eric Gray <eric.gray@ericsson.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: "ccamp@ietf.org" <ccamp@ietf.org>, "dimitri.papadimitriou@alcatel.be" <dimitri.papadimitriou@alcatel.be>, "adrian.farrel@huawei.com" <adrian.farrel@huawei.com>, "rcallon@juniper.net" <rcallon@juniper.net>, "eric.mannie@perceval.net" <eric.mannie@perceval.net>, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [CCAMP] [Technical Errata Reported] RFC4427 (1835)
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Aug 2009 22:25:16 -0000

Hi Eric,

Thats correct. I am ok with the suggestions you mention (which is what
I am saying too).

Thanks,
Vishwas

On Fri, Aug 21, 2009 at 2:36 PM, Eric Gray<eric.gray@ericsson.com> wrote:
> Vishwas,
>
>        The errata system is somewhat erratic.  Changes that are not
> absolutely necessary tend to discredit/devalue the utility of the
> (already easy to ignore) errata process.
>
>        If we had to make a change (to clarify what is understandably
> not very clear) it would be better to reduce the redundancy.  I'd
> offer as a possibly better "fix" -
>
>        Replace "(M, N > 1, N >= M)" with "(N >= M > 1)"
>
> - which is what I think you're now suggesting as well.
>
>        But that brings us back to the point - is this change really
> necessary at all?
>
> --
> Eric
>
> -----Original Message-----
> From: Vishwas Manral [mailto:vishwas.ietf@gmail.com]
> Sent: Friday, August 21, 2009 10:59 AM
> To: Eric Gray
> Cc: RFC Errata System; eric.mannie@perceval.net; dimitri.papadimitriou@alcatel.be; rcallon@juniper.net; adrian.farrel@huawei.com; lberger@labn.net; dbrungard@att.com; ccamp@ietf.org
> Subject: Re: [CCAMP] [Technical Errata Reported] RFC4427 (1835)
> Importance: High
>
> Hi Eric,
>
> Now I see it that way. However I got confused as "," is a seperator
> both for multiple conditions as well as multiple elements in a
> condition.
>
> The best way would be to put it would be only one condition (same for
> the other Errata):
>
> N >= M > 1.
>
> Thanks,
> Vishwas
>
> On Fri, Aug 21, 2009 at 5:43 AM, Eric Gray<eric.gray@ericsson.com> wrote:
>> In this case, the additional "M > 1" is redundant, since the parenthesized
>> statement starts by stating that _both_ M and N are reater than 1 - i.e. -
>> "M, N > 1" equates to "M > 1, N > 1"
>>
>> The text referred to is correct as is.
>>
>> --
>> Eric
>>
>> -----Original Message-----
>> From: ccamp-bounces@ietf.org [mailto:ccamp-bounces@ietf.org] On Behalf Of RFC Errata System
>> Sent: Thursday, August 20, 2009 7:03 PM
>> To: eric.mannie@perceval.net; dimitri.papadimitriou@alcatel.be; rcallon@juniper.net; adrian.farrel@huawei.com; lberger@labn.net; dbrungard@att.com
>> Cc: ccamp@ietf.org; rfc-editor@rfc-editor.org
>> Subject: [CCAMP] [Technical Errata Reported] RFC4427 (1835)
>>
>>
>> The following errata report has been submitted for RFC4427,
>> "Recovery (Protection and Restoration) Terminology for Generalized Multi-Protocol Label Switching (GMPLS)".
>>
>> --------------------------------------
>> You may review the report below and at:
>> http://www.rfc-editor.org/errata_search.php?rfc=4427&eid=1835
>>
>> --------------------------------------
>> Type: Technical
>> Reported by: Vishwas Manral <vishwas.ietf@gmail.com>
>>
>> Section: 6.3
>>
>> Original Text
>> -------------
>> 6.3. M:N (M, N > 1, N >= M) Protection
>>
>>
>>   M:N protection has N working LSPs/spans carrying normal traffic and M
>>   protection LSP/span that may carry extra-traffic.
>>
>> Corrected Text
>> --------------
>> 6.3. M:N (M, N > 1, N >= M > 1) Protection
>>
>>
>>   M:N protection has N working LSPs/spans carrying normal traffic and M
>>   protection LSP/span that may carry extra-traffic.
>>
>> Notes
>> -----
>> M > 1 is added
>>
>> Instructions:
>> -------------
>> This errata is currently posted as "Reported". If necessary, please
>> use "Reply All" to discuss whether it should be verified or
>> rejected. When a decision is reached, the verifying party (IESG)
>> can log in to change the status and edit the report, if necessary.
>>
>> --------------------------------------
>> RFC4427 (draft-ietf-ccamp-gmpls-recovery-terminology-06)
>> --------------------------------------
>> Title               : Recovery (Protection and Restoration) Terminology for Generalized Multi-Protocol Label Switching (GMPLS)
>> Publication Date    : March 2006
>> Author(s)           : E. Mannie, Ed., D. Papadimitriou, Ed.
>> Category            : INFORMATIONAL
>> Source              : Common Control and Measurement Plane
>> Area                : Routing
>> Stream              : IETF
>> Verifying Party     : IESG
>> _______________________________________________
>> CCAMP mailing list
>> CCAMP@ietf.org
>> https://www.ietf.org/mailman/listinfo/ccamp
>> _______________________________________________
>> CCAMP mailing list
>> CCAMP@ietf.org
>> https://www.ietf.org/mailman/listinfo/ccamp
>>
>