Re: [OSPF] [IANA #1047782] Protocol Action: 'OSPFv3 LSA Extendibility' to Proposed Standard (draft-ietf-ospf-ospfv3-lsa-extend-23.txt)

Peter Psenak <ppsenak@cisco.com> Thu, 01 February 2018 09:03 UTC

Return-Path: <ppsenak@cisco.com>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E92361316AC for <ospf@ietfa.amsl.com>; Thu, 1 Feb 2018 01:03:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 gci-FilAxbmR for <ospf@ietfa.amsl.com>; Thu, 1 Feb 2018 01:03:00 -0800 (PST)
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 EAA4E13165E for <ospf@ietf.org>; Thu, 1 Feb 2018 01:02:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6634; q=dns/txt; s=iport; t=1517475757; x=1518685357; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=YBPZ/dI6O5O9THpfN8ScjODB5P8ZrQr9mfVHvIA7Qtk=; b=bj2PR7ctZEjfuKS7VkiNTjLvDprCz0EAdbFjr9difjPmTsNmiP2oBHyN yPrmV+SmvfWEZrf+ejeEgzm9V9LcIPLVYPHjFBEj+9Jw1vF1bPEohttG9 48i5p17nu1eOqI/q/w0KFa2jCPBwxx5ODciT1e0OYSx5oV1hsPA7pzMRl s=;
X-IronPort-AV: E=Sophos;i="5.46,443,1511827200"; d="scan'208";a="1788369"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Feb 2018 09:02:35 +0000
Received: from [10.60.140.51] (ams-ppsenak-nitro2.cisco.com [10.60.140.51]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id w1192YiC004357; Thu, 1 Feb 2018 09:02:34 GMT
Message-ID: <5A72D7C0.8060502@cisco.com>
Date: Thu, 01 Feb 2018 10:02:56 +0100
From: Peter Psenak <ppsenak@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: "Acee Lindem (acee)" <acee@cisco.com>
CC: "Abhay Roy (akr)" <akr@cisco.com>, "dirk.goethals@nokia.com" <dirk.goethals@nokia.com>, OSPF List <ospf@ietf.org>
References: <RT-Ticket-1047782@icann.org> <151724292326.13004.18305618678457051977.idtracker@ietfa.amsl.com> <rt-4.2.9-12542-1517426260-517.1047782-7-0@icann.org> <631C95C8-94DC-4C78-9275-AD70051552C7@cisco.com> <rt-4.2.9-12550-1517426956-632.1047782-7-0@icann.org> <rt-4.2.9-12542-1517436764-99.1047782-7-0@icann.org> <CAF7A434-391F-494F-9EE6-3DDD73F51861@cisco.com>
In-Reply-To: <CAF7A434-391F-494F-9EE6-3DDD73F51861@cisco.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/n0Ylqno1DcayE4784sJO3l3tQ4I>
Subject: Re: [OSPF] [IANA #1047782] Protocol Action: 'OSPFv3 LSA Extendibility' to Proposed Standard (draft-ietf-ospf-ospfv3-lsa-extend-23.txt)
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ospf/>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Feb 2018 09:03:03 -0000

Hi Acee,

as a next step, can you please ask for a early IANA allocation from the 
new registries as specified in section 8 of 
draft-ietf-ospf-ospfv3-segment-routing-extensions-11.txt

thanks,
Peter

On 01/02/18 00:04 , Acee Lindem (acee) wrote:
> Hi Amanda,
>
> This is correct.
>
> Thanks
> Acee
>
> On 1/31/18, 5:12 PM, "Amanda Baber via RT" <drafts-approval@iana.org> wrote:
>
>      Hi Acee,
>
>      I apologize for my oversight. There's no problem with placing the registrations in Section 2.
>
>      Can you confirm that this action has been completed correctly?
>
>      ACTION 4
>
>      We've registered the following OSPFv3 LSA Function Codes:
>
>      33	E-Router-LSA	[RFC-ietf-ospf-ospfv3-lsa-extend-23]
>      34	E-Network-LSA	[RFC-ietf-ospf-ospfv3-lsa-extend-23]
>      35	E-Inter-Area-Prefix-LSA	[RFC-ietf-ospf-ospfv3-lsa-extend-23]
>      36	E-Inter-Area-Router-LSA	[RFC-ietf-ospf-ospfv3-lsa-extend-23]
>      37	E-AS-External-LSA	[RFC-ietf-ospf-ospfv3-lsa-extend-23]
>      38	Unused (Not to be allocated)	[RFC-ietf-ospf-ospfv3-lsa-extend-23]
>      39	E-Type-7-LSA	[RFC-ietf-ospf-ospfv3-lsa-extend-23]
>      40	E-Link-LSA	[RFC-ietf-ospf-ospfv3-lsa-extend-23]
>      41	E-Intra-Area-Prefix-LSA	[RFC-ietf-ospf-ospfv3-lsa-extend-23]
>
>      Please see
>      https://www.iana.org/assignments/ospfv3-parameters
>
>      thanks,
>      Amanda
>
>
>      On Wed Jan 31 19:29:16 2018, acee@cisco.com wrote:
>      > Hi Amanda,
>      >
>      > The actions below are correct. However, the one (the first) IANA
>      > action from the draft is missing:
>      >
>      > This specification defines nine OSPFv3 Extended LSA types as
>      > described in Section 2.  These are added the existing OSPFv3 LSA
>      > Function Codes registry.
>      >
>      > I guess I should have repeated these in the IANA Considerations
>      > section.
>      >
>      >
>      > LSA function code   LS Type   Description
>      > ----------------------------------------------------
>      > 33                  0xA021    E-Router-LSA
>      > 34                  0xA022    E-Network-LSA
>      > 35                  0xA023    E-Inter-Area-Prefix-LSA
>      > 36                  0xA024    E-Inter-Area-Router-LSA
>      > 37                  0xC025    E-AS-External-LSA
>      > 38                  N/A       Unused (Not to be allocated)
>      > 39                  0xA027    E-Type-7-LSA
>      > 40                  0x8028    E-Link-LSA
>      > 41                  0xA029    E-Intra-Area-Prefix-LSA
>      >
>      >
>      > OSPFv3 Extended LSA Types
>      >
>      > Thanks,
>      >  Acee
>      >
>      >
>      >
>      >
>      > On 1/31/18, 2:17 PM, "Amanda Baber via RT" <drafts-approval@iana.org>
>      > wrote:
>      >
>      > Dear Authors:
>      >
>      > ATTENTION: A RESPONSE TO THIS MESSAGE IS NEEDED
>      >
>      > We've completed the registry actions for the following RFC-to-be:
>      >
>      > draft-ietf-ospf-ospfv3-lsa-extend-23
>      >
>      > ACTION 1:
>      >
>      > We've added the following entry to the OSPFv3 Prefix Options (8 bits)
>      > registry:
>      >
>      > 0x20        N-bit   [RFC-ietf-ospf-ospfv3-lsa-extend-23]
>      >
>      > Please see
>      > https://www.iana.org/assignments/ospfv3-parameters
>      >
>      >
>      > ACTION 2:
>      >
>      > We've created the following registry:
>      >
>      > OSPFv3 Extended-LSA TLVs
>      > Reference: [RFC-ietf-ospf-ospfv3-lsa-extend-23]
>      >
>      > Range       Registration Procedures
>      > 9-32767     IETF Review or IESG Approval
>      > 33024-45055 First Come First Served
>      >
>      > Value       Description     Reference
>      > 0   Reserved        [RFC-ietf-ospf-ospfv3-lsa-extend-23]
>      > 1   Router-Link TLV [RFC-ietf-ospf-ospfv3-lsa-extend-23]
>      > 2   Attached-Routers TLV    [RFC-ietf-ospf-ospfv3-lsa-extend-23]
>      > 3   Inter-Area Prefix TLV   [RFC-ietf-ospf-ospfv3-lsa-extend-23]
>      > 4   Inter-Area Router TLV   [RFC-ietf-ospf-ospfv3-lsa-extend-23]
>      > 5   External Prefix TLV     [RFC-ietf-ospf-ospfv3-lsa-extend-23]
>      > 6   Intra-Area Prefix TLV   [RFC-ietf-ospf-ospfv3-lsa-extend-23]
>      > 7   IPv6 Link-Local Address TLV     [RFC-ietf-ospf-ospfv3-lsa-extend-
>      > 23]
>      > 8   IPv4 Link-Local Address TLV     [RFC-ietf-ospf-ospfv3-lsa-extend-
>      > 23]
>      >      9-32767     Unassigned
>      > 32768-33023 Reserved for Experimental Use   [RFC-ietf-ospf-ospfv3-lsa-
>      > extend-23]
>      >      33024-45055 Unassigned
>      > 45056-65535 Reserved        [RFC-ietf-ospf-ospfv3-lsa-extend-23]
>      >
>      > Please see
>      > https://www.iana.org/assignments/ospfv3-parameters
>      >
>      >
>      > ACTION 3:
>      >
>      > We've created the following registry:
>      >
>      > OSPFv3 Extended-LSA sub-TLVs
>      > Reference: [RFC-ietf-ospf-ospfv3-lsa-extend-23]
>      >
>      > Range       Registration Procedures
>      > 4-32767     IETF Review or IESG Approval
>      > 33024-45055 First Come First Served
>      >
>      > Value       Description     Reference
>      > 0   Reserved        [RFC-ietf-ospf-ospfv3-lsa-extend-23]
>      > 1   IPv6 Forwarding Address sub-TLV  [RFC-ietf-ospf-ospfv3-lsa-extend-
>      > 23]
>      > 2   IPv4 Forwarding Address sub-TLV  [RFC-ietf-ospf-ospfv3-lsa-extend-
>      > 23]
>      > 3   Route Tag sub-TLV       [RFC-ietf-ospf-ospfv3-lsa-extend-23]
>      >      4-32767     Unassigned
>      > 32768-33023 Reserved for Experimental Use   [RFC-ietf-ospf-ospfv3-lsa-
>      > extend-23]
>      >      33024-45055 Unassigned
>      > 45056-65535 Reserved        [RFC-ietf-ospf-ospfv3-lsa-extend-23]
>      >
>      > Please see
>      > https://www.iana.org/assignments/ospfv3-parameters
>      >
>      >
>      > Please let us know whether this document's registry actions have been
>      > completed correctly. Once we receive your confirmation, we'll notify
>      > the RFC Editor that the actions are complete. If a team of authors is
>      > responsible for the document, and the actions have been performed
>      > correctly, please send a single confirmation message.
>      >
>      > We'll update any references to this document in the registries when
>      > the RFC Editor notifies us that they've assigned an RFC number.
>      >
>      > Best regards,
>      >
>      > Amanda Baber
>      > Lead IANA Services Specialist
>      >
>      >
>      >
>
>
>
>
>