Re: [mpls] Retiring ACH TLVs

Jeff Tantsura <jeff.tantsura@ericsson.com> Tue, 14 May 2013 16:10 UTC

Return-Path: <jeff.tantsura@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 0692521F8B64 for <mpls@ietfa.amsl.com>; Tue, 14 May 2013 09:10:45 -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=[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 jSiBd2SK5aSh for <mpls@ietfa.amsl.com>; Tue, 14 May 2013 09:10:40 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id C4DD721F92F4 for <mpls@ietf.org>; Tue, 14 May 2013 09:10:38 -0700 (PDT)
X-AuditID: c618062d-b7ff46d000006709-18-519261fd099b
Received: from EUSAAHC002.ericsson.se (Unknown_Domain [147.117.188.78]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id AF.4E.26377.DF162915; Tue, 14 May 2013 18:10:38 +0200 (CEST)
Received: from EUSAAMB109.ericsson.se ([147.117.188.126]) by EUSAAHC002.ericsson.se ([147.117.188.78]) with mapi id 14.02.0328.009; Tue, 14 May 2013 12:10:37 -0400
From: Jeff Tantsura <jeff.tantsura@ericsson.com>
To: "George Swallow (swallow)" <swallow@cisco.com>
Thread-Topic: [mpls] Retiring ACH TLVs
Thread-Index: Ac5LRX560irUVDlgRIKUWSY/7OcnkAEoO+2AADzDeAD//8grZQ==
Date: Tue, 14 May 2013 16:10:36 +0000
Message-ID: <AC73D31B-F667-4BE1-9922-8B82C477FA3A@ericsson.com>
References: <12BA262D-8402-4E44-B806-F40B8F868642@gmail.com>, <2FE467D3673DCE409A84D67EC2F607BB0FA778F0@xmb-rcd-x10.cisco.com>
In-Reply-To: <2FE467D3673DCE409A84D67EC2F607BB0FA778F0@xmb-rcd-x10.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrMLMWRmVeSWpSXmKPExsUyuXSPn+6/xEmBBtMaGC1+9NxgtpjQ+oXR 4tbSlawWt6c0MTqweEz5vZHVY+esu+weS5b8ZPJYsXklYwBLFJdNSmpOZllqkb5dAldGx171 guPyFRPfz2NuYHwt2cXIySEhYCJx7cFHNghbTOLCvfVANheHkMBRRonbnduYIJzljBJXDzWy g1SxCRhI/P92nAXEFhEwkrh4shcszixQIdF94iVQNweHsICqxNK7ZhAlahL7T39mAQmLCDhJ 7D4gDRJmAao4cfg62BReAXuJyXuPgNlCArUSHz99ZgSxOQV8Jf7d7AGbzgh02/dTa5ggNolL 3HoynwniZgGJJXvOM0PYohIvH/9jhajRkViw+xMbhK0tsWzha2aIXYISJ2c+YZnAKDoLyahZ SFpmIWmZhaRlASPLKkaO0uLUstx0I4NNjMCIOSbBpruDcc9Ly0OM0hwsSuK8UVyNgUIC6Ykl qdmpqQWpRfFFpTmpxYcYmTg4pRoYeffWPpvycnXLnOxZ597N/rL7WOBnjelSMzOu/elYJ7It ePmy7gf5n97O5OL/0/X3duCR5vPWh1yfSnktWz3p1oHqdfldSyuDg1h3cZxcf+vIdol+9rUf LH+wcO3bH5y4VCZ6vX1YQPD8Q7f5lu9/cGau2gnnDwvKehisC91ZpvLHZT1e921C4VElluKM REMt5qLiRADPub6iZgIAAA==
Cc: "<mpls@ietf.org>" <mpls@ietf.org>
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:10:46 -0000

Support

Regards,
Jeff

On May 14, 2013, at 5:30 PM, "George Swallow (swallow)" <swallow@cisco.com> wrote:

> Absolutely!
> 
> On 5/13/13 6:30 AM, "Sam Aldrin" <aldrin.ietf@gmail.com> wrote:
> 
>> Fully support.
>> 
>> -sam
>> 
>> Sent from my iPhone
>> 
>> On May 7, 2013, at 1:08 PM, "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
>> _______________________________________________
>> 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