s'okay by me. On Wed, Apr 22, 2009 at 10:29 AM, Larry Blunk <[email protected]> wrote: > > > > I would say it's definitely materially impacting. > The I-D tracker still shows the draft as just being > in the I-D Exists state. So I should just be able to > just spin a new -10 draft and we do another > last call. Correct? > > -Larry > > > > Christopher Morrow wrote: >> >> does this, if it's not materially impacting, fall into something that >> gets fixed in IESG comment/fixes? >> >> -Chris >> >> On Tue, Apr 21, 2009 at 1:41 PM, Larry Blunk <[email protected]> wrote: >> >>> >>> Ricard Oliveira of UCLA just noticed a discrepancy between >>> the MRT draft and the quagga and libbgpdump implementations. >>> The BGP4MP_STATE_CHANGE_AS4 type was added in the -04 >>> version of the MRT draft and defined to have a value of 4. The >>> BGP4MP_MESSAGE_AS4 type was assigned a value of 5 in >>> this draft (it had been orignally named BGP4MP_MESSAGE_32BIT_AS >>> and had been assigned a value of 4 in earlier drafts). >>> >>> The reason the value of the BGP4MP_MESSAGE_AS4 >>> type changed from 4 to 5 is because the BGP4MP_STATE_CHANGE >>> and BGP4MP_MESSAGE 16-bit AS types are defined as 0 and 1, respectively. >>> So it seemed reasonable to use the same ordering for the 4 byte >>> AS versions of these types (bit 2 is set in the 4 byte AS versions, >>> and clear in the 16-bit AS versions). >>> >>> Unfortunately, the libbgpdump and quagga implementations use >>> the original value of 4 for the BGP4MP_MESSAGE_AS4 type, and >>> the value of 5 for the BGP4MP_STATE_CHANGE_AS4 type. >>> >>> These type codes of been in production for about 2 years with the >>> RIPE RIS project and Oregon Routeviews just recently >>> switched to using these as well when it moved to the lastest >>> Quagga 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 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 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: [email protected] >>>>> Date: February 25, 2009 7:15:01 AM PST >>>>> To: [email protected] >>>>> Cc: [email protected] >>>>> Subject: [GROW] I-D Action:draft-ietf-grow-mrt-09.txt >>>>> >>>>> 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. >>>>> >>>>> >>>>> Title : MRT routing information export format >>>>> Author(s) : L. Blunk, et al. >>>>> Filename : 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 >>>>> format can be used 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-09.txt >>>>> >>>>> Internet-Drafts are also available by anonymous FTP at: >>>>> ftp://ftp.ietf.org/internet-drafts/ >>>>> >>>>> Below is the data which will enable a MIME compliant mail reader >>>>> implementation to automatically retrieve the ASCII version of the >>>>> Internet-Draft. >>>>> _______________________________________________ >>>>> GROW mailing list >>>>> [email protected] >>>>> https://www.ietf.org/mailman/listinfo/grow >>>>> >>> >>> _______________________________________________ >>> GROW mailing list >>> [email protected] >>> https://www.ietf.org/mailman/listinfo/grow >>> >>> >> >> <div><br></div> >> > >
<div><br></div> _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
