Re: [mpls] comments on draft-kompella-mpls-special-purpose-labels-02

Saku Ytti <saku@ytti.fi> Fri, 22 March 2013 07:14 UTC

Return-Path: <saku@ytti.fi>
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 55CE221F8489 for <mpls@ietfa.amsl.com>; Fri, 22 Mar 2013 00:14:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
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 C8Wvj3Vy-dIA for <mpls@ietfa.amsl.com>; Fri, 22 Mar 2013 00:14:06 -0700 (PDT)
Received: from mail-la0-x22d.google.com (mail-la0-x22d.google.com [IPv6:2a00:1450:4010:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 83A1021F8488 for <mpls@ietf.org>; Fri, 22 Mar 2013 00:14:06 -0700 (PDT)
Received: by mail-la0-f45.google.com with SMTP id er20so6604243lab.4 for <mpls@ietf.org>; Fri, 22 Mar 2013 00:14:05 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:date:from:to:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent :x-gm-message-state; bh=ne3kYXdqlsOqJ+alXeVSvVQ7BER6SvZyxTKRsgv4HsU=; b=EsVRXHRFGP6t4JBcum4OIJr8cT8g94G6EtoM9utiyTuoTTTtSP1ICRbLR3sCerVMTK Ep5z66DscmuXvvwKa6Td0KPDic0mH0hW6B2yhG2I99ed2+NFJHiWNBDKGB22EzwlffqW f36oIleFTy/XaS+RtiODiRz2SgeadIFuYl8zD0uaaglgwu7W2kuoruKxKoBIE1IT6J3w 2G7IONpyjCZ1t3yF3XteE0WQ33vsG8uRHiCsD0CllKahGCGj01EBJn6dTL4iNYi/Rz2S 4XMBvwdJ3FZ1XDIY1XmRRVm377MQC4GVky5LxOP8A7otuLZd8cpnn70vIR4bw8flZaP9 ELkw==
X-Received: by 10.112.131.227 with SMTP id op3mr541790lbb.76.1363936445016; Fri, 22 Mar 2013 00:14:05 -0700 (PDT)
Received: from pob.ytti.fi (ytti.fi. [2001:6e8:288::8]) by mx.google.com with ESMTPS id l1sm506515lbn.8.2013.03.22.00.14.02 (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Fri, 22 Mar 2013 00:14:03 -0700 (PDT)
Date: Fri, 22 Mar 2013 09:14:00 +0200
From: Saku Ytti <saku@ytti.fi>
To: mpls@ietf.org
Message-ID: <20130322071400.GA32063@pob.ytti.fi>
References: <D2FD2FE4B21AEB41A13FAA7498B10761E0C1C3@xmb-aln-x03.cisco.com> <31963.1363712582@erosen-linux> <D2FD2FE4B21AEB41A13FAA7498B10761E0F10A@xmb-aln-x03.cisco.com> <CAPWAtb+rF8WyG5BzrSdwMFnX_mh9eDcJicU4zsAyD78z9odfPg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAPWAtb+rF8WyG5BzrSdwMFnX_mh9eDcJicU4zsAyD78z9odfPg@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Gm-Message-State: ALoCoQkIUX0YEmaBIR4uCFvHAbLMAMWKoL6c4SFIfTHkCqBUI/O7QouLr3fgY4j3iAcDvyIzy5fC
Subject: Re: [mpls] comments on draft-kompella-mpls-special-purpose-labels-02
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, 22 Mar 2013 07:14:07 -0000

On (2013-03-21 14:11 -0400), Jeff Wheeler wrote:

> Do any routers exist where it is easier to deploy support for extended
> special purpose labels than for simply growing the reservation?  My

I'm quite interested in this as well. If someone can think of practical
example of MPLS product in use, where by HW labels 16 through say 16k will
be used and cannot not be used via software update, it would be easy to
disregard option of extending space.

I'm not concerned of trio or ezchip style products, I'm sure those will
adapt with very low cost to what we can think of essentially 8B mpls label
when certain 20b magic exists. But 'l3 switch' style products might be
problematic (7600, brocade, EX8k)

How commonly do we foresee the need for multiple subsequent SP labels, such
as [ 15 ext1 15 ext2 15 ext3 igp vpn ]? If this seems common, what would be
the implications of dedicating one bit in SP label for EOE or
end-of-extension?  So we'd have [15 ext1 ext2 ext3 igp vpn] with EOE bit
off in ext[12] and on in ext3.

-- 
  ++ytti