[Teas] Mirja Kühlewind's No Objection on draft-ietf-teas-rsvp-te-srlg-collect-06: (with COMMENT)

"Mirja Kuehlewind" <ietf@kuehlewind.net> Mon, 13 June 2016 11:39 UTC

Return-Path: <ietf@kuehlewind.net>
X-Original-To: teas@ietf.org
Delivered-To: teas@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id AD77412D662; Mon, 13 Jun 2016 04:39:41 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Mirja Kuehlewind <ietf@kuehlewind.net>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.21.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160613113941.12354.86828.idtracker@ietfa.amsl.com>
Date: Mon, 13 Jun 2016 04:39:41 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/JyzmauCJhqhJQOH_ptdSa0L1iGU>
Cc: teas-chairs@ietf.org, draft-ietf-teas-rsvp-te-srlg-collect@ietf.org, teas@ietf.org, vbeeram@juniper.net
Subject: [Teas] Mirja Kühlewind's No Objection on draft-ietf-teas-rsvp-te-srlg-collect-06: (with COMMENT)
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.17
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, 13 Jun 2016 11:39:42 -0000

Mirja Kühlewind has entered the following ballot position for
draft-ietf-teas-rsvp-te-srlg-collect-06: 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:


Minor comments/questions:

- Please spell out RRO in section 4.2

- Why are the following SHOULDs not MUSTs?
"[...] the Path message SHOULD NOT be rejected due to the SRLG recording
   restriction and the Path message SHOULD be forwarded without any SRLG
   sub-object(s) added to the RRO of the corresponding outgoing Path

- Why do you need two (potentially different) policies for the two points
below. Shouldn't a node that provides SRLG information initially, also
always provide updates (as the initial information might otherwise be
wrong and therefore not be able to address the originial intention
anymore - disjoint paths)?
   "o  Whether the node is allowed to participate in SRLG collection.
   o  Whether the node should notify changes to collected SRLG
      information to endpoint nodes as described in section 5.2."