Sue, did you want to queue yourself at the end to talk about the adoption request for MNHA?
", "time": "2023-11-10T08:34:27Z"}, {"author": "Susan Hares", "text": "I have queued myself to announce the upcoming adoption call.
", "time": "2023-11-10T08:42:09Z"}, {"author": "John Scudder", "text": "Pet peeve, RFC 5492 is Capabilities ADVERTISEMENT, not \u201cnegotiation\u201d. BGP does not and has never \u201cnegotiated\u201d capabilities.
", "time": "2023-11-10T08:47:34Z"}, {"author": "Jeffrey Haas", "text": "At some point we should do some archive arch\u00e6ology. I certainly remember it being negotiation at one point, but it's certainly not how it's ended up.
", "time": "2023-11-10T08:48:59Z"}, {"author": "Jeffrey Haas", "text": "@ketan did you still want the queue?
", "time": "2023-11-10T08:49:14Z"}, {"author": "John Scudder", "text": "Jeffrey Haas said:
\n\n\nAt some point we should do some archive arch\u00e6ology. I certainly remember it being negotiation at one point, but it's certainly not how it's ended up.
\n
I did that investigation recently. It was totally sloppy wording on the part of the original authors, and nothing more. Mea maxima culpa. :-(
", "time": "2023-11-10T08:55:00Z"}, {"author": "Jeffrey Haas", "text": "Linda sounds a bit faint in the room. Is she audible remotely?
", "time": "2023-11-10T09:05:54Z"}, {"author": "Srihari Sangli", "text": "yes
", "time": "2023-11-10T09:06:14Z"}, {"author": "Randy Bush", "text": "minor need to up the vol knob
", "time": "2023-11-10T09:06:17Z"}, {"author": "Susan Hares", "text": "she is faint
", "time": "2023-11-10T09:06:25Z"}, {"author": "Jeffrey Haas", "text": "should be better.
", "time": "2023-11-10T09:06:37Z"}, {"author": "Loa Andersson", "text": "isn't an upcominf wglc a counter indication for early allocation
", "time": "2023-11-10T09:13:18Z"}, {"author": "Susan Hares", "text": "Ketan and Jeff - please continue to comment to linda's text on list.
", "time": "2023-11-10T09:14:43Z"}, {"author": "Jeffrey Haas", "text": "@loa for chat as well minutes, the draft has received enough changes that early allocation and wglc are probably premature. we'll continue iterating.
", "time": "2023-11-10T09:16:58Z"}, {"author": "Jeffrey Haas", "text": "https://datatracker.ietf.org/meeting/97/materials/slides-97-idr-code-point-management-02
", "time": "2023-11-10T09:18:52Z"}, {"author": "Jeffrey Haas", "text": "@linda
", "time": "2023-11-10T09:18:57Z"}, {"author": "John Scudder", "text": "I seem to have blundered into the CATS WG.
", "time": "2023-11-10T09:22:47Z"}, {"author": "Keyur Patel", "text": "We are trying our best to fix that :)
", "time": "2023-11-10T09:23:08Z"}, {"author": "Jeffrey Haas", "text": "The prior two presentations are a bit better focused on solving a targeted problem with shipping code. I agree that they are cats-domain issues.
\nThe current presentation is a bit more abstract and covers more the problem statements of what you do about cats-stuff in bgp(-like) protocols.
", "time": "2023-11-10T09:27:23Z"}, {"author": "Susan Hares", "text": "Is BGP-LS information + communities sufficient for this draft?
", "time": "2023-11-10T09:28:03Z"}, {"author": "Ketan Talaulikar", "text": "definition of \"domain\" is important here :-)
", "time": "2023-11-10T09:29:18Z"}, {"author": "Jeffrey Haas", "text": "bgp-ls might be helpful, but dynamicity will still be a point of discussion.
", "time": "2023-11-10T09:33:58Z"}, {"author": "Susan Hares", "text": "remote sound is coming and going..
", "time": "2023-11-10T09:42:02Z"}, {"author": "Jeffrey Haas", "text": "room mic is fine. @meetecho ?
", "time": "2023-11-10T09:42:17Z"}, {"author": "Susan Hares", "text": "Anyone else with remote sound issues?
", "time": "2023-11-10T09:42:44Z"}, {"author": "Randy Bush", "text": "level here in portland
", "time": "2023-11-10T09:42:55Z"}, {"author": "Lorenzo Miniero", "text": "Sounds fine to us
", "time": "2023-11-10T09:43:04Z"}, {"author": "Susan Hares", "text": "ok - so it is the ietf wifi in hotel.
", "time": "2023-11-10T09:43:21Z"}, {"author": "Loa Andersson", "text": "I had expected that the authors for both draft declared that they will work together
", "time": "2023-11-10T09:51:24Z"}, {"author": "Jeffrey Haas", "text": "Jie's document is the adopted work. We'd require collaboration anyway.
", "time": "2023-11-10T09:54:14Z"}, {"author": "Keyur Patel", "text": "https://datatracker.ietf.org/doc/html/draft-idr-bgp-rt-oscillation-01
", "time": "2023-11-10T09:54:28Z"}, {"author": "Loa Andersson", "text": "@jeff, sure but it is a bit odd that they don't say so
", "time": "2023-11-10T09:56:55Z"}, {"author": "Susan Hares", "text": "@ketan - concerned about non-Walled garden case?
", "time": "2023-11-10T10:03:26Z"}, {"author": "Louis Chan", "text": "for v4/v6 mapping, I agree with Ketan 1st comment. There is no need for extra work for mapping.
", "time": "2023-11-10T10:10:08Z"}, {"author": "Jeffrey Haas", "text": "This is a flavor of interdomain provisioning for cgnat. I agree with ketan that the ability to carry the v4 piece is covered by rfc 5549. The encapsulation and translation is the piece that seems to need further discussion.
", "time": "2023-11-10T10:11:00Z"}, {"author": "Jeffrey Haas", "text": "a further option might include a new tunnel encapsulation attribute feature.
", "time": "2023-11-10T10:11:27Z"}, {"author": "Jeffrey Haas", "text": "I believe the authors are primarily interested in solving the problem rather than what the pdus look like.
", "time": "2023-11-10T10:12:05Z"}, {"author": "Robert Raszuk", "text": "Indeed extension to tunnel encap attr was something I suggested on the list in respect to this proposal
", "time": "2023-11-10T10:12:32Z"}, {"author": "Keyur Patel", "text": "rfc5549 --> rfc8950 (5549 is obsoleted)
", "time": "2023-11-10T10:12:55Z"}, {"author": "Jeffrey Haas", "text": "another rfc that makes us feel old. at least most people have stopped saying \"2547\" when they talk about l3vpn.
", "time": "2023-11-10T10:13:27Z"}, {"author": "Keyur Patel", "text": "@srihari - consider reducing/limiting authorlist to 5 please
", "time": "2023-11-10T10:15:56Z"}, {"author": "Susan Hares", "text": "#srihari - 5 authors is requirement for adoption.
", "time": "2023-11-10T10:16:57Z"}, {"author": "Boris Khasanov", "text": "how to distinguish existing and 'updated/extended' tunnel encap attribute?
", "time": "2023-11-10T10:19:02Z"}, {"author": "Jeffrey Haas", "text": "TEA is TLV based. Implementations are required to be able to handle unknown contents.
", "time": "2023-11-10T10:19:36Z"}, {"author": "Loa Andersson", "text": "I think AIGP need to be expanded at first use
", "time": "2023-11-10T10:23:09Z"}, {"author": "Louis Chan", "text": "@Srihari, instead of Accumulated, operations, like min/max, could be included.
", "time": "2023-11-10T10:23:44Z"}, {"author": "Srihari Sangli", "text": "@Sue - I understand about the author limit. Will update author list for adoption
", "time": "2023-11-10T10:24:15Z"}, {"author": "Srihari Sangli", "text": "@Loa - I
", "time": "2023-11-10T10:25:37Z"}, {"author": "Srihari Sangli", "text": "@Loa - I'm interpreting your comment as the \"first\" router to convert AIGP tlv to Generic-metric tlv, so to avoid all routers to be upgraded. Is it ? I have an issue with that
", "time": "2023-11-10T10:26:19Z"}, {"author": "Srihari Sangli", "text": "@Louis - the normalization procedure allows different operations that operator can do. At the end, the ingress router needs to compare paths for end-to-end cost and accumulation will help there.
", "time": "2023-11-10T10:27:53Z"}, {"author": "Jeffrey Haas", "text": "@prz I'll unlock queue once presentation as over. There's a bug that stops the presentation when that setting is touched.
", "time": "2023-11-10T10:28:30Z"}]