[Lsr] lsr - New Meeting Session Request for IETF 110

2021-01-04 Thread IETF Meeting Session Request Tool
A new meeting session request has just been submitted by Acee Lindem, a Chair of the lsr working group. - Working Group Name: Link State Routing Area Name: Routing Area Session Requester: Acee Lindem Number of Sessions: 1 Length of

Re: [Lsr] New Version Notification for draft-white-lsr-distoptflood-00.txt

2021-01-04 Thread Les Ginsberg (ginsberg)
Russ - I think you have too many email addresses.  Inline. > -Original Message- > From: op...@riw.us > Sent: Monday, January 04, 2021 10:01 AM > To: Les Ginsberg (ginsberg) ; 7ri...@gmail.com; > 'Shraddha Hegde' ; lsr@ietf.org > Subject: RE: [Lsr] New Version Notification for

Re: [Lsr] New Version Notification for draft-white-lsr-distoptflood-00.txt

2021-01-04 Thread opens
> [Les:] Signaling is required in your solution to indicate whether the neighbor > should/should not propagate the LSP(s) received from a given neighbor. > But Circuit Scoped LSPs as defined in RFC 7356 do not provide this > functionality. > > A Circuit Scoped LSP is to be used to send

Re: [Lsr] I-D Action: draft-ietf-lsr-yang-isis-reverse-metric-02.txt

2021-01-04 Thread Acee Lindem (acee)
Speaking as document shepherd: Hi Tom, Chris, I agree that the example prefix should match the module prefix. Given that ietf-isis-reverse-metric is a module specifically for this functionality and not a general building block, I'm less concerned about the length of the prefix. If it were a

Re: [Lsr] I-D Action: draft-ietf-lsr-yang-isis-reverse-metric-02.txt

2021-01-04 Thread tom petch
From: Lsr on behalf of internet-dra...@ietf.org Sent: 18 December 2020 18:43 I still have an issue with the prefix in -02 The examples use rm: which I find a bit short. The module should be the same but uses isis-rmetric: which I find a bit long. isis-rm: would suit me Tom Petch A New