[Idr] Re: WG adoption call for draft-scudder-idr-bgp4-rfc4271bis-00.txt - Ends 10/09/2025

[Robert Raszuk <[e-mail]>]

Hi Jimmy,

Ad 1)

But neither RFC 4271 nor RFC 4271 bis support IPv6. MP extensions and
AFI/SAFI are needed for other than IPv4 Unicast routing.

Your point is correct and we discussed it already; however based on my
observations adding MP-BGP and IPv6 to RFC4271bis is not going to happen.
It would be a rather significant rewrite.

Ad 2)

To your second point RFC6286 already addresses that point as a formal
update to RFC4271. Not sure if you are recommending merging RFC6286 with
4271bis.

Ad 3)

As far as redundant subsections ... only titles are redundant not entire
subsections:

5.1.4.  MULTI_EXIT_DISC

5.1.5.  MULTI_EXIT_DISC

&

9.2.1.1.  Frequency of Route Advertisement

9.2.1.2.  Frequency of Route Advertisement

Thx,
R.


On Thu, Oct 9, 2025 at 9:45 AM Dongjie (Jimmy) <jie.dong=
[e-mail]> wrote:

> Hi Keyur,
>
>
>
> I’ve read the -00 version of this draft and support its adoption. As
> discussed during the IDR session at IETF 123, this is a good starting
> point.
>
>
>
> I have the following few comments for the editors to consider:
>
>
>
> 1)       In section 3, the draft keeps the description about the term “IP
> address” as it was in RFC 4271:
>
>
>
> “In the context of this document, the term "IP address" refers to an IP
> Version 4 address [RFC791].”
>
>
>
> Since IPv6 has been widely deployed these years, it seems it would clearer
> for the bis to use “IPv4 address” throughout this document. And some text
> may be added to refer to RFC2545 for the support of IPv6.
>
>
>
> 2)       In section 1.1, the definition of BGP Identifier, currently it
> says:
>
>
>
> “A given BGP speaker sets the value of its BGP Identifier to an IP address
> assigned to that BGP speaker”.
>
>
>
> Does this assume a BGP speaker has at least one IPv4 address? May consider
> to relax or rephrase the text for BGP speakers with only IPv6 addresses.
>
>
>
> 3)       There are redundant subsections on “MULTI_EXIT_DISC” and
> “Frequency of Route Advertisement”.
>
>
>
>
>
> Best regards,
>
> Jie
>
>
>
> *From:* Keyur Patel <keyur=[e-mail]>
> *Sent:* Friday, September 26, 2025 2:45 AM
> *To:* idr <[e-mail]>
> *Subject:* [Idr] WG adoption call for
> draft-scudder-idr-bgp4-rfc4271bis-00.txt - Ends 10/09/2025
>
>
>
> Hi Folks,
>
>
>
> This is a Working Group adoption call for
> draft-scudder-idr-bgp4-rfc4271bis-00.txt,  “A Border Gateway Protocol 4
> (BGP-4)”.  Please reply to the list with your comments. This adoption call
> will conclude on October 9th, 2025.
>
>
>
> The draft can be found at:
> https://datatracker.ietf.org/doc/draft-scudder-idr-bgp4-rfc4271bis/.
>
>
>
> Best Regards,
>
> Keyur
> _______________________________________________
> Idr mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
>