[{"author": "Yingzhen Qu", "text": "

Hello, welcome to LSR session

", "time": "2024-03-21T03:00:11Z"}, {"author": "Andrew Stone", "text": "

oh no this is the room with the annoying mic sound :(

", "time": "2024-03-21T03:00:22Z"}, {"author": "Yingzhen Qu", "text": "

please help with note taking: https://notes.ietf.org/notes-ietf-119-lsr?both

", "time": "2024-03-21T03:00:23Z"}, {"author": "John Scudder", "text": "

Bad mic sound STILL? Dang.

", "time": "2024-03-21T03:01:07Z"}, {"author": "Les Ginsberg", "text": "

Thanx John.

", "time": "2024-03-21T03:01:51Z"}, {"author": "John Scudder", "text": "

I\u2019ll pass through the complaint for whatever good it will do. Can you characterize \u201cannoying\u201d for me?

", "time": "2024-03-21T03:03:01Z"}, {"author": "John Scudder", "text": "

(About the mic not the AD ;-)

", "time": "2024-03-21T03:03:18Z"}, {"author": "Andrew Cooks", "text": "

Any interest in resuming work on Multi-Topology routing for OSPFv3

", "time": "2024-03-21T03:03:36Z"}, {"author": "Andrew Stone", "text": "

digital sound effect like a whistle-like instrument trying to say \"zoo\". Like a futurist \"zoom\" effect.

\n

makes me wonder if it's some kind of sound detection check / loopback that happens to be coming through

", "time": "2024-03-21T03:04:08Z"}, {"author": "Lorenzo Miniero", "text": "

No need to report it, we're already aware of the issue: the AV team is already investigating it

", "time": "2024-03-21T03:04:54Z"}, {"author": "Andrew Stone", "text": "

thanks Lorenzo!

", "time": "2024-03-21T03:05:03Z"}, {"author": "John Scudder", "text": "

Note status slides are out of date w.r.t. dynamic-flooding draft. That one is on the IESG agenda for 4/4

", "time": "2024-03-21T03:09:36Z"}, {"author": "Yingzhen Qu", "text": "

noted. thanks, John.

", "time": "2024-03-21T03:10:08Z"}, {"author": "Tony Li", "text": "

And I think I've addressed LC comments. New version was uploaded Sunday.

", "time": "2024-03-21T03:13:29Z"}, {"author": "John Scudder", "text": "

@Tony Li right, I saw that and it\u2019s why it\u2019s now on the IESG agenda. Thanks for the updates.

", "time": "2024-03-21T03:15:58Z"}, {"author": "Gyan Mishra", "text": "

I see this OSPFv3 MT I-D from 2007. https://datatracker.ietf.org/doc/html/draft-ietf-ospf-mt-ospfv3-03

", "time": "2024-03-21T03:17:33Z"}, {"author": "Lorenzo Miniero", "text": "

The mic is still turned off, apparently, at least listening to the remote stream

", "time": "2024-03-21T03:18:26Z"}, {"author": "Boris Khasanov", "text": "

still very low sound from the presenter

", "time": "2024-03-21T03:18:26Z"}, {"author": "Mengxiao Chen", "text": "

very low +1

", "time": "2024-03-21T03:18:42Z"}, {"author": "Lorenzo Miniero", "text": "

is it played fine in the room there?

", "time": "2024-03-21T03:18:43Z"}, {"author": "Gyan Mishra", "text": "

I think most operators would opt for SR Flex Algo instead of MT

", "time": "2024-03-21T03:18:45Z"}, {"author": "Tony Przygienda", "text": "

mike impossible to hear

", "time": "2024-03-21T03:18:46Z"}, {"author": "Gyan Mishra", "text": "

Very low

", "time": "2024-03-21T03:19:00Z"}, {"author": "Christian Hopps", "text": "

it almost sounds like remote is getting the sound from another mic off the in room speakers system

", "time": "2024-03-21T03:19:03Z"}, {"author": "Andrew Cooks", "text": "

@gyan, that's the most recent work I could find on the topic. It would need to be reinterpreted in terms of RFC 8362

", "time": "2024-03-21T03:19:09Z"}, {"author": "Lorenzo Miniero", "text": "

Anyone in the room there that can relay the message?

", "time": "2024-03-21T03:19:44Z"}, {"author": "John Scudder", "text": "

Might as well say \u201cdon\u2019t think of a pink elephant\u201d!

", "time": "2024-03-21T03:20:10Z"}, {"author": "John Scudder", "text": "

@Lorenzo Miniero what message, sorry?

", "time": "2024-03-21T03:20:42Z"}, {"author": "Lorenzo Miniero", "text": "

That the speaker mic is turned off

", "time": "2024-03-21T03:20:54Z"}, {"author": "Lorenzo Miniero", "text": "

(unless it sounds fine there and we're not getting it in the remote feed)

", "time": "2024-03-21T03:21:15Z"}, {"author": "Gyan Mishra", "text": "

Agreed based or LSA TLV based formatting

", "time": "2024-03-21T03:21:17Z"}, {"author": "John Scudder", "text": "

How about now?

", "time": "2024-03-21T03:21:30Z"}, {"author": "Abdussalam Baryun", "text": "

now better

", "time": "2024-03-21T03:21:36Z"}, {"author": "Lorenzo Miniero", "text": "

Thanks! In the meanwhile we've notified the AV team about the issue

", "time": "2024-03-21T03:21:50Z"}, {"author": "John Scudder", "text": "

Thanks!

", "time": "2024-03-21T03:22:01Z"}, {"author": "Gunter Van de Velde", "text": "

is online ok now

", "time": "2024-03-21T03:22:54Z"}, {"author": "Christian Hopps", "text": "

the gain is not the same

", "time": "2024-03-21T03:23:02Z"}, {"author": "Abdussalam Baryun", "text": "

now ok

", "time": "2024-03-21T03:23:15Z"}, {"author": "Boris Khasanov", "text": "

okay now

", "time": "2024-03-21T03:23:22Z"}, {"author": "Tony Przygienda", "text": "

I encourage operators to have a close look at this draft depending how they write/check RFPs or operate in deployment and hence want to query the model

", "time": "2024-03-21T03:23:37Z"}, {"author": "Tony Przygienda", "text": "

e.g. almost all RFPs are structured on RFC numbers and hence we are still discussing how to query for \"is this RFC supported\" and \"what things of this RFC are not supported?\"

", "time": "2024-03-21T03:24:28Z"}, {"author": "Tony Li", "text": "

Put the RFC number in the leaf description?

", "time": "2024-03-21T03:25:11Z"}, {"author": "Tony Przygienda", "text": "

yeah, but that's just an unstructured comment

", "time": "2024-03-21T03:25:27Z"}, {"author": "Tony Przygienda", "text": "

so a possibility is to have multiple ways to group the leaves, one of the things we were looking at

", "time": "2024-03-21T03:25:49Z"}, {"author": "Tony Li", "text": "

You could add a numeric attribute to each item.

", "time": "2024-03-21T03:25:58Z"}, {"author": "Les Ginsberg", "text": "

I would not like a BIS to trigger unnecessary updates.

", "time": "2024-03-21T03:26:50Z"}, {"author": "Tony Przygienda", "text": "

@Tony: yeah, a possible idea

", "time": "2024-03-21T03:27:21Z"}, {"author": "Tony Przygienda", "text": "

again, input from operators' experience would be good, their thinking about tooling they'd deploy

", "time": "2024-03-21T03:27:48Z"}, {"author": "Tony Li", "text": "

@Les: Features could update the YANG model, so no BIS would be necessary.

", "time": "2024-03-21T03:28:50Z"}, {"author": "Les Ginsberg", "text": "

I meant a BIS for the RFC defining the feature which is being described in the YANG model.

", "time": "2024-03-21T03:29:29Z"}, {"author": "Christian Hopps", "text": "

@Les Ginsberg hmm or the opposite if an original feature RFC get's bis'd don't you maybe want to know which RFC is supported by the router?

", "time": "2024-03-21T03:29:30Z"}, {"author": "Shraddha Hegde", "text": "

What about LFA mechanisms and related calculations? Is that taken into account?

", "time": "2024-03-21T03:29:48Z"}, {"author": "Les Ginsberg", "text": "

@Chris YOu want to know whether the new features defined in the BIS are supported.

", "time": "2024-03-21T03:30:03Z"}, {"author": "Les Ginsberg", "text": "

The RFC # isn't the key - as others stated it is just a comment.

", "time": "2024-03-21T03:30:41Z"}, {"author": "Christian Hopps", "text": "

makes sense

", "time": "2024-03-21T03:31:23Z"}, {"author": "Tony Przygienda", "text": "

hmm, how will that work with ECMP on reverse path, both interfaces are valid?

", "time": "2024-03-21T03:32:06Z"}, {"author": "Tony Przygienda", "text": "

@Shraddha: yeah, the LFA comment is +1

", "time": "2024-03-21T03:32:33Z"}, {"author": "Tony Przygienda", "text": "

pointless having 50ms failover to wait for SAVNET blackhole ;-)

", "time": "2024-03-21T03:32:51Z"}, {"author": "Tony Przygienda", "text": "

fix the mike pls. I ran out of volume on my hearing aid ;-)

", "time": "2024-03-21T03:33:26Z"}, {"author": "Acee Lindem", "text": "

It is very loud for me.

", "time": "2024-03-21T03:33:53Z"}, {"author": "Yingzhen Qu", "text": "

the current presenter is remote @Tony P

", "time": "2024-03-21T03:34:00Z"}, {"author": "Tony Przygienda", "text": "

hmm, ok.

", "time": "2024-03-21T03:34:26Z"}, {"author": "Yingzhen Qu", "text": "

@meetecho, please point the camera to the presenter

", "time": "2024-03-21T03:39:13Z"}, {"author": "Les Ginsberg", "text": "

@Tony: I think we have already used the MSD advertisements for things that don;t match that name. Give us a bit of slack here as regards naming...

", "time": "2024-03-21T03:45:28Z"}, {"author": "Tony Li", "text": "

I will give you slack now. I will repeat my complaint to those who defined MSD incorrectly in the first place.

", "time": "2024-03-21T03:46:08Z"}, {"author": "Christian Hopps", "text": "

:)

", "time": "2024-03-21T03:46:16Z"}, {"author": "Les Ginsberg", "text": "

That's fair.

", "time": "2024-03-21T03:46:22Z"}, {"author": "Tony Li", "text": "

And for this case, it would be nice not to compound the error.

", "time": "2024-03-21T03:47:26Z"}, {"author": "Tony Przygienda", "text": "

calling things names that don't mean what things are and calling different things same names are strong indications of confusion ;-)

", "time": "2024-03-21T03:47:36Z"}, {"author": "Srihari Sangli", "text": "

:)

