[Bgp-autoconf] Plans on IETF 108? \\RE: Move forward with bgp autoconf requirements and design principle

["Dongjie (Jimmy)" <[e-mail]>]

Hi all,

Since I didn’t receive any feedback about the initial draft before the submission cut-off, I was not sure whether the current version can reflect the team’s opinion, thus it was not submitted yesterday.

I need some feedback about whether we should submit this draft when the submission reopens, and whether we want to present something to the WG on IETF 108.

Also it would be great if you could provide review suggestions or proposed text to improve this document. Thanks.

Best regards,
Jie

From: Bgp-autoconf [mailto:[e-mail]] On Behalf Of Dongjie (Jimmy)
Sent: Friday, July 10, 2020 12:45 AM
To: [e-mail]
Subject: Re: [Bgp-autoconf] Move forward with bgp autoconf requirements and design principle

Hi all,

As promised please find attached an updated version of the draft. I changed the draft title a little bit to better reflect the content and purpose. Thanks again to Randy for his effort on the initial version.

The design principles are listed in section 4 for further discussion. Some description about the candidate approaches draft-xu and draft-raszuk are added. The rest are some editorial changes.

Please review this document and provide your comments and suggestions, proposing text would be better. Note that the authorship and contributor of the design team document would be based on the contribution.

Although it may be quite challenging to get the draft ready before the submission cut-off, depending on the progress we made, perhaps we could have an -00 version first, then have it further revised before the meeting.

Many thanks,
Jie

From: 徐小虎(义先) [mailto:[e-mail]]
Sent: Thursday, July 9, 2020 9:47 AM
To: Bgp-autoconf <[e-mail]<mailto:[e-mail]>>; Randy Bush <[e-mail]<mailto:[e-mail]>>; Robert Raszuk <[e-mail]<mailto:[e-mail]>>; Dongjie (Jimmy) <[e-mail]<mailto:[e-mail]>>
Cc: [e-mail]<mailto:[e-mail]>
Subject: Re: [Bgp-autoconf] Move forward with bgp autoconf requirements and design principle

+1

------------------------------------------------------------------
From:Jeff Tantsura <[e-mail]<mailto:[e-mail]>>
Send Time:2020年7月9日(星期四) 02:02
To:Randy Bush <[e-mail]<mailto:[e-mail]>>; Robert Raszuk <[e-mail]<mailto:[e-mail]>>; Dongjie (Jimmy) <[e-mail]<mailto:[e-mail]>>
Cc:[e-mail] <[e-mail]<mailto:[e-mail]>>
Subject:Re: [Bgp-autoconf] Move forward with bgp autoconf requirements and design principle

Jie,

Sounds good, I don’t really see any convergence yet, so unbiased summary would be a great start

Cheers,
Jeff
On Jul 8, 2020, 8:47 AM -0700, Dongjie (Jimmy) <[e-mail]<mailto:[e-mail]>>, wrote:
Hi Randy and all,

It is good we agreed on the scope of this document is DC. Certainly in the design team we can analyze and discuss the difference between the design for DC and WAN, my understanding is the details about it does not belong to this document.

Coming back to the preparation of the draft deliverable, in addition to revising the existing text in the draft, my suggestion is to also add some brief description about each candidate solution regarding the functions, extensibility, etc., this may be similar to what was presented in the slides to the WG in last IETF meeting. I will work on some text and provide an update tomorrow. Any contribution to this is welcome.

As for the design principle (including which layer the protocol should be based on and the interaction with BGP), if we cannot reach agreement before the meeting, probably we could provide a summary of the considerations first, and ask for some feedbacks from the WG. Thoughts?

Best regards,
Jie

-----Original Message-----
From: Randy Bush [mailto:[e-mail]]
Sent: Monday, July 6, 2020 11:53 PM
To: Robert Raszuk <[e-mail]<mailto:[e-mail]>>
Cc: Dongjie (Jimmy) <[e-mail]<mailto:[e-mail]>>; [e-mail]<mailto:[e-mail]>
Subject: Re: [Bgp-autoconf] Move forward with bgp autoconf requirements
and design principle

The draft in question specifically adds WAN auto conf.

that was certainly not the intent; and it's not really there in the words.. on
the other hand, if we should keep an eye on the WAN as we design the LAN,
we should be aware of choices which might unnecessarily restriict ourselves
next year.

Then the L3 peer auto discovery is just deferred to
draft-ietf-lsvr-l3dl

also not intended. i did ask for your help stitching multicast in, and you
declined. perhaps you have time now.

However reading thorough draft-ietf-lsvr-l3dl it is clear that it is
not applicable to WAN.

it is not applicable to many things :)

as i said at the beginning, i do not think l3dl is really a serious candidate here.
otoh, we would be silly if we did not keep an eye to see if there are lessons to
be learned from it.

[ fwiw, i think the scalability added to lsoe to become l3dl was not
worth the complexity. but that is a discussion for another universe ]

randy

--
Bgp-autoconf mailing list
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/bgp-autoconf