Re: [mpls] FW: New Version Notification for draft-keten-mpls-expbit-00.txt

"Adrian Farrel" <adrian@olddog.co.uk> Wed, 14 September 2016 09:35 UTC

Return-Path: <adrian@olddog.co.uk>
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 00BAA12B22A for <mpls@ietfa.amsl.com>; Wed, 14 Sep 2016 02:35:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level:
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fJp-rxa6xqe9 for <mpls@ietfa.amsl.com>; Wed, 14 Sep 2016 02:35:18 -0700 (PDT)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B5FD212B227 for <mpls@ietf.org>; Wed, 14 Sep 2016 02:35:16 -0700 (PDT)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id u8E9ZE89005886; Wed, 14 Sep 2016 10:35:14 +0100
Received: from 950129200 ([178.103.22.188]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id u8E9YrmX005401 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Wed, 14 Sep 2016 10:35:08 +0100
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Umut Keten' <umut.keten@turktelekom.com.tr>
References: <cvuifsybtov39macfmufuc5f.1473802811888@email.android.com>
In-Reply-To: <cvuifsybtov39macfmufuc5f.1473802811888@email.android.com>
Date: Wed, 14 Sep 2016 10:34:22 +0100
Message-ID: <0ea601d20e6b$47d77dc0$d7867940$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIqrgVBVT456XII/qqAuwxf0J24d5/Hcv+A
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.0.0.1202-22576.001
X-TM-AS-Result: No--11.958-10.0-31-10
X-imss-scan-details: No--11.958-10.0-31-10
X-TMASE-MatchedRID: xcONGPdDH5o4HKI/yaqRm+YAh37ZsBDC1kqyrcMalqWLaDxfPEIN+6Es hzqhV9N+oFnVuixmQhL/FlIeEJqc9rb2zTAv899lSEQN/D/3cG59dcdZFPV3M9JgDNnoqapa5vV qf4A1CX8Za3NuuEtGCHNg1qWIDIy9ig2uZvub1niJQ9k+Ypk5CcMdI0UcXEHzh3oG8n7LZDqUfp ETB+BNowUoLAuctTakNaTPCVfgIvSrk4SVjTOUqntItsHAduPxjdbk0QitxRXDra5IbmQvVoivL sP3YMwIl8pkA7kKUYzIUWRkKNlWpfQVlT07zIBdTd1FGyH+HrK1qkcTY8iYs5Dfs75l/ZCj07za VZEg+DNi3Wfqm1DIPmd76JWYnRilWYK9Y7qO8/D9zT4slMys3SHAogh2SU5Xqe7f8q1Z8ZBIXHt RCIa3mG8aRpI61RUKVHp5oqbnqh7lRxm3A2wKuoMbH85DUZXy3QfwsVk0UbtuRXh7bFKB7roV9+ jk8V20cRQynjTMA0D0S81KjMDOPnsBTPWHBe9qWClYJu9r4yY=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/QfYGTMVRzvUvrIFfs_lofWAEfok>
Cc: mpls@ietf.org
Subject: Re: [mpls] FW: New Version Notification for draft-keten-mpls-expbit-00.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: adrian@olddog.co.uk
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 14 Sep 2016 09:35:20 -0000

Umut,

> Thanks for your reply. I will answer your question regarding compatability after asking
> a question first. What is your opinion on the huge TTL and couldn't it be better used as
> QoS?

What if I respond by asking you a question first?  ;-)

I think you are asking four questions that need to be handled separately.
1. Do we need more service differentiation in MPLS networks?
2. Would MPLS routers be able to deliver the differentiation if the packets
   were marked accordingly?
3. How should we achieve additional service differentiation in MPLS
   networks. There are many possible approaches (TC bits, label stacks,
   control plane, using some of the label bits, reworking the shim header
   as you suggest, ...) and I don't (yet) have an opinion although it seems
   to me that a non-backward compatible forwarding plane change is an 
   expensive solution.
4. Are all 8 bits of the TTL field needed?

> Regarding your question new/old format.
> My expectation is the following and correct me if I am wrong:  I do not
> expect an MPLS network to be half upgraded with new format router.

Well, this works for greenfield, but this is not necessarily a field upgrade (i.e., some implementations may need hardware upgrades) and that is a really expensive solution. I guess the vendors will be delighted to sell a whole set of new routers to replace what is deployed, but are the operators willing to spend the money? And will they upgrade the whole network in one go - that sounds like a little more than a flag day... maybe a flag month?

> Your last question however regarding if the 255 is ever set for special reasons? I
> have no clue! Even so if it is ever set for some special occasion the more QoS
> possibilities surely should outweigh that.

So this is just an example of a backwards compatibility issue. If special settings of TTL are configurable options that can be disabled, then everything will be fine (so long as you remember to configure your entire network). On the other hand, if the special settings are more fundamental then more protocol work may be needed. An approach here is to ask the working group a specific question -- Does anyone know of reasons why the MPLS TTL is set greater than 63? e

I'd be really interested to hear what other operators think about your problem statement. That's not because I don't believe you, but because I find it interesting that others haven't previously raised the concern - but someone has to be first :-)

Cheers,
Adrian