Re: [OSPF] Mirja Kühlewind's No Objection on draft-ietf-ospf-ttz-05: (with COMMENT)

Greg Mirsky <gregimirsky@gmail.com> Thu, 05 January 2017 19:24 UTC

Return-Path: <gregimirsky@gmail.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 89427129638; Thu, 5 Jan 2017 11:24:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 6K6wXWOA82MC; Thu, 5 Jan 2017 11:24:11 -0800 (PST)
Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A4E5C12961F; Thu, 5 Jan 2017 11:24:11 -0800 (PST)
Received: by mail-oi0-x22d.google.com with SMTP id u143so53635oif.3; Thu, 05 Jan 2017 11:24:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=EBjU38Kwi3njrIMKw2iFl1JNhxzj04MMZDdK6r034LU=; b=OcJIznlgq9EOweqUc8e26omKXVFjaByul/syiVU98fm8rm0ufoEK6IZ5PSeDpj1EQP 5JuiDOGJ3XJZz/gf7mc9lXiBNuaOTfvJynAns+3TOM5w8g2oOmfS93mKX4fB9wj6AbF6 +8gSSpgnffovARD00Qh9Ns3jTjIZxSwVO8ZDfKd9MCfrh2bFgzDAiFOw90vuJOmYNUN/ eKKK1r3virMau16QiFdScBNlQjn9yIbQvTohoEPV31+aobVW4t/f1C9dcEQBGOaZy7hD oeifW7diT+hplSTolxf45kMNmwfMARTdEcqQ0KZx6VdHWav+Uiym7P5raVutjk80GIW5 Q/xA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=EBjU38Kwi3njrIMKw2iFl1JNhxzj04MMZDdK6r034LU=; b=cnMo87i/1M9TOu0TCYxT4kfCcVpsk6xFTW1XWp7VfWWx5X1rOCNS+tinSUrxPo1wwA CkiBripE4/KQwxipUydATLEsJ0Rq/UpaEMsuYVf1V+viCg9UsFA6DMj2gARf2zYOsBwC f8A3tIRKnYM6cxXFBwWtt00DLw+jNBeFCVRrbJnIytPtKsz12RpMQo9YnL8qAqGEq8pO JebLs4Ho1W9f2m/1nWfWlz4L7MCsTqoeeG8SmmaPhQnhtoOXkvC+0LjyeeGNqnZlOks8 zWUiGMHla1/yJye65RIOMQqT0gc78FHW9b8nfYnxORa5OHLVFpNnT5H9OYNzpnOrgs7P n2+Q==
X-Gm-Message-State: AIkVDXIVDnnLDNfvolIJbt/arh4Pz13I+3/hjzwzsTWAxn04OD8+iFRlbbtNBF1Tb6Jnq5o/NoVBFivk9NXQ/A==
X-Received: by 10.157.4.66 with SMTP id 60mr33152088otc.205.1483644251006; Thu, 05 Jan 2017 11:24:11 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.42.82 with HTTP; Thu, 5 Jan 2017 11:24:10 -0800 (PST)
In-Reply-To: <148355128660.12937.10479853684898662995.idtracker@ietfa.amsl.com>
References: <148355128660.12937.10479853684898662995.idtracker@ietfa.amsl.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Thu, 05 Jan 2017 11:24:10 -0800
Message-ID: <CA+RyBmVwkXryxg5+Xsgu+oc0Dj2VeYFK2m_gOs4uDPiuCUO3cw@mail.gmail.com>
To: Mirja Kuehlewind <ietf@kuehlewind.net>
Content-Type: multipart/alternative; boundary="001a1136effe8df7ac05455dd83a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/BjTjenhn7X-L3rrwiRD0Wk3mGqs>
Cc: "ospf@ietf.org" <ospf@ietf.org>, The IESG <iesg@ietf.org>, draft-ietf-ospf-ttz@ietf.org, ospf-chairs@ietf.org
Subject: Re: [OSPF] Mirja Kühlewind's No Objection on draft-ietf-ospf-ttz-05: (with COMMENT)
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.17
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, 05 Jan 2017 19:24:13 -0000

Hi Mirja, Authors, et. al,
I have question about allocating new LSA type number for TTZ LSA for
Experimental document from IETF Consensus/IETF Review, as suggested in
Section 14, rather than from the Private Use range.
Or, which may be the best route, partition the Private use range into
Experimental and Private and then allocate the new value out of the
Experimental range.

Regards,
Greg

On Wed, Jan 4, 2017 at 9:34 AM, Mirja Kuehlewind <ietf@kuehlewind.net>
wrote:

> Mirja Kühlewind has entered the following ballot position for
> draft-ietf-ospf-ttz-05: No Objection
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-ospf-ttz/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> Questions on IANA section (not an OSPF expert, so please excuse me if I
> misunderstood something):
> - Don't you have to register both LS types 9 and 10 somehow?
> - And do the "Types for new TLVs in the new TTZ LSA" create a new
> registry or is this an existing one?
>
> Other minor comments:
> - What's a DR? Please spell this out!
> - There is only little normative language used in this doc. Potentially
> some more normative language could make things clearer. However I don't
> have concrete proposals what to change and I believe the most important
> parts are in normative language. So there is no urgent need to change
> anything but maybe another check would be good to make sure normative
> language is used where needed.
>
>
> _______________________________________________
> OSPF mailing list
> OSPF@ietf.org
> https://www.ietf.org/mailman/listinfo/ospf
>