Re: [mpls] Retiring ACH TLVs

Nitin Bahadur <nitinb@juniper.net> Fri, 10 May 2013 18:22 UTC

Return-Path: <nitinb@juniper.net>
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 AC48D21F901B for <mpls@ietfa.amsl.com>; Fri, 10 May 2013 11:22:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.467
X-Spam-Level:
X-Spam-Status: No, score=-3.467 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNRESOLVED_TEMPLATE=3.132]
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 d-foG3jusDCg for <mpls@ietfa.amsl.com>; Fri, 10 May 2013 11:22:30 -0700 (PDT)
Received: from exprod7og107.obsmtp.com (exprod7og107.obsmtp.com [64.18.2.167]) by ietfa.amsl.com (Postfix) with ESMTP id BEA1D21F9017 for <mpls@ietf.org>; Fri, 10 May 2013 11:22:29 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob107.postini.com ([64.18.6.12]) with SMTP ID DSNKUY065ZfcspcG2b7xGeLzJpDCXooAU0tk@postini.com; Fri, 10 May 2013 11:22:29 PDT
Received: from P-CLDFE01-HQ.jnpr.net (172.24.192.59) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.213.0; Fri, 10 May 2013 11:21:38 -0700
Received: from o365mail.juniper.net (207.17.137.224) by o365mail.juniper.net (172.24.192.59) with Microsoft SMTP Server id 14.1.355.2; Fri, 10 May 2013 11:21:37 -0700
Received: from co1outboundpool.messaging.microsoft.com (216.32.180.188) by o365mail.juniper.net (207.17.137.224) with Microsoft SMTP Server (TLS) id 14.1.355.2; Fri, 10 May 2013 11:32:31 -0700
Received: from mail185-co1-R.bigfish.com (10.243.78.245) by CO1EHSOBE009.bigfish.com (10.243.66.72) with Microsoft SMTP Server id 14.1.225.23; Fri, 10 May 2013 18:21:33 +0000
Received: from mail185-co1 (localhost [127.0.0.1]) by mail185-co1-R.bigfish.com (Postfix) with ESMTP id 65E0D8C0405 for <mpls@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Fri, 10 May 2013 18:21:33 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.234.117; KIP:(null); UIP:(null); (null); H:SN2PRD0510HT001.namprd05.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: -27
X-BigFish: PS-27(zzbb2dI98dI9371I936eI542I1432I4015Izz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hzz1033IL17326ah8275dhz2dh2a8h668h839h944he5bhf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h1ad9h1b0ah1d0ch1d2eh1d3fh1155h)
Received: from mail185-co1 (localhost.localdomain [127.0.0.1]) by mail185-co1 (MessageSwitch) id 1368210091519237_23593; Fri, 10 May 2013 18:21:31 +0000 (UTC)
Received: from CO1EHSMHS002.bigfish.com (unknown [10.243.78.252]) by mail185-co1.bigfish.com (Postfix) with ESMTP id 7C1B79E0050; Fri, 10 May 2013 18:21:31 +0000 (UTC)
Received: from SN2PRD0510HT001.namprd05.prod.outlook.com (157.56.234.117) by CO1EHSMHS002.bigfish.com (10.243.66.12) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 10 May 2013 18:21:29 +0000
Received: from SN2PRD0510MB383.namprd05.prod.outlook.com ([169.254.10.62]) by SN2PRD0510HT001.namprd05.prod.outlook.com ([10.255.116.36]) with mapi id 14.16.0305.001; Fri, 10 May 2013 18:21:24 +0000
From: Nitin Bahadur <nitinb@juniper.net>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "mpls@ietf.org" <mpls@ietf.org>
Thread-Topic: [mpls] Retiring ACH TLVs
Thread-Index: Ac5LRX560irUVDlgRIKUWSY/7OcnkACKv34A
Date: Fri, 10 May 2013 18:21:23 +0000
Message-ID: <CDB28894.268F1%nitinb@juniper.net>
In-Reply-To: <002a01ce4b45$82e38ae0$88aaa0a0$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.2.130206
x-originating-ip: [10.255.116.4]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <F15674D7EAC5FA42870135EDAE2C80A4@namprd05.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%12219$Dn%OLDDOG.CO.UK$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%IETF.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
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: Fri, 10 May 2013 18:22:36 -0000

Fully support the ID. I was never a fan of ACH TLVs.

Thanks
Nitin Bahadur





On 5/7/13 10:08 AM, "Adrian Farrel" <adrian@olddog.co.uk> wrote:

>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-00
>> 
>> 
>> 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
>