[trill] draft-ietf-trill-o-pw comments

Erik Nordmark <nordmark@acm.org> Mon, 25 November 2013 17:37 UTC

Return-Path: <nordmark@acm.org>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 6BFCB1ADFC3 for <trill@ietfa.amsl.com>; Mon, 25 Nov 2013 09:37:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id Ig2yvQtM5aUD for <trill@ietfa.amsl.com>; Mon, 25 Nov 2013 09:37:06 -0800 (PST)
Received: from d.mail.sonic.net (d.mail.sonic.net []) by ietfa.amsl.com (Postfix) with ESMTP id 6602D1ADF9A for <trill@ietf.org>; Mon, 25 Nov 2013 09:37:06 -0800 (PST)
Received: from [] ([]) (authenticated bits=0) by d.mail.sonic.net (8.14.4/8.14.4) with ESMTP id rAPHb4it010170 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Mon, 25 Nov 2013 09:37:04 -0800
Message-ID: <52938AC0.5060901@acm.org>
Date: Mon, 25 Nov 2013 09:37:04 -0800
From: Erik Nordmark <nordmark@acm.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: "trill@ietf.org" <trill@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Sonic-ID: C;COvsMvhV4xGZMT5I53gOpw== M;oJ0BM/hV4xGZMT5I53gOpw==
Subject: [trill] draft-ietf-trill-o-pw comments
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: Mon, 25 Nov 2013 17:37:07 -0000

I've reviewed the document before writing up the PROTO.
A few requests for clarifications.

The two packet formats include a specific bit pattern:
       |      PPP Header 0x005d        |  2 octets

       |      PPP Header 0x405d        |  2 octets

For the un-initiated it would make sense to add a reference in the text 
below the figures. Something like "The PPP Header (0x005d and 0x405d 
respectively) is the header for data frames and IS-IS packets as 
specified in RFC XXX". (Or something in that vein.)

In security considerations we have
    For security considerations introduced by carrying PPP TRILL links
    over pseudowires, see [RFC3985].
I assume RFC 3985 doesn't talk about TRILL - but about PPP in general. 
Thus it would be more clear if we drop "TRILL" from that sentence.

The 3rd paragraph starts with
    Not all implementations need to include specific security mechanisms
    at the pseudowire layer ...
Is this a relaxation of the general PW security requirements? Or merely 
re-stating the stance for security for PW? It would make sense to spell 
that out in the document.