Re: [mpls] to be rejected - Re: [Technical Errata Reported] RFC5586 (4364)

Loa Andersson <loa@pi.nu> Wed, 13 May 2015 15:43 UTC

Return-Path: <loa@pi.nu>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC2021B2FCC for <mpls@ietfa.amsl.com>; Wed, 13 May 2015 08:43:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.483
X-Spam-Level:
X-Spam-Status: No, score=0.483 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, TVD_PH_BODY_ACCOUNTS_PRE=2.393, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ydIcxje7l1qE for <mpls@ietfa.amsl.com>; Wed, 13 May 2015 08:43:21 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5EC8A1B2FCA for <mpls@ietf.org>; Wed, 13 May 2015 08:43:21 -0700 (PDT)
Received: from [192.168.0.101] (81-236-221-144-no93.tbcn.telia.com [81.236.221.144]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id ACAAF1800A76; Wed, 13 May 2015 17:43:19 +0200 (CEST)
Message-ID: <55537115.60002@pi.nu>
Date: Wed, 13 May 2015 17:43:17 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>, "BRUNGARD, DEBORAH A" <db3546@att.com>
References: <20150512141406.79F8E180092@rfc-editor.org> <5552F63E.9030806@pi.nu> <F64C10EAA68C8044B33656FA214632C83B5902B1@MISOUT7MSGUSRDE.ITServices.sbc.com> <AM3PR03MB077574B42B306094C97318399DD90@AM3PR03MB0775.eurprd03.prod.outlook.com>
In-Reply-To: <AM3PR03MB077574B42B306094C97318399DD90@AM3PR03MB0775.eurprd03.prod.outlook.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/2p-EfhO58TWXxb9Nwmy8w1M4mvk>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "rcallon@juniper.net" <rcallon@juniper.net>
Subject: Re: [mpls] to be rejected - Re: [Technical Errata Reported] RFC5586 (4364)
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 13 May 2015 15:43:24 -0000

Sasha,

I think the rationale is that the wg chairs don't see this as an
errata, but rather as a change.

Not being an errata, it seems odd to use the errata system to maintain a
non-errata.

/Loa

On 2015-05-13 14:14, Alexander Vainshtein wrote:
> Deborah, Loa and all,
> I accept the decision to reject the errata, of course.
>
> Revisiting this issue if/when the document is updated is OK with me, even if must admit that  I do not understand the difference between this and the disposition of errata that says "take into account when the document is updated" (or something like this).
>
> I would just like to clarify that my interest in the issue was triggered by a question I've received from the field, when a person examining some capture as asked me:
> "Why is the TTL in the LSE containing GAL set to 2" Is this standard?"
>
> I have looked up RFC 5586, and I did not find a straightforward answer to this question.
>
> Regards,
> Sasha
>
> Office: +972-39266302
> Cell:      +972-549266302
> Email:   Alexander.Vainshtein@ecitele.com
>
> -----Original Message-----
> From: BRUNGARD, DEBORAH A [mailto:db3546@att.com]
> Sent: Wednesday, May 13, 2015 2:58 PM
> To: Loa Andersson; RFC Errata System; matthew.bocci@alcatel-lucent.com; martin.vigoureux@alcatel-lucent.com; stbryant@cisco.com; akatlas@gmail.com; aretana@cisco.com; swallow@cisco.com; rcallon@juniper.net
> Cc: Alexander Vainshtein; mpls@ietf.org
> Subject: RE: to be rejected - Re: [Technical Errata Reported] RFC5586 (4364)
>
> Will do -
> Thanks Loa-
> Deborah
>
>
> -----Original Message-----
> From: Loa Andersson [mailto:loa@pi.nu]
> Sent: Wednesday, May 13, 2015 2:59 AM
> To: RFC Errata System; matthew.bocci@alcatel-lucent.com; martin.vigoureux@alcatel-lucent.com; stbryant@cisco.com; akatlas@gmail.com; BRUNGARD, DEBORAH A; aretana@cisco.com; swallow@cisco.com; rcallon@juniper.net
> Cc: Alexander.Vainshtein@ecitele.com; mpls@ietf.org
> Subject: to be rejected - Re: [Technical Errata Reported] RFC5586 (4364)
>
> Folks,
>
> MPLS chairs have discussed the errata.
>
> We feel that it is a change to the document rather than an errata, on that ground it should be rejected.
>
> We think that the appropriate would be to revisit this if the document is updated.
>
> I'm always uncertain of the procedures around accepting/rejecting errata, but I guess it requires AD decision.
>
> Deborah,
>
> Can you mark this a "rejected"?
>
>
> /Loa
>
> On 2015-05-12 16:14, RFC Errata System wrote:
>> The following errata report has been submitted for RFC5586, "MPLS
>> Generic Associated Channel".
>>
>> --------------------------------------
>> You may review the report below and at:
>> http://www.rfc-editor.org/errata_search.php?rfc=5586&eid=4364
>>
>> --------------------------------------
>> Type: Technical
>> Reported by: Alexander ("Sasha") Vainshtein
>> <Alexander.Vainshtein@ecitele.com>
>>
>> Section: 4.2.1
>>
>> Original Text
>> -------------
>>      The Time-To-Live (TTL) field of the LSE that contains the GAL follows
>>      the definition and processing rules specified in [RFC3443].
>>
>> Corrected Text
>> --------------
>> The value of the  Time-To-Live (TTL) field of the LSE that contains
>> the GAL follows is irrelevant as long as it exceeds 1. (Setting this
>> value to 0 or 1 SHOULD be avoided because it could result in trapping
>> the OAM packets in with wrong reason: "TTL expiration" instead of "GAL
>> encountered").
>>
>> Notes
>> -----
>> The processing rules specific in RFC 3443 deal with handling TTL in the LSE of a labeled packets that are forwarded based on this LSE, or with setting the TTL value by a LER pushing a label stack on an unlabeled packet.
>> As per the last para in Section 4.2, LSRs and LERs MUST NOT forward packets based on the LSE that contains GAL, hence these rules are mainly not applicable.
>>
>> Instructions:
>> -------------
>> This erratum 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.
>>
>> --------------------------------------
>> RFC5586 (draft-ietf-mpls-tp-gach-gal-06)
>> --------------------------------------
>> Title               : MPLS Generic Associated Channel
>> Publication Date    : June 2009
>> Author(s)           : M. Bocci, Ed., M. Vigoureux, Ed., S. Bryant, Ed.
>> Category            : PROPOSED STANDARD
>> Source              : Multiprotocol Label Switching
>> Area                : Routing
>> Stream              : IETF
>> Verifying Party     : IESG
>>
>

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64