Re: [Idr] I-D Action: draft-ietf-idr-bgp-fwd-rr-00.txt

[Susan Hares <[e-mail]>]

Robert:

Thank you for your technical comments on this draft.  It will be counted as part of the WG LC.

As to procedural issues, splitting drafts is always a challenge procedurally.    Rather than cycle on procedural issues for CAR and CT drafts, I decided to simply split the drafts and let the working group give feedback on the drafts.   Please note that the status of this draft is experimental and not proposed standard.

No draft will go forward to publication unless it has:

  1.  Solid consensus WG LC results, and
  2.  2 implementations

Sue

From: Robert Raszuk <[e-mail]>
Sent: Friday, February 16, 2024 3:28 PM
To: Kaliraj Vairavakkalai <[e-mail]>
Cc: Igor Malyushkin <[e-mail]>; Natrajan Venkataraman <[e-mail]>; idr@ietf. org <[e-mail]>; Susan Hares <[e-mail]>; Keyur Patel <[e-mail]>; Jeff Haas <[e-mail]>; [e-mail]
Subject: Re: [Idr] I-D Action: draft-ietf-idr-bgp-fwd-rr-00.txt

Hi Kaliraj & Sue, > The text in this draft has been reviewed by WG, as part of draft-ct. I do not agree with this explanation/justification. If someone is not interested at all in CT draft lot's of sm
External ([e-mail]<mailto:[e-mail]>)
  Report This Email<https://protection.inkyphishfence.com/report?id=bmV0b3JnMTA1ODY5MTIvc2hhcmVzQG5kemguY29tLzFmNGFlOTM2MmE0NzVkMTljOWFmZjVmYTc1MjIzMDViLzE3MDgxMTUyNzguMjU=#key=0d202aea27e7ab78f59fd14c79d971e9>  FAQ<https://www.godaddy.com/help/report-email-with-advanced-email-security-40813>  GoDaddy Advanced Email Security, Powered by INKY<https://www.inky.com/protection-by-inky>


Hi Kaliraj & Sue,



> The text in this draft has been reviewed by WG, as part of draft-ct.



I do not agree with this explanation/justification. If someone is not

interested at all in CT draft lot's of smuggled features and extensions may

not get sufficient attention.



So I am very glad chairs recommended to remove it from the CT draft into a

separate document. As such I am afraid it would have a hard time to even

become an IDR WG document so I am not sure if the fact that some orthogonal

text was pulled out of WG document makes is automatically a WG document.



On the technical side just configured same CLUSTER_ID on both RRs/ABRs and

there is no issue.



Cheers,

R.





On Fri, Feb 16, 2024 at 8:28 PM Kaliraj Vairavakkalai <[e-mail]<mailto:[e-mail]>>

wrote:



> Hi Robert, Igor,

>

>

>

> To provide some context –

>

>

>

> The text in this draft has been reviewed by WG, as part of draft-ct.

>

>

>

>

> https://www.ietf.org/archive/id/draft-ietf-idr-bgp-ct-23.html#name-avoiding-loops-between-rout<https://shared.outlook.inky.com/link?domain=www.ietf.org&t=h.eJwVzcGugyAQQNFfaei2gGCp2lV_BWUQUgUzjDXpy_v3yvom5_6xHRf2vLBAtJWnlMdxiAjkRcZZWpxC_ICMTjq0nngtPDrk47zxibhuRaB1uSa7ArefHF1MM19y3gofgQ6AxDHvxG4X9q6bBHTCqjH9Y1BalmARyiu5bxBTXqXydwtD-9D23hmnhmmw3htvO6N125hRqq7plTK664U2VYWqYh4B6YW2fPe3OB-1uLOkfVn-fyO0SNw.MEUCIG8bwN7YzH0G4q20XGratOE6uXqiLt971XFWCWhsuetMAiEAw2ZEMtGUM9d7JDyZEErched04ap07GWJ6FNwQPzEJMY>

