[trill] Suresh Krishnan's Discuss on draft-ietf-trill-arp-optimization-06: (with DISCUSS and COMMENT)

"Suresh Krishnan" <suresh.krishnan@ericsson.com> Wed, 06 July 2016 04:36 UTC

Return-Path: <suresh.krishnan@ericsson.com>
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 27C1912B03F; Tue, 5 Jul 2016 21:36:13 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.25.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160706043613.22358.34214.idtracker@ietfa.amsl.com>
Date: Tue, 05 Jul 2016 21:36:13 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/n3s99l1ykhjWpmFd8eWDrsd-T3Y>
Cc: draft-ietf-trill-arp-optimization@ietf.org, trill-chairs@ietf.org, trill@ietf.org, skh@ndzh.com
Subject: [trill] Suresh Krishnan's Discuss on draft-ietf-trill-arp-optimization-06: (with DISCUSS and 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: Wed, 06 Jul 2016 04:36:13 -0000

Suresh Krishnan has entered the following ballot position for
draft-ietf-trill-arp-optimization-06: Discuss

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-arp-optimization/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

* After the ingress RBridge learns the mapping between an IPv6 address
and a MAC address how is the liveness being tested/maintained? i.e. If a
"learnt" target IP goes off link and the Rbridge keeps responding to NS
messages wouldn't it make troubleshooting a nightmare?
* Section 3.2 case a): There is no guidance as to why or when an Rbridge
would pick cases a1..a5. e.g. When a SEND NS is received only option a2
can work and all others will fail.  
* Section 3.2 case a.1): What should be the source IPv6 address of the NA
generated by the ingress RBridge? Will this be an address of the target
of the NS or one of the ingress Rbridge that responds?
* Section 3.2: How is an ND message where the target IP is not known
handled? This case seems to be left out.


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

* The draft contains no discussion of SEND (RFC3971) in the Security
considerations section when talking about forged ND messages.