[pim] AD Review of draft-ietf-pim-multiple-upstreams-reqs-06
Alvaro Retana <aretana.ietf@gmail.com> Wed, 31 January 2018 18:46 UTC
Return-Path: <aretana.ietf@gmail.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71FDE12751F; Wed, 31 Jan 2018 10:46:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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_PASS=-0.001, UNPARSEABLE_RELAY=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 eFlwLzxXW8DJ; Wed, 31 Jan 2018 10:46:15 -0800 (PST)
Received: from mail-ot0-x243.google.com (mail-ot0-x243.google.com [IPv6:2607:f8b0:4003:c0f::243]) (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 F1E3F12ECEF; Wed, 31 Jan 2018 10:46:14 -0800 (PST)
Received: by mail-ot0-x243.google.com with SMTP id x4so14363158otg.7; Wed, 31 Jan 2018 10:46:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:mime-version:date:message-id:subject:to:cc; bh=ZDk6GxA/b396mU0vCHMqlXYLy1fXtmiDBOUlb842L4o=; b=n+v/0/gyf2rgxdXeOEenbH59jS+/k0P5FYX9EbAXgH+Mfc0Gb6q0evW9tP3DqUCTB+ M2jEhCgxS2zi5xgOiMYfhzj7dAD4M8vJ4vS9Vdrtjq4ZRFp2FnPSiFgnLQUDoBcZOwJO EXL2YCaRqTV9BAPdI55vNxY7znOaO/iAQL1lsTEusWl0bw7RZ6k9nUxFdxdTO9QcDgeD OvRjcnn4EpNo2zQTbY8omqPYU4C4xbf4A6eDdieLo+Uiu5/9WfZmDr1zObLXfdOeh/4m CBLKdR2n6V3HCHG52QACpuPhmwzz7VVCIAZ2MjGzaEDpO0iebXFf3HpDcAtj/OQ1LaST A/hg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:date:message-id:subject:to:cc; bh=ZDk6GxA/b396mU0vCHMqlXYLy1fXtmiDBOUlb842L4o=; b=gWCQUZSdnOFeU7LxQa8XzVKqdL5xAbqwMaD/WGPquh21g5N6N1uCN5UJCXytK3G8Ua r2MQE8eobEUo+0xxtIf1ZyGcX/RVfpB95VV680aYpX8BMbPNwnjfmTElR4MeMy4R74Ie pwPxjJF8l7ujArHrEwGiT6vua4HLXRWwTUiY61jGjC+CsD5g+3onDIM0o4mvAUfnAqbb MswITjrSTP38pZu1XuX0uw+TbIZSFn7cVpLU1tmDmTEr1UzGcg9LqSKPd0+3tnvKKpv/ KGBoLPWGf8CWiLArHyhQozcptbUqYWi2gfWWVG6PYP54WlvHTEzbAUX0iSdOUmwFCVPw n8CQ==
X-Gm-Message-State: AKwxytes4ecryRm92AMKP0wIAtlndSvqN1zeCCr4KuAfm+BfXDYSbD5A 71IK9rUwVeYHNLTV8XiGe+D5pz6bjfshttyqaQM=
X-Google-Smtp-Source: AH8x2256R0CVzRQTH3gm1SVjE/tq2Q7hn6t0aUHd687unW88GkX92gxH6+1TyYcBDfXvC20DSrRQhXuHpY0kuCIbmuk=
X-Received: by 10.157.114.150 with SMTP id t22mr8310588otj.164.1517424374143; Wed, 31 Jan 2018 10:46:14 -0800 (PST)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Wed, 31 Jan 2018 10:46:13 -0800
From: Alvaro Retana <aretana.ietf@gmail.com>
X-Mailer: Airmail (467)
MIME-Version: 1.0
Date: Wed, 31 Jan 2018 10:46:13 -0800
Message-ID: <CAMMESswutiMLwqUsGgczKxNsbdTUkZ4W24B=MEABi1s7K6gkeg@mail.gmail.com>
To: draft-ietf-pim-multiple-upstreams-reqs@ietf.org
Cc: pim@ietf.org, pim-chairs@ietf.org, Stig Venaas <stig@venaas.com>
Content-Type: multipart/alternative; boundary="94eb2c137f4ecb6079056416e4a3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/DUe-SfbHlt2jf8hSsrcmpowNMKo>
Subject: [pim] AD Review of draft-ietf-pim-multiple-upstreams-reqs-06
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Jan 2018 18:46:17 -0000
Dear authors: I just finished reading this document. In general, I am not a big fan of requirement documents on their own -- if the problem is important enough then ideally there will be solution work done as well. I seem to remember some talk about potential solutions (as far back as IETF 92), but didn't find a clearly related draft (or one that references this document) in pim, mboned or even magma. I want to encourage the WG to take on work that addresses the scenarios described in this document. The document presents some applicable scenarios, which at times are constraint by assuming that "both providers offer distinct multicast groups" or that "only one of the upstream interfaces is active in receiving the multicast content" -- leaving the decision to be straight forward: use the upstream that provides the required group/source/service. I then found the resulting requirements relatively weak and general. For one, it seems as if the bulk of the requirements can be summarized as: - the proxy should deliver control messages from/to the user to/from the corresponding upstream - the proxy should be able to select an upstream based on the requested service (group/source combination, when applicable) or other criteria (e.g. load balancing) Those two requirements seem both generic and pretty obvious to me...and don't offer too many details; for example: Should the user be able to set the other criteria? Is some criteria specific to the proxy itself and it's operator (load balancing, for example)? The description (related to load balancing) talks about "split the demand, alleviating the bandwidth requirements", but the requirements mention "balance...as a function of the group", or "consider the source", both of which have no direct relationship to helping with the bw requirements. When the document does get into slightly more interesting scenarios, the resulting requirements are not as specific as I would have expected to later successfully build a solution that addresses them: - "should be able of rapidly switching from the active to the standby upstream interface in case of network failure, transparently to the end user" How fast is that? Is there something more specific that could be used to quantify? Does it depend on the application? Are there expectations on the network failure detection? - "decide...according to the situation of the user with respect to the service migration"...or..."according to the situation of the group and source included in the request with respect to the service migration." Besides knowing which upstream provides the service, is there something else related to the "situation"? At times the document reads like a marketing brochure... For example: "For the multicast service, the use of an IGMP/MLD proxy with multiple upstream interfaces in those switches can provide service flexibility in a lightweight and simpler manner if compared with PIM-routing based alternatives." flexible, lightweight, simple... Nice! But the requirements don't directly seem to address those qualifications or offer a way for an eventual solution to measure flexibility, simplicity, lightweightness (?). Another example: "it is now possible to implement channel-based or subscriber-based upstream selection". Based on the requirements, I take that to mean that we can select an upstream based on what the subscriber wants (source/group). However, I could also interpret "subscriber-based" as related to the subscriber him/herself -- is the intent that the proxy could take into account personally identifiable information (who I am or where I am, for example) when deciding not just which upstream to use but whether to even provide the service? Maybe I'm reading too much into that, but clarifying that there are no requirements related to exchanging or using information that would explicitly identify the subscriber him/herself would help. I have other comments below. Let me be clear. We're at this point of the process because the WG thinks there's value in publishing this document — I’m not pushing back. The objective of my comments are aimed at making this document the best it can be -- again, so we can build solutions based on the requirements. I think that in its current state, this document doesn’t provide valuable direction for those eventual solutions. I would like to see a revision to the document, or at least a response to my comments before starting the IETF Last Call. Thanks! Alvaro. C1. The examples and scenarios are described based on 2 upstreams. I'm assuming that the requirements don't really change if it was more than 2, right? It would be nice if that statement was made at some point: "all this is applicable to 2 or more upstreams". C2. 4.1.1.1.: "Since the use case assumes that each provider offers distinct multicast groups, the IGMP/MLD proxy should be able to identify inconsistencies in the SSM requests when a source S does not deliver a certain group G." What does it mean to "identify inconsistencies"? What are "inconsistencies"? C3. PIM and PIM solutions are mentioned several times, but there's no reference. Please add some. C4. Same comment for "existing IGMP/MLD proxy functionality". C5. In 4.1.2.1, what's the difference between the first and last requirement? o The IGMP/MLD proxy should be able to deliver multicast control messages sent by the end user to the corresponding active upstream interface. ... o The IGMP/MLD proxy should be able to deliver IGMP/MLD messages sent by the end user (for both ASM and SSM modes) to the corresponding active upstream interface. C6. The case in 4.1.3 (Load balancing for multicast traffic in the metro segment) seems to contradict the assumptions in the previous sections: "both providers offer distinct multicast groups", "only one of the upstream interfaces is active in receiving the multicast content". I realize that the scenarios are different, or that the requirements describe different areas of (not necessarily concurrent) functionality -- it would be nice to be specific about that. C7. Security Considerations: "Apart from that, if proper mechanisms (i.e., implementation practices) are in place for channel-based or subscriber-based upstream interface selection, Denial of Service attacks can be prevented." Proper mechanisms like what? Please provide references.
- [pim] AD Review of draft-ietf-pim-multiple-upstre… Alvaro Retana
- Re: [pim] AD Review of draft-ietf-pim-multiple-up… LUIS MIGUEL CONTRERAS MURILLO
- Re: [pim] AD Review of draft-ietf-pim-multiple-up… Stig Venaas