Re: [GROW] Working Group Call for draft-msri-grow-bmp-bgp-rib-stats (start 06/Dec/2023 end 06/Jan/2024)

2024-01-19 Thread Zhuangshunwan 

Hi Mukul,

I have read draft-ietf-grow-bmp-bgp-rib-stats-00 and I think the description in 
your document is very clear and accurate. I think it's great to explicitly 
define Stat Type 7 and Stat Type 9 as counters for rib-in-pre-policy and also 
define counters for rib-in-post-policy.

Thanks,
Shunwan

From: Mukul Srivastava [mailto:msri=40juniper@dmarc.ietf.org]
Sent: Friday, January 19, 2024 11:01 PM
To: Zhuangshunwan ; Job Snijders ; 
grow@ietf.org
Subject: Re: [GROW] Working Group Call for draft-msri-grow-bmp-bgp-rib-stats 
(start 06/Dec/2023 end 06/Jan/2024)

Hi Shunwan

I looked at your proposed counter and I feel that they are already present in 
RFC 7854 for rib-in-pre-policy.
Copying it here from RFC 7854.

4.8.  Stats Reports


  o  Stat Type = 7: (64-bit Gauge) Number of routes in Adj-RIBs-In.


   o  Stat Type = 9: Number of routes in per-AFI/SAFI Adj-RIB-In.  The

  value is structured as: 2-byte Address Family Identifier (AFI),

  1-byte Subsequent Address Family Identifier (SAFI), followed by a

  64-bit Gauge.

For rib-in-post-policy, we don't have those counters and can be added. I will 
add them.
Let me know if you have any further comments.

Thanks
Mukul



Juniper Business Use Only
From: Mukul Srivastava mailto:m...@juniper.net>>
Date: Wednesday, January 17, 2024 at 9:15 AM
To: Zhuangshunwan 
mailto:zhuangshunwan=40huawei@dmarc.ietf.org>>,
 Job Snijders 
mailto:job=40fastly@dmarc.ietf.org>>, 
grow@ietf.org mailto:grow@ietf.org>>
Subject: Re: [GROW] Working Group Call for draft-msri-grow-bmp-bgp-rib-stats 
(start 06/Dec/2023 end 06/Jan/2024)
Thanks for the comments.  I will go over it and update docs accordingly.

Thanks
Mukul

From: GROW mailto:grow-boun...@ietf.org>> on behalf of 
Zhuangshunwan 
mailto:zhuangshunwan=40huawei@dmarc.ietf.org>>
Date: Saturday, December 9, 2023 at 3:27 AM
To: Zhuangshunwan 
mailto:zhuangshunwan=40huawei@dmarc.ietf.org>>,
 Job Snijders 
mailto:job=40fastly@dmarc.ietf.org>>, 
grow@ietf.org mailto:grow@ietf.org>>
Subject: Re: [GROW] Working Group Call for draft-msri-grow-bmp-bgp-rib-stats 
(start 06/Dec/2023 end 06/Jan/2024)
[External Email. Be cautious of content]


Hi GROW,

I've noticed this errata report under discussion: 
https://urldefense.com/v3/__https://mailarchive.ietf.org/arch/msg/grow/g1d3cJhNMuSnchQiqX0lkQCnQkk/__;!!NEt6yMaO-gk!GcBz8ozUcDW3DcFms2m15hiJUwCN7bBXSR3wS_UdvGYS603ApxdNMc2XqFW9jpNp1XgyHbKnvQqlauvtUtmAov7CA-Pm$
If GROW agrees that "the L flag is only applied to Route Monitoring messages", 
to distinguish between pre-policy statistics and post-policy statistics of the 
Adj-RIBs-In, I think the following types could be added for RIB-IN Statistics:

*  Type = TBD8: (64-bit Gauge) Number of routes in pre-policy Adj-RIBs-In.
*  Type = TBD9: (64-bit Gauge) Number of routes in post-policy Adj-RIBs-In.
*  Type = TBD10: Number of routes in per-AFI/SAFI pre-policy Adj-RIB-In.  The 
value is structured as: 2-byte Address Family Identifier (AFI), 1-byte 
Subsequent Address Family Identifier (SAFI), followed by a 64-bit Gauge.
*  Type = TBD11: Number of routes in per-AFI/SAFI post-policy Adj-RIB-In.  The 
value is structured as: 2-byte Address Family Identifier (AFI), 1-byte 
Subsequent Address Family Identifier (SAFI), followed by a 64-bit Gauge.

Waiting to hear your opinions, thanks.

Best regards,
Shunwan

