Re: [Lsr] Fwd: I-D Action: draft-ietf-lsr-isis-area-proxy-03.txt

[[e-mail]]

Hi Tony,

I may have a comment on 5.2.  Filtering LSP information.
This is old text, but new re-reading.

"A Level 2 LSP that contains the Area Proxy TLV MUST NOT be flooded to an Outside Router. >
Agreed (so far)

"A Level 2 LSP with a source system identifier that is found in the Level 1 LSDB MUST NOT be flooded to an Outside Router."
I'm not sure to agree.
If that LSP carries the Area Proxy TLV, the previous rule is enough.
If that LSP does not carry the Area Proxy TLV, then no Area Leader advertise the Area Proxy System Identifier Sub-TLV and hence the new Area Proxy is not enabled. In which case I feel that normal IS-IS flooding should occur, and L1-L2 nodes should have their L2 LSP flooded.
So, I would propose to remove that sentence which doesn't seem needed.


"A Level 2 LSP that contains the Area Proxy TLV MUST NOT be flooded to an Outside Router. >
I think we additionally need that an Area Leader advertise the Area Proxy System Identifier Sub-TLV. Otherwise, hence the new Area Proxy is not enabled. I which case I feel that normal IS-IS flooding should occur, and L1-L2 nodes should have their L1 & L2 LSP flooded.
That condition would seem application to the whole section 5.2 or even to the whole section 5

Thanks,
--Bruno


From: Lsr [mailto:[e-mail]] On Behalf Of [e-mail]<mailto:[e-mail]>
Sent: Friday, September 4, 2020 2:29 PM
To: [e-mail]<mailto:[e-mail]>
Cc: [e-mail]<mailto:[e-mail]>
Subject: Re: [Lsr] Fwd: I-D Action: draft-ietf-lsr-isis-area-proxy-03.txt

Hi Tony,

I've read the diff for -03 and -04.
The new encoding of the Area SID is good for me.

And thank you for listening to my use case and suggestion.

Thanks,
--Bruno


From: Lsr [mailto:[e-mail]] On Behalf Of [e-mail]<mailto:[e-mail]>
Sent: Monday, August 24, 2020 7:02 PM
To: [e-mail]<mailto:[e-mail]>
Subject: [Lsr] Fwd: I-D Action: draft-ietf-lsr-isis-area-proxy-03.txt


Hi folks,

This updated draft has been published for a few weeks now.  We would like to solicit your opinion on this.  In particular, we have changed the encoding of the Area SID.  Do you find this encoding adequate and appropriate?

Thanks,
Tony



Begin forwarded message:

From: [e-mail]<mailto:[e-mail]>
Subject: I-D Action: draft-ietf-lsr-isis-area-proxy-03.txt
Date: August 5, 2020 at 1:17:39 PM PDT
To: <[e-mail]<mailto:[e-mail]>>
Cc: [e-mail]<mailto:[e-mail]>
Reply-To: [e-mail]<mailto:[e-mail]>, [e-mail]<mailto:[e-mail]>


A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Link State Routing WG of the IETF.

       Title           : Area Proxy for IS-IS
       Authors         : Tony Li
                         Sarah Chen
                         Vivek Ilangovan
                         Gyan S. Mishra
        Filename        : draft-ietf-lsr-isis-area-proxy-03.txt
        Pages           : 19
        Date            : 2020-08-05

Abstract:
  Link state routing protocols have hierarchical abstraction already
  built into them.  However, when lower levels are used for transit,
  they must expose their internal topologies to each other, leading to
  scale issues.

  To avoid this, this document discusses extensions to the IS-IS
  routing protocol that would allow level 1 areas to provide transit,
  yet only inject an abstraction of the level 1 topology into level 2.
  Each level 1 area is represented as a single level 2 node, thereby
  enabling greater scale.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-lsr-isis-area-proxy/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-lsr-isis-area-proxy-03
https://datatracker.ietf.org/doc/html/draft-ietf-lsr-isis-area-proxy-03

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-lsr-isis-area-proxy-03


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.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


_______________________________________________
I-D-Announce mailing list
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


_________________________________________________________________________________________________________________________



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.

_________________________________________________________________________________________________________________________

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.