Re: [mpls] Retiring ACH TLVs
David Allan I <david.i.allan@ericsson.com> Tue, 14 May 2013 16:18 UTC
Return-Path: <david.i.allan@ericsson.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 DF68F21F8D8E for <mpls@ietfa.amsl.com>; Tue, 14 May 2013 09:18:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599]
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 lzxgxvq1lkCu for <mpls@ietfa.amsl.com>; Tue, 14 May 2013 09:17:48 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id 69C5621F8506 for <mpls@ietf.org>; Tue, 14 May 2013 09:17:40 -0700 (PDT)
X-AuditID: c6180641-b7f906d000003e3f-50-51926372f278
Received: from EUSAAHC008.ericsson.se (Unknown_Domain [147.117.188.96]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 24.7E.15935.27362915; Tue, 14 May 2013 18:16:51 +0200 (CEST)
Received: from EUSAAMB105.ericsson.se ([147.117.188.122]) by EUSAAHC008.ericsson.se ([147.117.188.96]) with mapi id 14.02.0328.009; Tue, 14 May 2013 12:16:50 -0400
From: David Allan I <david.i.allan@ericsson.com>
To: "<mpls@ietf.org>" <mpls@ietf.org>
Thread-Topic: [mpls] Retiring ACH TLVs
Thread-Index: Ac5LRX560irUVDlgRIKUWSY/7OcnkAEoO+2AADzDeAD//8grZf///prA
Date: Tue, 14 May 2013 16:16:49 +0000
Message-ID: <E6C17D2345AC7A45B7D054D407AA205C09B4F9@eusaamb105.ericsson.se>
References: <12BA262D-8402-4E44-B806-F40B8F868642@gmail.com>, <2FE467D3673DCE409A84D67EC2F607BB0FA778F0@xmb-rcd-x10.cisco.com> <AC73D31B-F667-4BE1-9922-8B82C477FA3A@ericsson.com>
In-Reply-To: <AC73D31B-F667-4BE1-9922-8B82C477FA3A@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.117.188.134]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrJLMWRmVeSWpSXmKPExsUyuXRPgm5x8qRAg01vhSxuLV3J6sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujF23VrIWXJermHerlbmBcb1kFyMnh4SAiUT7iYnsELaYxIV7 69m6GLk4hASOMkpM//0GylnOKLH5QAMLSBWbgIHEnv9fGEFsEQFViYbFN1lBbGEg+8SS08wQ cTWJ/ac/s0DYbhL/d1wAq2cBqvnXdxushlfAW6L3ejsrxIJtjBJPfl8Ea+AUcJDY8fsSWBEj 0EnfT61hArGZBcQlbj2ZzwRxqoDEkj3nmSFsUYmXj/+xQtjKEkue7GeBqNeRWLD7ExuErS2x bOFrqMWCEidnPmGZwCg6C8nYWUhaZiFpmYWkZQEjyypGjtLi1LLcdCPDTYzA4D8mwea4g3HB J8tDjNIcLErivIlcjYFCAumJJanZqakFqUXxRaU5qcWHGJk4OKUaGPtu3k/1cj6+yKCWt8o0 SZlhv3bbh8Dzu/of6c96mpEqtvDeLvsX52pDjfdOkltjyOikmqPPZvA0jOXO39Z4pSDbBfcb NiU0G7OpBzubM3pff3R8xq0NSx2/8+6fvrOLd9GM00ISp+Vy173YvaFK9m1yT4Ri88WH6rvt GqNiMhXj+flWlScoKrEUZyQaajEXFScCAJiN53RMAgAA
Subject: Re: [mpls] Retiring ACH TLVs
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: Tue, 14 May 2013 16:18:10 -0000
I'm all for deprecating ACH TLVs. Support Dave >>> Hi, >>> >>> ACH TLVs keep popping up and causing Stewart and me trouble. Mainly >>> it is about explaining why no-one actually wants to use them (i.e., >>> when each new ACH Type is defined and has a "No TLVs" written for >>> it, we get asked "why not?"). >>> >>> It seems to us that ACH TLVs are an idea that has been rejected. >>> Initially we thought they might be used (especially for >>> identifiers), but there seems to be good opinion that handling >>> generic TLVs would be a pain. >>> >>> Since I was heavily responsible for insisting that ACH TLVs were >>> included in RFC 5586, it seems reasonable that I do the work to fix it. >>> >>> The I-D below retires ACH TLVs and handles the necessary registry >>> changes. >>> >>> Note, of course, that structured data are still possible within >>> individual ACHs if the protocol spec for an individual ACH decides >>> to have them. >>> >>> We're directing this work to the MPLS working group because that is >>> where 5586 was written. I have BCC'ed PWE3, L2VPN, and BFD for >>> information. >>> >>> Thanks for any comments. >>> >>> As humble WG contributors we would be enthusiastic to see early WG >>> adoption and last call :-) >>> >>> Thanks, >>> Adrian >>> >>>> -----Original Message----- >>>> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] >>>> Sent: 07 May 2013 17:33 >>>> To: Adrian Farrel; Stewart Bryant >>>> Subject: New Version Notification for >>>> draft-farbryantrel-mpls-retire-ach-tlv- >>>> 00.txt >>>> >>>> >>>> A new version of I-D, draft-farbryantrel-mpls-retire-ach-tlv-00.txt >>>> has been successfully submitted by Adrian Farrel and posted to the >>>> IETF repository. >>>> >>>> Filename: draft-farbryantrel-mpls-retire-ach-tlv >>>> Revision: 00 >>>> Title: Retiring TLVs from the Associated Channel Header of the >>>> MPLS >>>> Generic Associated Channel >>>> Creation date: 2013-05-07 >>>> Group: Individual Submission >>>> Number of pages: 4 >>>> URL: >>>> http://www.ietf.org/internet-drafts/draft-farbryantrel-mpls-retire- >>>> ach-tlv-00.txt >>>> Status: >>>> http://datatracker.ietf.org/doc/draft-farbryantrel-mpls-retire-ach-tlv >>>> Htmlized: >>>> http://tools.ietf.org/html/draft-farbryantrel-mpls-retire-ach-tlv-0 >>>> 0 >>>> >>>> >>>> Abstract: >>>> The MPLS Generic Associated Channel (G-ACh) is a generalization of >>>> the applicability of the Pseudowire (PW) Associated Channel Header >>>> (ACH). RFC 5586 defines the concept of Type-Length-Variable (TLV) >>>> constructs that can be carried in messages on the G-ACh by placing >>>> them in the ACH. >>>> >>>> No Associated Channel Type yet defined uses a TLV. Furthermore, >>>> it is believed that handling TLVs in hardware introduces >>>> significant problems to the fast-path, and since G-ACh messages >>>> are intended to be processed substantially in hardware, the use of >>>> TLVs in undesirable. >>>> >>>> This document updates RFC 5586 by retiring ACH TLVs and removing >>>> the associated registry. >>>> >>>> >>>> >>>> >>>> The IETF Secretariat >>> >>> _______________________________________________ >>> mpls mailing list >>> mpls@ietf.org >>> https://www.ietf.org/mailman/listinfo/mpls >> _______________________________________________ >> mpls mailing list >> mpls@ietf.org >> https://www.ietf.org/mailman/listinfo/mpls > > _______________________________________________ > mpls mailing list > mpls@ietf.org > https://www.ietf.org/mailman/listinfo/mpls _______________________________________________ mpls mailing list mpls@ietf.org https://www.ietf.org/mailman/listinfo/mpls
- Re: [mpls] Retiring ACH TLVs Lizhong Jin
- [mpls] Retiring ACH TLVs Adrian Farrel
- Re: [mpls] Retiring ACH TLVs Nitin Bahadur
- Re: [mpls] Retiring ACH TLVs Giles Heron
- Re: [mpls] Retiring ACH TLVs Carlos Pignataro (cpignata)
- Re: [mpls] Retiring ACH TLVs Dan Frost
- Re: [mpls] Retiring ACH TLVs Sam Aldrin
- Re: [mpls] Retiring ACH TLVs George Swallow (swallow)
- Re: [mpls] Retiring ACH TLVs Jeff Tantsura
- Re: [mpls] Retiring ACH TLVs David Allan I
- Re: [mpls] Retiring ACH TLVs Shahram Davari
- Re: [mpls] Retiring ACH TLVs Pablo Frank
- Re: [mpls] Retiring ACH TLVs Yaakov Stein
- Re: [mpls] Retiring ACH TLVs Lizhong Jin
- Re: [mpls] Retiring ACH TLVs Adrian Farrel
- Re: [mpls] Retiring ACH TLVs Adrian Farrel
- Re: [mpls] Retiring ACH TLVs Stewart Bryant
- Re: [mpls] Retiring ACH TLVs Eric Gray