", "time": "2024-03-21T03:48:05Z"}, {"author": "Les Ginsberg", "text": "

It is conceptualy similar - hate to waste a codepoint.

", "time": "2024-03-21T03:48:09Z"}, {"author": "Tony Li", "text": "

And causes confusion for other implementors and operators. Our job is to NOT do that.

", "time": "2024-03-21T03:48:11Z"}, {"author": "Tony Przygienda", "text": "

and Tony was more successful in his valiant defence of IGP not becoming a dump truck while the packets by now are a full dumpsite it seems ;-)

", "time": "2024-03-21T03:48:24Z"}, {"author": "Christian Hopps", "text": "

what's a hippity anyway?

", "time": "2024-03-21T03:48:35Z"}, {"author": "Ketan Talaulikar", "text": "

MSD value is 1 byte, which means we cannot go beyond 256 bytes for IPv6 EH ... so that is another aspect to consider ...

", "time": "2024-03-21T03:48:54Z"}, {"author": "Tony Przygienda", "text": "

_this_ could be a feature actually ;-) surely, as almost always in SR case, unintended but nevertheless ;-)

", "time": "2024-03-21T03:49:25Z"}, {"author": "Tony Li", "text": "

MSD is maximum SID depth. So 255 indicates 255 SIDs. How this corresponds to an IPv6 header is still unclear.