>

>

>

> During the WG Directorate and Chair reviews of draft-ct, it was suggested

> to pull out this section to a new draft, as the described problem is not

> specific to CT.

>

>

>

> This document history is described in:

>

>

>

>

> https://datatracker.ietf.org/doc/html/draft-ietf-idr-bgp-fwd-rr-00#appendix-A.1<https://shared.outlook.inky.com/link?domain=datatracker.ietf.org&t=h.eJwVzUkOgkAQheGrkHZrj9gMrvQoBdUthDFFEQ3Gu0tv35987yt2GsU9Ex3zut21RmBggnYIpPrAUS300ri0uuNp1EgQWaZd9kiyea0yvlESSWMusK5hxv4jn8qKayaG5M6BT8EaXxW1dXrrgML2mPHoVLtM2sYbhDovHNxKj7Zua4jRRyi9c7nxjbalqaz1rqyU80kNSaWlCcQPgu3YB3V-pIJnmfdx_P0BCkpCaw.MEUCIQDs6a6y03nq4wioyvzjyc3xvypAFmBFRCb010Y7YqGSWwIgQn27-Z2FXMm4ndn-whoTWbnZsPvd-OezAjCiv-BWBcc>

>

>

>

> I will cleanup the Author and Contributor list, to not inherit from

> draft-CT.

>

>

>

> About whether the problem being described is real or not, we can have

> further discussions, and clarify draft text as required. We hit these

> issues in our testing with LU and CT, and I think it is very likely to hit

> it in the field. That’s why it is important to document it.

>

>

>

> Just wanted to first clear the confusion on the origin/history of this

> draft. So that we can focus on technical discussion.

>

>

>

> IDR-chairs may want to add something.

>

>

>

> Thanks

>

> Kaliraj

>

> Juniper Business Use Only

>

> *From: *Robert Raszuk <[e-mail]<mailto:[e-mail]>>

> *Date: *Friday, February 16, 2024 at 9:49 AM

> *To: *Igor Malyushkin <[e-mail]<mailto:[e-mail]>>

> *Cc: *Kaliraj Vairavakkalai <[e-mail]<mailto:[e-mail]>>, Natrajan Venkataraman <

> [e-mail]<mailto:[e-mail]>>, idr@ietf. org <[e-mail]<mailto:[e-mail]>>

> *Subject: *Re: [Idr] I-D Action: draft-ietf-idr-bgp-fwd-rr-00.txt

>

> *[External Email. Be cautious of content]*

>

>

>

> Hey Igor,

>

>

>

> Well I think there is no problem to be solved here to start with.

>

>

>

> It looks to me like someone completely unfamiliar with IETF process or

> even BGP Route Reflection took a CT draft and deleted most text except

> Appendix A, Co-Authors, Contributors and part of References :)

>

>

>

> I am actually surprised that IETF Submit script allowed to post it with

> such document name. Looks like it is broken.

>

>

>

> Cheers,

>

> R.

>

>

>

>

>

> On Fri, Feb 16, 2024 at 6:37 PM Igor Malyushkin <[e-mail]<mailto:[e-mail]>>

> wrote:

>

> Hello all,

>

> Agreed with Robert. I thought too I missed the adoption call and was

> surprised to see the doc already adopted.

>

> About CT parts, to me they look like a some form of advertising, not sure

> they are necessary to express the problem statement at all. Not to mention

> that it looks like AIGP solves the problem in general.

>

>

>

> пт, 16 февр. 2024 г. в 19:27, Robert Raszuk <[e-mail]<mailto:[e-mail]>>:

>

> All,

>

>

>

> > draft-ietf-idr-bgp-fwd-rr-00.txt

>

>

>

> Also please kindly indicate why this text is posted as an IDR WG document

> as the format of the name suggests ...

>

>

>

> I do not recall any single discussion on this proposal on the IDR WG list