IETF Logo Mail Archive

Re: [Int-area] Comments on current MPvD draft.

Ted Lemon <mellon@fugue.com> Wed, 15 November 2017 21:07 UTC

Return-Path: <mellon@fugue.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 839D312762F for <int-area@ietfa.amsl.com>; Wed, 15 Nov 2017 13:07:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 BaC7J3t9Zxua for <int-area@ietfa.amsl.com>; Wed, 15 Nov 2017 13:07:36 -0800 (PST)
Received: from mail-pg0-x234.google.com (mail-pg0-x234.google.com [IPv6:2607:f8b0:400e:c05::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E573A1271FD for <int-area@ietf.org>; Wed, 15 Nov 2017 13:07:35 -0800 (PST)
Received: by mail-pg0-x234.google.com with SMTP id t10so17868427pgo.3 for <int-area@ietf.org>; Wed, 15 Nov 2017 13:07:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=lHdhTKfi3e2RY7rvNIW3q/COtcXVQSzHOjdNgBUR9vU=; b=1XjV/2WZqFuoRBSUd6rgUK/JGB8HlgZ//m3qsaYKFwQniZfwLWKMKW7ct+7NcPRtzr 6uJYHsqrQuIcXZ/3C+1HfWKjfQ1yQvBX1nB4QtAXkDva3J00mqLCqVoS4F5xtI9h+c5k D1Y5f6QwqL8ld+v1Fx/0T2D1LSSsh1oI3Bb7WI/uGUNEAkoZWnaLPz0yShsDrgGRWOCT YPBtbCTrvmYnAlmQSpIbioB7u7LYyNuNjoIJLHSoThRHh48XtcURtTOqV+QOs3SWCPhF ag4HF3zgvgx2QLYIUmjh1ycrF5quLw3DqDW0/m0Y8AnIXnpxtJ7E1KpShCor+W+ZViQ+ YMMg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=lHdhTKfi3e2RY7rvNIW3q/COtcXVQSzHOjdNgBUR9vU=; b=W/kXEomUipO0Z8lKsww9I7xedtDVLdDPpl6BV0wqwzXwqoG/S/ph6tdEOsuRG+niNb aVG6IbPknjj7whDqiljMqiZwHSidVooYxeqU52vJdsjcgqVLG3OW6Tzj4TxUNj2VPluF Qwbz/QW84KnyDiQyEo7sdMoB5cPf/yTVPuVU7X6Y60FGqLxD8pzjIB8veMecRCr6+hqd cI5K64PxJd2ioq7KCYY7kJDqEw7+DftIgLElgnzt/fEWsrijs841Lkv3DCFoap8qFaop GV+tqA2zLrVP9l1l0aG9hLcTbRUW8RW17t45523iB4mhzHKPash8NpJuec/fAl3Cj5p/ 7H2w==
X-Gm-Message-State: AJaThX7ZKG7eHo0mShO91pn+xE329Lf4iDvpSuAlRCjpdPxylPAhtCHc GtoY/EbzeQQ6PcU756C4kFPeeomUtRo=
X-Google-Smtp-Source: AGs4zMYHmIdUNqtII9GjZg165B9xClFFmox6xs068pBgOhjMxeA8ZZFsV2+w64f8q8yRRWQV4OliXA==
X-Received: by 10.84.129.132 with SMTP id b4mr17097618plb.412.1510780055473; Wed, 15 Nov 2017 13:07:35 -0800 (PST)
Received: from [192.168.43.27] ([111.65.61.187]) by smtp.gmail.com with ESMTPSA id g5sm40604022pgo.83.2017.11.15.13.07.34 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 Nov 2017 13:07:34 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <AD475B56-F10F-4EBA-B93F-DBD4E4086602@cisco.com>
Date: Thu, 16 Nov 2017 05:07:26 +0800
Cc: int-area <int-area@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <B2E3A40F-0250-4C16-90A0-E27500B3A42D@fugue.com>
References: <45957315-A9A2-4E11-9069-5C41C7397034@fugue.com> <CE5C3A81-51FA-4042-90E0-04930B361A88@cisco.com> <CAPt1N1=xLg-a+sn+fij=3x4aaOBBen=tdFW1p2c_kB5xtua86w@mail.gmail.com> <AD475B56-F10F-4EBA-B93F-DBD4E4086602@cisco.com>
To: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/cMZjnmsifiaGiZlgAXnIukVyj1g>
Subject: Re: [Int-area] Comments on current MPvD draft.
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Nov 2017 21:07:37 -0000

On Nov 16, 2017, at 12:03 AM, Eric Vyncke (evyncke) <evyncke@cisco.com> wrote:
> This could be an alternative but I can only imagine the pile of changes to be done... RA-guard, RFC 4890, ...

Wouldn't these changes be required as well if you used a different multicast address?

> In either alternative (different link-local group, different ND code), we HAVE to ensure whether it is doable with the existing HW/SW in the routers/switches/AP... I am afraid that this is more complex to change the network/routers than the end-points (thinking about OS/HW refresh cycle) but I can, obviously, be wrong on this statement.

Yes.   So this is once again arguing for the encapsulation solution.

v2.23.0 | Report a Bug | By Email