", "time": "2024-03-21T03:50:06Z"}, {"author": "Tony Li", "text": "

You COULD treat it as the number of /128's in the extension header, but as Ketan pointed out, there can be other extensions.

", "time": "2024-03-21T03:50:58Z"}, {"author": "Ketan Talaulikar", "text": "

https://datatracker.ietf.org/doc/draft-ietf-6man-eh-limits/ ... just to give an idea of where this work might be going

", "time": "2024-03-21T03:52:45Z"}, {"author": "Boris Khasanov", "text": "

@Ketan, thanks for pointing this work

", "time": "2024-03-21T03:53:31Z"}, {"author": "Yingzhen Qu", "text": "

please move camera to the presenter

", "time": "2024-03-21T03:59:06Z"}, {"author": "Liu Yao", "text": "

the summary of previous descussions about AHL in LSR and 6man can be found at https://mailarchive.ietf.org/arch/msg/lsr/iEMsMFntQceI3y67dOd2fdcq0g4/

", "time": "2024-03-21T04:02:09Z"}, {"author": "Liu Yao", "text": "

@Ketan Talaulikar yes, there're diffrent EH limits,AHL is one of them,and not all of them need to be signaled. Diffrent nodes may process different EHs, HBH/DOH/SRH,but for the intermediate nodes between intermediate endpoint nodes\uff0cthey wouldn\u2018t process SRH, just IPv6 header and at most HBH,so the total size of the header in the packet they need to process is not that big. But for intermediate endpoints\uff0cmaybe it's HBH+DOH+SRH with many TLVs\u3002

