Job Snijders has requested publication of draft-ietf-grow-bmp-peer-up-04 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-peer-up/
___
GROW ma
Dear authors,
As part of the sheperd write-up I ask you whehter you are aware of any
claims to intellectual property rights in relationship to this
internet-draft.
Please respond on-list
Kind regards,
Job
On Tue, Jun 11, 2024 at 03:51:23PM -0700, internet-dra...@ietf.org wrote:
> Internet-Draf
On Thu, Aug 15, 2024 at 02:28:46PM +0200, Tim Bruijnzeels wrote:
> It is unclear to me how section 9.3 of draft-ramseyer-grow-peering-api
> intends to use RPKI Signed Checklists (RSC) to prove authority for an
> ASN.
>
> I think it would be beneficial to have a dedicated RPKI object for
> this ins
Dear Q,
I'd revise the ASN.1 as following:
* use IA5String so the peeringApiUri field is somewhat similar to an
AccessDescription (which is a GeneralName CHOICE to an IA5String),
what you'd also find in a SubjectInfoAccess or AuthorityInfoAccess.
* Define after first use (as appears to be the
Dear all,
My apologies for not having closed this call sooner! There was some
support to adopt this work, and no objection.
@ Authors - please resubmit the draft named
draft-ietf-grow-bmp-loc-peer-00
Kind regards,
Job
GROW co-chair
On Tue, Oct 24, 2023 at 01:34:17PM +0200, Job Snijders wrote
Dear Dr.-Ing. Fiebig,
On Wed, 3 Jul 2024 at 20:31, Tobias Fiebig wrote:
> as indicated earlier, I just pushed the two stub drafts for the content
> removed from draft-ietf-grow-bgpopsecupd-01:
>
> https://datatracker.ietf.org/doc/draft-fiebig-grow-routing-ops-sec-inform/
>
> https://datatracker.
> > On Apr 9, 2024, at 5:03 AM, Michael McBride
> > wrote:
> >
> > Hi Job,
> >
> > Please let us know if there is anything needed to help progress this draft.
On Sun, Jun 23, 2024 at 01:04:56PM -0400, Jeffrey Haas wrote:
> Perhaps address the points raised here:
> https://mailarchive.ietf.org
Dear all,
There was some support for this document, and no objections.
Authors, please submit as draft-ietf-grow-bmp-tcp-ao
Kind regards,
Job
On Mon, Apr 29, 2024 at 11:54:23PM +0200, Job Snijders wrote:
> Dear GROW,
>
> The author of draft-hmntsharma-bmp-tcp-ao asked whether t
Dear GROW working group,
The IETF 120 meeting in Vancouver, "The 604" 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 pr
On Sat, Jun 08, 2024 at 12:04:38AM +0200, Robert Raszuk wrote:
> Maybe it is out of scope. Or perhaps scope is just too narrow.
>
> Anyhow ...
>
> Imagine I an IXP client advertising a prefix to RS which I want to be
> distributed only to some client's ASNs.
>
> So how do I signal such policy us
Dear Robert,
The objective of the draft at hand (draft-ietf-grow-ixp-ext-comms) is to
seek consensus on whether Extended Communities (RFC 4360) have a
relevant role at IXP Route Servers or not. Reducing the number of
classes of BGP communities to contemplate in IXP RS operations is likely
to simpl
On Fri, Jun 07, 2024 at 06:58:26PM -0400, Jeffrey Haas wrote:
> The torches and pitchforks operator crowd that rammed through large
> communities in the current form weren't interested in slowing down and
> discussing how that'd work.
At best "torches and pitchforks operator crowd" is an incrowd j
IXPs.
>>
>> That may also in fact encourage faster migration to LCs from Extended
>> Commuities.
>>
>> Thx a lot,
>> Robert
>>
>>
>> On Fri, Jun 7, 2024 at 9:39 PM Job Snijders > 40fastly@dmarc.ietf.org> wrote:
>>
>>> Thank
5, 2024 at 11:09 AM wrote:
>
>> Internet-Draft draft-ietf-grow-ixp-ext-comms-00.txt is now available. It
>> is a
>> work item of the Global Routing Operations (GROW) WG of the IETF.
>>
>>Title: Recommendation to avoid use of BGP Extended Communities at
&
Dear GROW,
The author of draft-ramseyer-grow-peering-api 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: Peering API
Abstract:
We propose an API s
FYI
-- Forwarded message -
From: Robert Sparks
Date: Wed, 15 May 2024 at 00:23
Subject: Mailing lists delivery issues update
To:
(see also https://www.ietf.org/blog/ietf-mailing-list-delivery-issues/).
During the period from 6May to 9May, not all messages sent to the
mailing l
Hello folks,
If you sent messages to the ietf and didn’t see those come through in the
GROW mailarchive, please send them again!
See below
Kind regards,
Job
-- Forwarded message -
From: Robert Sparks
Date: Thu, 9 May 2024 at 21:29
Subject: Update on ongoing mail delivery issue
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 t
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
Ab
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 Commu
in chair capacity
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 fol
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 abstention.
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 email
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
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 rela
t doesn't
> 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 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 example
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
nts.
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 i
04:42:05PM +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
> i
+0100, Job 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 gro
Dear Tom,
Did you watch the presentation on this topic in the IETF 118 GROW
session? https://youtu.be/vkU8qYzSt1c?si=zWKpMPfo0kW0DUgv&t=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 Decemb
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
Abs
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 be
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
Abstrac
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
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 Last
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: draft-ietf-g
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 bumpi
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 Loc-R
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
GROW@
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-c
h 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:
> >>
> >> Dea
r.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 Sn
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 t
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
GROW@ietf.o
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 fo
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 intere
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
sta
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 w
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
ob
On 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
&
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 prefixe
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 Y
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 pur
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 s
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.
T
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.
My
2 at 04:19: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-draf
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 T
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 fo
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 BG
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
___
GRO
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 significanc
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 on
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
Dear GROW working group,
The IETF 113 meeting is approaching!
We'd like to ask the GROW working group for agenda items.
Please email your proposal to grow-cha...@ietf.org
Kind regards,
Job & Chris
GROW Chairs
/^-^\ /^-^\
/ o o \V o o V
/ Y \
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
oring and 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 f
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&short=&item=1
Agenda: https://datatracker.ietf.org/meeting/112/materia
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 t
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 feature
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 r
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
Informat
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 lon
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.
> draft-ietf-grow-
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 messages
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 more
can ask for early allocation on the 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]
&g
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
Commun
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 re-t
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&month=3&day=8&hour=13&min=0&sec=0&p1=16&p2=248&p3=64&p4=224
I'll be in the room to make people
1 - 100 of 338 matches
Mail list logo