Re: [Teas] Spencer Dawkins' No Objection on draft-ietf-teas-yang-te-topo-16: (with COMMENT)

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Mon, 25 June 2018 16:34 UTC

Return-Path: <spencerdawkins.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 9C13D130EB5; Mon, 25 Jun 2018 09:34:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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] 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 pTh_G1pRN7FO; Mon, 25 Jun 2018 09:34:34 -0700 (PDT)
Received: from mail-yb0-x242.google.com (mail-yb0-x242.google.com [IPv6:2607:f8b0:4002:c09::242]) (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 87291129C6B; Mon, 25 Jun 2018 09:34:34 -0700 (PDT)
Received: by mail-yb0-x242.google.com with SMTP id a2-v6so4816830ybe.11; Mon, 25 Jun 2018 09:34:34 -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=LhSDJB/MIatnorM0oJBVys99ohCqLUfrYJVDsK66YpU=; b=Pmbotcp+B0nX5X+wRFdGeH1dvDZUpwZr4sVGwOVBB/ul9+oAWso+pCTACFq53Z2Sql nzj8hCa+nl8qKJRxu+Wnyt4WEtG5tsDGzHrDmf/Q6hNDiiwtNxp5Tu8Y6tClYo/lCI5E xmTCNda0cWm7aU3Og6gIyBEObzDIBa9U2fJq7UNZvZqDVdWkbnJxmPXNPfAM9qhGmaqq RyPHJoYZFi6PTfF5+fr3ssYsTmkSjMPkskBYekZfuzLNo/1cEd9/wXymOJo9Ridw0XxX BpgG9RsJu//DKH2j/lxiAe2a1jQg73brk8mn0Zo4OLYFIEkZBmnCgz1c/N2j8zwia7kQ g6Ag==
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=LhSDJB/MIatnorM0oJBVys99ohCqLUfrYJVDsK66YpU=; b=j5zaXNQyl19ABfURWFKqogA+9LhE2xM/NPp5q7hV/1ioG5hepF4+s4KIU3uSPF2i7R RZF/iJXM7db83awOKsvDg+HmS0CzTHAu3n3mIX8l2gA9seCJEEKfLmCdEFTV5vxn+dCt 5qy6rhRtaHg9NKzSRsnuF/LqXdN8TFQo4nBoSi58DAImXyw+hZYIEOQqWv+QtpPqY0vg SSsKBRJKbZlpzB0GGlWt/TS5nAIuXFgruNjOdrsCLC6/ySxqEFDL+QEg0Gn8pmbIkIum 90j+hLtVqWaMi4JkxsV8J9edAXYefoYo9ftDVC5bYcWXVKuEtGuySUd2BsxDeK/i4WyV Xizg==
X-Gm-Message-State: APt69E0KeSy41kDX/pYLjvSl8zx3kYFoOJ1cKrthdsvJviOEPOxapHzi cU8DPK+MmzEqz2sVSQ3BbSch53OYf3ooIXfcP7E=
X-Google-Smtp-Source: ADUXVKIDnl9qJvvU0BAiPcyML7iPCRLqzBS54un3cVJ78sSxRHy9kG5OvWmzMo0S2F6+qNVf3Igmc7tNvkwI8fSngIQ=
X-Received: by 2002:a25:6156:: with SMTP id v83-v6mr6837839ybb.221.1529944473673; Mon, 25 Jun 2018 09:34:33 -0700 (PDT)
MIME-Version: 1.0
References: <152822909542.19153.18014474471246420890.idtracker@ietfa.amsl.com> <CAEz6PPTf9ArTxj29Mvs7gWX+_6g6zhL2xT6koL1i0HoaA01vCg@mail.gmail.com>
In-Reply-To: <CAEz6PPTf9ArTxj29Mvs7gWX+_6g6zhL2xT6koL1i0HoaA01vCg@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Mon, 25 Jun 2018 11:34:20 -0500
Message-ID: <CAKKJt-dXEV-rN8OOcCynWz9s-RoO30Gkk2z=qwDDJNM+A9F7tw@mail.gmail.com>
To: xufeng.liu.ietf@gmail.com
Cc: IESG <iesg@ietf.org>, draft-ietf-teas-yang-te-topo@ietf.org, Lou Berger <lberger@labn.net>, TEAS WG Chairs <teas-chairs@ietf.org>, "TEAS WG (teas@ietf.org)" <teas@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e13f26056f79f482"
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/-0X1SWn1t_FGyZf2USO-yTTr4Co>
Subject: Re: [Teas] Spencer Dawkins' No Objection on draft-ietf-teas-yang-te-topo-16: (with COMMENT)
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.26
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: Mon, 25 Jun 2018 16:34:38 -0000

Hi, Xufeng,

On Sat, Jun 23, 2018 at 9:30 PM Xufeng Liu <xufeng.liu.ietf@gmail.com>
wrote:

> Hi Spencer,
> Thanks for the comments. This section has been re-worded a bit in the
> updated version to clarify. It is reasonable to ask for more explanations,
> for this section, and for some others. The challenge is that a word or two
> might not be sufficient. The TEAS Working Group has discussed such issues,
> and decided to adopt another document *https://tools.ietf.org/html/draft-ietf-teas-te-topo-and-tunnel-modeling
> <https://tools.ietf.org/html/draft-ietf-teas-te-topo-and-tunnel-modeling>*,
> to describe the use cases, model usages, terminologies, and examples, in
> greater details. Another draft, *https://tools.ietf.org/html/draft-ietf-teas-yang-l3-te-topo
> <https://tools.ietf.org/html/draft-ietf-teas-yang-l3-te-topo>*, also
> discusses such a case.
>

(Keeping in mind that I'm a No-Obj ballot, so we're just talking ... if
you're able to point to this work ("to learn more, see ..."), I'd think
that would be helpful without you trying to describe something available in
another document, which would waste your time at best, even if your summary
in this document was perfect.

Do the right thing, of course.

Spencer


> Thanks,
> - Xufeng
>
> On Tue, Jun 5, 2018 at 4:04 PM Spencer Dawkins <
> spencerdawkins.ietf@gmail.com> wrote:
>
>> Spencer Dawkins has entered the following ballot position for
>> draft-ietf-teas-yang-te-topo-16: 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-teas-yang-te-topo/
>>
>>
>>
>> ----------------------------------------------------------------------
>> COMMENT:
>> ----------------------------------------------------------------------
>>
>> I found myself wondering what the last sentence in
>>
>>   - TE Topology may not be congruent to the routing topology (topology
>>      constructed based on routing adjacencies) in a given TE System.
>>      There isn't always a one-to-one association between a TE-link and
>>      a routing adjacency. For example, the presence of a TE link
>>      between a pair of nodes doesn't necessarily imply the existence of
>>      a routing-adjacency between these nodes.
>>
>> was saying about what IS implied between these nodes. I'm guessing, but
>> this
>> draft seems to assume a relatively low level amount of experience with
>> traffic
>> engineering, so I can imagine readers who could benefit from a word or
>> two of
>> explanation.
>>
>>
>>