4941bis and multicast & QOS
Gyan Mishra <hayabusagsm@gmail.com> Sun, 02 February 2020 07:26 UTC
Return-Path: <hayabusagsm@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3BC612008F for <ipv6@ietfa.amsl.com>; Sat, 1 Feb 2020 23:26:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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=gmail.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 ArZ0ewPu1rxn for <ipv6@ietfa.amsl.com>; Sat, 1 Feb 2020 23:26:34 -0800 (PST)
Received: from mail-il1-x130.google.com (mail-il1-x130.google.com [IPv6:2607:f8b0:4864:20::130]) (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 0A65D120019 for <6man@ietf.org>; Sat, 1 Feb 2020 23:26:34 -0800 (PST)
Received: by mail-il1-x130.google.com with SMTP id t17so9887998ilm.13 for <6man@ietf.org>; Sat, 01 Feb 2020 23:26:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=UjFNAI52jrwnkniWpSX/gjb7C0zPuqRk9YT+2fc4gV4=; b=cY0HsyeeJvm1iA+8iVXwAO5x2Z3JQAAOmyI0oPnEYelfMEsAh6x8xGgepAivQ3q8y9 FlMu4sHfNrcQFoF8v20mxdQ7l2lXgerRM907exJ1YfX+vh3OkReneB0+iElkE5cIMfv/ jyHV/ZFHk6U/MM7CqJXfXfveGx8l6oNha1HYEZu41xIErtnu2eTooa08kDYV248rZ7EG pq3Lgql3Ne7JxOBN5AC/eaYd2gn00sttyFUlyVWFoCNHTawYoY08YH9i44Ri00hjJX27 kn/WFpoN5DJeHHqvROSejXE1cNqZRdEpiYDZFQ2XqM8lgXvbQOLA5pZ/en9Y0mu5hw7t OLdQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=UjFNAI52jrwnkniWpSX/gjb7C0zPuqRk9YT+2fc4gV4=; b=dMAAcOO0mXJOia3hdfMeSaXJigfCKVEWJF+3AgLIem1GHJLnUwsS/0iQZkTTO//jOr NKhQuGDGNGR7toFTwqXudIObAJQxGH+GTft0tQRpzdhrUUqA9bQbpojAhF/CmqSG1sKB 2TgOQfNoMhPMSD/nct0zmHIym28H9xLzCU56WxII0NUvcVu67+/Oo4WhKpr1co2tp+O1 S49ZNDOxxTeP1kgciZcqojBcwrFxDjW1rTzrPIZeJlnlDsRnVEoaP+R9efWg1St4ZSI2 Ei1qlocBS4LOPn5Q8/VUio98WbJGlYeg5eo0cEMVrq5KVri3FnuKEM+j7AUGq+HBTOqd hFyA==
X-Gm-Message-State: APjAAAUUPLMWEtwJd0HguRFRkuPIR2vDgTK5+8AcMQ7q4e4lNjYVUD3p r8aT14zgaIkB0BQcfvfHzQ/mvwKarHKzAsONLUb9BwsN
X-Google-Smtp-Source: APXvYqwwwJVyl5rQyrw4fB3COHM33UUpee0xVhCeubKX84nJWD/p6cPtC8p/sXIhepnfDg0vCfQm0ldvPPyRvZRC7DI=
X-Received: by 2002:a92:1948:: with SMTP id e8mr16334758ilm.158.1580628393152; Sat, 01 Feb 2020 23:26:33 -0800 (PST)
MIME-Version: 1.0
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Sun, 02 Feb 2020 02:26:22 -0500
Message-ID: <CABNhwV0AHFmq9QcTwhgUWmaahaXvGW95abg+s8Uf7NQ2KHhhKw@mail.gmail.com>
Subject: 4941bis and multicast & QOS
To: 6MAN <6man@ietf.org>, Fernando Gont <fgont@si6networks.com>
Content-Type: multipart/alternative; boundary="000000000000e555fa059d92b94b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/c17X0Z_mxXPZ4oz-rURLC1TE5-U>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 02 Feb 2020 07:26:36 -0000
How would multicast ASM or SSM work with the privacy extension temporary address enabled. With the privacy temporary address enabled the IGMP Join would go out the temporary addresses, just as would normal unicast traffic. The temporary address would be the RPF path shared and SPT tree. The unidirectional multicast video stream should flow over the temporary address. Have the stable IID for incoming connections and temporary address for outgoing connections I am guessing should not result in an RPF check failure. Has anyone tried testing multicast? Has anyone tried setting QOS DSCP values outbound on peer to peer Cisco Jabber voice or video flows sourced out the temporary address? Gyan -- Gyan Mishra Network Engineering & Technology Verizon Silver Spring, MD 20904 Phone: 301 502-1347 Email: gyan.s.mishra@verizon.com
- 4941bis and multicast & QOS Gyan Mishra
- RE: 4941bis and multicast & QOS Manfredi (US), Albert E
- Re: 4941bis and multicast & QOS Gyan Mishra
- Re: 4941bis and multicast & QOS Mark Smith
- Re: 4941bis and multicast & QOS Gyan Mishra
- Re: 4941bis and multicast & QOS Mark Smith
- Re: 4941bis and multicast & QOS Gyan Mishra
- Re: 4941bis and multicast & QOS Fernando Gont
- Re: 4941bis and multicast & QOS Gyan Mishra
- Re: 4941bis and multicast & QOS Gyan Mishra