Re: [Lsr] [mpls] Comments on draft-ietf-mpls-spring-entropy-label

Jeff Tantsura <jefftant.ietf@gmail.com> Thu, 05 July 2018 23:48 UTC

Return-Path: <jefftant.ietf@gmail.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF6AB130E21; Thu, 5 Jul 2018 16:48:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 enTkFoo5WlNS; Thu, 5 Jul 2018 16:48:42 -0700 (PDT)
Received: from mail-it0-x22c.google.com (mail-it0-x22c.google.com [IPv6:2607:f8b0:4001:c0b::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 77921130DE0; Thu, 5 Jul 2018 16:48:42 -0700 (PDT)
Received: by mail-it0-x22c.google.com with SMTP id 16-v6so14258503itl.5; Thu, 05 Jul 2018 16:48:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :references:in-reply-to:mime-version; bh=Xq0PfqYyO+YpEnx+6Ps9sXF/7IO5IrHv7E24IbsEj8k=; b=g+2a0slpaOl/EQwiivcXaVfv9SE60MH29pj/cSdflkvHEV18ZhVTxXi4gVECziTTCr oOBZMMAClgNTu9FkdLJYAIm9wmpQQDQbXSh9zOniTdB2P3tYx8tKgPjoRvHWR5Q2nXz6 4yoM+u1c8bWlByJw75QaeKo6LQ7sI7zschXy6EWh2VjANtblrjChajJ0S1PprVKhisNm 4AzErxKw0NH7Vc7AOs/KY1t8CwZIW1LDHCJObn3uvgXQtXbJ24A8KFAUSEUa6VEWDrVM qOrt0i9eHlaChseOUt9I9PC+1/z6wMGvhDkX0V/mGv5gLdv5A1VLUKvF6TdG0zYtvb7z x65g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:user-agent:date:subject:from:to:cc:message-id :thread-topic:references:in-reply-to:mime-version; bh=Xq0PfqYyO+YpEnx+6Ps9sXF/7IO5IrHv7E24IbsEj8k=; b=CCe8jjej2LrYWWhTuUJwfHD3Q+i5hkr7Oc4AfLzEO4wp23KsvVhp8FMFEA5YbYk8wT tAl6bVq5HVLpIy3gqa4Le9otndDuoC15ZF8udgNeszx+rzYjs+mZQRUAVxP160fxhOkd LaWDkUeqZiq9SUTbfdtKxIX0EUQfqXE26JYThV8y5FeE5mW/A0d4BDKOfMT1dAO4KohZ uYWg2ZkRo5+rTkhxNNZOUE71gySK/xrGI9tTrFI6YeBGtryT/ftDjRBpw1FBlH3M0VyX 7AHeM/U6AvBfr+tGq+6Cp3ohPw/tPcvjQre2+eFX8MxK0GbdmOlw8/Q0lllLylXYPG2F VymQ==
X-Gm-Message-State: APt69E3h8dcmIQCBEYSsJPh5KxaTJdCF0m2YQF+7bjWhOjpFzOeJBiFd X0IYzESORW1GLJ79TMJYrR4=
X-Google-Smtp-Source: AAOMgpfDCkitfzKhWnWK9EFrNJiETcwZdZTkYu69hTGmBZMCn/YNtvZpgvMm3/G8g4Ce/eO7CGhtvQ==
X-Received: by 2002:a24:6196:: with SMTP id s144-v6mr6515275itc.68.1530834521878; Thu, 05 Jul 2018 16:48:41 -0700 (PDT)
Received: from [192.168.0.125] (47-36-65-40.dhcp.reno.nv.charter.com. [47.36.65.40]) by smtp.gmail.com with ESMTPSA id h71-v6sm3752928ith.5.2018.07.05.16.48.40 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 05 Jul 2018 16:48:41 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/10.e.1.180613
Date: Thu, 05 Jul 2018 16:48:39 -0700
From: Jeff Tantsura <jefftant.ietf@gmail.com>
To: <stephane.litkowski@orange.com>, "=?UTF-8?B?5b6Q5bCP6JmO?= (=?UTF-8?B?5LmJ5YWI?=)" <xiaohu.xxh@alibaba-inc.com>, "mpls@ietf.org" <mpls@ietf.org>
CC: "lsr@ietf.org" <lsr@ietf.org>, "pce@ietf.org" <pce@ietf.org>
Message-ID: <EC8F6C49-5D83-467B-9C4D-07EEFC9CBEFE@gmail.com>
Thread-Topic: [mpls] Comments on draft-ietf-mpls-spring-entropy-label
References: <43768014-1ce8-43d0-9f9b-04eba6f87904.xiaohu.xxh@alibaba-inc.com> <7608_1530829167_5B3E996F_7608_323_1_9E32478DFA9976438E7A22F69B08FF924B1F0131@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
In-Reply-To: <7608_1530829167_5B3E996F_7608_323_1_9E32478DFA9976438E7A22F69B08FF924B1F0131@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3613654121_139486885"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/-JCsj8TKSJNos0--nhWG4iDdkNk>
Subject: Re: [Lsr] [mpls] Comments on draft-ietf-mpls-spring-entropy-label
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jul 2018 23:48:45 -0000

Hi,

 

Please see inline (MSD section).

Hope this clarifies, thanks!

 

Cheers,

Jeff

 

 

 

[jeff] both IGP drafts have identical description of the BMI-MSD:

“Base MPLS Imposition MSD (BMI-MSD) signals the total number of MPLS labels a node is capable of imposing, including all service/transport/special labels.”

PCEP draft supports only a subset of overall MSD functionality and in general it is expected that this info would come from IGPs(BGP-LS).

However the functoriality provided by PCEP is inline with the  BMI-MSD definition in the IGP drafts, at the node granularity only though. 

 

 

3. Section 5 introduces the MSD concept. I wonder whether this concept is aligned with the MSD concept as defined in the PCEP-SR draft or the MSD concept as defined in the IGP-MSD draft. In PCEP-SR draft, it said "
The "Maximum SID Depth" (1
   octet) field (MSD) specifies the maximum number of SIDs (MPLS label
   stack depth in the context of this document) that a PCC is capable of
   imposing on a packet.
 
In the IGP-MSD draft, it said "
MSD of type 1 (IANA Registry), called Base MSD is used to signal the
   total number of SIDs a node is capable of imposing, to be used by a
   path computation element/controller.  "
 
If I understand it correctly, the MSD in this draft==the MSD in PCEP-SR draft==the Base MSD (i.e., the MSD of type 1), No?
 

[SLI] Today, the two IGP drafts does not seem to agree on the definition
ISIS says:” Base MPLS Imposition MSD (BMI-MSD) signals the total number of MPLS
   labels a node is capable of imposing, including all

   service/transport/special labels.”
OSPF says:” MSD of type 1 (IANA Registry) is used to signal the number of SIDs a
   node is capable of imposing, to be used by a path computation

   element/controller and is only relevant to the part of the stack

   created as the result of the computation.”

 

MSD is just MSD is defines a maximum number of labels to be pushed. This is the definition we use and it is compliant with the one used in PCEP-SR:
“The "Maximum SID Depth" (1
   octet) field (MSD) specifies the maximum number of SIDs (MPLS label

   stack depth in context of this document) that a PCC is capable of

   imposing on a packet.”

 

As we also say: “This includes any kind of labels (service, entropy, transport...).”, we are compliant with the BMI-MSD defined in IS-IS.

 

 

 

Best regards,

Xiaohu
_________________________________________________________________________________________________________________________
 
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
 
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
_______________________________________________ mpls mailing list mpls@ietf.org https://www.ietf.org/mailman/listinfo/mpls