Re: [trill] Suresh Krishnan's Discuss on draft-ietf-trill-irb-13: (with DISCUSS and COMMENT)

Suresh Krishnan <suresh.krishnan@ericsson.com> Fri, 01 July 2016 03:14 UTC

Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BEB512B077; Thu, 30 Jun 2016 20:14:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 VXpHZvlaK_-5; Thu, 30 Jun 2016 20:14:37 -0700 (PDT)
Received: from usplmg20.ericsson.net (usplmg20.ericsson.net [198.24.6.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5001B12B037; Thu, 30 Jun 2016 20:14:37 -0700 (PDT)
X-AuditID: c618062d-f79886d000002334-56-5775d5c043b9
Received: from EUSAAHC005.ericsson.se (Unknown_Domain [147.117.188.87]) by usplmg20.ericsson.net (Symantec Mail Security) with SMTP id A6.6C.09012.0C5D5775; Fri, 1 Jul 2016 04:30:24 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC005.ericsson.se ([147.117.188.87]) with mapi id 14.03.0294.000; Thu, 30 Jun 2016 23:14:36 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Thread-Topic: Suresh Krishnan's Discuss on draft-ietf-trill-irb-13: (with DISCUSS and COMMENT)
Thread-Index: AQHR0lsu1+43kL5jpUC7R8Hg/QlIDg==
Date: Fri, 1 Jul 2016 03:14:35 +0000
Message-ID: <E87B771635882B4BA20096B589152EF643D4B4A2@eusaamb107.ericsson.se>
References: <20160629230835.30452.44953.idtracker@ietfa.amsl.com> <CAF4+nEEaFy26uW3k1fxm0pG0J+-dZ5YGn64oW71=GhMNMEsB5Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.117.188.11]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrLLMWRmVeSWpSXmKPExsUyuXRPuO6Bq6XhBlMf6Fgc3K5p8ezyWmaL GX8mMlv8PHGZ2eL95O1sDqweO2fdZfdYsuQnUwBTFJdNSmpOZllqkb5dAlfGzxdLWQqmSFcs nfWBvYFxpVgXIweHhICJxL85Vl2MnECmmMSFe+vZuhi5OIQEjjJK9E58CeUsZ5RYN/sSI0gV G1DDhp2fmUBsEQE1idfLF7CA2MwCWxkltmyQBbGFBeIl/h88yASyQEQgQeLHpAKIcj2JnefW s4LYLAIqEm8vzwQbySvgK/GgfREzxK4ORonmGzPBZjICXfT91BomiPniEreezGeCuFRAYsme 88wQtqjEy8f/WCFsJYmPv+ezQ9TrSCzY/YkNwtaWWLbwNTPEMkGJkzOfsExgFJ2FZOwsJC2z kLTMQtKygJFlFSNHaXFBTm66kcEmRmCkHJNg093BeH+65yFGAQ5GJR7ehGml4UKsiWXFlbmH GCU4mJVEeL3vAIV4UxIrq1KL8uOLSnNSiw8xSnOwKInzij1SDBcSSE8sSc1OTS1ILYLJMnFw SjUwFn1N+pT/cb3UdZOvGkcPN/UfMq08pJL1nLu59oxoztdiiYWfeiuO19r+3z9NPYXlwWuB +7620q0diot8i+aI2ecXBh1Xv9QvzXTekbtps9vdr/znlH4sU+PjNj+g/ECg+unh1nfauYbz V6V9kOuZ++eS5hyh6slM9dcKTfT6p7LekKySnTxJiaU4I9FQi7moOBEAurHW5pACAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/YN6WS-rkW6l1PUWo_rGXcyLyAIQ>
Cc: "trill-chairs@ietf.org" <trill-chairs@ietf.org>, The IESG <iesg@ietf.org>, "trill@ietf.org" <trill@ietf.org>, "draft-ietf-trill-irb@ietf.org" <draft-ietf-trill-irb@ietf.org>
Subject: Re: [trill] Suresh Krishnan's Discuss on draft-ietf-trill-irb-13: (with DISCUSS and COMMENT)
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.17
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: <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: Fri, 01 Jul 2016 03:14:39 -0000

Hi Donald,
   Your proposed changes and clarifications look good to me. I will look over 
the new version when it is posted.

Thanks
Suresh

On 06/30/2016 02:13 PM, Donald Eastlake wrote:
> Hi Suresh,
>
> Thanks for your comments. See below.
>
> On Wed, Jun 29, 2016 at 7:08 PM, Suresh Krishnan
> <suresh.krishnan@ericsson.com> wrote:
>> Suresh Krishnan has entered the following ballot position for
>> draft-ietf-trill-irb-13: Discuss
>>
>> ...
>>
>> ----------------------------------------------------------------------
>> DISCUSS:
>> ----------------------------------------------------------------------
>>
>> * Section 6 has a few errors that need to get fixed before this document
>> goes forward. e.g. It is not clear what a "192.0.2.0/32" subnet means
>> especially since the only host shown to be on the subnet 192.0.2.2 cannot
>> obviously fall inside the subnet range. The /32 needs to be replaced with
>> something shorter depending on what the authors/WG intended (say a /24).
>
> Yes. That should have been "/24".
>
>> * RB2 seems to be advertising ES2s IPv4 address 198.51.100.2/32 instead
>> of the prefix of the subnet while RB1 seems to be advertising the the
>> IPv4 prefix of the ES1 subnet. One of these is wrong. Not sure which one
>> is intended.
>
> It should be the prefix in both cases.
>
>> * What is the rationale for using a /112 IPv6 prefix for numbering an
>> IPv6 link with hosts? Things like SLAAC (RFC4862) will not work in such
>> links. Is there a reason the authors want to use a longer than /64?
>> Please read RFC7421 for advantages of using a /64 instead and to find out
>> what things break if you do not use a /64.
>
> The Distributed Layer 3 gateway specified in this draft is expect to
> primarily be used in data centers where I would expect everything to
> be strictly configured by an orchestration system. Thus stateless
> autoconfiguration seems less likely and I suspect it just wasn't
> through of. However, I don't see a problem with changing this to "/64"
> and the mechanism specified could be used in other contexts outside
> data centers.
>
>> ----------------------------------------------------------------------
>> COMMENT:
>> ----------------------------------------------------------------------
>>
>> Section 5: What does "Layer 2 routing" mean in this context?
>
> Previously standardized TRILL routing, which is based on destination
> MAC address as mapped into a TRILL nickname. The wording can be
> clarified.
>
>> Sections 7.3 & 7.4: What is the point of including these sub-TLVs if no
>> prefix is being advertised? (The Total Length=0 case specified in the
>> document)
>
> Sometimes a zero length has some special meaning. The draft just says
> that it has the obvious meaning although it is not a particularly
> useful value.
>
> Thanks,
> Donald
> ===============================
>   Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>   155 Beaver Street, Milford, MA 01757 USA
>   d3e3e3@gmail.com
>