> -Original Message-
> From: GROW [mailto:grow-boun...@ietf.org] On Behalf Of Zhuangshunwan
> Sent: Saturday, December 9, 2023 3:15 PM
> To: Job Snijders 
> mailto:job=40fastly@dmarc.ietf.org>>; 
> grow@ietf.org
> Subject: Re: [GROW] Working Group Call for
> draft-msri-grow-bmp-bgp-rib-stats (start 06/Dec/2023 end 06/Jan/2024)
>
>
> Hi Job, GROW,
>
> I have read the draft and support its adoption.
>
> Best regards,
> Shunwan
>
> > -Original Message-
> > From: GROW [mailto:grow-boun...@ietf.org] On Behalf Of Job Snijders
> > Sent: Wednesday, December 6, 2023 11:49 PM
> > To: grow@ietf.org
> > Subject: [GROW] Working Group Call for
> > draft-msri-grow-bmp-bgp-rib-stats (start 06/Dec/2023 end 06/Jan/2024)
> >
> > Dear GROW,
> >
> > The author of draft-msri-grow-bmp-bgp-rib-stats asked whether the GROW
> > working group could consider adoption of their internet-draft.
> >
> > This message is a request to the group for feedback on whether this
> > internet-draft should be adopted.
> >
> > Title: Definition For New BMP Statistics Type
> > Abstract:
> >   RFC 7854 defined different BMP statistics messages types to observe
> >   interesting events that occur on the router.  This document updates
> >   RFC 7854 by adding new statistics type.
> >
>

Re: [GROW] Peering API: Internet Draft submission

2024-01-19 Thread Christopher Morrow 
On Fri, Jan 19, 2024 at 11:55 AM Jenny Ramseyer  wrote:
>
> Thank you, I have joined the list now.
>
>
>
> I look forward to discussing with you all—please do let me know if anyone has 
> any feedback or questions on the draft.  I’ll be at the IETF 119 meeting, and 
> hope to meet some of you there.
>
>

I was corrected off list by a different reader/wg-member...

howdy this is JENNY not JEREMY.
I hope to have new glasses (srsly) before the next meeting ;(


>
> Thanks!
>
>
>
> Jenny
>
>
>
> From: GROW  on behalf of Christopher Morrow 
> 
> Date: Thursday, January 18, 2024 at 11:34 PM
> To: Jenny Ramseyer 
> Cc: grow@ietf.org , Matt Joras 
> Subject: Re: [GROW] Peering API: Internet Draft submission
>
> !---|
>   This Message Is From an Untrusted Sender
>   You have not previously corresponded with this sender.
> |---!
>
> Jeremy, you'll want to take a moment to join the mailing-list... else
> someone will have to keep accepting your mails in the mailman
> interface :)
> (delaying and unnecessarily gatekeeping your part of the conversation)
>
> thanks!
> -chris
> (also, thanks for the submission!)
>
> On Thu, Jan 18, 2024 at 11:32 PM Jenny Ramseyer
>  wrote:
> >
> > Hello GROW chairs,
> >
> >
> >
> > I’m Jenny Ramseyer, from Meta.  I have just submitted an Internet Draft, 
> > which I would like to share for your review.  I believe it falls under the 
> > GROW working group’s charter.
> >
> >
> > Here is the draft: 
> > https://datatracker.ietf.org/doc/draft-ramseyer-grow-peering-api/
> >
> >
> >
> > In this draft, I outline a proposed standard for programmatically 
> > configuring BGP peering connections through a machine-to-machine API.  With 
> > this work, I and my collaborators hope to standardize and simplify peering 
> > automation, and encourage fast, reliable, and cost-effective 
> > interconnection for networks.
> >
> >
> >
> > This work started as an extension of an earlier NANOG85 presentation: 
> > https://youtu.be/Cko5-lWyN60?si=4w_ZicpGIgGoyaTR .  Out of that 
> > presentation, we established a discussion group, and presented an early 
> > proposal at NANOG88: https://youtu.be/kMxsoplROYs?si=nKvkkL9aXa8pjAGw
> >
> > This draft is built from the discussions through that group, and is joint 
> > work with my collaborators at AWS, Cloudflare, Google, and FullCtl.
> >
> >
> >
> > As we are proposing a standard way to automate BGP interconnections with 
> > the goal of simplifying and encouraging peering, I am hoping that it would 
> > fall under your charter’s second goal: “Document and suggest operational 
> > solutions to problematic aspects of the currently deployed routing system.”
> >
> >
> >
> > I would like to request a talking slot at the upcoming GROW meeting at IETF 
> > 119 to discuss the draft.  Please let me know if you think this draft might 
> > meet your charter, and if it would be possible to discuss at the next GROW 
> > meeting.
> >
> >
> >
> > Thank you,
> >
> >
> >
> > Jenny Ramseyer
> >
> >
> >
> > ___
> > GROW mailing list
> > GROW@ietf.org
> > https://www.ietf.org/mailman/listinfo/grow
>
> ___
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow

