Re: [bess] handling DAD in draft-ietf-bess-evpn-inter-subnet-forwarding-05

"Ali Sajassi (sajassi)" <sajassi@cisco.com> Mon, 04 February 2019 05:56 UTC

Return-Path: <sajassi@cisco.com>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D846130E09 for <bess@ietfa.amsl.com>; Sun, 3 Feb 2019 21:56:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.643
X-Spam-Level:
X-Spam-Status: No, score=-14.643 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 gNJipTGZGF3m for <bess@ietfa.amsl.com>; Sun, 3 Feb 2019 21:56:18 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 85CDA1294FA for <bess@ietf.org>; Sun, 3 Feb 2019 21:56:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2116; q=dns/txt; s=iport; t=1549259778; x=1550469378; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=Cyv7b1D6Q5XeohxpZjqgD7PCGDP6dwKNSkRGw6UhANw=; b=c9s+FsDzXqIpXQvg+JkVy3+fqjt5jSVULq3rHUJXHJyVKpq1xuw8NBWp 0rwJzYPFwq0B8VuxBHaU1NkYLQuX4pLqDQ5fB+2/n8+ZAmqFqyaCRzo5F Vxh/pcftNkrzNOZsQmoQKc3SwcSWZMPqsBKrPFdiJjFslMyPPpESpRN12 Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AHAACV01dc/5hdJa1kGQEBAQEBAQEBAQEBAQcBAQEBAQGBUwIBAQEBAQsBggOBaicKg3mfQY5ogXsLAQGEbAIXgn0iNgcNAQMBAQIBAQJtKIVLBiMRRRACAQgaAiYCAgIfERUQAgQOBYMigWoDFalcgS+Hfg2CHhR3izYXgX+BOB+CFzWCV4UzMYImAolVgiOWRzMJAo59gzsZkkSQeIpgAhEUgScmATCBVnAVZQGCQYIoF44eQTGOD4EfAQE
X-IronPort-AV: E=Sophos;i="5.56,559,1539648000"; d="scan'208";a="512391624"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Feb 2019 05:56:17 +0000
Received: from XCH-RTP-018.cisco.com (xch-rtp-018.cisco.com [64.101.220.158]) by rcdn-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id x145uGhp003569 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 4 Feb 2019 05:56:17 GMT
Received: from xch-rtp-005.cisco.com (64.101.220.145) by XCH-RTP-018.cisco.com (64.101.220.158) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Mon, 4 Feb 2019 00:56:15 -0500
Received: from xch-rtp-005.cisco.com ([64.101.220.145]) by XCH-RTP-005.cisco.com ([64.101.220.145]) with mapi id 15.00.1395.000; Mon, 4 Feb 2019 00:56:15 -0500
From: "Ali Sajassi (sajassi)" <sajassi@cisco.com>
To: Sowmini Varadhan <sowmini05@gmail.com>
CC: "bess@ietf.org" <bess@ietf.org>, John E Drake <jdrake@juniper.net>, "Samir Thoria (sthoria)" <sthoria@cisco.com>, Sowmini Varadhan <sowmini.varadhan@oracle.com>, "jorge.rabadan@nokia.com" <jorge.rabadan@nokia.com>, "sslam(mailer list)" <sslam@cisco.com>
Thread-Topic: [bess] handling DAD in draft-ietf-bess-evpn-inter-subnet-forwarding-05
Thread-Index: AQHUTth9DYwQe3Tt8kuuiLpnlPC+DaXJRy4AgAEArwCABYTUgA==
Date: Mon, 04 Feb 2019 05:56:15 +0000
Message-ID: <182DE29B-03D4-45D8-981F-E497386EB86A@cisco.com>
References: <CACP96tSk0zGUaYaPR7KAg1Jdyw3iJJxZXtAzoQaPrVe94WhgpA@mail.gmail.com> <D0CCF0DC-09BD-4336-908F-292AFA76D12D@cisco.com> <CACP96tSkO6gH3KWka7LGSnriRyE7jz8CQj7JGTgFE2buEXiixg@mail.gmail.com>
In-Reply-To: <CACP96tSkO6gH3KWka7LGSnriRyE7jz8CQj7JGTgFE2buEXiixg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-Auto-Response-Suppress: DR, OOF, AutoReply
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.10.6.190114
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.65.227]
Content-Type: text/plain; charset="utf-8"
Content-ID: <E3E2996DDE2A7048B53BAE8DBF6718C5@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Outbound-SMTP-Client: 64.101.220.158, xch-rtp-018.cisco.com
X-Outbound-Node: rcdn-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/VYppHtHf4qmJDnlDGpIitv_8NJs>
Subject: Re: [bess] handling DAD in draft-ietf-bess-evpn-inter-subnet-forwarding-05
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Feb 2019 05:56:20 -0000


On 1/31/19, 1:39 AM, "Sowmini Varadhan" <sowmini05@gmail.com> wrote:

    On Wed, Jan 30, 2019 at 9:20 PM Ali Sajassi (sajassi) sajassi@cisco.com wrote:
    
    sajassi> AS> RFC 7431 has procedures for duplicate MAC address detection.
    
    rfc 7431 is the Informational RFC titled "Multicast-Only Fast Reroute".
    
    Perhaps you mean rfc 7432. And I suspect you mean Section 15.1
    
    draft*evpn-inter-subnet-forwarding should call out this cross-reference
    explicitly, so that the reader does not have to speculate (as I
    just did)
    
AS>> I will call out the reference explicitly. 

    sajassi> AS> If ARP probing is done before the target NVE gets to
    declare that the TS has moved, then the MAC move is delayed
    unnecessarily for ALL the legitimate MAC move cases which in turn can
    cause some loss of traffic and degradation in service. It should be
    noted that the MAC move procedures in here is consistent with RFC
    7432.
    sajassi> AS> same reply as above.
    
    it's a bit odd that lot of chaos can happen for approx 3 mins
    when there is actually a duplicate address (created accidentally
    or maliciously) but I suppose you could say that this is already
    based on 7431, so not something introduced by
    draft*evpn-inter-subnet-forwarding
    
AS>> That's correct. The important thing is the detection of such duplication and avoid re-advertisements of MAC addresses as specified in RFC 7432.
Cheers,
Ali

    Thanks
    --Sowmini