Re: [mpls] Working Group Last Call on draft-ietf-mpls-retire-ach-tlv

Loa Andersson <loa@pi.nu> Fri, 28 June 2013 12:59 UTC

Return-Path: <loa@pi.nu>
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 798AB21F938E; Fri, 28 Jun 2013 05:59:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D9g8ocC4hIwY; Fri, 28 Jun 2013 05:59:02 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id DF90F21F93B9; Fri, 28 Jun 2013 05:51:02 -0700 (PDT)
Received: from [95.209.167.247] (95.209.167.247.mobile.tre.se [95.209.167.247]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 1F8681800272; Fri, 28 Jun 2013 14:51:02 +0200 (CEST)
Message-ID: <51CD86B5.3060606@pi.nu>
Date: Fri, 28 Jun 2013 14:51:01 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: adrian@olddog.co.uk
References: <51B9BE97.2090103@pi.nu> <51CD64A1.4010408@pi.nu> <001401ce73fa$8f45d620$add18260$@olddog.co.uk>
In-Reply-To: <001401ce73fa$8f45d620$add18260$@olddog.co.uk>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: mpls@ietf.org, mpls-chairs@tools.ietf.org, pwe3@ietf.org, pwe3-chairs@tools.ietf.org
Subject: Re: [mpls] Working Group Last Call on draft-ietf-mpls-retire-ach-tlv
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: Fri, 28 Jun 2013 12:59:13 -0000

Adrian,

Yes this works for me.

/Loa

On 2013-06-28 14:25, Adrian Farrel wrote:
>> However TLVs might be carried in the GACh messages, the disticnction
>> is not entirely clear in the draft, can the authors please make
>> this clear.
>
> Happily.
>
> The current version defines "ACH TLV" as "TLV constructs that can be carried in
> messages on the G-ACh by placing them in the ACH between the fixed header fields
> and the G-ACh message."
>
> Thus, retiring ACH TLVs, obviously means only removing this concept and not any
> other TLV-related concept.
>
> I would propose to change the last sentence of Section 1 as follows:
>
> OLD
>     This document states that ACH TLVs as specified in RFC 5586 are not
>     useful and might be harmful.  It updates RFC 5586 by deprecating the
>     ACH TLV and updating the associated IANA registries as described in
>     Section 4 of this document.
> NEW
>     This document states that ACH TLVs as specified in RFC 5586 are not
>     useful and might be harmful.  It updates RFC 5586 by deprecating the
>     ACH TLV and updating the associated IANA registries as described in
>     Section 4 of this document.  This document makes no comment about the
>     use of TLVs in other places.  In particular, proposals to use TLVs
>     within ACH messages, or as an appendage to ACH messages are not in
>     scope of this document.
> END
>
> Does that work?
>
> Thanks,
> Adrian
>

-- 


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