On Fri, Nov 01, 2019 at 07:57:06PM +, Colin Petrie wrote:
> On 01/11/2019 19:22, Paolo Lucente wrote:
> >> The one addition I'd suggest for the document is that information about
> >> peer-up/down messages is needed to usefully decode some information or
> >> context about the other BMP message
On 01/11/2019 19:22, Paolo Lucente wrote:
>> The one addition I'd suggest for the document is that information about
>> peer-up/down messages is needed to usefully decode some information or
>> context about the other BMP messages. You'll want a bit of operational
>> procedure in your text about "
On 01/11/2019 19:04, Jeffrey Haas wrote:
> The one addition I'd suggest for the document is that information about
> peer-up/down messages is needed to usefully decode some information or
> context about the other BMP messages. You'll want a bit of operational
> procedure in your text about "pleas
Hi Jeff,
On 1 Nov 2019, at 19:04, Jeffrey Haas mailto:jh...@pfrc.org>>
wrote:
The one addition I'd suggest for the document is that information about
peer-up/down messages is needed to usefully decode some information or
context about the other BMP messages. You'll want a bit of operational
pr
Colin,
On Fri, Nov 01, 2019 at 04:19:59PM +, Colin Petrie wrote:
> I posted draft-petrie-grow-mrt-bmp-00,
> any and all comments are welcome.
>
> This was a result of a discussion I had with some people about using MRT
> as a storage format for BMP messages.
While we'
Hello Grow,
I posted draft-petrie-grow-mrt-bmp-00,
any and all comments are welcome.
This was a result of a discussion I had with some people about using MRT
as a storage format for BMP messages.
Thanks,
Colin
On 01/11/2019 16:45, internet-dra...@ietf.org wrote:
>
> A new version
The IESG has approved the following document:
- 'Multi-Threaded Routing Toolkit (MRT) Routing Information Export
Format
with BGP Additional Paths Extensions'
(draft-ietf-grow-mrt-add-paths-03.txt) as Proposed Standard
This document is the product of the Global Routing Operatio
Ben Campbell has entered the following ballot position for
draft-ietf-grow-mrt-add-paths-03: No Objection
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please refer
could consider them along with any other IETF Last Call
comments that you receive, and strive to resolve them through discussion or by
updating the draft.
Document: draft-ietf-grow-mrt-add-paths-03
Reviewer: Daniele Ceccarelli
Review Date: 2017-02-14
IETF LC End Date: 2017-02-15
Intended
nd WG chairs should treat
these comments just like any other last call comments.
Document : draft-ietf-grow-mrt-add-paths-03
Summary: Ready for publication as Proposed Standard
This document simply carries an extension to BGP forward into this
routing
information export format. It notes i
information, please see the FAQ at
<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
Document: draft-ietf-grow-mrt-add-paths-??
Reviewer: Vijay Gurbani
Review Date: 2017-02-13
IETF LC End Date: 2017-02-15
IESG Telechat date: Not scheduled for a telechat
Summary: Document is ready as a PS.
Major
Authors : Colin Petrie
Thomas King
Filename: draft-ietf-grow-mrt-add-paths-03.txt
Pages : 6
Date: 2017-01-14
Abstract:
This document updates the Multi-threaded Routing Toolkit (MRT) export
format for Border
Authors : Colin Petrie
Thomas King
Filename: draft-ietf-grow-mrt-add-paths-02.txt
Pages : 7
Date: 2017-01-08
Abstract:
This document updates the Multi-threaded Routing Toolkit (MRT) export
format for Border
Hi,
This is last call for draft-ietf-grow-mrt-add-paths. With IETF, and
Thanksgiving in the US, last call will end the 2nd of December.
Please provide all final comments or issues before this date. If you have read
the draft and feel it is ready to progres, those comments are appreciated too
Very much IMO:
Don't take meeting time slots to say "nothing's changed, the document's
ready". Just WGLC it. :-)
-- Jeff
On Tue, Oct 25, 2016 at 12:24:39PM +0200, Colin Petrie wrote:
> I'll be there, so if anyone thinks it needs discussion, I am happy to
> talk about it. Or we can just go for WG
from the on-line Internet-Drafts
>> directories.
>>> This draft is a work item of the Global Routing Operations of the IETF.
>>>
>>> Title : Multi-Threaded Routing Toolkit (MRT) Routing
>> Information Export Format with BGP Additional Paths Extensions
>
> > Authors : Colin Petrie
> > Thomas King
> > Filename: draft-ietf-grow-mrt-add-paths-01.txt
> > Pages : 7
> > Date: 2016-07-08
> >
> > Abstract:
> >This do
(MRT) Routing
> Information Export Format with BGP Additional Paths Extensions
> Authors : Colin Petrie
> Thomas King
> Filename: draft-ietf-grow-mrt-add-paths-01.txt
> Pages : 7
> Date: 2016-0
Authors : Colin Petrie
Thomas King
Filename: draft-ietf-grow-mrt-add-paths-01.txt
Pages : 7
Date: 2016-07-08
Abstract:
This document updates the Multi-threaded Routing Toolkit (MRT) export
format for
orking Group of
> the IETF.
>
> Title : Multi-Threaded Routing Toolkit (MRT) Routing
> Information Export Format with BGP Additional Paths Extensions
> Authors : Colin Petrie
> Thomas King
> Filename:
Extensions
Authors : Colin Petrie
Thomas King
Filename: draft-ietf-grow-mrt-add-paths-00.txt
Pages : 7
Date: 2016-01-05
Abstract:
This document updates the Multi-threaded Routing Toolkit (MRT) export
Oops! time passed... this looks to have finished successfully, could
the authors please submit a new version (catch all the comments you
care to) with the new proper naming as well?
thanks!
On Fri, Nov 6, 2015 at 7:42 AM, Rick Casarez wrote:
> Support.
>
> ---
> Cheers, Rick
>
>
Support.
---
Cheers, Rick
Experiences not things.
On Wed, Nov 4, 2015 at 10:38 PM, Colin Petrie wrote:
> On 05/11/15 10:20, Jon Mitchell wrote:
> > Nit for author - any reason why such short abbreviation for ADDPATH (AP)
> > in section 4/5 subtypes while unicast/multicast spell
On 05/11/15 10:20, Jon Mitchell wrote:
> Nit for author - any reason why such short abbreviation for ADDPATH (AP)
> in section 4/5 subtypes while unicast/multicast spelled out - would it
> be more readable as ADDPATH?
I was using the 'AS4' abbreviation that is already in place as a suggestion.
S
On 02/11/15 17:48 +1100, Christopher Morrow wrote:
> Please consider this the start of a 3 week Adoption call for the noted
> draft who's abstract is:
>"This document updates the Multi-threaded Routing Toolkit (MRT) export
>format for Border Gateway Protocol (BGP) routing information by
>
Support
On Nov 3, 2015 7:45 PM, "Thomas King" wrote:
> Hi all,
>
> I support this draft as Add-Path is important as well as MRT is.
>
> Best regards,
> Thomas
>
> > On 2 Nov 2015, at 15:48, Christopher Morrow <
> christopher.mor...@gmail.com> wrote:
> >
> > Howdy WG folks,
> >
> > Please consider
Hi all,
I support this draft as Add-Path is important as well as MRT is.
Best regards,
Thomas
> On 2 Nov 2015, at 15:48, Christopher Morrow
> wrote:
>
> Howdy WG folks,
>
> Please consider this the start of a 3 week Adoption call for the noted
> draft who's abstract is:
> "This document up
2, 2015 11:25 AM
> To: Jeffrey Haas
> Cc: grow-cha...@ietf.org; grow@ietf.org grow@ietf.org;
> grow-...@tools.ietf.org
> Subject: Re: [GROW] Working Group Adoption Call:
> draft-petrie-grow-mrt-add-paths
>
> Mon, Nov 02, 2015 at 05:27:15PM +0900, Jeffrey Haas:
>>> Pleas
@ietf.org;
grow-...@tools.ietf.org
Subject: Re: [GROW] Working Group Adoption Call:
draft-petrie-grow-mrt-add-paths
Mon, Nov 02, 2015 at 05:27:15PM +0900, Jeffrey Haas:
> > Please consider this the start of a 3 week Adoption call for the
> > noted draft who's abstract is:
>
Mon, Nov 02, 2015 at 05:27:15PM +0900, Jeffrey Haas:
> > Please consider this the start of a 3 week Adoption call for the noted
> > draft who's abstract is:
> > "This document updates the Multi-threaded Routing Toolkit (MRT) export
> > format for Border Gateway Protocol (BGP) routing informatio
I support the adoption of this draft.
Thomas
http://exa.net.uk/about/contact-us
On 2 Nov 2015, at 6:48, Christopher Morrow wrote:
> Howdy WG folks,
>
> Please consider this the start of a 3 week Adoption call for the noted
> draft who's abstract is:
> "This document updates the Multi-threaded R
> On Nov 2, 2015, at 3:48 PM, Christopher Morrow
> wrote:
>
> Howdy WG folks,
>
> Please consider this the start of a 3 week Adoption call for the noted
> draft who's abstract is:
> "This document updates the Multi-threaded Routing Toolkit (MRT) export
> format for Border Gateway Protocol
I support adoption of this draft.
Job
___
GROW mailing list
GROW@ietf.org
https://www.ietf.org/mailman/listinfo/grow
Howdy WG folks,
Please consider this the start of a 3 week Adoption call for the noted
draft who's abstract is:
"This document updates the Multi-threaded Routing Toolkit (MRT) export
format for Border Gateway Protocol (BGP) routing information by
extending it to support the Advertisement
Grow folks,
Can we read/review/discuss this draft for the next 3 wks (so people
traveling to/from yokohama can review as well) ending 11/16/2015 (Nov
16).
Draft: draft-petrie-grow-mrt-add-path
Abstract:
This document updates the Multi-threaded Routing Toolkit (MRT) export
format for Border
let's ask!
On Sun, Oct 25, 2015 at 7:58 AM, Colin Petrie wrote:
> Yes, I think it is appropriate - assuming the wg concurs
>
> On 24/10/15 03:32, Christopher Morrow wrote:
>> This would be good, yes... are you aiming to ask for wg adoption for
>> this perhaps?
>>
>> On Thu, Oct 22, 2015 at 1:04
Yes, I think it is appropriate - assuming the wg concurs
On 24/10/15 03:32, Christopher Morrow wrote:
> This would be good, yes... are you aiming to ask for wg adoption for
> this perhaps?
>
> On Thu, Oct 22, 2015 at 1:04 PM, Colin Petrie wrote:
>> On 19/10/15 21:54, Jeffrey Haas wrote:
>>> Thi
This would be good, yes... are you aiming to ask for wg adoption for
this perhaps?
On Thu, Oct 22, 2015 at 1:04 PM, Colin Petrie wrote:
> On 19/10/15 21:54, Jeffrey Haas wrote:
>> This seems to be a very straight forward proposal. I suspect it should be
>> adopted and quickly moved through revi
On 19/10/15 21:54, Jeffrey Haas wrote:
> This seems to be a very straight forward proposal. I suspect it should be
> adopted and quickly moved through review toward RFC.
Thanks for the feedback, Jeff.
The next question would be - can anyone see anything flawed with the
approach? :)
Cheers
Colin
On Sun, Oct 11, 2015 at 07:42:49PM +0200, Colin Petrie wrote:
> This is a -00 individual draft contribution.
> Any comments and suggestions are welcome.
> I'm happy to present on this at IETF94 if there is interest.
This seems to be a very straight forward proposal. I suspect it should be
adopted
Hello Grow,
This is a -00 individual draft contribution.
Any comments and suggestions are welcome.
I'm happy to present on this at IETF94 if there is interest.
Regards,
Colin
Forwarded Message
Subject: New Version Notification for draft-petrie-grow-mrt-add-paths-00.txt
On Fri, Dec 7, 2012 at 12:52 PM, Christopher Morrow
wrote:
> On Thu, Nov 29, 2012 at 3:00 AM, Mattia Rossi
> wrote:
>> Am 28.11.2012 13:01, schrieb Arturo Servin:
>>
>>> Chris,
>>>
>>> The problem that I had is that it pybgpdum requires dpkt and it
>>> did not
>>> support 4 byte ASN and y
On Thu, Nov 29, 2012 at 3:00 AM, Mattia Rossi
wrote:
> Am 28.11.2012 13:01, schrieb Arturo Servin:
>
>> Chris,
>>
>> The problem that I had is that it pybgpdum requires dpkt and it
>> did not
>> support 4 byte ASN and you need a hack.
>>
>> Not sure if that is was problem as well.
On Thu, Nov 29, 2012 at 3:09 AM, Mattia Rossi
wrote:
> Am 28.11.2012 19:41, schrieb Christopher Morrow:
>
>> On Wed, Nov 28, 2012 at 12:47 PM, Pedro Andres Aranda Gutierrez
>> wrote:
>>>
>>> I had to write my own MRT parser library for my PhD. After my defense
>>> next January, I plan to release
Am 28.11.2012 19:41, schrieb Christopher Morrow:
On Wed, Nov 28, 2012 at 12:47 PM, Pedro Andres Aranda Gutierrez
wrote:
I had to write my own MRT parser library for my PhD. After my defense
next January, I plan to release it. (one step at a time, I'm quite
busy right now preparing the defense ;
Am 28.11.2012 13:01, schrieb Arturo Servin:
Chris,
The problem that I had is that it pybgpdum requires dpkt and it did not
support 4 byte ASN and you need a hack.
Not sure if that is was problem as well. If it were, let me know and I
will try to remember what I did to make it wo
On Wed, Nov 28, 2012 at 06:47:02PM +0100, Pedro Andres Aranda Gutierrez wrote:
> I had to write my own MRT parser library for my PhD. After my defense
> next January, I plan to release it. (one step at a time, I'm quite
> busy right now preparing the defense ;-) ) It's written in Java. Re:
> pybgpd
example: BGPDUMP_TYPE_ZEBRA_BGP instead BGP4MP.
>>
>> https://bitbucket.org/ripencc/bgpdump/wiki/Home
>> They say: "This format is described in the Internet Draft grow-mrt-13."
>>
>> According to what they says the lib follow a draft. I don't think it
Unfortunately the source code still use some defines that not follow
> RFC-6396, example: BGPDUMP_TYPE_ZEBRA_BGP instead BGP4MP.
>
> https://bitbucket.org/ripencc/bgpdump/wiki/Home
> They say: "This format is described in the Internet Draft grow-mrt-13."
>
> According t
;This format is described in the Internet Draft grow-mrt-13."
According to what they says the lib follow a draft. I don't think it's
a big problem because no big changes was done since MRT draft 13 until
RFC-6396 but could be a good idea to update the documentation and
nomenclatures
Chris,
The problem that I had is that it pybgpdum requires dpkt and it did not
support 4 byte ASN and you need a hack.
Not sure if that is was problem as well. If it were, let me know and I
will try to remember what I did to make it work but I think this is the
place with the answ
On Tue, Nov 27, 2012 at 1:20 PM, Jared Mauch wrote:
>
> On Nov 27, 2012, at 12:58 PM, Christopher Morrow wrote:
>
>> On Tue, Nov 27, 2012 at 11:43 AM, Mattia Rossi
>> wrote:
>>> (http://jon.oberheide.org/projects/pybgpdump/) which is very nice for a
>>> quick analysis of MRT dumps.
>>
>> sadly jo
On Nov 27, 2012, at 12:58 PM, Christopher Morrow wrote:
> On Tue, Nov 27, 2012 at 11:43 AM, Mattia Rossi
> wrote:
>> (http://jon.oberheide.org/projects/pybgpdump/) which is very nice for a
>> quick analysis of MRT dumps.
>
> sadly jon's tool is ... not very well updated :( or gives me lots and
On Tue, Nov 27, 2012 at 11:43 AM, Mattia Rossi
wrote:
> (http://jon.oberheide.org/projects/pybgpdump/) which is very nice for a
> quick analysis of MRT dumps.
sadly jon's tool is ... not very well updated :( or gives me lots and
LOTS of error messages on reading current routeviews/ris update
stre
this document:
http://tools.ietf.org/id/draft-ietf-grow-mrt-04.txt
Thx,
R.
It's an RFC now --
http://tools.ietf.org/html/rfc6396
Unfortunately, section 4.3.4 does not match the
current Quagga/libbgpdump implementations. The RFC
says to omit the AFI/SAFI/NLRI fields in the MP_REACH
>> R.
>>
>> On Tue, Nov 27, 2012 at 5:28 PM, Larry Blunk wrote:
>>>
>>> On 11/27/2012 11:17 AM, Robert Raszuk wrote:
>>>>
>>>>
>>>> Hello,
>>>>
>>>> Does anyone (in particular cc-ed authors)
the status,
planned update, planned progress to RFC of this document:
http://tools.ietf.org/id/draft-ietf-grow-mrt-04.txt
Thx,
R.
It's an RFC now --
http://tools.ietf.org/html/rfc6396
Unfortunately, section 4.3.4 does not match the
current Quagga/libbgpdump implementations. The RFC
pdate, planned progress to RFC of this document:
http://tools.ietf.org/id/draft-ietf-grow-mrt-04.txt
Thx,
R.
It's an RFC now --
http://tools.ietf.org/html/rfc6396
Unfortunately, section 4.3.4 does not match the
current Quagga/libbgpdump implementations. The RFC
says to omit the AFI
>> Hello,
>>
>> Does anyone (in particular cc-ed authors) recall what is the status,
>> planned update, planned progress to RFC of this document:
>>
>> http://tools.ietf.org/id/draft-ietf-grow-mrt-04.txt
>>
>> Thx,
>> R.
>>
>
> It's
lar cc-ed authors) recall what is the status,
>> planned update, planned progress to RFC of this document:
>>
>> http://tools.ietf.org/id/draft-ietf-grow-mrt-04.txt
>>
>> Thx,
>> R.
>> ___
>> GR
On 11/27/2012 11:17 AM, Robert Raszuk wrote:
Hello,
Does anyone (in particular cc-ed authors) recall what is the status,
planned update, planned progress to RFC of this document:
http://tools.ietf.org/id/draft-ietf-grow-mrt-04.txt
Thx,
R.
It's an RFC now --
http://tools.ietf.org
http://tools.ietf.org/html/rfc6396
On Nov 27, 2012, at 11:17 AM, Robert Raszuk wrote:
> Hello,
>
> Does anyone (in particular cc-ed authors) recall what is the status,
> planned update, planned progress to RFC of this document:
>
> http://tools.ietf.org/id/draft-ietf-grow-m
Hello,
Does anyone (in particular cc-ed authors) recall what is the status,
planned update, planned progress to RFC of this document:
http://tools.ietf.org/id/draft-ietf-grow-mrt-04.txt
Thx,
R.
___
GROW mailing list
GROW@ietf.org
https://www.ietf.org
On Thu, Jul 07, 2011 at 09:51:39AM -0400, Larry Blunk wrote:
> On 07/07/2011 07:37 AM, Nick Hilliard wrote:
> >>This document describes the MRT format for routing information
> >>export. This format was developed in concert with the Multi-threaded
> >>Routing Toolkit (MRT) from whence
The IESG has approved the following document:
- 'MRT routing information export format'
(draft-ietf-grow-mrt-17.txt) as a Proposed Standard
This document is the product of the Global Routing Operations Working
Group.
The IESG contact persons are Ron Bonica and Dan Romascanu.
A U
Manish Karir
Craig Labovitz
Filename: draft-ietf-grow-mrt-17.txt
Pages : 37
Date: 2011-08-17
This document describes the MRT format for routing information
export. This format was developed in concert with the
Manish Karir
Craig Labovitz
Filename: draft-ietf-grow-mrt-16.txt
Pages : 37
Date: 2011-08-17
This document describes the MRT format for routing information
export. This format was developed in concert with the
On 07/07/2011 07:37 AM, Nick Hilliard wrote:
This document describes the MRT format for routing information
export. This format was developed in concert with the Multi-threaded
Routing Toolkit (MRT) from whence the format takes it name. The
format can be used to export routing p
>This document describes the MRT format for routing information
>export. This format was developed in concert with the Multi-threaded
>Routing Toolkit (MRT) from whence the format takes it name. The
>format can be used to export routing protocol messages, state
>changes, and r
Manish Karir
Craig Labovitz
Filename: draft-ietf-grow-mrt-15.txt
Pages : 35
Date: 2011-07-06
This document describes the MRT format for routing information
export. This format was developed in concert with the
to export routing protocol messages, state
changes, and routing information base contents.
A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-grow-mrt-14.txt
Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/
Below is the
rg [mailto:grow-boun...@ietf.org] On Behalf Of
>>> Ronald Bonica
>>> Sent: Friday, February 11, 2011 2:05 PM
>>> To: draft-ietf-grow-...@tools.ietf.org; grow@ietf.org
>>> Subject: [GROW] Mail regarding draft-ietf-grow-mrt
>>>
&
riday, February 11, 2011 2:05 PM
>> To: draft-ietf-grow-...@tools.ietf.org; grow@ietf.org
>> Subject: [GROW] Mail regarding draft-ietf-grow-mrt
>>
>> Guys,
>>
>> This draft has been in the revised ID needed state for almost six
>> months. Do you need any hel
2:05 PM
> To: draft-ietf-grow-...@tools.ietf.org; grow@ietf.org
> Subject: [GROW] Mail regarding draft-ietf-grow-mrt
>
> Guys,
>
> This draft has been in the revised ID needed state for almost six
> months. Do you need any hel
Guys,
This draft has been in the revised ID needed state for almost six months. Do
you need any help getting it over the finish line?
Ron
___
GROW mailing list
GROW@ietf.org
https://www.ietf.org/mailman/
: draft-ietf-grow-mrt-13.txt
Pages : 32
Date: 2010-09-09
This document describes the MRT format for routing information
export. This format was developed in concert with the Multi-threaded
Routing Toolkit (MRT) from whence the format takes it name. The
: draft-ietf-grow-mrt-12.txt
Pages : 32
Date: 2010-09-09
This document describes the MRT format for routing information
export. This format was developed in concert with the Multi-threaded
Routing Toolkit (MRT) from whence the format takes it name. The
Hi,
I am issuing last call for draft-ietf-grow-mrt-11. Please review the
document, and notify the list of any comments.
Last call will close april 14th, 2010.
Thanks
Peter & chris
___
GROW mailing list
GROW@ietf.org
https://www.ietf.org/mai
: draft-ietf-grow-mrt-11.txt
Pages : 29
Date: 2010-03-08
This document describes the MRT format for routing information
export. This format was developed in concert with the Multi-threaded
Routing Toolkit (MRT) from whence the format takes it name. The
Jeffrey Haas wrote:
In draft-ietf-grow-mrt-10, the IANA considerations contain the following
verbiage:
: Type Codes have a range from 0 to 65535, of which 0-64 have been
: allocated. New Type Codes MUST be allocated starting at 65. Type
: Codes 65 - 32767 are to be assigned by IETF
In draft-ietf-grow-mrt-10, the IANA considerations contain the following
verbiage:
: Type Codes have a range from 0 to 65535, of which 0-64 have been
: allocated. New Type Codes MUST be allocated starting at 65. Type
: Codes 65 - 32767 are to be assigned by IETF Consensus. Type Codes
: draft-ietf-grow-mrt-10.txt
Pages : 28
Date: 2009-07-13
This document describes the MRT format for routing information
export. This format was developed in concert with the Multi-threaded
Routing Toolkit (MRT) from whence the format takes it name. The
a version.
>>>
>>> So, the options would be to update the draft to reflect these
>>> two known implementations, or ask the implementers to update
>>> their code and the archives to update their archived BGP data.
>>> I'm guessing it will be preferable
sing it will be preferable to update the draft, but I'd like to
hear if there are any other implementations out there first.I did
check the lastest OpenBGPD, and it does not yet support the
AS4 types.
-Larry Blunk
Peter Schoenmaker wrote:
Hello,
I would like to issue last call for dr
. I did
> check the lastest OpenBGPD, and it does not yet support the
> AS4 types.
>
>
>
>
> -Larry Blunk
>
>
>
>
> Peter Schoenmaker wrote:
>>
>> Hello,
>>
>> I would like to issue last call for draft-ietf-grow-mrt-09.txt. Please
>
he lastest OpenBGPD, and it does not yet support the
AS4 types.
-Larry Blunk
Peter Schoenmaker wrote:
Hello,
I would like to issue last call for draft-ietf-grow-mrt-09.txt.
Please provide any final comments by March 20th (just before IETF 74
San Francisco.)
thanks
peter
Begin forward
Hello,
I would like to issue last call for draft-ietf-grow-mrt-09.txt.
Please provide any final comments by March 20th (just before IETF 74
San Francisco.)
thanks
peter
Begin forwarded message:
From: internet-dra...@ietf.org
Date: February 25, 2009 7:15:01 AM PST
To: i-d-annou
: draft-ietf-grow-mrt-09.txt
Pages : 28
Date: 2009-02-25
This document describes the MRT format for routing information
export. This format was developed in concert with the Multi-threaded
Routing Toolkit (MRT) from whence the format takes it name. The
Hi,
I would like to know if there are any comments or feedback for
revision 08 of the mrt draft.
I hope we can half a final call soon.
peter
On Jul 14, 2008, at 2:09 PM, Larry Blunk wrote:
The -08 version of the MRT draft moves the deprecated
types to an Appendix. This should hopeful
The -08 version of the MRT draft moves the deprecated
types to an Appendix. This should hopefully make it an
easier read. A couple of minor error in the -07 draft
were also fixed.
-Larry Blunk
___
GROW mailing list
GROW@ietf.org
https://www.ietf
: draft-ietf-grow-mrt-08.txt
Pages : 29
Date: 2008-07-14
This document describes the MRT format for routing information
export. This format was developed in concert with the Multi-threaded
Routing Toolkit (MRT) from whence the format takes it name. The
A note about the -07 MRT draft.I tried to address most
of the comments, but I haven't yet moved the deprecated types
to an appendix (as suggested by Geoff Huston). I'm planning an
-08 draft for that. Unfortunately, I introduced a couple of bugs and typos
into the -07 draft (that will als
: draft-ietf-grow-mrt-07.txt
Pages : 29
Date: 2008-02-25
This document describes the MRT format for routing information
export. This format was developed in concert with the Multi-threaded
Routing Toolkit (MRT) from whence the format takes it name. The
: draft-ietf-grow-mrt-06.txt
Pages : 29
Date: 2007-11-19
This document describes the MRT format for routing information
export. This format was developed in concert with the Multi-threaded
Routing Toolkit (MRT) from whence the format takes it name. The
: draft-ietf-grow-mrt-05.txt
Pages : 28
Date: 2007-11-16
This document describes the MRT format for routing information
export. This format was developed in concert with the Multi-threaded
Routing Toolkit (MRT) from whence the format takes it name. The
On Thu, Mar 08, 2007 at 03:50:04PM -0500, [EMAIL PROTECTED] wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Global Routing Operations Working Group of
> the IETF.
Another minor error, but worth the effort to fix in the
On Thu, Mar 08, 2007 at 03:50:04PM -0500, [EMAIL PROTECTED] wrote:
> Title : MRT routing information export format
> Author(s) : L. Blunk, et al.
> Filename: draft-ietf-grow-mrt-04.txt
I thought we renamed INDEX_TABLE to PEER_INDEX_TABLE
On Thu, Mar 08, 2007 at 03:50:04PM -0500, [EMAIL PROTECTED] wrote:
> Title : MRT routing information export format
> Author(s) : L. Blunk, et al.
> Filename: draft-ietf-grow-mrt-04.txt
The STATE_CHANGE_AS4 BGP4MP type is described under 5.9, b
: draft-ietf-grow-mrt-04.txt
Pages : 27
Date: 2007-3-8
This document describes the MRT format for routing information
export. This format was developed in concert with the Multi-threaded
Routing Toolkit (MRT) from whence the format takes it
Erik Romijn wrote:
On Wed, Feb 21, 2007 at 10:28:37AM +0100, Erik Romijn wrote:
On Sat, Feb 10, 2007 at 02:06:01AM -0500, Larry Blunk wrote:
The IPV4_UNICAST_NLRI header is shown below. The Prefix Length
and Prefix fields are encoded in the same manner as the BGP
NLRI field.
I
1 - 100 of 128 matches
Mail list logo