", "time": "2024-03-21T04:11:14Z"}, {"author": "Ketan Talaulikar", "text": "

@ Liu Yao, what I am looking for is what all info is needed and who is the consumer that is going to use them. As an example, I mentioned, ALH has no relevance on an transit IPv6 router - it only needs to process HBH.

", "time": "2024-03-21T04:12:50Z"}, {"author": "Ketan Talaulikar", "text": "

The point is that we need all sorts of limits depending on who is parsing what.

", "time": "2024-03-21T04:13:51Z"}, {"author": "Ketan Talaulikar", "text": "

My suggestion, please put together the whole story - then the WG can better understand what this is where it is going. Then comes the point if IGP is indeed the right place to put this.

", "time": "2024-03-21T04:14:43Z"}, {"author": "Shraddha Hegde", "text": "

IP flex-algo can be used as another alternative solution instead of new color extensions

", "time": "2024-03-21T04:19:13Z"}, {"author": "Mengxiao Chen", "text": "

@Shraddha, do you mean to use IP flex-algo for TE-tunnel shortcut?

", "time": "2024-03-21T04:22:40Z"}, {"author": "Shraddha Hegde", "text": "

@Mengxiao the IP flex-algo has ways to advertise prefixes with associated IP flex-algo which can match to the color of the tunnel to shortcut. As long as the number of colors are limited it's a possible solution

", "time": "2024-03-21T04:25:13Z"}, {"author": "Liu Yao", "text": "

@Ketan Talaulikar I can provide some analysis in SRv6 network (who will process what, and what are the limits on them)based on https://datatracker.ietf.org/doc/draft-ietf-6man-eh-limits/ and take it to the 6MAN as well\uff0cI think some packet dropping issues are not easy to solve, but we'll try and see.

", "time": "2024-03-21T04:27:13Z"}, {"author": "Mengxiao Chen", "text": "

@Peter Psenak, could you please help to provide the document you mentioned about coloring IGP prefix?

", "time": "2024-03-21T04:28:09Z"}, {"author": "Peter Psenak", "text": "

Standard IGP tags

", "time": "2024-03-21T04:28:38Z"}, {"author": "Acee Lindem", "text": "

For OSPF: https://datatracker.ietf.org/doc/draft-ietf-lsr-ospf-admin-tags/

", "time": "2024-03-21T04:29:49Z"}, {"author": "Changwang Lin", "text": "

It is possible to use tags to map colors, but tags are typically used for management and may be utilized for policy filtering. When multiple tags are present, it can be challenging to determine which tag is being used to represent a color.

", "time": "2024-03-21T04:30:05Z"}, {"author": "Mengxiao Chen", "text": "

@Shraddha, thanks a lot. I will check the IP flex-algo document.

", "time": "2024-03-21T04:30:31Z"}, {"author": "Christian Hopps", "text": "

I don't understand why it's difficult

", "time": "2024-03-21T04:31:17Z"}, {"author": "Changwang Lin", "text": "

@shraddha, the flex-algo is fundamentally for BE forwarding and cannot replace TE. Therefore, flex-algo and IGP shortcut are two different technologies that are not inherently related.

", "time": "2024-03-21T04:31:39Z"}, {"author": "Changwang Lin", "text": "

@Christian Hopps:Multiple tags could be attached to one prefix. There must be a mechanism for the
\nreceiver to know which tag is used as color.

