Re: [trill] Working group LC on draft-ietf-trill-address-flush-03 (10/2 - 10/16)

R Parameswaran <> Wed, 11 October 2017 15:33 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B6048120720 for <>; Wed, 11 Oct 2017 08:33:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -0.749
X-Spam-Status: No, score=-0.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id y8ANIymJDsyY for <>; Wed, 11 Oct 2017 08:33:39 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:400d:c0d::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 0CB8412008A for <>; Wed, 11 Oct 2017 08:33:39 -0700 (PDT)
Received: by with SMTP id z50so6380390qtj.4 for <>; Wed, 11 Oct 2017 08:33:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=6mCkGCewtoHfYHypYlFj/JaNaYC1v9sbZFA96iQUO6w=; b=r3jEpeTbwl2Mj8pp7Tqjle3EqT5d9AKMPnVvWODMz2haFb+leiOTnH3A93W0Y19Qtk nB9XhKcgrsH2YEb+qu9P9lD4jOTQdDzLP6HWX2kChvheFmsKWjxv7WL7o6VvAWWJdjr2 L8rFum85wKfl0HIe5SSkwAZiVsK8bawxaByQXBErEoJ5p9LBxmhKuaDVMpLDzY2Zwk4q vOVTCzYRwJE1E++zXx7Mxs+Nb8kPtG/7j2YsVm0FN3s/+598MixjMEsemGBxs9hG2p23 +AZxexA4+1vo2h46Oc35YA9DoUh7d2eQ/Pxx0nsLjsd4/tRHUKu4jOaYsfi0lP6KR3DQ oHzA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=6mCkGCewtoHfYHypYlFj/JaNaYC1v9sbZFA96iQUO6w=; b=rapJERf/zEWSgZGRUKnA0zsiMix/uo6VseUKpBk19j9bsmspF87RsZPl/GdrRGxWkU P8lhXpS3rwjbC6LYZiZ7OvxAn9DL7p5mP36FflM0CcwPicjv5UzXgupEccdCikU9LX5G wztl3tdBeOVEe4OiYUEUtKtndTn8TPyR0FOUbPlW7vNIReuitpfqFoofwCzqK1lKeQT2 0ePxtsVQ3z/fo0ZQAg7EJTpfInQco81ryx+epxv1n0t9bC6NWkxmi1xCumT5FPKFsfEW uRjfF6dhTwYqUOVBWv6XgP5tCP8HLJ7IX89UxJun3Rt2uDlvEdnbc6Lqb9/0Q9DOHt/z 5Z1g==
X-Gm-Message-State: AMCzsaVIu24/jDuFofxykSLbg6VYuPehnmh00l+Re6S465cOUqNhnZBb HOAOo6R++i4lst5qCRYtYBbeH94wxXXgthFG77Dz4L6q
X-Google-Smtp-Source: ABhQp+SqZ9FlaPVTcYx304rEApAbEmHqs2hTJV55BD4utVA5XYd3LN+7YxrZNZr2OykMesEyEfSWL3hzuckJ9un+qiI=
X-Received: by with SMTP id 30mr45612qtp.334.1507736017508; Wed, 11 Oct 2017 08:33:37 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Wed, 11 Oct 2017 08:33:36 -0700 (PDT)
From: R Parameswaran <>
Date: Wed, 11 Oct 2017 08:33:36 -0700
Message-ID: <>
Cc: Donald Eastlake <>
Content-Type: multipart/alternative; boundary="001a11407326bd1f0e055b472592"
Archived-At: <>
Subject: Re: [trill] Working group LC on draft-ietf-trill-address-flush-03 (10/2 - 10/16)
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Developing a hybrid router/bridge." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 11 Oct 2017 15:33:41 -0000


I support the adoption/standardization of this draft, use case seems real.
Informal review per request, comments:

1. Could probably use a text review prior to the next step. One or
   two sentences can be tightened up:

   a. 2.2 item 3 ("The TLVs in an extensible Address Flush message are .. ")

   b. typo in 2.2.8 (type = 8 vs 7 in figure).

2. The draft gives a number of ways to specify an address flush e.g.
   various ways specify vlans, FGLs and MAC addresses (e.g. lists
   blocks, bitlists). Do we know if valid use cases for all these ways of
   specifying a flush? Also, for block specifiers what happens if there
   are overlapping blocks?

3. With a TLV length of 8 bits you cannot really specify more than
   192 FGLs and 42 MAC addresses. Are multiple TLVs of the same type
   allowed? Instead, would it make sense to have a longer TLV length
   field of say 16 bits?

4. It looks like a spoofed address flush can be used to mount a denial
   of service attack. If that is protected by encryption or by perimeter
   security, it might be good to explicitly call this out in Section 4,
   Security Considerations.



[trill] Working group LC on draft-ietf-trill-address-flush-03 (10/2 - 10/16)

Donald Eastlake <> Mon, 02 October 2017 23:11 UTCShow header

This begins a 2 week WG LC on draft-ietf-trill-address-flush-03.txt.
Please indicate if you think the draft is ready for publication and is
useful for TRILL deployments.

(WG Secretary for the Chairs: Sue Hares & Jon Hudson)
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA


   - [trill] 答复: Working group LC on draft-ietf-trill-address-flush-03
   (10/2 - 10/16)
   zhangdacheng <>