Re: [bess] Last Call: <draft-ietf-bess-bgp-sdwan-usage-19.txt> (BGP Usage for SD-WAN Overlay Networks) to Informational RFC

[John Scudder <[e-mail]>]

Yes, I noticed that, hence “no *IETF* specification”, it’s an individual draft. If the security model of the present spec relies on BGP-over-TLS, maybe a 00 individual contribution isn’t as firm a foundation as you’d like. 

Of course, I can’t speak for Roman, it’s his DISCUSS, I was just drawing attention to it.

—John

> On Feb 6, 2024, at 12:12 PM, Linda Dunbar <[e-mail]> wrote:
> 
> John,
> 
> There is a draft on BGP over TLS: https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-wirtgen-bgp-tls/__;!!NEt6yMaO-gk!EMln0MoNjY8Fex0l37MA8JE4Nvpdsho8KhznAatU81RneYnfGVqYueaJT2WggxyJfkcPuhO1uie8yo67KbfHq0s$
> We are working with the author to enhance the draft.
> 
> We will add the reference to BGP over TLS. And remove the BGP over DTLS.
> 
> Can those changes address your comments?
> 
> Thank you,
> Linda
> 
> -----Original Message-----
> From: John Scudder <[e-mail]>
> Sent: Tuesday, February 6, 2024 9:36 AM
> To: [e-mail]
> Cc: Andrew Alston - IETF <[e-mail]>; [e-mail]; [e-mail]; [e-mail]; [e-mail]
> Subject: Re: Last Call: <draft-ietf-bess-bgp-sdwan-usage-19.txt> (BGP Usage for SD-WAN Overlay Networks) to Informational RFC
> 
> I haven't done a full review of this document, but I did notice that Roman Danyliw balloted DISCUSS on version 15 [1], asking, among other things, "Are there pointers for BGP over DTLS? Over TLS?". This doesn't appear to have been addressed, either in Linda's reply to Roman [2], or in the text of the document. It seems ill-advised to be last calling a document with an unaddressed DISCUSS. For what it's worth, Roman's point seems to me to be on target - as far as I'm aware, there is no IETF specification for BGP over TLS, and I don't expect that there will ever be a specification for BGP over DTLS, given that BGP assumes a stream transport.
> 
> $0.02,
> 
> -John
> 
> [1] https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-ietf-bess-bgp-sdwan-usage/ballot/*draft-ietf-bess-bgp-sdwan-usage_roman-danyliw__;Iw!!NEt6yMaO-gk!EMln0MoNjY8Fex0l37MA8JE4Nvpdsho8KhznAatU81RneYnfGVqYueaJT2WggxyJfkcPuhO1uie8yo67tnMhp0o$
> [2] https://urldefense.com/v3/__https://mailarchive.ietf.org/arch/msg/bess/-AT3GpMR6rr6-ywB5vWD7EbGk0w/__;!!NEt6yMaO-gk!EMln0MoNjY8Fex0l37MA8JE4Nvpdsho8KhznAatU81RneYnfGVqYueaJT2WggxyJfkcPuhO1uie8yo67ip_VfT4$
> 
>> On Feb 1, 2024, at 11:58 AM, The IESG <[e-mail]> wrote:
>> 
>> 
>> The IESG has received a request from the BGP Enabled ServiceS WG
>> (bess) to consider the following document: - 'BGP Usage for SD-WAN Overlay Networks'
>> <draft-ietf-bess-bgp-sdwan-usage-19.txt> as Informational RFC
>> 
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to the
>> [e-mail] mailing lists by 2024-02-15. Exceptionally,
>> comments may be sent to [e-mail] instead. In either case, please
>> retain the beginning of the Subject line to allow automated sorting.
>> 
>> Abstract
>> 
>> 
>>  The document discusses the usage and applicability of BGP as the
>>  control plane for multiple SD-WAN scenarios. The document aims to
>>  demonstrate how the BGP-based control plane is used for large-
>>  scale SD-WAN overlay networks with little manual intervention.
>> 
>>  SD-WAN edge nodes are commonly interconnected by multiple types of
>>  underlay networks owned and managed by different network
>>  providers.
>> 
>> 
>> 
>> 
>> The file can be obtained via
>> https://urldefense.com/v3/__https://urld/__;!!NEt6yMaO-gk!EMln0MoNjY8Fex0l37MA8JE4Nvpdsho8KhznAatU81RneYnfGVqYueaJT2WggxyJfkcPuhO1uie8yo67G5eRVA0$
>> efense.com%2Fv3%2F__https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-i
>> etf-bess-bgp-sdwan-usage%2F__%3B!!NEt6yMaO-gk!E4My2sQFYwfDPTtjIaFd1jpC
>> RXVBB-u6OkgI3yHHnKfSsS4Kc80iA-x0qPn_krxB9c0LBSQsXvI1RN7dGgEtnA%24&data
>> =05%7C02%7Clinda.dunbar%40futurewei.com%7C1a3011314c3340c61f4a08dc2729
>> 9e48%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C638428306920978448%7
>> CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1
>> haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=kzAz9c%2BLozBWwbLB6YBJxN3QsIBU1
>> Fu%2Bv2BiXF2a6ek%3D&reserved=0
>> 
>> 
>> 
>> No IPR declarations have been submitted directly on this I-D.
>> 
>> 
>> 
>> 
>> 
>> _______________________________________________
>> IETF-Announce mailing list
>> [e-mail]
>> https://urldefense.com/v3/__https://urld/__;!!NEt6yMaO-gk!EMln0MoNjY8Fex0l37MA8JE4Nvpdsho8KhznAatU81RneYnfGVqYueaJT2WggxyJfkcPuhO1uie8yo67G5eRVA0$
>> efense.com%2Fv3%2F__https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2F
>> ietf-announce__%3B!!NEt6yMaO-gk!E4My2sQFYwfDPTtjIaFd1jpCRXVBB-u6OkgI3y
>> HHnKfSsS4Kc80iA-x0qPn_krxB9c0LBSQsXvI1RN5i_8mwVg%24&data=05%7C02%7Clin
>> da.dunbar%40futurewei.com%7C1a3011314c3340c61f4a08dc27299e48%7C0fee8ff
>> 2a3b240189c753a1d5591fedc%7C1%7C0%7C638428306920983211%7CUnknown%7CTWF
>> pbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6M
>> n0%3D%7C0%7C%7C%7C&sdata=Rp1mvl6HqT6OrlmZbcKKnl3GgVLNckjOiojGF%2BDj12I
>> %3D&reserved=0
>