", "time": "2024-03-21T04:32:33Z"}, {"author": "Christian Hopps", "text": "

yes, but that doesn't seem challenging to me

", "time": "2024-03-21T04:33:01Z"}, {"author": "Peter Psenak", "text": "

it is not

", "time": "2024-03-21T04:33:31Z"}, {"author": "Shraddha Hegde", "text": "

@Changwang SPF is BE forwarding and it stitches onto shortcut tunnels so I dont understand your concern

", "time": "2024-03-21T04:33:51Z"}, {"author": "Randy Bush", "text": "

when, or why, is a bundle not a bundle?

", "time": "2024-03-21T04:34:49Z"}, {"author": "Christian Hopps", "text": "

i mean typically you are doing things based on a tag being present. you don't really have to do anything more if that's the case.

", "time": "2024-03-21T04:34:51Z"}, {"author": "Mengxiao Chen", "text": "

do we have such mechanism now? sorry, I haven't followed the discussion on tags.

", "time": "2024-03-21T04:36:47Z"}, {"author": "Christian Hopps", "text": "

there's no mechnism if it's just \"do this if tag A is present\" \"do that if tag B is present\"

", "time": "2024-03-21T04:37:15Z"}, {"author": "Changwang Lin", "text": "

\uff20Shraddha Hegde: Each prefix corresponds to a flex-algo, and the essence of flex-algo computation is the BE forwarding calculated by all devices based on the same constraints. Meanwhile, the essence of IGP shortcut is TE forwarding.

", "time": "2024-03-21T04:39:12Z"}, {"author": "Srihari Sangli", "text": "

@Ketan, bundles are extensively deployed today, so opening up the bundle members as L3 interfaces is not a good option. I know you are not recommending it.

", "time": "2024-03-21T04:39:16Z"}, {"author": "Ketan Talaulikar", "text": "

@Srihari, no, that is definitely not a general recommendation :-)

", "time": "2024-03-21T04:40:02Z"}, {"author": "Mengxiao Chen", "text": "

it seems tags can be used at will, and the receiver needs to be decide how to handle them through local configuration. is my understanding correct?

", "time": "2024-03-21T04:41:45Z"}, {"author": "Peter Psenak", "text": "

you can split the tag space and use some of it to signal your color

", "time": "2024-03-21T04:43:29Z"}, {"author": "Changwang Lin", "text": "

If we use tags, multiple tags are required to accommodate management needs, and consistent constraints and definitions are necessary for interoperability between different devices.

", "time": "2024-03-21T04:43:40Z"}, {"author": "Randy Bush", "text": "

crickets

", "time": "2024-03-21T04:44:33Z"}, {"author": "Andrew Cooks", "text": "

reset here too

", "time": "2024-03-21T04:44:40Z"}, {"author": "Ketan Talaulikar", "text": "

meetecho reset

", "time": "2024-03-21T04:44:50Z"}, {"author": "Lorenzo Miniero", "text": "

Looking into it

", "time": "2024-03-21T04:45:29Z"}, {"author": "Tony Przygienda", "text": "

hutis_ cut more cables ;-)

", "time": "2024-03-21T04:45:49Z"}, {"author": "Yingzhen Qu", "text": "

we're waiting, please let us know when it's back

", "time": "2024-03-21T04:45:57Z"}, {"author": "Acee Lindem", "text": "

The remote people are able to communicate.

", "time": "2024-03-21T04:46:28Z"}, {"author": "Tony Przygienda", "text": "

well, it's only a draft about a new _fad_ ;-) so cannot be that important ;-)

", "time": "2024-03-21T04:46:33Z"}, {"author": "Christian Hopps", "text": "

move to the slide which shows the one sentence change :)

", "time": "2024-03-21T04:46:34Z"}, {"author": "Les Ginsberg", "text": "

You are back

", "time": "2024-03-21T04:46:35Z"}, {"author": "Gyan Mishra", "text": "

@Jie I understand the idea and it makes sense to be able to color different member links with different SLA queuing characteristics per SR Algo sub topology makes sense. I can see you want to have a single high capacity bundle with many member links but want to carry multiple Algo / NRPs on a bundle. Also you may want 1-1 or 1-many member link to NRP/Algo color mapping. Thank you

", "time": "2024-03-21T04:46:57Z"}]