___
GROW mailing list
GROW@ietf.org
https://www.ietf.org/mailman/listinfo/grow

Re: [GROW] Peering API: Internet Draft submission

2024-01-19 Thread Job Snijders 
On Wed, Jan 17, 2024 at 09:08:00PM +, Jenny Ramseyer wrote:
> I would like to request a talking slot at the upcoming GROW meeting at
> IETF 119 to discuss the draft.  Please let me know if you think this
> draft might meet your charter, and if it would be possible to discuss
> at the next GROW meeting.

I've added a talking slot for you to the agenda for the next meeting!

Kind regards,

Job
GROW co-chair

___
GROW mailing list
GROW@ietf.org
https://www.ietf.org/mailman/listinfo/grow

Re: [GROW] Peering API: Internet Draft submission

2024-01-19 Thread Jenny Ramseyer 
Thank you, I have joined the list now.

I look forward to discussing with you all—please do let me know if anyone has 
any feedback or questions on the draft.  I’ll be at the IETF 119 meeting, and 
hope to meet some of you there.

Thanks!

Jenny

From: GROW  on behalf of Christopher Morrow 

Date: Thursday, January 18, 2024 at 11:34 PM
To: Jenny Ramseyer 
Cc: grow@ietf.org , Matt Joras 
Subject: Re: [GROW] Peering API: Internet Draft submission
!---|
  This Message Is From an Untrusted Sender
  You have not previously corresponded with this sender.
|---!

Jeremy, you'll want to take a moment to join the mailing-list... else
someone will have to keep accepting your mails in the mailman
interface :)
(delaying and unnecessarily gatekeeping your part of the conversation)

thanks!
-chris
(also, thanks for the submission!)

On Thu, Jan 18, 2024 at 11:32 PM Jenny Ramseyer
 wrote:
>
> Hello GROW chairs,
>
>
>
> I’m Jenny Ramseyer, from Meta.  I have just submitted an Internet Draft, 
> which I would like to share for your review.  I believe it falls under the 
> GROW working group’s charter.
>
>
> Here is the draft: 
> https://datatracker.ietf.org/doc/draft-ramseyer-grow-peering-api/
>
>
>
> In this draft, I outline a proposed standard for programmatically configuring 
> BGP peering connections through a machine-to-machine API.  With this work, I 
> and my collaborators hope to standardize and simplify peering automation, and 
> encourage fast, reliable, and cost-effective interconnection for networks.
>
>
>
> This work started as an extension of an earlier NANOG85 presentation: 
> https://youtu.be/Cko5-lWyN60?si=4w_ZicpGIgGoyaTR
>  .  Out of that presentation, we established a discussion group, and 
> presented an early proposal at NANOG88: 
> https://youtu.be/kMxsoplROYs?si=nKvkkL9aXa8pjAGw
>
> This draft is built from the discussions through that group, and is joint 
> work with my collaborators at AWS, Cloudflare, Google, and FullCtl.
>
>
>
> As we are proposing a standard way to automate BGP interconnections with the 
> goal of simplifying and encouraging peering, I am hoping that it would fall 
> under your charter’s second goal: “Document and suggest operational solutions 
> to problematic aspects of the currently deployed routing system.”
>
>
>
> I would like to request a talking slot at the upcoming GROW meeting at IETF 
> 119 to discuss the draft.  Please let me know if you think this draft might 
> meet your charter, and if it would be possible to discuss at the next GROW 
> meeting.
>
>
>
> Thank you,
>
>
>
> Jenny Ramseyer
>
>
>
> ___
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow

___
GROW mailing list
GROW@ietf.org
https://www.ietf.org/mailman/listinfo/grow
___
GROW mailing list
GROW@ietf.org
https://www.ietf.org/mailman/listinfo/grow

[GROW] I-D Action: draft-ietf-grow-bmp-bgp-rib-stats-00.txt

2024-01-19 Thread internet-drafts 
Internet-Draft draft-ietf-grow-bmp-bgp-rib-stats-00.txt is now available. It
is a work item of the Global Routing Operations (GROW) WG of the IETF.

   Title:   Definition For New BMP Statistics Type
   Author:  Mukul Srivastava
   Name:draft-ietf-grow-bmp-bgp-rib-stats-00.txt
   Pages:   5
   Dates:   2024-01-19

Abstract:

   RFC 7854 defined different BMP statistics messages types to observe
   interesting events that occur on the router.  This document updates
   RFC 7854 by adding new statistics type.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-grow-bmp-bgp-rib-stats/

There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-grow-bmp-bgp-rib-stats-00

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts


___
GROW mailing list
GROW@ietf.org
https://www.ietf.org/mailman/listinfo/grow

Re: [GROW] Working Group Call for draft-msri-grow-bmp-bgp-rib-stats (start 06/Dec/2023 end 06/Jan/2024)

2024-01-19 Thread Mukul Srivastava 
Hi Job

I have submitted 'draft-ietf-grow-bmp-bgp-rib-stats-00'.

Thanks
Mukul



Juniper Business Use Only
From: GROW  on behalf of Job Snijders 

Date: Monday, January 8, 2024 at 4:46 AM
To: grow@ietf.org 
Subject: Re: [GROW] Working Group Call for draft-msri-grow-bmp-bgp-rib-stats 
(start 06/Dec/2023 end 06/Jan/2024)
[External Email. Be cautious of content]


Dear Working Group,

Thank you all for your comments and feedback. The
draft-msri-grow-bmp-bgp-rib-stats document has been adopted by the GROW
working group.

Mukul, please re-submit as 'draft-ietf-grow-bmp-bgp-rib-stats-00'

Additionally, we can work on IANA Early Allocation for codepoints.

Kind regards,

Job
GROW co-chair


On Wed, Dec 06, 2023 at 04:48:32PM +0100, Job Snijders wrote:
> Dear GROW,
>
> The author of draft-msri-grow-bmp-bgp-rib-stats asked whether the
> GROW working group could consider adoption of their internet-draft.
>
> This message is a request to the group for feedback on whether this
> internet-draft should be adopted.
>
> Title: Definition For New BMP Statistics Type
> Abstract:
>   RFC 7854 defined different BMP statistics messages types to observe
>   interesting events that occur on the router.  This document updates
>   RFC 7854 by adding new statistics type.
>
> The Internet-Draft can be found here:
> https://urldefense.com/v3/__https://www.ietf.org/archive/id/draft-msri-grow-bmp-bgp-rib-stats-00.html__;!!NEt6yMaO-gk!CPNC-mMNBnGxYEXZ-0R4WfX06dFeVenDZTG8gpdhwnZIYAW6ynLyOUQi9JXZ9AAEJ4liWArbJ2AP37WYEXgvSSQ3VSde$
>
> *** NOTE *** This draft has nothing other than BMP code point requests
> for counters. If adoption fails, the authors can go off an request FCFS
> instead.
>
> Please share with the mailing list if you would like this work to be
> adopted by GROW, are willing to review and/or otherwise contribute to
> this draft!
>
> WG Adoption call ends January 6th, 2024.
>
> Kind regards,
>
> Job / Chris
> GROW co-chairs

___
GROW mailing list
GROW@ietf.org
https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/grow__;!!NEt6yMaO-gk!CPNC-mMNBnGxYEXZ-0R4WfX06dFeVenDZTG8gpdhwnZIYAW6ynLyOUQi9JXZ9AAEJ4liWArbJ2AP37WYEXgvSebUR3Zj$
___
GROW mailing list
GROW@ietf.org
https://www.ietf.org/mailman/listinfo/grow

Re: [GROW] Working Group Call for draft-msri-grow-bmp-bgp-rib-stats (start 06/Dec/2023 end 06/Jan/2024)

2024-01-19 Thread Mukul Srivastava 
Hi Shunwan

I looked at your proposed counter and I feel that they are already present in 
RFC 7854 for rib-in-pre-policy.
Copying it here from RFC 7854.

4.8.  Stats Reports


  o  Stat Type = 7: (64-bit Gauge) Number of routes in Adj-RIBs-In.


   o  Stat Type = 9: Number of routes in per-AFI/SAFI Adj-RIB-In.  The

  value is structured as: 2-byte Address Family Identifier (AFI),

  1-byte Subsequent Address Family Identifier (SAFI), followed by a

  64-bit Gauge.

For rib-in-post-policy, we don’t have those counters and can be added. I will 
add them.
Let me know if you have any further comments.

Thanks
Mukul



Juniper Business Use Only
From: Mukul Srivastava 
Date: Wednesday, January 17, 2024 at 9:15 AM
To: Zhuangshunwan , Job Snijders 
, grow@ietf.org 
Subject: Re: [GROW] Working Group Call for draft-msri-grow-bmp-bgp-rib-stats 
(start 06/Dec/2023 end 06/Jan/2024)
Thanks for the comments.  I will go over it and update docs accordingly.

Thanks
Mukul

From: GROW  on behalf of Zhuangshunwan 

Date: Saturday, December 9, 2023 at 3:27 AM
To: Zhuangshunwan , Job Snijders 
, grow@ietf.org 
Subject: Re: [GROW] Working Group Call for draft-msri-grow-bmp-bgp-rib-stats 
(start 06/Dec/2023 end 06/Jan/2024)
[External Email. Be cautious of content]


Hi GROW,

I've noticed this errata report under discussion: 
https://urldefense.com/v3/__https://mailarchive.ietf.org/arch/msg/grow/g1d3cJhNMuSnchQiqX0lkQCnQkk/__;!!NEt6yMaO-gk!GcBz8ozUcDW3DcFms2m15hiJUwCN7bBXSR3wS_UdvGYS603ApxdNMc2XqFW9jpNp1XgyHbKnvQqlauvtUtmAov7CA-Pm$
If GROW agrees that "the L flag is only applied to Route Monitoring messages", 
to distinguish between pre-policy statistics and post-policy statistics of the 
Adj-RIBs-In, I think the following types could be added for RIB-IN Statistics:

*  Type = TBD8: (64-bit Gauge) Number of routes in pre-policy Adj-RIBs-In.
*  Type = TBD9: (64-bit Gauge) Number of routes in post-policy Adj-RIBs-In.
*  Type = TBD10: Number of routes in per-AFI/SAFI pre-policy Adj-RIB-In.  The 
value is structured as: 2-byte Address Family Identifier (AFI), 1-byte 
Subsequent Address Family Identifier (SAFI), followed by a 64-bit Gauge.
*  Type = TBD11: Number of routes in per-AFI/SAFI post-policy Adj-RIB-In.  The 
value is structured as: 2-byte Address Family Identifier (AFI), 1-byte 
Subsequent Address Family Identifier (SAFI), followed by a 64-bit Gauge.

Waiting to hear your opinions, thanks.

Best regards,
Shunwan

> -Original Message-
> From: GROW [mailto:grow-boun...@ietf.org] On Behalf Of Zhuangshunwan
> Sent: Saturday, December 9, 2023 3:15 PM
> To: Job Snijders ; grow@ietf.org
> Subject: Re: [GROW] Working Group Call for
> draft-msri-grow-bmp-bgp-rib-stats (start 06/Dec/2023 end 06/Jan/2024)
>
>
> Hi Job, GROW,
>
> I have read the draft and support its adoption.
>
> Best regards,
> Shunwan
>
> > -Original Message-
> > From: GROW [mailto:grow-boun...@ietf.org] On Behalf Of Job Snijders
> > Sent: Wednesday, December 6, 2023 11:49 PM
> > To: grow@ietf.org
> > Subject: [GROW] Working Group Call for
> > draft-msri-grow-bmp-bgp-rib-stats (start 06/Dec/2023 end 06/Jan/2024)
> >
> > Dear GROW,
> >
> > The author of draft-msri-grow-bmp-bgp-rib-stats asked whether the GROW
> > working group could consider adoption of their internet-draft.
> >
> > This message is a request to the group for feedback on whether this
> > internet-draft should be adopted.
> >
> > Title: Definition For New BMP Statistics Type
> > Abstract:
> >   RFC 7854 defined different BMP statistics messages types to observe
> >   interesting events that occur on the router.  This document updates
> >   RFC 7854 by adding new statistics type.
> >
> > The Internet-Draft can be found here:
> > https://urldefense.com/v3/__https://www.ietf.org/archive/id/draft-msri-grow-bmp-bgp-rib-stats-00.h__;!!NEt6yMaO-gk!GcBz8ozUcDW3DcFms2m15hiJUwCN7bBXSR3wS_UdvGYS603ApxdNMc2XqFW9jpNp1XgyHbKnvQqlauvtUtmAohLYbTUy$
> > tml
> >
> > *** NOTE *** This draft has nothing other than BMP code point requests
> > for counters. If adoption fails, the authors can go off an request FCFS
> instead.
> >
> > Please share with the mailing list if you would like this work to be
> > adopted by GROW, are willing to review and/or otherwise contribute to
> this draft!
> >
> > WG Adoption call ends January 6th, 2024.
> >
> > Kind regards,
> >
> > Job / Chris
> > GROW co-chairs
> >
> > ___
> > GROW mailing list
> > GROW@ietf.org
> >