[trill] Stephen Farrell's No Objection on draft-ietf-trill-directory-assist-mechanisms-11: (with COMMENT)
"Stephen Farrell" <stephen.farrell@cs.tcd.ie> Thu, 19 January 2017 12:19 UTC
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: trill@ietf.org
Delivered-To: trill@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BB7C129499; Thu, 19 Jan 2017 04:19:26 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.40.3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148482836602.10328.15276840045846655138.idtracker@ietfa.amsl.com>
Date: Thu, 19 Jan 2017 04:19:26 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/ny1QF1n06psrEnPJukLmo_AfXac>
Cc: trill-chairs@ietf.org, draft-ietf-trill-directory-assist-mechanisms@ietf.org, shares@ndzh.com, trill@ietf.org
Subject: [trill] Stephen Farrell's No Objection on draft-ietf-trill-directory-assist-mechanisms-11: (with COMMENT)
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "Developing a hybrid router/bridge." <trill.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trill>, <mailto:trill-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/trill/>
List-Post: <mailto:trill@ietf.org>
List-Help: <mailto:trill-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trill>, <mailto:trill-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jan 2017 12:19:26 -0000
Stephen Farrell has entered the following ballot position for draft-ietf-trill-directory-assist-mechanisms-11: 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-trill-directory-assist-mechanisms/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- - 2.6: I wondered why this was useful. Is it for cases where the secondary push service is differently connected or is it in case the primary goes down? Might be good to say. - section 6: what security mechanism differences are there between the push and pull cases? Why aren't those called out here? Forcing the reader to delve into the various other security mechanism RFCs and figure this out themselves seems less good. - section 6: apologies if I asked this before (in which case I forget the answer;-) but how fictional/real is the crypto stuff with TRILL in terms of the likelihood of it being actually used? I ask again, as if the crypto stuff is mostly fictional, then I think you ought note that here, given the attack surface that the directory function creates.
- [trill] Stephen Farrell's No Objection on draft-i… Stephen Farrell
- Re: [trill] Stephen Farrell's No Objection on dra… Donald Eastlake