Re: [Teas] Status update on draft-ietf-teas-sf-aware-topo-model
Xufeng Liu <xufeng.liu.ietf@gmail.com> Tue, 26 March 2019 16:00 UTC
Return-Path: <xufeng.liu.ietf@gmail.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4C6B120540 for <teas@ietfa.amsl.com>; Tue, 26 Mar 2019 09:00:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=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 wsmr7d-E8e_b for <teas@ietfa.amsl.com>; Tue, 26 Mar 2019 09:00:13 -0700 (PDT)
Received: from mail-it1-x136.google.com (mail-it1-x136.google.com [IPv6:2607:f8b0:4864:20::136]) (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 5B6A5120521 for <teas@ietf.org>; Tue, 26 Mar 2019 09:00:13 -0700 (PDT)
Received: by mail-it1-x136.google.com with SMTP id h9so20825553itl.1 for <teas@ietf.org>; Tue, 26 Mar 2019 09:00:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=9oHCYVG4mq5uxGXzmup+72QTC+X4gS/T7h7VEfzwYf4=; b=fiRnqqtz7cL3tmL3XPLnzmmCL0OTtX/wVEHvQmW9vElycSfVPY32948nPLFlQQDxJW 1xqKeTvH2l6G0q3+9zwOCQuDJyJIu4Fw8XeQJVFKhqqg7q/7Dam9Q4eOSRvQ0oTbVqSc MW6fY5QulX0zuK+J47/7YFPfgz7zkUs+ibOkU8c6fVjKlebN+1/sZXzJvtg6I3bBtQSR weniJBX6Fxr1lU8i7bt1n89XpNkQW9UlkUEcyS9pEX4pkGvjr6j5tg3JnXdaVgWLOgjD HpFKkGwko141jY76aY9ZeuPsca9tjZD9q42nYgUTizhNXrTiT93ED4hA7HjmtMmvq+3V IYsA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=9oHCYVG4mq5uxGXzmup+72QTC+X4gS/T7h7VEfzwYf4=; b=aI8v1YSn6gCFAyn487vkFTveFz5xKBdNHEKM00F/X1G5PK3CyqjfvfbReraed3pUgS dOHURL/sYVeX8vBSWGx1k9tXHJ5txsUjspf1bm0/orUmdYDPPd2k8eECXR48wUAWDjnY mgegGWVWkCIsY/65pUlFGAMDfTeRyJrKop/DBpSMwDfSdIgI/aIX6IRQaCOMQ3rCieE5 YC3P05SbCkYA7obmGRuHkVx33PzeVoi2Hqa6CkQUfRCKBsmcvpqqyQBqa/z/lwsvdoQB 3VuAIzrfBjY6e8wcbfybAqVLbhMQJJxYG7SsBlH8rnmgMWPAmQDhyqGrwbLSl0EtqZft N6bw==
X-Gm-Message-State: APjAAAU99QdCsos3ChqjvI4MzwcYzAYL/KaCNv2+KhvHboX1bkS9mPpT VvbA1YFw3MBIimjy6Gj4WsyaSOqjtgA/vQkfhqA=
X-Google-Smtp-Source: APXvYqzSFBvjwrjvHG0M1jx9KtJ0SzeR8KdUWsM5Jm/jFy7WQ0DEWgCEfS23vaNzThGMMO9yvhrvnwZG3rdBzucGQKk=
X-Received: by 2002:a24:f30d:: with SMTP id t13mr827349ith.90.1553616012151; Tue, 26 Mar 2019 09:00:12 -0700 (PDT)
MIME-Version: 1.0
References: <CAEz6PPRNjcZZ+m9ZHX7zCyD7VqueftpZCW_UuyBdozfmzSik-g@mail.gmail.com> <030801d4e3bb$26523be0$4001a8c0@gateway.2wire.net>
In-Reply-To: <030801d4e3bb$26523be0$4001a8c0@gateway.2wire.net>
From: Xufeng Liu <xufeng.liu.ietf@gmail.com>
Date: Tue, 26 Mar 2019 12:00:00 -0400
Message-ID: <CAEz6PPRmEvCkKgkn2ybPW4+eZXckk0m5sFzuU_M3a9p-EtVr1w@mail.gmail.com>
To: tom petch <ietfa@btconnect.com>
Cc: TEAS WG <teas@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000858de80585016a71"
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/RtsnZ3qIO-cwh1PnBCE0hmYB9Ew>
Subject: Re: [Teas] Status update on draft-ietf-teas-sf-aware-topo-model
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Mar 2019 16:00:18 -0000
Hi Tom, Thanks for pointing these out. We will fix them in the next revision. - Xufeng On Tue, Mar 26, 2019 at 6:05 AM tom petch <ietfa@btconnect.com> wrote: > Xufeng > > Some quirks. > > Introduction/Abstract do not mention support or lack thereof for NMDA > (which the IESG have been calling for). > > Introduction does not have a reference for YANG leaving the question of > version number uncertain > > Terminology fails to reference RFC8174 > > Expand on first use, perhaps in Terminology, is helpful - TOSCA, SF2LTP, > SF2SF, SF2TTP, CSO > > yang-version 1 is rather limiting > > YANG import statements lack references (which YANG 1.1 allows) > > / reference "TBD";/ > reference "RFC XXXX - SF Aware TE Topology YANG Model"; / > > module ietf-cso-dc > no version > no copyright > no reference to the I-D > no description clauses > no reference clauses > somewhat short of ready IMHO- I think that this needs a lot of work! > > IANA Considerations > RFC Ed.: In this section, replace all occurrences of 'XXXX' with the > actual RFC number (and remove this note). > I suggest that this apply throughout the I-D and that the Note is placed > at the start, before the Introduction (the RFC Editor are happy with > just the one note) > > RFC6020 is a better reference for the IANA Considerations > > [I-D.ietf-netmod-revised-datastores] > RFC8342 > > [I-D.ietf-netmod-yang-tree-diagrams] > RFC8340 > > [I-D.ietf-i2rs-yang-network-topo] > RFC8345 > > import ietf-actn-vn { > does not appear in section 1.3 > > Tom Petch > > ----- Original Message ----- > From: "Xufeng Liu" <xufeng.liu.ietf@gmail.com> > To: "TEAS WG" <teas@ietf.org> > Sent: Saturday, March 23, 2019 12:02 PM > Subject: [Teas] Status update on draft-ietf-teas-sf-aware-topo-model > > > > Current Status: > > > > * The updated revision -03 was posted on Mar 11, 2019: > > > > > Editorial fixes. > > > > Open Issues: > > > > * None. > > > > Next Steps: > > > > * Update the document to align with the latest versions of > > referenced documents, including draft-ietf-teas-yang-te-topo, > > RFC8340, RFC8342, RFC8345, and RFC8459. > > * Update the section of Security Considerations according to latest > > guidelines. > > * Get further reviews. > > * YANG doctor's review. > > * Working Group Last Call after completing above. > > > > Thanks, > > - Xufeng > > > > > ------------------------------------------------------------------------ > -------- > > > > _______________________________________________ > > Teas mailing list > > Teas@ietf.org > > https://www.ietf.org/mailman/listinfo/teas > > > >
- [Teas] Status update on draft-ietf-teas-sf-aware-… Xufeng Liu
- Re: [Teas] Status update on draft-ietf-teas-sf-aw… tom petch
- Re: [Teas] Status update on draft-ietf-teas-sf-aw… Xufeng Liu
- Re: [Teas] Status update on draft-ietf-teas-sf-aw… Xufeng Liu
- Re: [Teas] Status update on draft-ietf-teas-sf-aw… ietfa
- Re: [Teas] Status update on draft-ietf-teas-sf-aw… Xufeng Liu
- Re: [Teas] Status update on draft-ietf-teas-sf-aw… Xufeng Liu
- Re: [Teas] Status update on draft-ietf-teas-sf-aw… tom petch
- Re: [Teas] Status update on draft-ietf-teas-sf-aw… Xufeng Liu
- Re: [Teas] Status update on draft-ietf-teas-sf-aw… tom petch
- Re: [Teas] Status update on draft-ietf-teas-sf-aw… Xufeng Liu