Bruno,
On 19/10/2020 18:52, bruno.decra...@orange.com wrote:
Ron, all,
From a use case standpoint, I have a use case for having both SR-MPLS and IP
flexalgo in the same network.
From a protocol standpoint, I think that the functionality could be equally met
by advertising SR-MPLS SID as per RFC 8667 but using a label 3 (implicit null)
to instruct the LER/LSR to not use a label in the forwarding plane. (while
still advertising a label in the control plane because we have to).
does not work, as it does not allow you to associate the prefix with
Flex-algo without advertising the reachability in algo 0. Making the
prefix reachability in default algo conditional based on the presence of
the Prefix SID Sub-TLV with Imnplicit Null would be a nasty hack.
Not to mention that advertising a Prefix SID in pure IP network would be
ugly.
thanks,
Peter
I feel that this would be less change in the protocol (no new tlv), a good fit for
network requiring both MPLS and IP flex algo, and would not require
implementations/network operator to duplicate the "prefix sub-TLV" [1] on both
advertisements (IP based and SR-MPLS based).
That would still requires a protocol extension/STD track RFC as RFC 8667 does
not allow for this. That would still require change to implementations as only
the signalling is different while the feature/behavior is the same (i.e. no
magic).
Regards,
--Bruno
[1] aka "Sub-TLVs for TLVs 135, 235, 236, and 237 (Extended IP reachability, MT IP.
Reach, IPv6 IP. Reach, and MT IPv6 IP. Reach TLVs)"
-----Original Message-----
From: Lsr [mailto:lsr-boun...@ietf.org] On Behalf Of Ron Bonica
Sent: Tuesday, September 29, 2020 3:38 PM
To: lsr@ietf.org
Subject: [Lsr] FW: New Version Notification for draft-bonica-lsr-ip-flexalgo-
00.txt
Please review and comment
Ron
Juniper Business Use Only
-----Original Message-----
From: internet-dra...@ietf.org <internet-dra...@ietf.org>
Sent: Tuesday, September 29, 2020 9:36 AM
To: Parag Kaneriya <pkane...@juniper.net>; Shraddha Hegde
<shrad...@juniper.net>; Ron Bonica <rbon...@juniper.net>; Rajesh M
<mraj...@juniper.net>; William Britto A J <bwill...@juniper.net>
Subject: New Version Notification for draft-bonica-lsr-ip-flexalgo-00.txt
[External Email. Be cautious of content]
A new version of I-D, draft-bonica-lsr-ip-flexalgo-00.txt
has been successfully submitted by Ron Bonica and posted to the IETF
repository.
Name: draft-bonica-lsr-ip-flexalgo
Revision: 00
Title: IGP Flexible Algorithms (Flexalgo) In IP Networks
Document date: 2020-09-29
Group: Individual Submission
Pages: 14
URL: https://urldefense.com/v3/__https://www.ietf.org/id/draft-
bonica-
lsr-ip-flexalgo-00.txt__;!!NEt6yMaO-gk!X7PVDP-
FnUA0oCcZMw3Qde6in0C72hu_9hOZ53kPspIarR8fNDyU9Vck80Zbjoij$
Status:
https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-
bonica-lsr-
ip-flexalgo/__;!!NEt6yMaO-gk!X7PVDP-
FnUA0oCcZMw3Qde6in0C72hu_9hOZ53kPspIarR8fNDyU9Vck8x7e5ZqI$
Htmlized:
https://urldefense.com/v3/__https://datatracker.ietf.org/doc/html/draft-
bonica-lsr-ip-flexalgo__;!!NEt6yMaO-gk!X7PVDP-
FnUA0oCcZMw3Qde6in0C72hu_9hOZ53kPspIarR8fNDyU9Vck82w_6CyU$
Htmlized:
https://urldefense.com/v3/__https://tools.ietf.org/html/draft-
bonica-lsr-ip-flexalgo-00__;!!NEt6yMaO-gk!X7PVDP-
FnUA0oCcZMw3Qde6in0C72hu_9hOZ53kPspIarR8fNDyU9Vck81_QrJ_p$
Abstract:
An IGP Flexible Algorithm computes a constraint-based path and maps
that path to an identifier. As currently defined, Flexalgo can only
map the paths that it computes to Segment Routing (SR) identifiers.
Therefore, Flexalgo cannot be deployed in the absence of SR.
This document extends Flexalgo, so that it can map the paths that it
computes to IP addresses. This allows Flexalgo to be deployed in any
IP network, even in the absence of SR.
Please note that it may take a couple of minutes from the time of
submission
until the htmlized version and diff are available at tools.ietf.org.
The IETF Secretariat
_______________________________________________
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr
_________________________________________________________________________________________________________________________
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.
_______________________________________________
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr
_______________________________________________
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr
