Hi Acee, Alvaro, all, Alvaro: can you approve the request for early registration of the B-bit in the LLS Type 1 Extended Options and Flags registry at https://www.iana.org/assignments/ospf-lls-tlvs?
Acee, Ketan: the document says that it's registering 0x00000010, but that value was allocated to draft-ietf-lsr-dynamic-flooding last year. If Alvaro approves, should we register 0x00000020 instead? Acee, Ketan, Gunter, Peter: because it's using a different registration procedure, I'm creating a separate ticket for the Link Local Signalling TLV Identifiers (LLS Types) registration. I'll send an expert review request from that ticket. Best regards, Amanda Baber Lead IANA Services Specialist On Wed Jul 01 19:38:00 2020, [email protected] wrote: > Hi Ketan, IANA, Alvaro, > I don't see any problem with early allocation of this LLS bit and TLV > - pretty straight forward. It would make sense to put the respective > registries in the IANA section (included below for info). > > Open Shortest Path First (OSPF) Link Local Signalling (LLS) - > Type/Length/Value Identifiers (TLV) > Link Local Signalling TLV Identifiers (LLS Types) RFC 5613 > IETF Review > LLS Type 1 Extended Options and Flags RFC 5613 > Expert Review (Expert: Gunter Van De Velde, Peter Psenak) > > For the flag, the designated experts are Gunter and Peter (copied). > > Please initiate the early allocation process pending expert and AD > approval. > Thanks, > Acee > > On 6/30/20, 4:58 AM, "Ketan Talaulikar (ketant)" <[email protected]> > wrote: ts > > Hello Acee/Chris, > > The authors would like to request IANA early allocations for this > draft. > > Thanks, > Ketan (on behalf of co-authors) > > -----Original Message----- > From: Ketan Talaulikar (ketant) > Sent: 30 June 2020 14:25 > To: [email protected] > Subject: RE: [Lsr] I-D Action: draft-ietf-lsr-ospf-bfd-strict-mode- > 01.txt > > Hi All, > > This is mostly a refresh with editorial updates. We look forward to > review and feedback. > > Thanks, > Ketan (on behalf of co-authors) > > -----Original Message----- > From: Lsr <[email protected]> On Behalf Of [email protected] > Sent: 30 June 2020 14:20 > To: [email protected] > Cc: [email protected] > Subject: [Lsr] I-D Action: draft-ietf-lsr-ospf-bfd-strict-mode-01.txt > > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > This draft is a work item of the Link State Routing WG of the IETF. > > Title : OSPF Strict-Mode for BFD > Authors : Ketan Talaulikar > Peter Psenak > Albert Fu > Rajesh M > Filename : draft-ietf-lsr-ospf-bfd-strict-mode-01.txt > Pages : 10 > Date : 2020-06-30 > > Abstract: > This document specifies the extensions to OSPF that enable an OSPF > router to signal the requirement for a Bidirectional Forwarding > Detection (BFD) session prior to adjacency formation. Link-Local > Signaling (LLS) is used to advertise this requirement of "strict- > mode" of BFD session establishment for OSPF adjacency. If both > OSPF > neighbors advertise the "strict-mode" of BFD, adjacency formation > will be blocked until a BFD session has been successfully > established. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-lsr-ospf-bfd-strict-mode/ > > There are also htmlized versions available at: > https://tools.ietf.org/html/draft-ietf-lsr-ospf-bfd-strict-mode-01 > https://datatracker.ietf.org/doc/html/draft-ietf-lsr-ospf-bfd-strict- > mode-01 > > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=draft-ietf-lsr-ospf-bfd-strict-mode- > 01 > > > Please note that it may take a couple of minutes from the time of > submission until the htmlized version and diff are available at > tools.ietf.org. > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > > _______________________________________________ > Lsr mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/lsr > _______________________________________________ Lsr mailing list [email protected] https://www.ietf.org/mailman/listinfo/lsr
