[trill] Suggested non-technical additions to draft-ietf-trill-esadi-07

Donald Eastlake <d3e3e3@gmail.com> Tue, 27 May 2014 03:42 UTC

Return-Path: <d3e3e3@gmail.com>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD4351A0347 for <trill@ietfa.amsl.com>; Mon, 26 May 2014 20:42:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.749
X-Spam-Level:
X-Spam-Status: No, score=0.749 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, J_CHICKENPOX_12=0.6, SPF_PASS=-0.001] autolearn=no
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 K_5xPnb9_Ck0 for <trill@ietfa.amsl.com>; Mon, 26 May 2014 20:42:11 -0700 (PDT)
Received: from mail-ob0-x232.google.com (mail-ob0-x232.google.com [IPv6:2607:f8b0:4003:c01::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E2181A02D2 for <trill@ietf.org>; Mon, 26 May 2014 20:42:11 -0700 (PDT)
Received: by mail-ob0-f178.google.com with SMTP id va2so8781991obc.9 for <trill@ietf.org>; Mon, 26 May 2014 20:42:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=DVE/qjqnBnM9NKH+kj384V9S+eBhYAYXFP1bu8wxYas=; b=M7LmgcQLpBXCs2BUGJREVkjnJ3oeM3VFBkl776onYu2YvfzCOlLNLj2k/P26/0Uyle fCPGD6HfOGho4OeTVMA/+V4tvhJbHNVR5JXbUjSD6z6hF1LNjyYynSQa0ryF96MPYrlQ 1kNacLLzRuAMVj9MM0/URuoCkLd3jWE1pEaFSG3LrKOmvG4GmJt8CpQBfpSQ2lxTIX5l Uawke+zThMlkd4VUDbV4PW+HYuzwJ29SLLbVf6sAQkb/+JzzsoKiVCzNehtMRagROb5e V3sikZ5x28ffvo1BGjJp/gs37g1y7iWv5jroNTyJfyeCC5LdleTwT9YJxsX/aN1OgISk fLJw==
X-Received: by 10.60.39.103 with SMTP id o7mr29089876oek.17.1401162127895; Mon, 26 May 2014 20:42:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.25.41 with HTTP; Mon, 26 May 2014 20:41:46 -0700 (PDT)
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Mon, 26 May 2014 23:41:46 -0400
Message-ID: <CAF4+nEF7ywBS=WQMfQuoomL_o96YD836nPs9t0s4YSAr7r_dEQ@mail.gmail.com>
To: "trill@ietf.org" <trill@ietf.org>
Content-Type: multipart/mixed; boundary="089e013cba44e8d1bc04fa597a54"
Archived-At: http://mailarchive.ietf.org/arch/msg/trill/NMQ7zc0eDSh4fll-9laa0-nbKr0
Subject: [trill] Suggested non-technical additions to draft-ietf-trill-esadi-07
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
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: <http://www.ietf.org/mail-archive/web/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: Tue, 27 May 2014 03:42:12 -0000

Hi,

In its review of draft-ietf-trill-esadi-07, members of the IESG
suggested a number of areas for additions. In my opinion, none of
these make any significant technical change to the draft, but together
they are extensive enough that I'd like to give the WG an opportunity
to comment on the changes. If you have comments on these changes,
please post them to this list or send them to Jon Hudson and myself
within a week.

Changes (ignoring typo corrections and reference updates for recently
published RFCs) are as follows:

(1) Addition of a Privacy Considerations section as a subsection of
the existing Security Considerations. See attachment 1.

(2) Additional information about changes from [RFC6325] ESADI and what
would happen in a TRILL campus with a mix of RBridges implementing
[RFC6325] ESADI and those implementing ESADI according to this draft.
See attachment 2, an updated and extended version of Appendix A. If
there are responses to the query posted by Jon Hudson
http://www.ietf.org/mail-archive/web/trill/current/msg06286.html
indicating that there are customer deployments of [RFC6325] ESADI,
then additional changes may be required.

(3) Change the first sentence of the Security Considerations section
to the following two sentences and add a reference to [RFC5310] to
Section 6.3:

   "ESADI PDUs can be authenticated through the inclusion of the
   Authentication TLV [RFC5310]. Defaults for such authentication are
   described in Section 6.3."

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com