[bess] Mirja Kühlewind's No Objection on draft-ietf-bess-fat-pw-bgp-03: (with COMMENT)
Mirja Kühlewind <ietf@kuehlewind.net> Fri, 16 February 2018 13:09 UTC
Return-Path: <ietf@kuehlewind.net>
X-Original-To: bess@ietf.org
Delivered-To: bess@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 05F6F120047; Fri, 16 Feb 2018 05:09:47 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Mirja Kühlewind <ietf@kuehlewind.net>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-bess-fat-pw-bgp@ietf.org, aretana.ietf@gmail.com, bess-chairs@ietf.org, martin.vigoureux@nokia.com, bess@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.72.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151878658700.4869.13053386147837719392.idtracker@ietfa.amsl.com>
Date: Fri, 16 Feb 2018 05:09:47 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/VjPo6nVItuvcpT6DclugBwu2kSY>
Subject: [bess] Mirja Kühlewind's No Objection on draft-ietf-bess-fat-pw-bgp-03: (with COMMENT)
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.22
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Feb 2018 13:09:47 -0000
Mirja Kühlewind has entered the following ballot position for draft-ietf-bess-fat-pw-bgp-03: 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-bess-fat-pw-bgp/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- I would be really happy if the document could say lightly more about how flow labels are supposed to be assigned. Is the assumption that all packets of an TCP flow get the same flow label assigned? Just a comment, no action required: Given there are only 4 unsigned bits left and the registry policy is "IETF review", I actually don't think a registry is necessarily needed. The remaining bits could just be assigned by additional RFCs that update RFC4761. Some nits, minor comments: 1) sec 1: Please spell out "ASBR" 2) sec 3: "a PE sending a Control Flags field with T = 1 and receiving a Control Flags field with R = 1 MUST include a flow label in the Pseudowire packet." Must this be a MUST or could this be a SHOULD? 3) In sec 2 there is this text: "the remaining bits, designated Z, MUST be set to zero when sending and MUST be ignored when receiving this Extended Community." In the IANA Consideration section there is this text: "As per [RFC4761] and this document, the remaining bits are unassigned, and MUST be set to zero when sending and MUST be ignored when receiving the Layer2 Info Extended Community." I think the text in section 2 is actually incorrect because it should not talked about the bits that are marked Z but rather about bits that are not assigned in the newly created registry because otherwise you'd need to update this RFC (and RFC4761) every time you assign a new bit. Further I don't think this need to be mentioned in the IANA section and should only be correctly specified in section 2. Except you would like IANA to note this on the registration page but then you should say that...
- [bess] Mirja Kühlewind's No Objection on draft-ie… Mirja Kühlewind