Re: [Lsr] [IANA #1173602] Re: IANA early allocation request for draft-ietf-lsr-ospf-bfd-strict-mode

Peter Psenak <ppsenak@cisco.com> Thu, 02 July 2020 07:41 UTC

Return-Path: <ppsenak@cisco.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D1433A0DE8 for <lsr@ietfa.amsl.com>; Thu, 2 Jul 2020 00:41:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.601
X-Spam-Level:
X-Spam-Status: No, score=-9.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AN3n9w9ZwCHI for <lsr@ietfa.amsl.com>; Thu, 2 Jul 2020 00:41:07 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 095BD3A0DE5 for <lsr@ietf.org>; Thu, 2 Jul 2020 00:41:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5640; q=dns/txt; s=iport; t=1593675667; x=1594885267; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=L3oVWBRzt1pApZ1W2g8U0fwdnk2LJXusYlGzqTsSU5Q=; b=NFrVFQO3/nNZQQapP97KBWgVsEbIW59EIozzFPM1Fxztk84SOV5s0Wt5 ol7GYJkJdFondPZyBVkYFv993v3gDwlWPmx1PPyih5Wb2+C0CF9eGpPsm Dkro9Yfa+BtrLnaet47wUd5ixbMCZe2xGlsA+/e4K8WIQwR9Jho2IBJ0P 0=;
X-IronPort-AV: E=Sophos;i="5.75,303,1589241600"; d="scan'208";a="27601982"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 02 Jul 2020 07:41:04 +0000
Received: from [10.60.140.51] (ams-ppsenak-nitro2.cisco.com [10.60.140.51]) by aer-core-3.cisco.com (8.15.2/8.15.2) with ESMTP id 0627f43j021142; Thu, 2 Jul 2020 07:41:04 GMT
To: "Acee Lindem (acee)" <acee@cisco.com>, "iana-prot-param@iana.org" <iana-prot-param@iana.org>
Cc: "lsr@ietf.org" <lsr@ietf.org>, "Ketan Talaulikar (ketant)" <ketant@cisco.com>, "gunter.van_de_velde@nokia.com" <gunter.van_de_velde@nokia.com>, "alvaro.retana@futurewei.com" <alvaro.retana@futurewei.com>
References: <RT-Ticket-1173602@icann.org> <MW3PR11MB457075D951B2EAD4E765BE6DC16F0@MW3PR11MB4570.namprd11.prod.outlook.com> <A1585595-0C7F-4457-B0B0-5B5E3B5F3767@cisco.com> <rt-4.4.3-19904-1593637843-1345.1173602-37-0@icann.org> <F0375E46-732F-4BE7-A893-6F410E6E561A@cisco.com>
From: Peter Psenak <ppsenak@cisco.com>
Message-ID: <6da74fed-96c8-8ac2-697c-d3747ef5c3e4@cisco.com>
Date: Thu, 2 Jul 2020 09:41:03 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <F0375E46-732F-4BE7-A893-6F410E6E561A@cisco.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Outbound-SMTP-Client: 10.60.140.51, ams-ppsenak-nitro2.cisco.com
X-Outbound-Node: aer-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/qoyvJvph7k3sjZ-GilkQKIurLvA>
Subject: Re: [Lsr] [IANA #1173602] Re: IANA early allocation request for draft-ietf-lsr-ospf-bfd-strict-mode
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jul 2020 07:41:09 -0000

Hi Ketan, Acee,

On 01/07/2020 23:24, Acee Lindem (acee) wrote:
> Hi Amanda,
> 
> On 7/1/20, 5:10 PM, "Amanda Baber via RT" <iana-prot-param@iana.org> wrote:
> 
>      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?

I doubt there is any OSPF implementation of 
draft-ietf-lsr-dynamic-flooding, so it may be safer to use the 
0x00000010 for draft-ietf-lsr-ospf-bfd-strict-mode and 0x00000020 for 
draft-ietf-lsr-dynamic-flooding.

thanks,
Peter

> 
> Yes. While a few implementations have the BFD strict-mode configuration, I don't believe any have shipped the LLS signaling yet.
> 
>      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.
> 
> Fine - Thanks,
> Acee
> 
>      Best regards,
> 
>      Amanda Baber
>      Lead IANA Services Specialist
> 
>      On Wed Jul 01 19:38:00 2020, acee@cisco.com 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)" <ketant@cisco.com>
>      > 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: lsr@ietf.org
>      > 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 <lsr-bounces@ietf.org> On Behalf Of internet-drafts@ietf.org
>      > Sent: 30 June 2020 14:20
>      > To: i-d-announce@ietf.org
>      > Cc: lsr@ietf.org
>      > 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
>      > Lsr@ietf.org
>      > https://www.ietf.org/mailman/listinfo/lsr
>      >
> 
> 
> 
>