Hi Muthu,
Thanks for the review.
An interface can be associated with, at most, one Flexible Algorithm. Likewise,
an IP address can be associated with, at most, one Flexible Algorithm.
I tried to express this in the text below, but probably didn't do a very good
job. If you can think of a better way to say it, I would appreciate suggestions.
Ron
Text from draft
============
Network operators configure multiple loopback interfaces on an egress
node. They can associate each loopback interface with:
o Zero or more IP addresses.
o Zero or one Flexible Algorithms.
If an IP address and a Flexible Algorithm are associated with the
same interface, they are also associated with one another. An IP
address MAY be associated with, at most, one interface.
Juniper Business Use Only
From: Muthu Arul Mozhi Perumal <muthu.a...@gmail.com>
Sent: Wednesday, September 30, 2020 9:59 AM
To: Ron Bonica <rbon...@juniper.net>
Cc: lsr@ietf.org
Subject: Re: [Lsr] FW: New Version Notification for
draft-bonica-lsr-ip-flexalgo-00.txt
[External Email. Be cautious of content]
A quick question:
If an IP address and a Flexible Algorithm are associated with the
same interface, they are also associated with one another. An IP
address MAY be associated with, at most, one interface.
If multiple IP addresses and multiple flexible algorithms are associated with a
loopback interface, is each IP address associated with all flexible algorithms?
What matters is the association b/w an IP address and a flexalgo, so the
relationship should be defined in a direct way rather than each being
associated with an interface, right?
Regards,
Muthu
On Tue, Sep 29, 2020 at 7:07 PM Ron Bonica
<rbonica=40juniper....@dmarc.ietf.org<mailto:40juniper....@dmarc.ietf.org>>
wrote:
Please review and comment
Ron
Juniper Business Use Only
> -----Original Message-----
> From: internet-dra...@ietf.org<mailto:internet-dra...@ietf.org>
> <internet-dra...@ietf.org<mailto:internet-dra...@ietf.org>>
> Sent: Tuesday, September 29, 2020 9:36 AM
> To: Parag Kaneriya <pkane...@juniper.net<mailto:pkane...@juniper.net>>;
> Shraddha Hegde
> <shrad...@juniper.net<mailto:shrad...@juniper.net>>; Ron Bonica
> <rbon...@juniper.net<mailto:rbon...@juniper.net>>; Rajesh M
> <mraj...@juniper.net<mailto:mraj...@juniper.net>>; William Britto A J
> <bwill...@juniper.net<mailto: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-<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-<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-<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-<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<https://urldefense.com/v3/__http:/tools.ietf.org__;!!NEt6yMaO-gk!VQoAwwHICHoY23KWJbKL7SpeHYGiY6hT9pSpTh7Mfn5lQyaC9E5JcOlvhG1kuR-O$>.
>
> The IETF Secretariat
>
_______________________________________________
Lsr mailing list
Lsr@ietf.org<mailto:Lsr@ietf.org>
https://www.ietf.org/mailman/listinfo/lsr<https://urldefense.com/v3/__https:/www.ietf.org/mailman/listinfo/lsr__;!!NEt6yMaO-gk!VQoAwwHICHoY23KWJbKL7SpeHYGiY6hT9pSpTh7Mfn5lQyaC9E5JcOlvhOxbdTsH$>
_______________________________________________
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr
