Dear Mukul,
Thanks for posting a new version of the document.
Can you expand the "IANA Considerations" section a bit more?
Precise instructions from which sub-registries exactly codepoints need
to be allocated with what names would be good.
Right now the section reads: "This document requests
Dear GROW,
The author of draft-hmntsharma-bmp-tcp-ao 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: TCP-AO Protection for BGP Monitoring Protocol
Thanks Tom!
Looks like it was a good meeting.
I’ll wait for a next revision before issuing the call for the working group
adoption.
Kind regards,
Job
Co-chair GROW
On Thu, 21 Mar 2024 at 16:41, Tom Strickx wrote:
> Dear grow members, please find the minutes of the Peering API side meeting
>
On Sat, Mar 16, 2024 at 08:19:42PM -0400, Jeffrey Haas wrote:
> > Moreover, we know at least another IXP that dropped support for
> Extended Communities 2 years ago with big success, thus adopting
> such a practice from other fellow IXPs shouldn’t be of
> an issue as long as support for Large
On Mon, Mar 11, 2024 at 07:51:55PM +, Stavros Konstantaras wrote:
> Dear colleagues of GROW-WG,
>
> We (Stavros Konstantaras, Job Snijders and Moyaze Shivji) have submitted the
> draft-spaghetti-grow-bcp-ext-comms-00, which you can find it in the following
> URL: https://datatrack
Hi Jeff,
On Thu, Mar 14, 2024 at 10:54:54PM -0400, Jeff Haas wrote:
> I’m at least 90%, “Meh, whatever “ for the
> proposal as long as it doesn’t become a recommendation to filter
> the extended communities by default. For purposes of the adoption poll,
> consider this a conditional
On Thu, Mar 07, 2024 at 10:42:26AM -0500, Jeffrey Haas wrote:
> On Mon, Jan 22, 2024 at 08:34:58PM +0100, Job Snijders wrote:
> > Dear GROW working group,
> >
> > The IETF 119 meeting in Brisbane, "Down Under" is approaching!
> >
> > Through this em
Dear all,
The WGLC has concluded. A few people spoke out in favor of publication,
no objections were raised. I'll work on the shepherd write-up.
Thanks!
Kind regards,
Job
On Mon, Jan 22, 2024 at 08:20:36PM +0100, Job Snijders wrote:
> Dear all,
>
> As requested during the IETF
On Tue, Feb 06, 2024 at 09:11:12PM -0600, David Farmer wrote:
> If you keep it as updating RFC 7454, I believe you need to say it does
> so in the abstract. Also, somewhere in the document, probably in the
> introduction, you need to explain how it updates RFC 7454, that is how
> this document
> make sense.
>
> Thanks,
> mike
>
> -Original Message-
> From: Job Snijders
> Sent: Tuesday, February 6, 2024 11:13 AM
> To: Michael McBride
> Cc: grow@ietf.org
> Subject: Re: [GROW] I-D Action: draft-ietf-grow-as-path-prepending-09.txt
>
> Dear Mich
Dear Michael,
Before we proceed, can you clarify how exactly
draft-ietf-grow-as-path-prepending updates RFC 7454 and RFC 8195?
In relationship to 8195, the only sentence I see is "AS Path Prepending
is discussed in Use of BGP Large Communities [RFC8195]." - which is true
(8915 contains an
Dear GROW working group,
The IETF 119 meeting in Brisbane, "Down Under" is approaching!
Through this email we'd like to ask the GROW working group for agenda
items. We should have a 90 minute slot this time around.
Please email your presentation proposal to grow-cha...@ietf.org if you'd
like to
Dear all,
As requested during the IETF 118 GROW session in Prague, Czechia, a
"Working Group Last Call" is now issued for draft-ietf-grow-bmp-peer-up.
This phase will last about 2 weeks. We'd love to hear from you,
especially from BMP implementers!
Please review the document, consider whether it
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
On Mon, Jan 08, 2024 at 10:44:26AM +0100, Job Snijders wrote:
> Dear Working Group,
>
> Thank you all for your comments and feedback. The
> draft-fiebig-grow-bgpopsecupd document has been adopted by the GROW
> working group.
Apologies, the above sentence should of course read
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 re
+0100, Job Snijders wrote:
> Dear GROW,
>
> The author of draft-pels-grow-yang-bgp-communities 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-dr
Snijders wrote:
> Wed, Dec 06, 2023 at 04:42:05PM +0100, Job Snijders wrote:
> Dear GROW,
>
> The author of draft-fiebig-grow-bgpopsecupd asked whether the
> GROW working group could consider adoption of their internet-draft.
>
> This message is a request to the group fo
Dear Tom,
Did you watch the presentation on this topic in the IETF 118 GROW
session? https://youtu.be/vkU8qYzSt1c?si=zWKpMPfo0kW0DUgv=262
Kind regards,
Job
On Wed, Dec 06, 2023 at 05:05:53PM +, tom petch wrote:
> From: GROW on behalf of Job Snijders
>
> Sent: 06 December 2
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
Wed, Dec 06, 2023 at 04:42:05PM +0100, Job Snijders wrote:
Dear GROW,
The author of draft-fiebig-grow-bgpopsecupd 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
Dear GROW,
The author of draft-pels-grow-yang-bgp-communities 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: YANG Module for BGP Communities
Dear all,
This document has been adopted by the Working Group.
Authors, please submit the document as 'draft-ietf-grow-bmp-rel-00'
Kind regards,
Job
On Wed, Oct 25, 2023 at 12:57:08AM +0200, Job Snijders wrote:
> Dear GROW,
>
> The authors of draft-lucente-grow-bmp-rel asked whe
Dear Maximilian,
On Sun, Nov 26, 2023 at 02:45:58PM +0100, Maximilian Wilhelm wrote:
> Anno domini 2023 Maximilian Wilhelm scripsit:
>
> [...]
> > Some time has past and I don't see any new comments, neither here nor
> > to us authors.
> >
> > Hence I'd like to ask the chairs to start the WG
Dear all,
The todo items I noted for myself:
IETF 119: request 90 minutes
Call for working group adoption: draft-pels-grow-yang-bgp-communities
Call for working group adoption: draft-fiebig-grow-bgpopsecupd
Call for working group adoption: draft-msri-grow-bmp-bgp-rib-stats
Last Call:
Dear all,
The draft agenda for the GROW @ IETF 118 session has been uploaded here:
https://datatracker.ietf.org/doc/agenda-118-grow/
Let me know if we forgot someone or something, there still is some room.
Kind regards,
Job & Chris
GROW co-chairs
Dear GROW working group,
The IETF 118 meeting is approaching!
Through this email we'd like to ask the GROW working group for agenda
items.
Please email your presentation proposal to grow-cha...@ietf.org if you'd
like to present an update on an existing Internet-Draft, or would like
to bring new
Dear all,
I believe all todo items have been cleared now:
On Tue, Jul 25, 2023 at 04:43:01PM -0700, Christopher Morrow wrote:
> * note about BMP and TLV and how lovely the new world will be
I received word that potential concerns with bumping the version number
have been addressed and that
Dear GROW,
The authors of draft-lucente-grow-bmp-rel asked whether GROW
working group could consider adoption of the internet-draft.
This message is a request to the group for feedback on whether this
internet-draft should be adopted.
Title: Logging of routing events in BGP Monitoring Protocol
Dear GROW,
The authors of draft-francois-grow-bmp-loc-peer asked whether GROW
working group could consider adoption of the internet-draft.
This message is a request to the group for feedback on whether this
internet-draft should be adopted.
Title: BMP Loc-RIB: Peer address
Abstract:
BMP
On Fri, Sep 22, 2023 at 03:46:50PM +, John Scudder wrote:
> This version removes "BMP Peer Down Reason Codes” from the list of
> affected registries, per Tom Petch’s IETF LC review.
Thanks, good catch.
Kind regards,
Job
___
GROW mailing list
Job Snijders has requested publication of
draft-ietf-grow-bmp-registries-change-03 as Proposed Standard on behalf of the
GROW working group.
Please verify the document's state at
https://datatracker.ietf.org/doc/draft-ietf-grow-bmp-registries-change
; With overwhelmingly positive response, let's move this forward!
> > I'll see about sending the IESG bits forward in the next day.
> >
> > Thanks!
> > -chris
> >
> > On Wed, May 22, 2019 at 1:25 PM Job Snijders wrote:
> >>
> >> Dear G
gt; christopher.mor...@gmail.com> wrote:
> >
> > With overwhelmingly positive response, let's move this forward!
> > I'll see about sending the IESG bits forward in the next day.
> >
> > Thanks!
> > -chris
> >
> > On Wed, May 22, 2019 at 1:25 PM Job Snijders wr
Dear GROW working group,
The IETF 117 meeting is approaching!
Through this email we'd like to ask the GROW working group for agenda
items.
Please email your proposal to grow-cha...@ietf.org if you'd like to
present an update on an existing Internet-Draft, or would like to bring
new material to
Dear GROW,
It seems there is good support to adopt
draft-cppy-grow-bmp-path-marking-tlv as working group document.
Thank you all for your responses.
Authors, please upload the file as draft-ietf-grow-bmp-path-marking-tlv-00
Kind regards,
Job
On Thu, Mar 30, 2023 at 04:35:32AM +, Job
On Thu, Jun 01, 2023 at 01:43:42PM -0700, Chris Smiley wrote:
> Greetings,
>
> FYI - this report has been deleted as junk.
Thanks!
Kind regards,
Job
co-chair GROW
___
GROW mailing list
GROW@ietf.org
https://www.ietf.org/mailman/listinfo/grow
On Sat, May 27, 2023 at 08:43:59PM +0200, Maximilian Wilhelm wrote:
> Anno domini 2022 Job Snijders scripsit:
>
> > Thank you for your feedback! There was good support to adopt this
> > internet-draft and continue work on it as a working group document.
> >
> > Aut
Hi folks!
The minutes have been published:
https://datatracker.ietf.org/doc/minutes-116-grow-202303300400/
Many thanks to Peter Schoenmaker and Zhen Tan for observing the session
and taking minutes!
Kind regards,
Job
___
GROW mailing list
Dear GROW,
The authors of draft-cppy-grow-bmp-path-marking-tlv asked whether GROW
working group could consider adoption of the internet-draft.
This message is a request to the group for feedback on whether this
internet-draft should be adopted.
Title: BMP Extension for Path Status TLV
Abstract:
Dear all,
Just a reminder that we need to work on finalizing the agenda! Please
send grow-cha...@ietf.org requests for a slot during the IETF 116
GROW meeting!
Kind regards,
Job
On Thu, Feb 23, 2023 at 02:36:47PM +0100, Job Snijders wrote:
> Dear GROW working group,
>
> The IETF 11
Dear GROW working group,
The IETF 116 meeting is approaching!
We'd like to ask the GROW working group for agenda items.
Please email your proposal to grow-cha...@ietf.org if you'd like to
present an update on an existing Internet-Draft, or would like to bring
new material to the working group
Dear Jeff,
On Sun, Jan 29, 2023 at 08:28:27AM -0500, Jeffrey Haas wrote:
> On Sun, Jan 29, 2023 at 11:26:02AM +0100, Job Snijders wrote:
> > On Wed, Jan 25, 2023 at 05:17:08PM +, Sriram, Kotikalapudi (Fed) wrote:
> > > Please let us also know if you would have int
Dear Sriram, others,
(speaking as working group participant)
On Wed, Jan 25, 2023 at 05:17:08PM +, Sriram, Kotikalapudi (Fed) wrote:
> Please let us also know if you would have interest in providing an
> implementation.
Perhaps it is worthwhile adding a suggestion to the document for BGP
Dear Maximilian,
On Sat, Nov 26, 2022 at 11:17:06PM +0100, Maximilian Wilhelm wrote:
> thanks for the support!
>
> I re-uploaded the draft with the updated name.
>
> Chairs, I heard there is an option to ask for an early allocation for
> a community? I have to admit that I'm not deeply familar
ards,
Job
GROW co-chair
On Sat, Nov 05, 2022 at 03:48:16PM +0100, Job Snijders wrote:
> Dear GROW,
>
> The authors of draft-wilhelm-grow-anycast-community asked whether this
> working group could consider adoption of the internet-draft.
>
> This message is a request to the g
n Thu, Aug 25, 2022 at 04:20:18PM +0200, Job Snijders wrote:
> Hi GROW,
>
> At the IETF 114 GROW session Paolo asked whether this working group
> could consider adoption for draft-cptb-grow-bmp-yang.
>
> This message is a request to the group for feedback on whether this
> i
Dear GROW,
The authors of draft-wilhelm-grow-anycast-community asked whether this
working group could consider adoption of the internet-draft.
This message is a request to the group for feedback on whether this
internet-draft should be adopted.
Title: A well-known BGP community to denote
Hi GROW,
At the IETF 114 GROW session Paolo asked whether this working group
could consider adoption for draft-cptb-grow-bmp-yang.
This message is a request to the group for feedback on whether this
internet-draft should be adopted.
Title: BMP YANG Module
Abstract:
This document proposes a
On Thu, Jul 28, 2022 at 05:59:36PM -0400, Jeffrey Haas wrote:
> [In the context of the anycast community at-mic discussion during IETF-114]
>
> Grow WG,
>
> As part of the RFC process for Large BGP Communities, there was strong
> objection to having any large communities set aside for special
On Thu, Jul 28, 2022 at 03:16:24PM -0400, Christopher Morrow wrote:
> On Thu, Jul 28, 2022 at 9:02 AM Christopher Morrow
> christopher.mor...@gmail.com> wrote:
> > Howdy folks!
> > If you have a presentation slot, ideally know this already...
> > Ideally you ALSO have prepared slides?
> >
> > If
Dear Alexander, others,
On Tue, Jul 26, 2022 at 04:14:36PM +0300, Alexander Azimov wrote:
> The current version of the draft follows the wording from
> draft-ietf-idr-deprecate-as-set-confed-set
>
>BGP speakers conforming to this document (i.e., conformant BGP
>speakers) MUST NOT locally
Dear Sriram,
On Thu, 21 Jul 2022 at 14:08, Sriram, Kotikalapudi (Fed) <
kotikalapudi.sri...@nist.gov> wrote:
> Treating an UPDATE with an AS_SET as always 'Invalid' may be reasonable
> and simplifies the algorithm description except the diagnostic value of the
> 'Unverifiable' flavor is lost.
On Thu, 21 Jul 2022 at 10:37, Nick Hilliard wrote:
> Sriram, Kotikalapudi (Fed) wrote on 19/07/2022 22:24:
> > Question: Operationally, is an AS_SET ever used in the*middle*
> > between AS_SEQUENCEs? Or, should one simply give zero credence to
> > it?
>
> tl;dr: epsilon levels of credence.
:19PM +0200, Job Snijders wrote:
> Hi GROW,
>
> At the IETF 113 GROW session Paolo asked whether this working group
> could consider adoption for draft-lucente-grow-bmp-tlv-ebit.
>
> This message is a request to the group for feedback on whether this
> internet-draft should b
Dear Max,
On Tue, Jul 05, 2022 at 12:40:48PM +0200, Maximilian Wilhelm wrote:
> after some discussion at RIPE84 we took the time to formalize a draft
> to define a well-known BGP community to indicate a given prefix is
> carrying Anycast traffic. The intent is to allow ISPs to do well
> informed
Dear GROW working group,
The IETF 114 meeting is approaching!
We'd like to ask the GROW working group for agenda items.
Please email your proposal to grow-cha...@ietf.org if you'd like to
present an update on an existing Internet-Draft, or would like to bring
new material to the working group
Hi GROW,
At the IETF 113 GROW session Paolo asked whether this working group
could consider adoption for draft-lucente-grow-bmp-tlv-ebit.
This message is a request to the group for feedback on whether this
internet-draft should be adopted.
Title:
Support for Enterprise-specific TLVs in the
Hi all,
Here is the current draft GROW @ IETF 113 agenda:
https://datatracker.ietf.org/meeting/113/materials/agenda-113-grow-00.txt
Please let the chairs know if you'd also like to contribute agenda items.
Kind regards,
Job & Chris
___
On Tue, Mar 08, 2022 at 12:43:37AM +0100, Paolo Lucente wrote:
> I have processed all outstanding feedback for draft-ietf-grow-bmp-tlv, once
> again big thanks to Jeff Haas and Ben Maddison for their valuable new input,
> plus indeed all reviewers.
>
> May i ask <= 5 mins of time to summarize the
On Mon, Mar 07, 2022 at 11:06:55AM +0100, Camilo Cardona wrote:
> We just submitted a new draft proposing a yang module for configuring
> and managing BMP on a device.
>
> It would be nice to get some comments, observations, etc.
>
> Grow Chairs, will it be possible to get a 5 minute slot in the
Hi Randy, Emile,
A few small notes that might be of interest should you wish to progress
this draft:
* 32-bit ASNs don't fit in 16-bit fields. Consider using a set of
Extended Communities?
* The Local Administrator values {64994,64995,64996} might already
be in use and carry local
Hi GROW,
Cause for celebration for the WG, and Tim, Serpil, Manish, & Paolo! :-)
Thank you for your work (and patience, this doc took about 5 years!)
Kind regards,
Job
On Tue, Feb 15, 2022 at 10:25:03PM -0800, rfc-edi...@rfc-editor.org wrote:
> A new Request for Comments is now available in
Hi all,
(no hats)
On Thu, Feb 10, 2022 at 09:53:44PM +, Keyur Patel wrote:
> IDR is requesting input on the use of AS prepend in BGP policy. This
> begins a 2 week call for requested input on the beneficial use of AS
> Prepend. draft-ietf-grow-as-path-prepending-05.txt indicates there is
> a
it to
IESG territory.
Kind regards,
Job & Chris
Thu, Dec 02, 2021 at 04:10:43PM +0100, Job Snijders wrote:
> Hi Folks,
>
> Please take 15 minutes out of your day to review this *really short!*
> internet-draft. The authors were kind enough to make it only 3 pages of
peer_down messages as
> well.
>
> Best wishes
> Thomas
>
> -Original Message-
> From: GROW On Behalf Of Job Snijders
> Sent: Tuesday, November 16, 2021 5:16 PM
> To: Paolo Lucente
> Cc: grow@ietf.org grow@ietf.org
> Subject: Re: [GROW] On LC for draft-i
Dear all,
This starts the formal WGLC period which will run from November 16th
until December 1st 2021.
Please review https://datatracker.ietf.org/doc/html/draft-ietf-grow-bmp-tlv-06
and provide comments or feedback on the grow@ietf.org mailing list!
Kind regards,
Job
On Tue, Nov 16, 2021 at
Hi all,
As we've replaced frantically searching where the heck the room is in a
giant building with ... 'where the heck is the URL?!' :-)
For your convenience:
Meetecho: https://wws.conf.meetecho.com/conference/?group=grow==1
Agenda:
Hi everyone,
We're having a light meeting schedule this time around!
"Tuesday, 16:00-18:00 (UTC) - Session III"
https://datatracker.ietf.org/meeting/112/materials/agenda-112-grow-00
Please send slides no later than Monday, so we're ready to go on
Tuesday! :-)
If anyone has a last minute item
Dear GROW working group,
The virtual IETF 112 meeting is approaching! You can register here
https://registration.ietf.org/112/
We'd like to ask the working group for agenda items!
Please email your proposal to grow-cha...@ietf.org
Kind regards,
Job & Chris
GROW Chairs
Dear Sriram, Doug, others,
On Thu, Apr 29, 2021 at 01:06:58PM +, Sriram, Kotikalapudi (Fed) wrote:
> We (NIST) have released a new version of the NIST RPKI Monitor (v2.0):
>
> https://www.nist.gov/services-resources/software/nist-rpki-deployment-monitor
>
> We are open to adding more
t 07:34:22PM +0200, Job Snijders wrote:
> Dear Alvaro, draft authors,
>
> Perhaps it would be good to have a voice discussion? This might expedite
> figuring out a solution to how we describe things.
>
> From what I understand the BMP Loc-RIB draft to propose is that all BMP
>
On Mon, Apr 26, 2021 at 01:16:55AM +0200, Rayhaan Jaufeerally (IETF) wrote:
> > Consistent API that serves RIB data
>
> Initially I tried to avoid defining the exact API of the looking glass by
> pointing to https://tools.ietf.org/html/rfc8522, but unfortunately it does
> not strictly define the
Dear Alvaro, draft authors,
Perhaps it would be good to have a voice discussion? This might expedite
figuring out a solution to how we describe things.
>From what I understand the BMP Loc-RIB draft to propose is that all BMP
messages of the Loc-RIB instance type are 'synthesized', as the
On Wed, Mar 31, 2021 at 06:09:42PM -0400, Jeffrey Haas wrote:
> > There is already a separate draft in IDR that has passed WGLC, and it uses
> > a new transitive BGP Path Attribute 'Only to Customer (OTC)':
> > https://tools.ietf.org/html/draft-ietf-idr-bgp-open-policy-15
> > We view that as a
Dear Jakob,
On Wed, Mar 10, 2021 at 02:10:24AM +, Jakob Heitz (jheitz) wrote:
> Job, your suggestion kicks a different goal than
> draft-ietf-grow-route-leak-detection-mitigation does.
Yes, I'm aware I am suggesting a different approach to solve the problem
of route leaks.
>
On Wed, Mar 10, 2021 at 03:08:34AM +, Jakob Heitz (jheitz) wrote:
> >From the BGP speaker (client) implementation point of view,
>
> I would do it like this:
> The client keeps a ring buffer of data it sent to the server.
> The bottom of the buffer is at a certain sequence number.
> As
On Tue, Mar 09, 2021 at 08:44:18PM +, Jakob Heitz (jheitz) wrote:
> BMP is a one-way protocol. The BMP server sends nothing.
In the proposal at hand, the BMP server would send a client-specific
TCP_FAST_OPEN cookie (on top of TCP ACKs), and possibly eventually a TCP
RST, which is slightly
registry.
> Before that point, let me chat with the IDR co-chairs and ADs to what other
> options you have.
>
> Cheers, Sue
>
> -Original Message-
> From: Sriram, Kotikalapudi (Fed) [mailto:kotikalapudi.sri...@nist.gov]
> Sent: Sunday, March 7, 2021 6:26
Dear GROW,
(Removed sidrops@ from CC)
*Wearing a Working Group participant hat*
I reviewed draft-ietf-grow-route-leak-detection-mitigation-04 and it
appears to me there is a shortcut possible in the mitigation algorithm.
This shortcut in turn negates the need to specify any ASN in the "DO
Dear group,
Yesterday we had the pleasure to hear a report from Thomas Graf on new
BMP work.
The https://datatracker.ietf.org/doc/html/draft-tppy-bmp-seamless-session-00
document outlines a concept to allow BMP clients to resume 'an existing'
session with the BMP server, reducing the need to
Dear all,
To resolve a scheduling conflict, and because this meeting's agenda
allows it... the GROW meeting will start 1 hour later!
https://www.timeanddate.com/worldclock/meetingdetails.html?year=2021=3=8=13=0=0=16=248=64=224
I'll be in the room to make people aware we're starting a bit later.
Dear all,
I'd like to draw attention to our fairly empty agenda... please help fill
it! :-)
Kind regards,
GROW Chairs
Job & Chris
On Wed, Jan 27, 2021 at 3:35 PM Job Snijders wrote:
> Dear GROW working group,
>
> The virtual IETF 110 meeting is approaching! You can register
Job Snijders has requested publication of draft-ietf-grow-bmp-local-rib-09 as
Proposed Standard on behalf of the GROW working group.
Please verify the document's state at
https://datatracker.ietf.org/doc/draft-ietf-grow-bmp-local-rib/
___
GROW
Dear GROW working group,
The virtual IETF 110 meeting is approaching! You can register here
https://registration.ietf.org/110/
We'd like to ask the working group for agenda items!
Please email your proposal to grow-cha...@ietf.org
Kind regards,
Job & Chris
GROW Chairs
Dear Tim,
Hi Tim,
On Wed, Nov 04, 2020 at 05:49:48PM +, Tim Evens (tievens) wrote:
> [tievens] Agree. The draft itself has local in the name. Does it make
> sense to change the draft name or keep it as is?
The filename is not relevant, I'd leave it as-is. Ultimately the
document will have
Dear group, authors
As part of the sheperd write-up I am reviewing the
draft-ietf-grow-bmp-local-rib-07 Internet-Draft. Overall the document
looks good to me.
Please consider these notes as input from an individual working group
participant. The suggestions are editorial in nature, my focus on
Dear group,
Taking Alvaro's and other people's feedback into account, here is the
fourth version of the charter.
OK? good to go? Warren Kumari? :-)
Kind regards,
Job
GROW co-chair
Charter for Working Group
The purpose of GROW is to consider the operational problems associated
with the
Dear draft-ietf-grow-bmp-local-rib authors,
Are you aware of any IPR for draft-ietf-grow-bmp-local-rib?
IPR resources:
https://datatracker.ietf.org/ipr/about/
RFC 8179 "Intellectual Property Rights in IETF Technology"
https://tools.ietf.org/html/rfc8179
Kind regards,
Job
Chair GROW
I support adoption too
(no hats)
On Wed, Jul 29, 2020 at 05:19:07PM +, Christopher Morrow wrote:
> + the real slim-shady.
>
> On Wed, Jul 29, 2020 at 5:17 PM Christopher Morrow
> wrote:
> >
> > Howdy WG Folks!
> > There's been significant chatter on-list about:
> >
Dear all,
Below is a third revision of the charter proposal, we attempted to
incorporate all the feedback received so far, specifically Alvaro's.
Please let us know your feedback!
Kind regards,
Job & Chris
--
Charter for Working Group
Dear all,
I'd like to abandon draft-snijders-rpsl-via and mark it dead. I don't think we
can make the mechanism as proposed work in a meaningful way for common internet
deployments.
Describing "routing policy" (the *import* / *export* attributes in Autnum
objects) within the constrains of the
On Sun, Apr 12, 2020 at 08:39:58PM +0200, Robert Raszuk wrote:
> Would anyone be able to explain the below phenomenon?
>
> RPKI Origin validation marks net 45.227.254.0/24 as INVALID as it expects
> it to be originated by ASN: 395978
If you look at
Does anyone have agenda items for this specific meeting?
If things can wait a little bit we can request a virtual interim meeting
to accomodate what should've been handled this IETF around.
Kind regards,
Job
On Thu, Mar 05, 2020 at 04:34:56PM +, Chris Morrow wrote:
>
> Howdy folks! It's
Dear Alvaro,
Thank you for your comments.
On Thu, Nov 21, 2019 at 07:42:05PM -0800, Alvaro Retana wrote:
> > Finally, where appropriate, the GROW documents the operational
> > aspects of measurement, monitoring, policy, security, and VPN
> > infrastructures, and safe default behavior of
Forking this thread.
On Fri, Nov 22, 2019 at 03:44:26AM +, thomas.g...@swisscom.com wrote:
> Very good input regarding „Devise a BGP Community Description System
> to IESG.
>
> I think a YANG informational BGP community modell might be the right
> thing to do. I would volunteer to support
On Fri, Nov 22, 2019 at 1:58 AM Jeffrey Haas wrote:
>
> On Fri, Nov 22, 2019 at 01:44:03AM +0000, Job Snijders wrote:
> > Goals
> > * Provide stewardship and maintenance for the Multi-Threaded Routing
> > Toolkit (MRT)
>
> I think you may wish to narrow the sc
Dear all,
Below is a revision of the charter proposal.
Kind regards,
Job
Charter for GROW Working Group
===
The Border Gateway Protocol (BGP) is fundamental to the operation of the
Internet. In recent years, occurrences of BGP related operational issues
have
Dear all,
On Mon, Oct 28, 2019 at 07:21:13PM +, Job Snijders wrote:
> Milestones
> ==
>
> Jan 2020 - "Support for Local RIB in BGP Monitoring Protocol (BMP)" to IESG
> Feb 2020 - "BMP Peer Up Message Namespace" to IESG
> Apr 2020 - "Revis
Thanks for the heads-up!
On Mon, Nov 4, 2019 at 14:18 IETF Secretariat wrote:
> Dear Tim Evens, Serpil Bayraktar, Paolo Lucente, Kevin Mi, Shunwan Zhuang:
>
>
> An IPR disclosure that pertains to your Internet-Draft entitled "Support
> for
> Adj-RIB-Out in BGP Monitoring Protocol (BMP)"
>
1 - 100 of 279 matches
Mail list logo
