Thanks David for providing the early allocation,. Acee
> On Jul 11, 2026, at 1:24 AM, David Dong via RT <[email protected]> > wrote: > > Hi Yingzhen, Authors, > > We've added "Modified MANET Reduction" to the IGP Algorithm Type For > Computing Flooding Topology registry: > > 1 Modified MANET Reduction [draft-ietf-lsr-distoptflood-13] > > Registry: > https://www.iana.org/assignments/igp-parameters/ > > Thank you. > > Best regards, > > David Dong > IANA Services Sr. Specialist > > On Fri Jul 10 07:32:16 2026, [email protected] wrote: >> Hi Sabrina, >> >> On 10/07/2026 00:30, Sabrina Tanamal via RT wrote: >>> Hi Peter, all, >>> >>> Apologies for the confusion. >>> >>> Since this is an Expert Review registry, the early allocation >>> procedures described in RFC 7120 do not apply. As a result, the >>> requested registration would be made as a permanent registration >>> based on your approval. >>> >>> Peter, could you please confirm that we can proceed with the >>> permanent registration? >> >> I approve. >> >> thanks, >> Peter >> >>> >>> We don't need AD approval for this. >>> >>> Thanks, >>> Sabrina >>> >>> On Thu Jul 09 07:41:04 2026, [email protected] wrote: >>>> Hi David, >>>> >>>> On 09/07/2026 06:59, David Dong via RT wrote: >>>>> Hi Gunter, Peter, >>>>> >>>>> Gunter, as the AD, could you approve this early allocation for >>>>> codepoint 1 in the IGP Algorithm Type For Computing Flooding >>>>> Topology >>>>> registry for draft-ietf-lsr-distoptflood-13? >>>>> >>>>> Peter, just to confirm, as the DE, could you confirm your approval >>>>> of >>>>> this early allocation for codepoint 1 in the IGP Algorithm Type For >>>>> Computing Flooding Topology registry for draft-ietf-lsr- >>>>> distoptflood- >>>>> 13? >>>> I approve this early allocation for codepoint 1. >>>> >>>> thanks, >>>> Peter >>>> >>>> >>>>> Thank you. >>>>> >>>>> Best regards, >>>>> >>>>> David Dongxa >>>>> IANA Services Sr. Specialist >>>>> >>>>> On Tue Jun 30 18:22:38 2026,[email protected] wrote: >>>>>> Hi David, >>>>>> >>>>>> I have to recuse myself, but I see no objections. >>>>>> >>>>>> Tony >>>>>> >>>>>> >>>>>>> On Jun 30, 2026, at 11:09 AM, David Dong via RT - iana-prot- >>>>>>> param- >>>>>>> comment at iana.org<[email protected]> wrote: >>>>>>> >>>>>>> Hi Gunter, Peter / Tony Li, >>>>>>> >>>>>>> Gunter, as the AD, could you approve this early allocation for >>>>>>> codepoint 1 in the IGP Algorithm Type For Computing Flooding >>>>>>> Topology >>>>>>> registry for draft-ietf-lsr-distoptflood-13? >>>>>>> >>>>>>> Peter / Tony L., just to confirm, as the DEs, could you confirm >>>>>>> your >>>>>>> approval of this early allocation for codepoint 1 in the IGP >>>>>>> Algorithm Type For Computing Flooding Topology registry for >>>>>>> draft- >>>>>>> ietf-lsr-distoptflood-13? >>>>>>> >>>>>>> Thank you. >>>>>>> >>>>>>> Best regards, >>>>>>> >>>>>>> David Dongxa >>>>>>> IANA Services Sr. Specialist >>>>>>> >>>>>>> On Tue Jun 30 08:36:42 2026,[email protected] wrote: >>>>>>>> On Tue, Jun 30, 2026 at 10:28 AM Peter Psenak<[email protected]> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Tony, >>>>>>>>> >>>>>>>>> On 30/06/2026 09:50, Przygienda, Tony wrote: >>>>>>>>> >>>>>>>>> Who can argue with being #1 ;-) >>>>>>>>> >>>>>>>>> you can, if you have shipped something and changing it would >>>>>>>>> create >>>>>>>>> a >>>>>>>>> backward compatibility issue. In such case we could go with >>>>>>>>> 125. >>>>>>>>> But if that's not the case, I would prefer to start with 1. >>>>>>>>> >>>>>>>> Peter, we will bend implementation here gladly. we're not in the >>>>>>>> "no >>>>>>>> way we >>>>>>>> can change it anymore" territory completely yet ;-) >>>>>>>> >>>>>>>> thanks for the alloc' >>>>>>>> >>>>>>>> -- tony >>>>>>>> >>>>>>>> >>>>>>>>> Peter >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Sure, whatever we get that fixes the thing so we don’t have to >>>>>>>>> squat >>>>>>>>> on it >>>>>>>>> while deploying is great, especially since I have an inkling >>>>>>>>> another >>>>>>>>> implementation out there may be in the planning/cooking 😉 >>>>>>>>> >>>>>>>>> >>>>>>>>> - Tony >>>>>>>>> >>>>>>>>> >>>>>>>>> Sent from Outlook for Mac >>>>>>>>> *From: *Hegde, Shraddha<[email protected]> >>>>>>>>> <[email protected]> >>>>>>>>> *Date: *Tuesday, 30 June 2026 at 05:18 >>>>>>>>> *To: *Yingzhen Qu<[email protected]> >>>>>>>>> <[email protected]>; >>>>>>>>> Peter Psenak<[email protected]> <[email protected]>; >>>>>>>>> [email protected] >>>>>>>>> <[email protected]> >>>>>>>>> <[email protected]>; Tony Przygienda >>>>>>>>> <[email protected]> <[email protected]> >>>>>>>>> *Cc: *Les Ginsberg (ginsberg)<[email protected]> >>>>>>>>> <[email protected]>; >>>>>>>>> [email protected] <[email protected]> <[email protected]>; Hannes Gredler >>>>>>>>> <[email protected]> <[email protected]>; Christian Hopps >>>>>>>>> <[email protected]> <[email protected]>; lsr-chairs<lsr- >>>>>>>>> [email protected]> >>>>>>>>> <[email protected]>; Van De Velde, Gunter (Nokia - BE) ( >>>>>>>>> [email protected])<[email protected]> >>>>>>>>> <[email protected]>; Tony Li<[email protected]> >>>>>>>>> <[email protected]> >>>>>>>>> *Subject: *Re: Request for early allocation of codepoint >>>>>>>>> >>>>>>>>> Assigning value of 1 should be ok. >>>>>>>>> Tony, >>>>>>>>> Are you fine with that? >>>>>>>>> >>>>>>>>> Rgds >>>>>>>>> Shraddha >>>>>>>>> ------------------------------ >>>>>>>>> *From:* Yingzhen Qu<[email protected]> >>>>>>>>> <[email protected]> >>>>>>>>> *Sent:* 30 June 2026 03:58 >>>>>>>>> *To:* Peter Psenak<[email protected]> <[email protected]>; >>>>>>>>> [email protected] >>>>>>>>> <[email protected]> >>>>>>>>> <[email protected]>; Hegde, Shraddha >>>>>>>>> <[email protected]> <[email protected]>; Tony >>>>>>>>> Przygienda >>>>>>>>> <[email protected]> <[email protected]> >>>>>>>>> *Cc:* Les Ginsberg (ginsberg)<[email protected]> >>>>>>>>> <[email protected]>; >>>>>>>>> [email protected] <[email protected]> <[email protected]>; Hannes Gredler >>>>>>>>> <[email protected]> <[email protected]>; Christian Hopps >>>>>>>>> <[email protected]> <[email protected]>; lsr-chairs<lsr- >>>>>>>>> [email protected]> >>>>>>>>> <[email protected]>; Van De Velde, Gunter (Nokia - BE) ( >>>>>>>>> [email protected])<[email protected]> >>>>>>>>> <[email protected]>; Tony Li<[email protected]> >>>>>>>>> <[email protected]> >>>>>>>>> *Subject:* Re: Request for early allocation of codepoint >>>>>>>>> >>>>>>>>> Adding the draft authors. >>>>>>>>> >>>>>>>>> I don't see any special value requirement in the draft (a TBD >>>>>>>>> value >>>>>>>>> in >>>>>>>>> 1-127 range). >>>>>>>>> >>>>>>>>> Shraddha, any reason you're asking for 125? or 1 is ok? >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> Yingzhen >>>>>>>>> >>>>>>>>> On Mon, Jun 29, 2026 at 1:36 AM Peter Psenak<[email protected]> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>> Hi Yingzhen, >>>>>>>>> >>>>>>>>> why 125? >>>>>>>>> >>>>>>>>> Should not we start to allocate from 1? >>>>>>>>> >>>>>>>>> thanks, >>>>>>>>> Peter >>>>>>>>> >>>>>>>>> On 29/06/2026 08:30, Yingzhen Qu wrote: >>>>>>>>> >>>>>>>>> Hi, >>>>>>>>> >>>>>>>>> draft-ietf-lsr-distoptflood is requesting a code point from the >>>>>>>>> "IGP >>>>>>>>> Algorithm Type For Computing Flooding Topology" registry, and >>>>>>>>> the >>>>>>>>> WG >>>>>>>>> approves the request. Since we now have the DEs for the >>>>>>>>> registry, >>>>>>>>> can >>>>>>>>> the >>>>>>>>> code point be reviewed by the DEs and assigned? >>>>>>>>> - IGP Algorithm registry for disttopo 125 >>>>>>>>> >>>>>>>>> Peter and Tony (CCed) are the assigned DEs for the registry: >>>>>>>>> https://www.iana.org/assignments/igp-parameters/igp- >>>>>>>>> parameters.xhtml#algorithm-type-computing-flooding-topology >>>>>>>>> <https://urldefense.com/v3/__https://www.iana.org/assignments/igp- >>>>>>>>> parameters/igp-parameters.xhtml*algorithm-type-computing- >>>>>>>>> flooding- >>>>>>>>> topology__;Iw!!NpxR!h4hGknLygF4aGJP4WHhhhfg4kcWTpuE- >>>>>>>>> F2uCVkOU8SrR63ZRQ6UIj4ErW2CEZ26u7lSGtcxeOxOLyun81EDn5Vbg$> >>>>>>>>> >>>>>>>>> Please kindly let me know if any other information is needed. >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> Yingzhen >>>>>>>>> >>>>>>>>> On Wed, May 20, 2026 at 7:45 AM Les Ginsberg (ginsberg)< >>>>>>>>> [email protected]> wrote: >>>>>>>>> >>>>>>>>> Folks – >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> As per the thread below, the authors of >>>>>>>>> https://datatracker.ietf.org/doc/draft-ietf-lsr-flood- >>>>>>>>> reduction- >>>>>>>>> arch/ >>>>>>>>> <https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft- >>>>>>>>> ietf-lsr-flood-reduction- >>>>>>>>> arch/__;!!NpxR!h4hGknLygF4aGJP4WHhhhfg4kcWTpuE- >>>>>>>>> F2uCVkOU8SrR63ZRQ6UIj4ErW2CEZ26u7lSGtcxeOxOLyun81NaYBSGc$> have >>>>>>>>> requested early allocation of a sub-TLV codepoint from the IS- >>>>>>>>> IS >>>>>>>>> Sub- >>>>>>>>> TLVs >>>>>>>>> for IS-IS Router CAPABILITY TLV >>>>>>>>> <https://urldefense.com/v3/__https://www.iana.org/assignments/isis- >>>>>>>>> tlv-codepoints/isis-tlv-codepoints.xhtml*isis-tlv-codepoints- >>>>>>>>> 242__;Iw!!NpxR!h4hGknLygF4aGJP4WHhhhfg4kcWTpuE- >>>>>>>>> F2uCVkOU8SrR63ZRQ6UIj4ErW2CEZ26u7lSGtcxeOxOLyun81OJH7wIe$> >>>>>>>>> registry >>>>>>>>> and WG chairs have approved making an early allocation. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> As per the procedures specified in rfc7370 >>>>>>>>> >>>>>>>>> <https://urldefense.com/v3/__https://datatracker.ietf.org/doc/rfc7370/__;!!NpxR!h4hGknLygF4aGJP4WHhhhfg4kcWTpuE- >>>>>>>>> F2uCVkOU8SrR63ZRQ6UIj4ErW2CEZ26u7lSGtcxeOxOLyun81D7_SLXq$> >>>>>>>>> Chris, >>>>>>>>> Hannes, and myself as the Designated Experts for this registry >>>>>>>>> have >>>>>>>>> approved the request. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Value: 250 >>>>>>>>> >>>>>>>>> Description: Flood Reduction Algorithm >>>>>>>>> >>>>>>>>> MP: N >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Please enter this early allocation in the corresponding >>>>>>>>> registry >>>>>>>>> and >>>>>>>>> notify the WG and draft authors. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Les (on behalf of all the designated experts) >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> NOTE: Other codepoint allocations discussed below are for other >>>>>>>>> registries >>>>>>>>> and will be addressed separately. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> *From:* Yingzhen Qu<[email protected]> >>>>>>>>> *Sent:* Tuesday, May 19, 2026 8:54 AM >>>>>>>>> *To:* Gunter van de Velde >>>>>>>>> (Nokia)<[email protected]> >>>>>>>>> *Cc:* Les Ginsberg (ginsberg)<[email protected]>; Acee Lindem< >>>>>>>>> [email protected]>; Tony Przygienda<[email protected]>; >>>>>>>>> lsr< >>>>>>>>> [email protected]>; lsr-chairs<[email protected]>; Hannes Gredler >>>>>>>>> ( >>>>>>>>> [email protected])<[email protected]> >>>>>>>>> *Subject:* Re: [Lsr] Re: Request for temporary assignements of >>>>>>>>> code4points >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Hi Gunter and all, >>>>>>>>> >>>>>>>>> >>>>>>>>> draft-ietf-lsr-flood-reduction-arch is a WG document that has >>>>>>>>> been >>>>>>>>> discussed multiple times in meeting sessions; the WG approves >>>>>>>>> allocating >>>>>>>>> the following code points: >>>>>>>>> >>>>>>>>> The IS-IS registry - IS-IS Sub-TLVs for IS-IS Router CAPABILITY >>>>>>>>> TLV >>>>>>>>> The OSPF registry - OSPF Router Information (RI) TLVs >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> draft-ietf-lsr-distoptflood is requesting a code point from the >>>>>>>>> "IGP >>>>>>>>> Algorithm Type For Computing Flooding Topology" registry, and >>>>>>>>> the >>>>>>>>> WG >>>>>>>>> approves the request. However, the registry is missing experts. >>>>>>>>> This >>>>>>>>> needs >>>>>>>>> to be fixed before the requested code point can be allocated. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> >>>>>>>>> Yingzhen >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Mon, Mar 30, 2026 at 11:16 PM Gunter van de Velde (Nokia)< >>>>>>>>> [email protected]> wrote: >>>>>>>>> >>>>>>>>> Hi Acee, All, >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> First thanks to Les for the datapoints and input regarding the >>>>>>>>> request for >>>>>>>>> code points under the IS-IS Sub-TLVs for IS-IS Router >>>>>>>>> CAPABILITY >>>>>>>>> TLV >>>>>>>>> with >>>>>>>>> "Expert Review" >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> For "The OSPF registry - OSPF Router Information (RI) TLVs is >>>>>>>>> "IETF >>>>>>>>> Review"" there is the path of RFC7120 early allocation assuming >>>>>>>>> the >>>>>>>>> conditions outlined in section 2 are met. >>>>>>>>> >>>>>>>>> In general that boils down to the following: >>>>>>>>> >>>>>>>>> 1) The code point specifications "must be adequately >>>>>>>>> described" >>>>>>>>> >>>>>>>>> 2) The specifications must be considered stable >>>>>>>>> >>>>>>>>> 3) WG chairs and AD judge judge that there is sufficient >>>>>>>>> community >>>>>>>>> interest >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Assuming (1) and (2) are confirmed, then similar as with the >>>>>>>>> ISIS >>>>>>>>> request >>>>>>>>> the chairs provide indication (presumably w Acee abstaining as >>>>>>>>> a >>>>>>>>> co- >>>>>>>>> author) >>>>>>>>> of community interest to IANA with an early code point request, >>>>>>>>> and >>>>>>>>> the >>>>>>>>> allocation processing will take place. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> G/ >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> ------------------------------ >>>>>>>>> >>>>>>>>> *From:* Les Ginsberg (ginsberg)<[email protected]> >>>>>>>>> *Sent:* Saturday, March 28, 2026 3:13 AM >>>>>>>>> *To:* Acee Lindem<[email protected]>; Tony Przygienda< >>>>>>>>> [email protected]>; Gunter van de Velde (Nokia)< >>>>>>>>> [email protected]>; lsr<[email protected]> >>>>>>>>> *Cc:* lsr-chairs<[email protected]>; Hannes Gredler >>>>>>>>> ([email protected]) >>>>>>>>> <[email protected]> >>>>>>>>> *Subject:* RE: [Lsr] Re: Request for temporary assignements of >>>>>>>>> code4points >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> CAUTION: This is an external email. Please be very careful when >>>>>>>>> clicking >>>>>>>>> links or opening attachments. See the URL nok.it/ext >>>>>>>>> >>>>>>>>> <https://urldefense.com/v3/__http://nok.it/ext__;!!NpxR!h4hGknLygF4aGJP4WHhhhfg4kcWTpuE- >>>>>>>>> F2uCVkOU8SrR63ZRQ6UIj4ErW2CEZ26u7lSGtcxeOxOLyun81ETArY46$> for >>>>>>>>> additional information. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Sooo...without trying to be overly formal... >>>>>>>>> >>>>>>>>> https://www.rfc-editor.org/rfc/rfc7370.html#section-4 >>>>>>>>> <https://urldefense.com/v3/__https://www.rfc- >>>>>>>>> editor.org/rfc/rfc7370.html*section- >>>>>>>>> 4__;Iw!!NpxR!h4hGknLygF4aGJP4WHhhhfg4kcWTpuE- >>>>>>>>> F2uCVkOU8SrR63ZRQ6UIj4ErW2CEZ26u7lSGtcxeOxOLyun81FHWzFeW$> >>>>>>>>> applies... >>>>>>>>> >>>>>>>>> Summarizing >>>>>>>>> >>>>>>>>> 1)We need a request from the draft authors. >>>>>>>>> Let 's consider that requirement met. >>>>>>>>> >>>>>>>>> 2)We need an indication from the WG chairs that >>>>>>>>> "there is consensus within the Working Group to make the >>>>>>>>> allocation >>>>>>>>> at >>>>>>>>> this time." >>>>>>>>> >>>>>>>>> I think once the chairs provide that indication (presumably w >>>>>>>>> Acee >>>>>>>>> abstaining as a co-author) then the Designated Experts (Hannes, >>>>>>>>> Chris, and >>>>>>>>> myself) >>>>>>>>> can proceed. >>>>>>>>> >>>>>>>>> Les >>>>>>>>> >>>>>>>>>> -----Original Message----- >>>>>>>>>> From: Acee Lindem<[email protected]> >>>>>>>>>> Sent: Thursday, March 26, 2026 10:32 AM >>>>>>>>>> To: Tony Przygienda<[email protected]>; Gunter van de Velde >>>>>>>>>> (Nokia) >>>>>>>>>> <[email protected]>; lsr<[email protected]> >>>>>>>>>> Cc: lsr-chairs<[email protected]> >>>>>>>>>> Subject: [Lsr] Re: Request for temporary assignements of >>>>>>>>>> code4points >>>>>>>>>> >>>>>>>>>> +Gunter and LSR list. I'm a co-author so I won't comment. >>>>>>>>>> >>>>>>>>>> The IS-IS registry - IS-IS Sub-TLVs for IS-IS Router >>>>>>>>>> CAPABILITY >>>>>>>>>> TLV >>>>>>>>>> is >>>>>>>>> "Expert >>>>>>>>>> Review" >>>>>>>>>> The OSPF registry - OSPF Router Information (RI) TLVs is "IETF >>>>>>>>>> Review" >>>>>>>>>> >>>>>>>>>> Thanks, >>>>>>>>>> Acee >>>>>>>>>> >>>>>>>>>>> On Mar 26, 2026, at 5:16 AM, Tony Przygienda >>>>>>>>>>> <[email protected]> >>>>>>>>>> wrote: >>>>>>>>>>> Hey, as indicated in my preso we are at interoping flood >>>>>>>>>>> reduction >>>>>>>>>>> and >>>>>>>>> need >>>>>>>>>> codepoints by now >>>>>>>>> https://datatracker.ietf.org/doc/draft-ietf-lsr-flood- >>>>>>>>> reduction- >>>>>>>>> arch/01/ >>>>>>>>> <https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft- >>>>>>>>> ietf-lsr-flood-reduction- >>>>>>>>> arch/01/__;!!NpxR!h4hGknLygF4aGJP4WHhhhfg4kcWTpuE- >>>>>>>>> F2uCVkOU8SrR63ZRQ6UIj4ErW2CEZ26u7lSGtcxeOxOLyun81OJgNxfa$> >>>>>>>>>>> needs >>>>>>>>>>> >>>>>>>>>>> sub-TLV within a Router Capability TLV (242) defined in >>>>>>>>>>> [RFC7981] >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> and for OSPF >>>>>>>>>>> >>>>>>>>>>> The Flood Reduction Algorithm TLV is advertised within a >>>>>>>>>>> OSPFv2 >>>>>>>>>>> Router Information (RI) Opaque LSA or OSPFv3 Router >>>>>>>>>>> Information >>>>>>>>>>> LSA >>>>>>>>>>> as defined in [RFC7770] >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> We will also need an algorithm value for >>>>>>>>>>> >>>>>>>>>>> https://datatracker.ietf.org/doc/html/draft-ietf-lsr- >>>>>>>>>>> distoptflood- >>>>>>>>>>> 13 >>>>>>>>> <https://urldefense.com/v3/__https://datatracker.ietf.org/doc/html/draft- >>>>>>>>> ietf-lsr-distoptflood- >>>>>>>>> 13__;!!NpxR!h4hGknLygF4aGJP4WHhhhfg4kcWTpuE- >>>>>>>>> F2uCVkOU8SrR63ZRQ6UIj4ErW2CEZ26u7lSGtcxeOxOLyun81H0YbVTu$> >>>>>>>>>>> IANA is requested to allocate a TBD value in 1-127 range with >>>>>>>>> description of >>>>>>>>>> "Modified MANET Reduction" further referring to >>>>>>>>>>> this document as specification in the "IGP Algorithm Type For >>>>>>>>>>> Computing >>>>>>>>>> Flooding Topology" registry. >>>>>>>>>>> whereas personally I still think having a separate registry >>>>>>>>>>> for >>>>>>>>> "_Distributed_ >>>>>>>>>> IGP Algorithm Type For Computing Flooding Topology" would be >>>>>>>>>> better >>>>>>>>>>> >>>>>>>>>>> Could you please issue the according calls ? >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> thanks >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> --- tony >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Lsr mailing list [email protected] >>>>>>>>>> To unsubscribe send an email [email protected] >>>>>>>>> >>>>>>>>> > _______________________________________________ Lsr mailing list -- [email protected] To unsubscribe send an email to [email protected]
