
From nobody Fri Sep  1 06:34:37 2017
Return-Path: <lenny@juniper.net>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35CB1132E11 for <mboned@ietfa.amsl.com>; Fri,  1 Sep 2017 06:34:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.121
X-Spam-Level: 
X-Spam-Status: No, score=-0.121 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=juniper.net
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 RMyOyNLqBFph for <mboned@ietfa.amsl.com>; Fri,  1 Sep 2017 06:34:34 -0700 (PDT)
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (mail-bn3nam01on0137.outbound.protection.outlook.com [104.47.33.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 00C9013303F for <mboned@ietf.org>; Fri,  1 Sep 2017 06:34:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=gzQCnD6k2+1B82J5Yj6QKE5KXJRHhN3ED/qgqqCAolM=; b=VSM2wyKL+gGA7uUVjg2Njq06T4s5bCEQqfkARIOX5ZhKuUko4nWaz8IBki5xbC3y7LaF+q4rDDCBNoYU7CA4FdbopGfsqYqJglFIpeQ11hWfHPGZFP649J80RbZ/iquFgwtsTN9PBW5JxOb3j3GKVU2eB7vTfY+IMx7CNIbH2Yo=
Received: from BY2PR05CA024.namprd05.prod.outlook.com (10.141.250.14) by CY1PR05MB2473.namprd05.prod.outlook.com (10.167.10.18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.35.3; Fri, 1 Sep 2017 13:34:32 +0000
Received: from BY2NAM05FT028.eop-nam05.prod.protection.outlook.com (2a01:111:f400:7e52::207) by BY2PR05CA024.outlook.office365.com (2a01:111:e400:2c5f::14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.35.3 via Frontend Transport; Fri, 1 Sep 2017 13:34:31 +0000
Received-SPF: SoftFail (protection.outlook.com: domain of transitioning juniper.net discourages use of 66.129.239.15 as permitted sender)
Received: from P-EMFE01C-SAC.jnpr.net (66.129.239.15) by BY2NAM05FT028.mail.protection.outlook.com (10.152.100.165) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P256) id 15.1.1385.11 via Frontend Transport; Fri, 1 Sep 2017 13:34:31 +0000
Received: from svl-jtac-lnx06.juniper.net (172.17.28.215) by P-EMFE01C-SAC.jnpr.net (172.24.192.21) with Microsoft SMTP Server id 14.3.123.3; Fri, 1 Sep 2017 06:34:24 -0700
Received: by svl-jtac-lnx06.juniper.net (Postfix, from userid 1709)	id E0AC19F6CD; Fri,  1 Sep 2017 06:34:23 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])	by svl-jtac-lnx06.juniper.net (Postfix) with ESMTP id DD4B89F6CC; Fri,  1 Sep 2017 06:34:23 -0700 (PDT)
Date: Fri, 1 Sep 2017 06:34:23 -0700
From: Leonard Giuliano <lenny@juniper.net>
To: Hitoshi Asaeda <asaeda@ieee.org>
CC: MBONED WG <mboned@ietf.org>
In-Reply-To: <6405DF4D-AE9B-4BC2-84D7-E379ABF408E5@ieee.org>
Message-ID: <alpine.DEB.2.02.1709010631020.17646@svl-jtac-lnx02.juniper.net>
References: <150397252029.13230.634170751860522228@ietfa.amsl.com> <6405DF4D-AE9B-4BC2-84D7-E379ABF408E5@ieee.org>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
X-EOPAttributedMessage: 0
X-MS-Office365-Filtering-HT: Tenant
X-Forefront-Antispam-Report: CIP:66.129.239.15; IPV:NLI; CTRY:US; EFV:NLI; SFV:NSPM; SFS:(10019020)(6009001)(39860400002)(2980300002)(377424004)(199003)(24454002)(189002)(45336002)(86362001)(966005)(229853002)(57986006)(76506005)(53936002)(110136004)(6246003)(6266002)(478600001)(105596002)(6306002)(356003)(7126002)(106466001)(5660300001)(76176999)(50986999)(54356999)(46386002)(77096006)(69596002)(626005)(50466002)(83506001)(97736004)(4001350100001)(47776003)(2906002)(23726003)(2810700001)(4326008)(3240700002)(8936002)(5005980100005)(189998001)(68736007)(305945005)(81166006)(81156014)(6916009)(8676002)(90966002)(2950100002)(230783001)(46406003)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:CY1PR05MB2473; H:P-EMFE01C-SAC.jnpr.net; FPR:;  SPF:SoftFail; PTR:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-Microsoft-Exchange-Diagnostics: 1; BY2NAM05FT028; 1:JsfpMmHJXKEWW/7eylEgbxkfwwsCtURNNYqxxEA1rqMUjMGjB4pC5DI4nV92ELWHkrhUzwXrQYBUkF4tLWYtIXP1c82KRmm4wL2F/yj8/SdH3Bw2OIrmZwuvHAbtj0XA
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 3d80c825-0db8-45f7-7ae1-08d4f13e2d5c
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(2017030254152)(300000503095)(300135400095)(2017052603199)(201703131423075)(201703031133081)(201702281549075)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:CY1PR05MB2473; 
X-Microsoft-Exchange-Diagnostics: 1; CY1PR05MB2473; 3:ye/0oUSz0CcJuuNALa/bUzjaL7mdMJJMN2xg1ZY0U/45tip5hG0soJZyATWopd8BAAih7KkGkdMDFaBDDrOKdHBgDeAsNSwq6ReJHj6W7RpcMrxIlVs47o/S6MVhbs0dDPJnx8l2kP7enI/GjFBejpQHc+nr1nRPu5WOlUcpb9qsHEhEhpGnJb9tclXBmxpFwJFENY9T+rCZa9T7SJ3mDS+gDXQuEEAxiFYm771ze9ME0CTUW5cy7LCZ9dr+8Smgv4a7vNcBlX/kf5Zn+4uOPUGj/hfXbXqs9i32U0MfDXIdeAUm0DBpi/+hByFnQjaWbqSKzf5b3GGkmPk4oD6Hec8Xneg+e9oVUM56D5T9lb8=; 25:WEStn6hh0I2J5K1mdg2t3NNMhivUDnQ6xSKq/3zC6T69ejdLrJWonDRuH8RKLWetMuySMX4Uam2Or8+DjKI0JSjL1x2gfThGYCLg/hGvn6QtStvPbUPDsINVTkClpbCKTXL+pNArdKffBq14PyHkI9OMWCvVK5jFhCfzOA6QllVhesO41HhAybf1vAjryKIUR6oNYvJ+PmU2NK+WSFMyNiRP8j91e6PbTa3sBk4z/1TntXbA+PJllqw3QSomWWpHQzqS2NjWmSrj232zIkdwVTW51qhTFhtaaJ4SSJZVwZplEbvYLu+BDwOs/VpdPOS/03+JU6Z+pkS+t02B2f2ckQ==
X-MS-TrafficTypeDiagnostic: CY1PR05MB2473:
X-Microsoft-Exchange-Diagnostics: 1; CY1PR05MB2473; 31:3PUPCefzhU8e0PZriMEElOeS89I4dHwG0N7UUID3l28l/ORY7mdL+ZfLY9QnBaDDdDWsrPHXk0R4UF0+fB5O4WPeUjNPz8rUXQJWy57D4ed3ACKE4rVk5EGJxIWHwWIucXJNMJDhPxXdfJzT9FtKEWH9eHUrDNfim/UyvJkBMdAy+F4F8Xq3rbs1x/ldx7VSnjFF0SfZrwXGUGu1rnlqi+t/3HWKjBpavqKgMTWyuh8=; 20:PcEFf3jy6udqqsq18eG8/JM6/fx0Cl62h6crbZRHebkV/YEBbLx3GPEehHDJ+b3xyJpJXotLiFc9osogeV0LE8tZh3wiBKC9nncI+3EwXSJQ2qB5onu7YDVdeK/GoVGQr/IqL1+1icYQi9dzy18NGDDq2BJYrlyUI2yFrRVmTaUG94hNKsQOvq3HphP5UKLCDpiJmwwjH9UplDA/NagGMIEcmEv/k178ODSrNvQxGq8VlyNmSIT3hXftReIj4MPYFO21nV857ErZWwoeUOfdy6bUmus2oBAtKuDiALVkgIaL0aB2zJBcBRxBKG+Q73JioP0eX4Wti5XbIHcGOP17vp+YXBWR1JZ94MI9vzwppKH6a6ey1NGmPfOafCZOHnYkgWONoz80VYQ5U71OBXfZ1/8qUHIg+erspErW/xywZOIA8ACXIaIuB5mm1+DkxQGw/8FlMHx5pBscyYigEY/P1ytC3GsUXIX8Ql6jbHI/MEEkXhLjonBNWQiO4P+Gvgx6
X-Exchange-Antispam-Report-Test: UriScan:(120809045254105);
X-Microsoft-Antispam-PRVS: <CY1PR05MB2473B6BC30B0512801325B6FA4920@CY1PR05MB2473.namprd05.prod.outlook.com>
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(8121501046)(13016025)(5005006)(13018025)(3002001)(100000703101)(100105400095)(10201501046)(93006095)(93001095)(6055026)(6041248)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123562025)(20161123564025)(20161123555025)(20161123558100)(20161123560025)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:CY1PR05MB2473; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:CY1PR05MB2473; 
X-Microsoft-Exchange-Diagnostics: 1; CY1PR05MB2473; 4:Vm33KtLXi4vsWv/uFFd5aNWtgD4JDj2lxOaErWt4ljqZWGPGvbh2sw+I1r36d7Sgnm2Mhj0pioDWQGQiOL1CjlPpGR7QUnoILKaSWG8e0qmeSAYI3VeiNyNOlPNGNX6xKUUSjBCvV9ynhgDlWA0k58mW4xOUoDNNTCbBx2dtM4Lk5vENVkIKg1miXMkEbK+wt7F3zY0HGVGb5Jce9JYbLKpDwYkEINYnp5x8PUfoyLQ604xJmqlh+8d0lgoK467HKeNgbbdlZpyGVXHt2rJakRiwbZhmD3oU9PqM4tqnKjE=
X-Forefront-PRVS: 0417A3FFD2
X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; CY1PR05MB2473; 23:8b2BzdBnI2Pll5+SAM8tLUbVC9h3I2PP7Sgu+iZ05?= =?us-ascii?Q?wgNUtVElqt8GuqXHmp7MeUevPEsctsiQ6y3YyCgNYsUp4irerxc0Jnj6q3It?= =?us-ascii?Q?+2i5mp6QevDQ3APHEezzOk7FGnuY4r3vi2LFsFecdWNGIm8jS4XrydzJmfj5?= =?us-ascii?Q?VRfA2lPh4lHenl0hRMOTpA4o7o7CzIOfowoFQlT9PP2p8BWbl1nlsSwKtSy4?= =?us-ascii?Q?roJAMKS2FJDHuqZPMjivik6lJVLB0RDeufFg/WtQLj1MahMiwLCqVS7++5mE?= =?us-ascii?Q?3EDEMIW3JoWyFG9NLIqz+C2k4L67QCAj9T2PlKkCcJjxsduzV/J1JqTiw/1J?= =?us-ascii?Q?0qCHpfKzCTXd6OifWey3XytPbbgRAt+4iHPYeK923lzlDcxrKVY6AgOjEIQy?= =?us-ascii?Q?5cSPVcxvYs3RobnOC2929F10r9Hv5YPNqFpKSeICpQ3+VINY3g8X/uA8Bz8+?= =?us-ascii?Q?IxGUy3k2uN7awqodCYZV+J4skVyHZhS+QNrhW3PcLn/25bEWOCXlgA3t3EaK?= =?us-ascii?Q?zupX7CiLWjjkYoYTh7S0Fh2/1UYuWm1cTQBWXpA0U1yEypFH5dDNfwY3t3lu?= =?us-ascii?Q?KL9arUWHGoiftOP3a0agFR06Vci+IdsaL+cdTLFDDD8+tpmcvd0/sasWoabJ?= =?us-ascii?Q?1csB15JvUjytzWXm+hYpXDMjmy8W204GSXXeUqjXi9b2vuPuzGYmkFPYHrYJ?= =?us-ascii?Q?v1LYjzrIEUpkDaY504GMpnLJKiMmfoGDaC/aPIm2MuQ/lZfDhIrHZJsoIsWK?= =?us-ascii?Q?lNP5hsTnYvUtHt6rQ2X1eRfY2a+huUCWMRkhv+uJqWhWr3OIVghfFN93Iml/?= =?us-ascii?Q?JwJ1v/DVgJcgFcVxqgW/0Ndb4Rj9WdNGQWdAKRDYJYkZl7dw30HEh6wxaK65?= =?us-ascii?Q?aYO9NY30KBFw8mdfMLnKBk+lArFzuCVYFGAB2ztQYHcEGxZupQZQYruEFVx1?= =?us-ascii?Q?QspxwqYDCIZ25cbCFPMcCxGmwHPapTIhgI4FAUGm6G0pmSQE9KDWftkIoJGz?= =?us-ascii?Q?N6u1WlXiKgp4DcWJVWvrYzVjMfjrPlumM78dPEMtm0GmYVwNGV1ahlG3BFoM?= =?us-ascii?Q?Ndx4icJIPP1i6m22uGtNlqQ2KwcMdtShyMxmPeUi1clRf0ENYTfWoMfoCEVr?= =?us-ascii?Q?NwziqxOVzQ7peKuQQpoT/0+1CKFzawMavARhh6X24YCIR9Bb/yC4kdTVZNky?= =?us-ascii?Q?CURWLm6WQDMw9+mK8Gy/ae0VxWmAWXk53bEhA0t9jNBb32+pRSuvG0zb+CjO?= =?us-ascii?Q?a6w5kCCmaR2G6tqag/V5dDYS6NhxJhWpZ3617DO4lE2ojEbz5xb0bOyxfw/B?= =?us-ascii?Q?E7A8T+U5l+P5WyxQTXzIn4=3D?=
X-Microsoft-Exchange-Diagnostics: 1; CY1PR05MB2473; 6:5Qa9p3P9JmAvutu+1a2gWJfpunLBEgdwLBlUYx/U7PTqZNLZpEeqsv66q2u0POqWPDwr4Vf5T8Ss+7xvzjVQh9Z4eck926Wbxp91ytJIzeoDuMPJE+NQYxdfVMcTvW68JcJ4QCdLJZAD5IM+1qutvZBYfuShja7jFRGBv0oFsaYW9nCSRTW4wLAR3fFY/CdBEPUwt1pwS1X0bRzDMTsajSp2s4PfGoVBgbhnYO6e6oJWGbY1MQrs58pwQmjdDY2WyIDC7D833OP434hJRpKki9OhdUFLmGo7Zi6S5INAywyTI5CwsBCbNdBS+e30ipVvTPj1RQG88+o0Xm4wps+A3A==; 5:zgwU422DNxJofUAAgo/CbYyOwc/aKQ1oUR+PH0sV+x1hiQTe8BMg4iaU5MS8X6G7fEvLMF4yeGV3xeX26oX/3KCIUhCtirHTZkYEXdwr756ASNPu7ycCV6eMa8GpZfkeZtQnEnk6YhQGXFHfQ4l0sg==; 24:xWwZ43LvVLw6G0+RggqfSNHabi7A6nv4PdT1FKagJRsBiWZcWKqq/XeOZ3NhFTpxfOQ4duq94m9+ExlRrPYhTH5IdOEWFtcOthuffdrHNjw=; 7:BzBS4FEB7rzFhPJwe2LweO+VZuqyCEfTLMppFTaVxFlZ2IhzeCMrwyb1P0trfWhF1P3omSlINerW0t4BH5xDD9Bp20FOYLXzX6w3hGKR01XOEM+Sa2J+UHnfT4tSUurto317jTEac2b0JpBtMahAPY0KWMmZ9E2DCdLfEeyQXKcOqQZtO1e9rmjQi9gq2IA6QVcoEvxAzvM5gTWS3JtPJ4Y2sHbBG/2Yw+7Nh0VJeOg=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 01 Sep 2017 13:34:31.6134 (UTC)
X-MS-Exchange-CrossTenant-Id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=bea78b3c-4cdb-4130-854a-1d193232e5f4; Ip=[66.129.239.15];  Helo=[P-EMFE01C-SAC.jnpr.net]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR05MB2473
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/JOGQH78LVAPeNh3RRSRKWWCd-ic>
Subject: Re: [MBONED] I-D Action: draft-ietf-mboned-mtrace-v2-18.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Sep 2017 13:34:36 -0000

Thanks Hitoshi.  And with the recent additional support from several folks 
on the list, we will now begin the process to advance the doc.  Thanks 
all.

-chairs

On Tue, 29 Aug 2017, Hitoshi Asaeda wrote:

| Hello folks,
| 
| We received comments from Jake/Lenny and Mankamana during the WGLC for the mtrace2 draft.
| We then applied the comments to the draft and have submitted the revised one.
| 
| The followings are the summary of the changes.
| If there are no other concerns or comments, we'd like to ask chairs to move it forward.
| 
| Changes:
| 
| 1. section 1, add the following sentence to clarify the target and scope of this document;
| 
| "This document describes the base specification of Mtrace2 that can serve as a basis for future proposals such as Mtrace2 for AMT [9] and Mtrace2 for MVPN [10]. They are therefore out of the scope of this document."
| 
| 2. section 3.2.2, add the following sentence at the end of the first paragraph to make the meaning more clearer;
| 
| "If the actual number of hops is not known, an Mtrace2 client could send an initial Query message with a large # Hops (e.g., 0xffffffff), in order to try to trace the full path."
| 
| 3. section 4.4, change the first paragraph as follows, to clearly explain the meaning;
| 
| "An Mtrace2 Reply MUST be returned to the client by a router if any of the following conditions occur:
| 
| 1.  The total number of the traced routers are equal to the # of hops
|     in the request (including the one just added) plus the number of
|     the returned blocks, if any.
| 
| 2.  Appending the Standard Response Block would make the Mtrace2
|     Request packet longer than the MTU of the Incoming interface.
|     (In case of IPv6 not more than 1280 bytes; see Section 4.3.3 for
|     additional details on handling of this case.)
| 
| 3.  The request has reached the RP for a non source specific query or
|     has reached the first hop router for a source specific query (see
|     Section 4.2.2, items 9 and 10 for additional details)."
| 
| Regards,
| --
| Hitoshi Asaeda
| 
| 
| 
| 
| > 2017/08/29 11:08, internet-drafts@ietf.org wrote:
| > 
| > 
| > A New Internet-Draft is available from the on-line Internet-Drafts directories.
| > This draft is a work item of the MBONE Deployment WG of the IETF.
| > 
| >        Title           : Mtrace Version 2: Traceroute Facility for IP Multicast
| >        Authors         : Hitoshi Asaeda
| >                          Kerry Meyer
| >                          WeeSan Lee
| > 	Filename        : draft-ietf-mboned-mtrace-v2-18.txt
| > 	Pages           : 36
| > 	Date            : 2017-08-28
| > 
| > Abstract:
| >   This document describes the IP multicast traceroute facility, named
| >   Mtrace version 2 (Mtrace2).  Unlike unicast traceroute, Mtrace2
| >   requires special implementations on the part of routers.  This
| >   specification describes the required functionality in multicast
| >   routers, as well as how an Mtrace2 client invokes a query and
| >   receives a reply.
| > 
| > 
| > The IETF datatracker status page for this draft is:
| > https://datatracker.ietf.org/doc/draft-ietf-mboned-mtrace-v2/
| > 
| > There are also htmlized versions available at:
| > https://tools.ietf.org/html/draft-ietf-mboned-mtrace-v2-18
| > https://datatracker.ietf.org/doc/html/draft-ietf-mboned-mtrace-v2-18
| > 
| > A diff from the previous version is available at:
| > https://www.ietf.org/rfcdiff?url2=draft-ietf-mboned-mtrace-v2-18
| > 
| > 
| > Please note that it may take a couple of minutes from the time of submission
| > until the htmlized version and diff are available at tools.ietf.org.
| > 
| > Internet-Drafts are also available by anonymous FTP at:
| > ftp://ftp.ietf.org/internet-drafts/
| > 
| > _______________________________________________
| > MBONED mailing list
| > MBONED@ietf.org
| > https://www.ietf.org/mailman/listinfo/mboned
| 
| _______________________________________________
| MBONED mailing list
| MBONED@ietf.org
| https://www.ietf.org/mailman/listinfo/mboned
| 


From nobody Mon Sep  4 06:50:58 2017
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 142FC1321A7 for <mboned@ietfa.amsl.com>; Mon,  4 Sep 2017 06:50:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
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 M5-uUpFQC2VA for <mboned@ietfa.amsl.com>; Mon,  4 Sep 2017 06:50:54 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 55980132191 for <mboned@ietf.org>; Mon,  4 Sep 2017 06:50:54 -0700 (PDT)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [131.188.34.77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 2CF8A58C4B2; Mon,  4 Sep 2017 15:50:46 +0200 (CEST)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id 13F88B0CAB1; Mon,  4 Sep 2017 15:50:45 +0200 (CEST)
Date: Mon, 4 Sep 2017 15:50:45 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Hitoshi Asaeda <asaeda@ieee.org>
Cc: Leonard Giuliano <lenny@juniper.net>, mboned@ietf.org
Message-ID: <20170904135045.GA3194@faui40p.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/nL0WPuw-q1_ZiKCSrL68KZiyZ3E>
Subject: [MBONED] SSM migration mechanisms (was: Re:  deprecating MSDP)
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Sep 2017 13:50:57 -0000

[Let me change subject here]

Hitoshi, *:

There is a wide range of mappings to enable SSM forwarding in networks,
implemented by various vendors. IGMP/MLD EXCLUDE G mappings to IGMPv3/MLDv2
INCLUDE (S,G) via manual config or via DNS learned mappings. Likewise
the same thing for PIM (*,G) joins translated to (S,G) joins. Starting
as early as 2004? if i remember correctly.

The reason why i never opted to document any of these mechanisms in the
IETF (beside "there is something more important to do") was always
two fold:

a) These transition solutions do not give you SSM. Calling them SSM
   is a lie in disguise. Oops: great marketing. !!!!!

   You still need to do ASM style multicast group addess management:
   You can not have two uncordinated application receivers randomnly
   choose group addresses and get away with it!!! With SSM, there
   is no need for any multicast group address management/allocation
   to application instances!!!

b) With a) taken into accoun, I thought and still think that these
   are transition mechanisms.  Documentating them would give them
   more credit than i think they should have. Aka: Especially today,
   there is IMHO no reason why any applications should not be able to 
   generate (S,G) memberships.
   
   If someone thinks there is a good reason, let me know!

Now, there are transition mechanisms that do not suffer from a),
namely IGMPv3 lite and URD. These are a class better, but never
catched on as much as the IGMP/PIM SSM mapping mechanisms - because
they did require application developers to do something - as opposed
to hos IGMP/PIM SSM mapping mechanisms, IGMPv3lite and URD where
only meant to get around the limitation of the OS not supporting
IGMPv3/MLDv2. But guess what: the whole reason why SSM has not catched
on as much as it should is LAZY APPLICATION DEVELOPERS and 
LAZY API STANDARDISERS (eg: IGMPv3 support in Java, websockets etc. pp).
And all OSs today support IGMPv3/MLDv2.

So, i would opt against documenting these mechanisms in a way that
would promote them. Besides, there are patents with my name
or other Cisco inventors on these, and given how i do not work for
Cisco anymore, i can not help in getting IPR disclosures from
Cisco.

I would be happy to write up an extended version of above text
for informational purposes describing the mechanisms, and doing
my best to stay factual and not let my opinions trickle in too much
(which i took the freedom to do above). If this is something the WG
would like to see. And maybe get some co-author...

Cheers
    Toerless

On Thu, Jul 27, 2017 at 02:55:35PM +0900, Hitoshi Asaeda wrote:
> Basic question.
> Why we should not have a function/mechanism to translate (*,G) join/leave to (S,G) join/leave?
> All (*,G) join/leave requests with global scope multicast address should be translated to appropriate (S,G) join/leave requests based on ???something???.
> This ???something??? may be a multicast database, a directory system, or some network protocol. If no ???S??? information on this ???something???, routers receiving join/leave just discards the request.
> 
> In fact, one big issue would be the deployment of SSM-aware applications. Recently, IGMPv3/MLDv2 are implemented on major OSes. (It took long years!) How about iOS and Android OS? (Maybe not?)
> Now???s the time to consider SSM-aware applications? (Wait for long years again?)
> 
> Long years ago, I tackled the issue and published a paper, whose title is ???Multicast routers cooperating with channel announcement system???.
> (http://ieeexplore.ieee.org/document/1266120/)
> It is an old paper. And the work was in progress at that moment but I stopped the work as my task was done; however this idea may be still interesting. It introduces various benefits, not only (*,G) to (S,G) translation.
> 
> I???m interested in hearing thoughts about (*,G) to (S,G) translation.
> (Sorry for changing the discussion about ???deprecating MDSP???.)
> 
> Regards,
> 
> Hitoshi


From nobody Mon Sep  4 07:12:46 2017
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57E33132A8E for <mboned@ietfa.amsl.com>; Mon,  4 Sep 2017 07:12:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
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 n77pPPHC7CW2 for <mboned@ietfa.amsl.com>; Mon,  4 Sep 2017 07:12:43 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F551132A89 for <mboned@ietf.org>; Mon,  4 Sep 2017 07:12:43 -0700 (PDT)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 79C2C58C4B2; Mon,  4 Sep 2017 16:12:35 +0200 (CEST)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id 6216EB0CAB2; Mon,  4 Sep 2017 16:12:35 +0200 (CEST)
Date: Mon, 4 Sep 2017 16:12:35 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Leonard Giuliano <lenny@juniper.net>
Cc: "Dale W. Carder" <dwcarder@es.net>, mboned@ietf.org
Message-ID: <20170904141235.GC3194@faui40p.informatik.uni-erlangen.de>
References: <20170725221330.GA4821@cs-it-6805697.local> <alpine.DEB.2.02.1707260908550.29724@svl-jtac-lnx02>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.DEB.2.02.1707260908550.29724@svl-jtac-lnx02>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/9-UkCQXNqZLz_bYGMkBMlzjEeeA>
Subject: Re: [MBONED] deprecating MSDP
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Sep 2017 14:12:45 -0000

Depending to some degree to the vendor implementation,
I was suggesting to use MSDP for anycast-RP over RFC4610 because it
had evolved a lot earlier and has a lot more bells and whistles that are
IMHO highly relevant for business criticial anycast PIM-SM deployments.

Alas of course, MSDP is only IPv4, and we should have something equally
good for IPv6 as MSDP has been for IPv4 - for anycast-RP. 

So, IMHO, we should close the gaps of RFC4610 over MSDP: Give
it the option to use TCP (arguably in line with PORT), have a
config/ops model equivalent to the MSDP MIB (subest required for
anycast-RP), and IMHO introduce the equivalent to the MSDP cache
for troubleshooting and per-neighbor state limiters and total state
limiters.

IMHO thats whats needed to deprecate MSDP completely. Shorter term
we can of course have some deployment guide that calls MSDP deprecated,
but not change the doc status to historic/deprecated.

Toerless

On Wed, Jul 26, 2017 at 09:43:37AM -0700, Leonard Giuliano wrote:
> Dale, 
> 
> Great questions and thanks for bringing up, as we'd love feedback from the 
> I2 community- it's probably the largest user of interdomain MSDP and 
> the centerpiece of this conversation.
> 
> draft-ietf-mboned-interdomainpeering-bcp is scoped to just focus on SSM.  
> The plan is for draft-acg-mboned-multicast-models to pick up from there 
> and make the strong recommendation to use SSM, not ASM, for interdomain 
> mcast deployment.  I am not sure about moving MSDP to historic and what 
> that would practically mean, but in IMO, MSDP is somewhat of a scapegoat 
> here.  The real culprit is ASM (or rather, network-based source 
> discovery); MSDP is merely driving the getaway vehicle, albeit with a 
> reckless and dangerous driving style.  Eliminate network-based source 
> discovery for interdomain mcast and the vast majority of the complexity 
> and problems of mcast go away (RPs, PIM registers, RPTs, SPT switchover, 
> MSDP, data-driven state creation, etc).
> 
> We are scoping this to *interdomain*, as it has been mentioned that within 
> a domain there might be reasonable uses for ASM.  And for that matter, 
> what you do in your own house is your business, but once you leave your 
> home and interact with your neighbors and share the roads with other 
> drivers, more stringent rules and guidelines are appropriate for the sake 
> of safety and order.  So we are not saying anything about MSDP for 
> *intradomain* use (for now).  Aside: there is of course RFC4610, but 
> Anycast PIM is pretty much identical to internal MSDP- same behavior by a 
> different name.
> 
> So recommending SSM (and not ASM) for interdomain has overwhelming 
> support, and is basically a no-brainer from a network perspective.  But 
> the big open question is if it's feasible/meaningful given the state of 
> apps today? That is, for those users of interdomain mcast on I2, are the 
> apps they use SSM aware?  Is there a good way to find this out from the I2 
> community?
> 
> -Lenny
> 
> On Tue, 25 Jul 2017, Dale W. Carder wrote:
> 
> | 
> | As was noted in the minutes, there is perhaps a significant set of the
> | multicast community (including ourselves) seriously considering 
> | turning off inter-domain MSDP for good.
> | 
> | Related, I am curious what are the barriers to moving MSDP to historic 
> | status?  In RFC4611, that document differentiates intra-domain vs 
> | inter-domain MSDP.  For that matter, it does a pretty good job at
> | explaining the state of MSDP, but doesn't necessarily reflect what to 
> | do in deployments today.  
> | 
> | That seems to me to be different than where draft-acg-mboned-multicast-models
> | is headed?  
> | 
> | draft-ietf-mboned-interdomainpeering-bcp clearly is not advocating for
> | more inter-domain MSDP.
> | 
> | Dale
> | 
> | _______________________________________________
> | MBONED mailing list
> | MBONED@ietf.org
> | https://www.ietf.org/mailman/listinfo/mboned
> | 
> 
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned

-- 
---
tte@cs.fau.de


From nobody Mon Sep  4 21:19:01 2017
Return-Path: <asaeda@ieee.org>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 140541321AF for <mboned@ietfa.amsl.com>; Mon,  4 Sep 2017 21:19:00 -0700 (PDT)
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=ieee-org.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 DuoAv250xvU9 for <mboned@ietfa.amsl.com>; Mon,  4 Sep 2017 21:18:57 -0700 (PDT)
Received: from mail-pg0-x235.google.com (mail-pg0-x235.google.com [IPv6:2607:f8b0:400e:c05::235]) (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 BA7061241F3 for <mboned@ietf.org>; Mon,  4 Sep 2017 21:18:57 -0700 (PDT)
Received: by mail-pg0-x235.google.com with SMTP id t3so6362861pgt.0 for <mboned@ietf.org>; Mon, 04 Sep 2017 21:18:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ieee-org.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=SWs7bBg6xT7REl01FdAf3o0RsxMvltEH71JHOMYHKkc=; b=x6UtltfUgfViy/A0WoUvQ4S/8Rd8sR4VguGswZQpQAKWnVKFPQVwsd2i6RVI/ouF7D Y0NzxVRN37zOPCMXfRMzFK6ipt6F/VPtR2gdeK3g4mi/m/Zvm7ggJITkMudQP+rj7hd5 inzOcNd1ugivd8SprNq5cQ06cmY+MUiMAPnMBdU3OFyhJzeTQaXWdYMgru3ERrMy+bLC msJlSeNQ1zR+1Q2/eUGJtkYTaqXiejxGzXnnrjeipByYvDiBSjXFj0EJRCB+o4GPwzR8 Zp5cQiYW2t55m9iBzblFaJW60j38k/yuGuOfIIhnIj9RxJN7M4U89ddcWjOCX5XVgGgZ xzAw==
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=SWs7bBg6xT7REl01FdAf3o0RsxMvltEH71JHOMYHKkc=; b=Wq5cXBSf0nGIFWy0l7iAi1p+Rhhx0rmyjh3WluH5rYM5PPnUMPBM1Tl/RBxBIOpZuV 5hCqnzILcUpGyWS1f2Gzgbp3EvmUixwcacBdMZHVVdotjCZtv7XS3uMWgaFctDmCxGIU CczMjY2To1/HiRvD5cEuZ1+zF8nAE9Jq+kSDOnivULGtcZsgf4E3Akn1mWcg+CdoHGfX l+xLVCKf9NwdkCzd5Ex2v/YAKWAKha4ueZiQNTb9FOUxfXus0Rdji6t6jEpMpjpB9KwH 9ifXaManTzcxhd70P3KpiDY87fQ61zFkBMTzr3WLbj5FmTo49lb10EDgi5lOw54a3eVk GNDw==
X-Gm-Message-State: AHPjjUhbr9WWWu2fFtrM8oucR3tNRVDoHmlnFXcXxs5YrRSNZcFDHO6j dwgp/2Tqy27OjcmY
X-Google-Smtp-Source: ADKCNb7Uyhp1kBWvXo152w0Zgewx+Hxs3+eOYVDceOYSbgpDMKXI0t/PFYAlrAA0Viu22RcMclJDkg==
X-Received: by 10.99.132.199 with SMTP id k190mr2692265pgd.25.1504585137105; Mon, 04 Sep 2017 21:18:57 -0700 (PDT)
Received: from ?IPv6:2001:200:e103:1000:585b:17f1:2f20:8fd? ([2001:200:e103:1000:585b:17f1:2f20:8fd]) by smtp.gmail.com with ESMTPSA id u187sm12088874pfu.140.2017.09.04.21.18.55 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 04 Sep 2017 21:18:56 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Hitoshi Asaeda <asaeda@ieee.org>
In-Reply-To: <20170904135045.GA3194@faui40p.informatik.uni-erlangen.de>
Date: Tue, 5 Sep 2017 13:18:53 +0900
Cc: MBONED WG <mboned@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <F2A57762-E181-4921-A1DE-29DF0CDDBB8D@ieee.org>
References: <20170904135045.GA3194@faui40p.informatik.uni-erlangen.de>
To: Toerless Eckert <tte@cs.fau.de>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/j3TMRHFS_od9VixukfeZRGalwwg>
Subject: Re: [MBONED] SSM migration mechanisms (was: Re:  deprecating MSDP)
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Sep 2017 04:19:00 -0000

Hi Toerless,

> There is a wide range of mappings to enable SSM forwarding in =
networks,
> implemented by various vendors. IGMP/MLD EXCLUDE G mappings to =
IGMPv3/MLDv2
> INCLUDE (S,G) via manual config or via DNS learned mappings.

Manual config is troublesome and does not change the conditions better, =
unfortunately. Config via DNS doesn=E2=80=99t require fully functional =
deployment for all DNS servers? I also doubt to modify DNS to support =
the function to maintain volatile (S,G) information.

> Likewise
> the same thing for PIM (*,G) joins translated to (S,G) joins. Starting
> as early as 2004? if i remember correctly.

I previously worked on session announcement vs. source discovery vs. =
directory system, and my paper focusing on multicast routers cooperating =
with a session directory system was published on Jan. 2004.
The requirements for session announcement/discovery were also previously =
given in the following draft;
=
https://tools.ietf.org/html/draft-ietf-mboned-session-announcement-req-03

> The reason why i never opted to document any of these mechanisms in =
the
> IETF (beside "there is something more important to do") was always
> two fold:
>=20
> a) These transition solutions do not give you SSM. Calling them SSM
>   is a lie in disguise. Oops: great marketing. !!!!!

Native solutions are obviously better, but if some mechanism (which must =
be of course technically sound) breaks the deployment barrier, I support =
to use it.
If calling them SSM is the problem, then let=E2=80=99s say here =
SSM-compatible multicast.:)

>   You still need to do ASM style multicast group addess management:
>   You can not have two uncordinated application receivers randomnly
>   choose group addresses and get away with it!!! With SSM, there
>   is no need for any multicast group address management/allocation
>   to application instances!!!

A system, which could be a mapping system, directory system, or =
announcement system, translating (*,G) to (S,G) will in any case =
maintain group addresses and hence can assign a unique group address for =
each application. Applications only need to connect the system to obtain =
"G" information and register "S" information, and routers only need to =
translate (*,G) to (S,G). There is no need for any multicast group =
address management/allocation to application instances themselves.

> b) With a) taken into accoun, I thought and still think that these
>   are transition mechanisms.  Documentating them would give them
>   more credit than i think they should have. Aka: Especially today,
>   there is IMHO no reason why any applications should not be able to=20=

>   generate (S,G) memberships.
>=20
>   If someone thinks there is a good reason, let me know!

=46rom a view of the host side implementation, IGMPv3/MLDv2 must be =
supported in kernel, and applications must use MSF APIs such as =
IP_ADD_SOURCE_MEMBERSHIP with setsockopt() in C. MSF APIs are not used =
for the traditional multicast applications, requesting (*,G) join.
IMO, android does not support IGMPv3/MLDv2 and has no application using =
IP_ADD_SOURCE_MEMBERSHIP or equivalent APIs.
I don=E2=80=99t know Apple iOS, but at least, I=E2=80=99ve never seen =
SSM-capable applications (i.e. using IP_ADD_SOURCE_MEMBERSHIP etc.) for =
iOS.

I believe you don=E2=80=99t want to ignore android (and iPhone as well).

> Now, there are transition mechanisms that do not suffer from a),
> namely IGMPv3 lite and URD. These are a class better, but never
> catched on as much as the IGMP/PIM SSM mapping mechanisms - because
> they did require application developers to do something - as opposed
> to hos IGMP/PIM SSM mapping mechanisms, IGMPv3lite and URD where
> only meant to get around the limitation of the OS not supporting
> IGMPv3/MLDv2. But guess what: the whole reason why SSM has not catched
> on as much as it should is LAZY APPLICATION DEVELOPERS and=20
> LAZY API STANDARDISERS (eg: IGMPv3 support in Java, websockets etc. =
pp).

Many application developpers do not know or do not take care MSF APIs as =
they do not recognize the benefit given by SSM. They may think SSM or =
multicast itself only gives the networking benefit.
However, if the service qualities or performances for the current =
applications (having no MSF APIs) becomes better due to SSM-compatible =
networking, the application developers may change their minds as they =
recognize the application-level benefit. I don=E2=80=99t know the level =
of this benefit, though.

> And all OSs today support IGMPv3/MLDv2.

How about android and iOS?

> So, i would opt against documenting these mechanisms in a way that
> would promote them. Besides, there are patents with my name
> or other Cisco inventors on these, and given how i do not work for
> Cisco anymore, i can not help in getting IPR disclosures from
> Cisco.

I=E2=80=99m afraid that I cannot say anything about this issue.. But =
maybe I support your thought.

> I would be happy to write up an extended version of above text
> for informational purposes describing the mechanisms, and doing
> my best to stay factual and not let my opinions trickle in too much
> (which i took the freedom to do above). If this is something the WG
> would like to see. And maybe get some co-author=E2=80=A6

If some positive situation can be documented, I=E2=80=99m happy to work =
on it as well.:)

Regards,

Hitoshi


> Cheers
>    Toerless
>=20
> On Thu, Jul 27, 2017 at 02:55:35PM +0900, Hitoshi Asaeda wrote:
>> Basic question.
>> Why we should not have a function/mechanism to translate (*,G) =
join/leave to (S,G) join/leave?
>> All (*,G) join/leave requests with global scope multicast address =
should be translated to appropriate (S,G) join/leave requests based on =
"something".
>> This "something" may be a multicast database, a directory system, or =
some network protocol. If no "S" information on this "something", =
routers receiving join/leave just discards the request.
>>=20
>> In fact, one big issue would be the deployment of SSM-aware =
applications. Recently, IGMPv3/MLDv2 are implemented on major OSes. (It =
took long years!) How about iOS and Android OS? (Maybe not?)
>> Now=E2=80=99s the time to consider SSM-aware applications? (Wait for =
long years again?)
>>=20
>> Long years ago, I tackled the issue and published a paper, whose =
title is "Multicast routers cooperating with channel announcement =
system".
>> (http://ieeexplore.ieee.org/document/1266120/)
>> It is an old paper. And the work was in progress at that moment but I =
stopped the work as my task was done; however this idea may be still =
interesting. It introduces various benefits, not only (*,G) to (S,G) =
translation.
>>=20
>> I=E2=80=99m interested in hearing thoughts about (*,G) to (S,G) =
translation.
>> (Sorry for changing the discussion about ???deprecating MDSP???.)
>>=20
>> Regards,
>>=20
>> Hitoshi


From nobody Tue Sep  5 01:26:47 2017
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AFF74132715 for <mboned@ietfa.amsl.com>; Tue,  5 Sep 2017 01:26:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level: 
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 VIeqxO9UyUHy for <mboned@ietfa.amsl.com>; Tue,  5 Sep 2017 01:26:43 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F9F9132396 for <mboned@ietf.org>; Tue,  5 Sep 2017 01:26:43 -0700 (PDT)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [131.188.34.77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 04C2B58C4B4; Tue,  5 Sep 2017 10:26:35 +0200 (CEST)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id DBDB4B0CACC; Tue,  5 Sep 2017 10:26:34 +0200 (CEST)
Date: Tue, 5 Sep 2017 10:26:34 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Hitoshi Asaeda <asaeda@ieee.org>
Cc: MBONED WG <mboned@ietf.org>
Message-ID: <20170905082634.GA32298@faui40p.informatik.uni-erlangen.de>
References: <20170904135045.GA3194@faui40p.informatik.uni-erlangen.de> <F2A57762-E181-4921-A1DE-29DF0CDDBB8D@ieee.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <F2A57762-E181-4921-A1DE-29DF0CDDBB8D@ieee.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/p1z1uUzSkpWckxr_5Y9xwyK8_v8>
Subject: Re: [MBONED] SSM migration mechanisms (was: Re:  deprecating MSDP)
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Sep 2017 08:26:46 -0000

Thanks, Hitoski


1. Calling SSM mapping

I do not 't think we can call IGMP/MLD/PIM G->S mapping config options
"SSM compatible", because it really is not: SSM means no group allocation.

"(S,G)-only multicast" would work, but PIM-DM and DVMRP also do that.
"sparse (S,G)-only multicast" ? Correct but not catchy.

I am going to call it "Imitation SSM".
Like imitation crab meat it sells more than the original.
And it wll expresses what i think about it.

2. Address allocation systems

It does not make sense to consider work on a system that enables applications
to allocate multicast group addresses. That work was done in the 1990th
and ended up in RFC2730 (MADCAP), RFC2776 (MZAP), RFC2909 (MASC)  and
RFC2908 (architecture). That stuff was never adopted. I you ask me because
of my pet theory: application developers did never care about doing multicast
well.

3. Automating imitation SSM

Automating the configuration of imitation SSM was of course always
interesting. The DNS lookup for SSM mapping from yours truly 
does not require any new RR types but simply encodes the group address
into domain names (similar to .arpa) and uses A RRs, so runs on any DNS server
and can be set up to use a sub-zone explicitly set up for DNS mapping
so that it doesn't impact any existing DNS Zone.

Today one could think about automating SSM mapping configs via YANG, but
i am not quite sure how. Or if that would ever be better than DNS. And,
as mentioned, i am not a fan of imitation SSM, i just worked a lot on
it because it was the best we could get deployed in this industry.

4. SSM support for apps

These days, SSM is really supported on every relevant OS for at least
5 years i think. It got into linux in some 2.x kernel, so all 3.x and
4.x have it. It went last into MacOS X in something like 10.7 or
10.8 and at the same time into iOS. Android just inherits linux, so
it should havee s been there foreever, see eg:

https://github.com/android/platform_prebuilt/blob/master/ndk/android-ndk-r5/platforms/android-3/arch-arm/usr/include/linux/in.h

The main issue once it was in all OSs was language binding into
all languages, like Java, etc. I think it's now in all languages
that run native on OSs. Aka: with something like javascript the
main issue is the slow proliferation of UDP websockets, and yes, on
UDP websockets multicast is stsill missing AFAIK. But AFAIK thats ASM
and SSM.

Aka: SSM is ubiquitous for non-web-browser based apps. Ad for web-browser
based apps we could rely on AMT (unicast) web sockets for the time
being.

Cheers
    Toerless

On Tue, Sep 05, 2017 at 01:18:53PM +0900, Hitoshi Asaeda wrote:
> Hi Toerless,
> 
> > There is a wide range of mappings to enable SSM forwarding in networks,
> > implemented by various vendors. IGMP/MLD EXCLUDE G mappings to IGMPv3/MLDv2
> > INCLUDE (S,G) via manual config or via DNS learned mappings.
> 
> Manual config is troublesome and does not change the conditions better, unfortunately. Config via DNS doesn???t require fully functional deployment for all DNS servers? I also doubt to modify DNS to support the function to maintain volatile (S,G) information.
> 
> > Likewise
> > the same thing for PIM (*,G) joins translated to (S,G) joins. Starting
> > as early as 2004? if i remember correctly.
> 
> I previously worked on session announcement vs. source discovery vs. directory system, and my paper focusing on multicast routers cooperating with a session directory system was published on Jan. 2004.
> The requirements for session announcement/discovery were also previously given in the following draft;
> https://tools.ietf.org/html/draft-ietf-mboned-session-announcement-req-03
> 
> > The reason why i never opted to document any of these mechanisms in the
> > IETF (beside "there is something more important to do") was always
> > two fold:
> > 
> > a) These transition solutions do not give you SSM. Calling them SSM
> >   is a lie in disguise. Oops: great marketing. !!!!!
> 
> Native solutions are obviously better, but if some mechanism (which must be of course technically sound) breaks the deployment barrier, I support to use it.
> If calling them SSM is the problem, then let???s say here SSM-compatible multicast.:)
> 
> >   You still need to do ASM style multicast group addess management:
> >   You can not have two uncordinated application receivers randomnly
> >   choose group addresses and get away with it!!! With SSM, there
> >   is no need for any multicast group address management/allocation
> >   to application instances!!!
> 
> A system, which could be a mapping system, directory system, or announcement system, translating (*,G) to (S,G) will in any case maintain group addresses and hence can assign a unique group address for each application. Applications only need to connect the system to obtain "G" information and register "S" information, and routers only need to translate (*,G) to (S,G). There is no need for any multicast group address management/allocation to application instances themselves.
> 
> > b) With a) taken into accoun, I thought and still think that these
> >   are transition mechanisms.  Documentating them would give them
> >   more credit than i think they should have. Aka: Especially today,
> >   there is IMHO no reason why any applications should not be able to 
> >   generate (S,G) memberships.
> > 
> >   If someone thinks there is a good reason, let me know!
> 
> From a view of the host side implementation, IGMPv3/MLDv2 must be supported in kernel, and applications must use MSF APIs such as IP_ADD_SOURCE_MEMBERSHIP with setsockopt() in C. MSF APIs are not used for the traditional multicast applications, requesting (*,G) join.
> IMO, android does not support IGMPv3/MLDv2 and has no application using IP_ADD_SOURCE_MEMBERSHIP or equivalent APIs.
> I don???t know Apple iOS, but at least, I???ve never seen SSM-capable applications (i.e. using IP_ADD_SOURCE_MEMBERSHIP etc.) for iOS.
> 
> I believe you don???t want to ignore android (and iPhone as well).
> 
> > Now, there are transition mechanisms that do not suffer from a),
> > namely IGMPv3 lite and URD. These are a class better, but never
> > catched on as much as the IGMP/PIM SSM mapping mechanisms - because
> > they did require application developers to do something - as opposed
> > to hos IGMP/PIM SSM mapping mechanisms, IGMPv3lite and URD where
> > only meant to get around the limitation of the OS not supporting
> > IGMPv3/MLDv2. But guess what: the whole reason why SSM has not catched
> > on as much as it should is LAZY APPLICATION DEVELOPERS and 
> > LAZY API STANDARDISERS (eg: IGMPv3 support in Java, websockets etc. pp).
> 
> Many application developpers do not know or do not take care MSF APIs as they do not recognize the benefit given by SSM. They may think SSM or multicast itself only gives the networking benefit.
> However, if the service qualities or performances for the current applications (having no MSF APIs) becomes better due to SSM-compatible networking, the application developers may change their minds as they recognize the application-level benefit. I don???t know the level of this benefit, though.
> 
> > And all OSs today support IGMPv3/MLDv2.
> 
> How about android and iOS?
> 
> > So, i would opt against documenting these mechanisms in a way that
> > would promote them. Besides, there are patents with my name
> > or other Cisco inventors on these, and given how i do not work for
> > Cisco anymore, i can not help in getting IPR disclosures from
> > Cisco.
> 
> I???m afraid that I cannot say anything about this issue.. But maybe I support your thought.
> 
> > I would be happy to write up an extended version of above text
> > for informational purposes describing the mechanisms, and doing
> > my best to stay factual and not let my opinions trickle in too much
> > (which i took the freedom to do above). If this is something the WG
> > would like to see. And maybe get some co-author???
> 
> If some positive situation can be documented, I???m happy to work on it as well.:)
> 
> Regards,
> 
> Hitoshi
> 
> 
> > Cheers
> >    Toerless
> > 
> > On Thu, Jul 27, 2017 at 02:55:35PM +0900, Hitoshi Asaeda wrote:
> >> Basic question.
> >> Why we should not have a function/mechanism to translate (*,G) join/leave to (S,G) join/leave?
> >> All (*,G) join/leave requests with global scope multicast address should be translated to appropriate (S,G) join/leave requests based on "something".
> >> This "something" may be a multicast database, a directory system, or some network protocol. If no "S" information on this "something", routers receiving join/leave just discards the request.
> >> 
> >> In fact, one big issue would be the deployment of SSM-aware applications. Recently, IGMPv3/MLDv2 are implemented on major OSes. (It took long years!) How about iOS and Android OS? (Maybe not?)
> >> Now???s the time to consider SSM-aware applications? (Wait for long years again?)
> >> 
> >> Long years ago, I tackled the issue and published a paper, whose title is "Multicast routers cooperating with channel announcement system".
> >> (http://ieeexplore.ieee.org/document/1266120/)
> >> It is an old paper. And the work was in progress at that moment but I stopped the work as my task was done; however this idea may be still interesting. It introduces various benefits, not only (*,G) to (S,G) translation.
> >> 
> >> I???m interested in hearing thoughts about (*,G) to (S,G) translation.
> >> (Sorry for changing the discussion about ???deprecating MDSP???.)
> >> 
> >> Regards,
> >> 
> >> Hitoshi
> 
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned

-- 
---
tte@cs.fau.de


From nobody Tue Sep  5 14:21:00 2017
Return-Path: <lenny@juniper.net>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C8003132E33 for <mboned@ietfa.amsl.com>; Tue,  5 Sep 2017 14:20:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.02
X-Spam-Level: 
X-Spam-Status: No, score=-2.02 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=juniper.net
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 YH0Igo17ZYCS for <mboned@ietfa.amsl.com>; Tue,  5 Sep 2017 14:20:54 -0700 (PDT)
Received: from NAM03-CO1-obe.outbound.protection.outlook.com (mail-co1nam03on0124.outbound.protection.outlook.com [104.47.40.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C6BC12895E for <mboned@ietf.org>; Tue,  5 Sep 2017 14:20:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=OMqxeSXe8UH28tf/3zmdQJ3Z9jlr+R1gQQR3frb02KM=; b=ep9LJfLJXDC2hK+rOvWNODDJ/CPf1RJYCtG9HlHTGotiuJFWtqHSx/AAYuWT+IfBjaJNpssCuKxNCHewse9vNqYDZZFr5zoY+Z8ZOiRyn1vryWfMM2JfJ7am60XNnE5J5o35Yt4r9y+OyBGfW8pTQ56dvbiJifI+SwmIgaH2TP4=
Received: from CY1PR05CA0023.namprd05.prod.outlook.com (10.166.186.161) by BY2PR0501MB2071.namprd05.prod.outlook.com (10.163.197.153) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.35.3; Tue, 5 Sep 2017 21:20:52 +0000
Received: from DM3NAM05FT054.eop-nam05.prod.protection.outlook.com (2a01:111:f400:7e51::208) by CY1PR05CA0023.outlook.office365.com (2a01:111:e400:c5a4::33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.35.3 via Frontend Transport; Tue, 5 Sep 2017 21:20:52 +0000
Authentication-Results: spf=softfail (sender IP is 66.129.239.15) smtp.mailfrom=juniper.net; ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=fail action=none header.from=juniper.net;
Received-SPF: SoftFail (protection.outlook.com: domain of transitioning juniper.net discourages use of 66.129.239.15 as permitted sender)
Received: from P-EMFE01C-SAC.jnpr.net (66.129.239.15) by DM3NAM05FT054.mail.protection.outlook.com (10.152.98.168) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P256) id 15.1.1385.11 via Frontend Transport; Tue, 5 Sep 2017 21:20:52 +0000
Received: from svl-jtac-lnx06.juniper.net (172.17.28.215) by P-EMFE01C-SAC.jnpr.net (172.24.192.21) with Microsoft SMTP Server id 14.3.123.3; Tue, 5 Sep 2017 14:20:51 -0700
Received: by svl-jtac-lnx06.juniper.net (Postfix, from userid 1709)	id 182899F6DB; Tue,  5 Sep 2017 14:20:51 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])	by svl-jtac-lnx06.juniper.net (Postfix) with ESMTP id 12B889F6D0; Tue,  5 Sep 2017 14:20:51 -0700 (PDT)
Date: Tue, 5 Sep 2017 14:20:50 -0700
From: Leonard Giuliano <lenny@juniper.net>
To: Toerless Eckert <tte@cs.fau.de>
CC: "Dale W. Carder" <dwcarder@es.net>, <mboned@ietf.org>
In-Reply-To: <20170904141235.GC3194@faui40p.informatik.uni-erlangen.de>
Message-ID: <alpine.DEB.2.02.1709051358300.14937@svl-jtac-lnx02.juniper.net>
References: <20170725221330.GA4821@cs-it-6805697.local> <alpine.DEB.2.02.1707260908550.29724@svl-jtac-lnx02> <20170904141235.GC3194@faui40p.informatik.uni-erlangen.de>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
X-EOPAttributedMessage: 0
X-MS-Office365-Filtering-HT: Tenant
X-Forefront-Antispam-Report: CIP:66.129.239.15; IPV:NLI; CTRY:US; EFV:NLI; SFV:NSPM; SFS:(10019020)(6009001)(39860400002)(2980300002)(24454002)(189002)(199003)(46386002)(83506001)(45336002)(4001350100001)(90966002)(626005)(229853002)(6266002)(5005980100005)(106466001)(105596002)(97736004)(76506005)(76176999)(50986999)(46406003)(6916009)(5660300001)(57986006)(54356999)(2950100002)(356003)(47776003)(50466002)(3240700002)(7126002)(6246003)(86362001)(54906002)(966005)(68736007)(189998001)(77096006)(6306002)(69596002)(8936002)(8676002)(478600001)(305945005)(2906002)(4326008)(110136004)(53936002)(23726003)(2810700001)(81166006)(81156014)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR0501MB2071; H:P-EMFE01C-SAC.jnpr.net; FPR:; SPF:SoftFail; PTR:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-Microsoft-Exchange-Diagnostics: 1; DM3NAM05FT054; 1:a4MR9jFMefbXrT0niWW9gwNWNkL8SKVQKLa2YcVkUtnKJkqLQ6dQrLyQedk+ITxmD6AjvgCqUuug99aRsJx+tXW3A338IigfoS3BWN2OIeXpSKXI5Ny/7comqMBBj/zx
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 3ce7fd86-51ca-4ace-2f5f-08d4f4a3fcc1
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(2017030254152)(300000503095)(300135400095)(2017052603199)(201703131423075)(201703031133081)(201702281549075)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:BY2PR0501MB2071; 
X-Microsoft-Exchange-Diagnostics: 1; BY2PR0501MB2071; 3:+2OzKI4k174BqWZPi1NPK+xh9XnqhR4e92GVzVri7VIUFqmuo0P1jIlf9JT94iic0xVLQF1UQciYkH/EJOA0TUxCteQtfwR/KgvwmVK1axCcUmVhGOY7ST3VY0Rgc1RjdsgPbMS3p5hY6fc52JUspWUyR5bsfPHm/q4XYkBl67HB3xXXX9m4yX+cxi8v1klCrJIyJK2RB919yuTVJ2AMT6/Q8LzN5EEteJyohvuJ0PyDmKa5DU7StCVvtkz1yLzLE7MhrD63oKv3H5SOd77OafX5RoxSUbGhp8aX7gDbutp5/mj2ga2Q+rFhZ+GTQaW0OtFafc4q21RdTGoNp2zQcooMlSe6sv3K8N2iYT3X6Zo=; 25:xuv6uO9NYjf/IALNSU8+y50sJA+d156H7NxUpP5nHSy9oFFvEBZ8QcehYGyrNXVYQjanzK4eczD3/f6wAZQE9OkBsr4UFCDEMjUQ7FR01rSWtZGHDcj5YgE2/+tbmFHHgbfE4yDDmeg7ZApnEOCjyzUO7iKUDFzQH/IboqUPPFsxNzx/R4ZyVKy5w22pUXlu+Ymk/lLHUgUeWE5tDiIzucTBaOUB/Q+bBBuvRFl2BOnNfmkRBKiwWLFaBG6pU1rhW132ghqcWIzD9fzpTM8ovEWjVmCjSLdCgUhyAQpGlJRnF40K/kwEBFmZGs9aUX0vn07783E9oGZhhjWdiORfDw==
X-MS-TrafficTypeDiagnostic: BY2PR0501MB2071:
X-Microsoft-Exchange-Diagnostics: 1; BY2PR0501MB2071; 31:8nH3ZEnowLGSD0SKpkchjETkJ288eUNH+sHBbLOPXtFsXusuV2Sx2daBhOXm3Nkbx2XPOFwIcRr/PjM6iiPH7fDsNoPJe5TyhsYFIcEG14Kvq3MzZKtiqIcVnuw2DetEw8vtmpJAqnQBed2CDddEIRa/9UbAXaERT1zTBk80dGEgHCVCb+n3MlqmeE1ifSLLoSKmwohj4XhoZ+xT9i5gsvf7ZwOAFOCvJQ5/OWiRNWo=; 20:/AjHehZgkBuoqGkh/UK70Uok+sYbodzPirOw/rnLOUtHzdJDrKEbNSXuyViINO2jojBm22M9Drv9k9aqzzK5pNa6sV9OjMlaCSzbpZnPUSwjUA02ZkKBNhI8TQfEvWwYByAN8+U+XcNeHZu9FDBlhgaAf0PkKjc27SIkSJUOrJSKz1Ozn1FRLBbngO7pLw1Ss8fMYe2QLcK/kZSNwZ3MQYlBWLc7wisxex3cA+w1T0F+5EK4AOekFwONMo4dOIzoECGHjqPGQiHcYNyjteegm54OHZBjrtROvzeFpRQ9Zid3hedlHyYBVY3XXGwoY6uTAY4tJLR5FvEfDCItl0Obe3iCV6h6w9qewa8X7LsAMzMnLF6CmyI8cSsE/+3ObMROOUFtkoYeACS0XGiGEfEMrs0jgEHn1VT6wFIRkTOM9w8fqOPG8NnnSnxup8vanEbpqJm6nFv6AbC0uciZMIkxXq9YyG4b9I61V/h2/uOUpMhBLyiw8GyeN9V/xr7Wk0r4
X-Exchange-Antispam-Report-Test: UriScan:(35073007944872);
X-Microsoft-Antispam-PRVS: <BY2PR0501MB2071BC76C9D0C3CAB0729B10A4960@BY2PR0501MB2071.namprd05.prod.outlook.com>
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(8121501046)(5005006)(100000703101)(100105400095)(3002001)(93006095)(93001095)(10201501046)(6055026)(6041248)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123564025)(20161123562025)(20161123558100)(20161123560025)(20161123555025)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:BY2PR0501MB2071; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:BY2PR0501MB2071; 
X-Microsoft-Exchange-Diagnostics: 1; BY2PR0501MB2071; 4:SLBgiS0qiwEV9jqglzMHctoMOwcEfRXWshyJPwSwc2viKTGIvFfdtBJ4brhdbxJAgFt+dzry5ccrOopbl5qRxluc0avZ5HTpKoN3SZK/WkIFTSAOL2DZjQIV3oEUJMp1F7n3eP6k7YOqc1d9L4Lu5vgTOPagHz+jOJyNRg/d9azt3XZN/uVofpvXk3tEjrRW6g2T4YeNijnSooPv0BtEL1YBE6GpwrTGFW1wvL53rRKIzOVrUY7FcYJra1USqB0KCiAZJsx9HHZSAxUj6lP6RSkvEnhThEy2rzLfno+5z28=
X-Forefront-PRVS: 0421BF7135
X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; BY2PR0501MB2071; 23:0lUQzoCy096VQZaTsAu1FdNJUmpJ0iEXb/+Onx+?= =?us-ascii?Q?yIsm3Irl9oGolt//EfPi1WvqnXZVM+gKJtzqAkQUGTkCNQHviKIBmseYsjFt?= =?us-ascii?Q?wUs8/RdqSGDLGUeTtqEcYDMhySZz7lu4W19N4d2Tb/BsdqvJprfCUaRzKkgp?= =?us-ascii?Q?Ls/plLVB6ciC7utVdzJUxUZyWP0cFZNoSnM5PiDARjsGyONnsAkQEqA6IVWg?= =?us-ascii?Q?4iub3ZngxyBb4D9JtHoEf+XkIAniMaYO9VArfkAidNEVBxkE8niHC457MZyh?= =?us-ascii?Q?3iuW6tWk0EqTLZ0tDbeNk38vxdcJ+HW0Cm79h3J4ycvh1JTCyUmyr8VIxuX+?= =?us-ascii?Q?gKN+Pi2fEaKmb47BtdClSgTS1K8fRKa/rCyeh/TxiJpEqZGXhI1azv5LT9Rh?= =?us-ascii?Q?eFCtxUgL5/9ufIiE5MBc73bo5/z9jhMawr9fVl3K8nduomCLTnt0DdmDymKN?= =?us-ascii?Q?pzgsT/1Mp8I/Id68OPeuBISxdM1171vlWVzfB6aWEURphXQDnlivxOvgbfTh?= =?us-ascii?Q?xVp0ceUwaOBhh+jv35DpAAMWV1mSu1lg89jk/zIwdnugctTJoQ3isMBbUiKd?= =?us-ascii?Q?EuRAXnQJFWvp6+Kveq9Cwvxbjl22k6lByFrdZoNHqm5wPlBTuUeMMV2mGRsb?= =?us-ascii?Q?y58u4Of3eB40vH3rq8P86A4O1tGHyY7Cm1kt1oFTyf/LUV2F7ZzDBJSTLa4J?= =?us-ascii?Q?BPvsZyTmZ0GghtGFO3cYRP8MCyyqIAdr/zPoq4U4gVd8ak5N0+a/8BjaLdKE?= =?us-ascii?Q?ld0MF+AwutVWqSZ5UPvXcVkhGy44fsqeqLuoZb0RuKQSfPV+JMdo8OdWWpMj?= =?us-ascii?Q?trkvL/LPGPAGF9Db5YOSTlKH2nLruv4cFMcNIRrynrvKnClnvuZ9zDQfuX3l?= =?us-ascii?Q?OUdWM46e3+pVnRQVaY3bMEQfrj3EWdd2RgUS7azmdL9HxbtZYR3bRV/8voMI?= =?us-ascii?Q?8m+d8UTVthu19W9NoNS1gJmADUW40f5RDx9rgsn2YUrJROXF+kZJvcdvAao3?= =?us-ascii?Q?yAKhWCPnBs9QjNfrb78MyK/ybhhUhYDj+vNG5mPUx/3k4qVpRNqDrd2d2DCv?= =?us-ascii?Q?hlmtTjasY8Xq3iQHwWsRv5m2rYKfTX6R7VPUKWqFAU4J6ehc41XK43lA0u8X?= =?us-ascii?Q?P/mFGPJ5Ok8Kc6o1GwP3z1iFbyO8U+AIVj8B706kv8WnnyrPUqgpbq1takXm?= =?us-ascii?Q?8LYf/Rr2hUeBFoeo75sioCyFyUne0Lh3RRCOI/PKhWBHcL796qaM3YWgroEv?= =?us-ascii?Q?SbK1YMnohr/sBL2Pky9x9keYOLaQgYsr9o889dwAy0kmBmTEx2wvS++AZZhk?= =?us-ascii?Q?NJQ=3D=3D?=
X-Microsoft-Exchange-Diagnostics: 1; BY2PR0501MB2071; 6:WaNM+/O5WQ4YBD50Ie6/qj7q7Z5f2Ip9zCv9Qtm6kPSvOpjxex7+/sEbYdXBME1zyLhJaT2Qg4nntk80blprW8f6vDhpt/0Mr16aCbFO6m1IZ6iuKrno8QJ5ZMoYcWwZvDHEyJHxsvpxLAuXsjrez7YXqQQz6qmvPVwtcJS/yM7D3BVfsT4/8aAzmxCzioE/x5cdAQetLkzplOVq4jzQ7H2FI75Ot9aok/doXoW5mhv51HbePLnRZ4C5BvrwncCoP9Vq+5RGk7yQ7CWE8kHkMkKSJjxgdfgtMQ+5a0egQ211bvNYXNJ0RniJrJWDcQTTsEUmd4D6PI/RmcrxWjAupw==; 5:zXjcCy3xGNJ4fMHKvNPTIL7/yP87cOe9+o/vVOgIB5Swi/6DGRsgwHxWB6u7wZjBTvfmzb93OsWettCZnh+d2mZd26gUvtlO4YdbDGbGjIbIYV6veYG1OTwNzJ7VT1DW14vz2ZmnEcDQTkmulCj2dg==; 24:6sCePwRkZJND4r/BTZr+vR6GMNLjvrg+DUmOONiIOM/UVcr5t60JuEgSTEF5ylIlvrbxiEs4QSAgOrJGacw0LYA8i449RMm51+WDX1AurJA=; 7:kKgTUBMGvTB7IEau6AYldwYVURRfHq+rBwcjGGlyeDJK6gckLlD/aGp/jMmeziBhgu3WoPMxyfEWleWGQ+zcEh90BAlQI58eXBy+2Qyg0wljipy2a5UPPafzyqMcNoSVxbju4POoh+cFh4M6iUIgyhBB8EhuWXzQzvlblIeuNkJsLWSZfHVw50sqa/VJsx/ti+ifL39S62vFD3KPp3JxvhmkBC9CFCl+lddoWm5GHmA=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 05 Sep 2017 21:20:52.1260 (UTC)
X-MS-Exchange-CrossTenant-Id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=bea78b3c-4cdb-4130-854a-1d193232e5f4; Ip=[66.129.239.15];  Helo=[P-EMFE01C-SAC.jnpr.net]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR0501MB2071
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/PT3vxu22yxyJSC4XdhDMHLGTVmk>
Subject: Re: [MBONED] deprecating MSDP
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Sep 2017 21:20:57 -0000

IMO, closing the gap between RFC4610 and MSDP would be a step in the wrong 
direction.  Reinventing MSDP and calling it another name will solve 
nothing.  "A source discovery protocol by any other name would smell as 
sweet..."  If someone really wants to run Anycast RP in v6 within his 
domain, RFC4610 should be good enough.

Again, the problem isn't MSDP, the problem is ASM.  Tweaking RFC4610 to 
match the microscopic (and generally irrelevant) benefits MSDP might have 
will just create yet another overly complex mcast protocol to address the 
corner cases of a handful of ill-conceived network deployments.  And have 
the same result- no one deploys it bc of all this unnecessary complexity.

If the goal is to change course and get folks to deploy mcast, we should 
make things unambiguously simple- use SSM in the network layer and let the 
some other layer handle source discovery.


On Mon, 4 Sep 2017, Toerless Eckert wrote:

| 
| Depending to some degree to the vendor implementation,
| I was suggesting to use MSDP for anycast-RP over RFC4610 because it
| had evolved a lot earlier and has a lot more bells and whistles that are
| IMHO highly relevant for business criticial anycast PIM-SM deployments.
| 
| Alas of course, MSDP is only IPv4, and we should have something equally
| good for IPv6 as MSDP has been for IPv4 - for anycast-RP. 
| 
| So, IMHO, we should close the gaps of RFC4610 over MSDP: Give
| it the option to use TCP (arguably in line with PORT), have a
| config/ops model equivalent to the MSDP MIB (subest required for
| anycast-RP), and IMHO introduce the equivalent to the MSDP cache
| for troubleshooting and per-neighbor state limiters and total state
| limiters.
| 
| IMHO thats whats needed to deprecate MSDP completely. Shorter term
| we can of course have some deployment guide that calls MSDP deprecated,
| but not change the doc status to historic/deprecated.
| 
| Toerless
| 
| On Wed, Jul 26, 2017 at 09:43:37AM -0700, Leonard Giuliano wrote:
| > Dale, 
| > 
| > Great questions and thanks for bringing up, as we'd love feedback from the 
| > I2 community- it's probably the largest user of interdomain MSDP and 
| > the centerpiece of this conversation.
| > 
| > draft-ietf-mboned-interdomainpeering-bcp is scoped to just focus on SSM.  
| > The plan is for draft-acg-mboned-multicast-models to pick up from there 
| > and make the strong recommendation to use SSM, not ASM, for interdomain 
| > mcast deployment.  I am not sure about moving MSDP to historic and what 
| > that would practically mean, but in IMO, MSDP is somewhat of a scapegoat 
| > here.  The real culprit is ASM (or rather, network-based source 
| > discovery); MSDP is merely driving the getaway vehicle, albeit with a 
| > reckless and dangerous driving style.  Eliminate network-based source 
| > discovery for interdomain mcast and the vast majority of the complexity 
| > and problems of mcast go away (RPs, PIM registers, RPTs, SPT switchover, 
| > MSDP, data-driven state creation, etc).
| > 
| > We are scoping this to *interdomain*, as it has been mentioned that within 
| > a domain there might be reasonable uses for ASM.  And for that matter, 
| > what you do in your own house is your business, but once you leave your 
| > home and interact with your neighbors and share the roads with other 
| > drivers, more stringent rules and guidelines are appropriate for the sake 
| > of safety and order.  So we are not saying anything about MSDP for 
| > *intradomain* use (for now).  Aside: there is of course RFC4610, but 
| > Anycast PIM is pretty much identical to internal MSDP- same behavior by a 
| > different name.
| > 
| > So recommending SSM (and not ASM) for interdomain has overwhelming 
| > support, and is basically a no-brainer from a network perspective.  But 
| > the big open question is if it's feasible/meaningful given the state of 
| > apps today? That is, for those users of interdomain mcast on I2, are the 
| > apps they use SSM aware?  Is there a good way to find this out from the I2 
| > community?
| > 
| > -Lenny
| > 
| > On Tue, 25 Jul 2017, Dale W. Carder wrote:
| > 
| > | 
| > | As was noted in the minutes, there is perhaps a significant set of the
| > | multicast community (including ourselves) seriously considering 
| > | turning off inter-domain MSDP for good.
| > | 
| > | Related, I am curious what are the barriers to moving MSDP to historic 
| > | status?  In RFC4611, that document differentiates intra-domain vs 
| > | inter-domain MSDP.  For that matter, it does a pretty good job at
| > | explaining the state of MSDP, but doesn't necessarily reflect what to 
| > | do in deployments today.  
| > | 
| > | That seems to me to be different than where draft-acg-mboned-multicast-models
| > | is headed?  
| > | 
| > | draft-ietf-mboned-interdomainpeering-bcp clearly is not advocating for
| > | more inter-domain MSDP.
| > | 
| > | Dale
| > | 
| > | _______________________________________________
| > | MBONED mailing list
| > | MBONED@ietf.org
| > | https://www.ietf.org/mailman/listinfo/mboned
| > | 
| > 
| > _______________________________________________
| > MBONED mailing list
| > MBONED@ietf.org
| > https://www.ietf.org/mailman/listinfo/mboned
| 
| -- 
| ---
| tte@cs.fau.de
| 


From nobody Tue Sep  5 14:46:09 2017
Return-Path: <albert.e.manfredi@boeing.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4D7C13208E for <mboned@ietfa.amsl.com>; Tue,  5 Sep 2017 14:46:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 zl0QiHKJ6uam for <mboned@ietfa.amsl.com>; Tue,  5 Sep 2017 14:46:06 -0700 (PDT)
Received: from phx-mbsout-01.mbs.boeing.net (phx-mbsout-01.mbs.boeing.net [130.76.184.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 77738132076 for <mboned@ietf.org>; Tue,  5 Sep 2017 14:46:06 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id v85Lk5Ct001474; Tue, 5 Sep 2017 14:46:05 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (xch15-06-08.nw.nos.boeing.com [137.136.238.222]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v85LjsJ8000920 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Tue, 5 Sep 2017 14:45:54 -0700
Received: from XCH15-06-11.nw.nos.boeing.com (2002:8988:efdc::8988:efdc) by XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Tue, 5 Sep 2017 14:45:53 -0700
Received: from XCH15-06-11.nw.nos.boeing.com ([137.136.239.220]) by XCH15-06-11.nw.nos.boeing.com ([137.136.239.220]) with mapi id 15.00.1320.000; Tue, 5 Sep 2017 14:45:53 -0700
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Leonard Giuliano <lenny@juniper.net>
CC: "mboned@ietf.org" <mboned@ietf.org>
Thread-Topic: [MBONED] deprecating MSDP
Thread-Index: AQHTJozipkEF2OqzLEmcLnTedbG68KKmzvzA
Date: Tue, 5 Sep 2017 21:45:53 +0000
Message-ID: <f911d57bf77245b8b074d3c557ab28f2@XCH15-06-11.nw.nos.boeing.com>
References: <20170725221330.GA4821@cs-it-6805697.local> <alpine.DEB.2.02.1707260908550.29724@svl-jtac-lnx02> <20170904141235.GC3194@faui40p.informatik.uni-erlangen.de> <alpine.DEB.2.02.1709051358300.14937@svl-jtac-lnx02.juniper.net>
In-Reply-To: <alpine.DEB.2.02.1709051358300.14937@svl-jtac-lnx02.juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/1Kj5f5iscMA0x8slgNpA1Sd5374>
Subject: Re: [MBONED] deprecating MSDP
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Sep 2017 21:46:08 -0000

-----Original Message-----
From: MBONED [mailto:mboned-bounces@ietf.org] On Behalf Of Leonard Giuliano

> Tweaking RFC4610 to match the microscopic (and generally irrelevant)
> benefits MSDP might have will just create yet another overly complex
> mcast protocol to address the corner cases of a handful of ill-conceived
> network deployments.  And have the same result- no one deploys it bc of
> all this unnecessary complexity.

+1.

There should be, and apparently there is, no need for a special-purpose, mu=
lticast-only, source discovery mechanism.

I'm not as hard over as many others seem to be, on "SSM only." Because as m=
ulticast is actually implemented, usefully implemented, it is in individual=
 networks, such as enterprise networks or internal platform networks, in wh=
ich ASM is often the best choice. For instance, when one needs redundancy o=
f sources.

I should also point out that multicast is seen, by the security establishme=
nt, as a potential security threat. Therefore, inter-domain multicast is no=
t encouraged. Quite the contrary, it is blocked be default. I'm also inform=
ed, second hand I'll admit, that ISPs and CDNs do not much favor multicast,=
 for their own technical and economic reasons. I suppose one reason might b=
e the proliferation of streaming media protocols these days, specific to di=
fferent devices, which defeats the purpose of multicast.

Maybe multicast will remain a niche solution, very useful where it's requir=
ed, but also deliberately limited in scope. Which is okay, in my book.

Bert



From nobody Tue Sep  5 23:33:54 2017
Return-Path: <swmike@swm.pp.se>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B60A6132A1A for <mboned@ietfa.amsl.com>; Tue,  5 Sep 2017 23:33:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level: 
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 RUCXprF_uKWc for <mboned@ietfa.amsl.com>; Tue,  5 Sep 2017 23:33:50 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B461C126E7A for <mboned@ietf.org>; Tue,  5 Sep 2017 23:33:50 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 6014CB1; Wed,  6 Sep 2017 08:33:48 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1504679628; bh=V9bW84x2P99IeAeLSGBRkgAvWHaemN9Q1z+O7oTnglE=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=WDluP0Yd/vEDE8eyVEV/+tr8jRxquLRGptcRb6HmjINDEQqiMHhsZKhd3FBgRp0F8 CZMoXaezNmvL4A2yV6wUA9kA3tBaEQbPtNve9TlGLMtbNZtp02Uqm6jkAY89IkocNK tJGRtaciUG3bqgRpD6aUIlsFbPMBpZ2Og8ytV36M=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 48A21AF; Wed,  6 Sep 2017 08:33:48 +0200 (CEST)
Date: Wed, 6 Sep 2017 08:33:48 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
cc: "mboned@ietf.org" <mboned@ietf.org>
In-Reply-To: <f911d57bf77245b8b074d3c557ab28f2@XCH15-06-11.nw.nos.boeing.com>
Message-ID: <alpine.DEB.2.20.1709060825330.29378@uplift.swm.pp.se>
References: <20170725221330.GA4821@cs-it-6805697.local> <alpine.DEB.2.02.1707260908550.29724@svl-jtac-lnx02> <20170904141235.GC3194@faui40p.informatik.uni-erlangen.de> <alpine.DEB.2.02.1709051358300.14937@svl-jtac-lnx02.juniper.net> <f911d57bf77245b8b074d3c557ab28f2@XCH15-06-11.nw.nos.boeing.com>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/sV72fsg3xXXKhrebf3jey4CSsmI>
Subject: Re: [MBONED] deprecating MSDP
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Sep 2017 06:33:53 -0000

On Tue, 5 Sep 2017, Manfredi, Albert E wrote:

> default. I'm also informed, second hand I'll admit, that ISPs and CDNs 
> do not much favor multicast, for their own technical and economic 
> reasons. I suppose one reason might be the proliferation of streaming 
> media protocols these days, specific to different devices, which defeats 
> the purpose of multicast.

There are lots of benefits to using multicast, it's just that there are 
also drawbacks. You can run an imperfect network (0.1% packet loss) any 
few will notice as long you run unicast. As soon as you introduce 
multicast, most applications that an ISP might be interested in (generally 
linear TV), now all of a sudden you need a network that has 1 in million 
packet loss, you run into gnarly fault finding cases, you need network 
verification tools to make sure you're assuring quality over time, etc.

Running a unicast-only network is quite forgiving, running multicast for 
what people typically use multicast for in an ISP network, is a lot less 
forgiving. Upside is typically small, unless you're providing TV for a 
profit (I don't know of any other typical residential ISP revenue stream 
for multicast), it's just not worth it.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Wed Sep  6 03:00:47 2017
Return-Path: <farinacci@gmail.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2689A1320D9 for <mboned@ietfa.amsl.com>; Wed,  6 Sep 2017 03:00:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 fWFgJ2Q6m71e for <mboned@ietfa.amsl.com>; Wed,  6 Sep 2017 03:00:40 -0700 (PDT)
Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (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 D41531270AB for <mboned@ietf.org>; Wed,  6 Sep 2017 03:00:39 -0700 (PDT)
Received: by mail-wm0-x22f.google.com with SMTP id f199so7464415wme.0 for <mboned@ietf.org>; Wed, 06 Sep 2017 03:00:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=heY1sr1uf/Hds2pJnyHVyyBbQ8zDR8DAnsTNQG94+NM=; b=BHIgFCUOPQdLE6Pnq9GZoJEoolUxJ+v12CZAvXb4MikMz1Hp4sizEcVvtNEzylEGNR ebftjLN1ol2pmH4CDJxl97iTgMKskYGYb0Yf4cWiV2INevTUjt5zMC4wUlACnenNziFt kHf1IGnfyHh8/t5Los+S4JyuG3kWu3AFcK2zgqQmq3rFnMA8Jiov4mpsVWfwd59bSERQ 7zVEUlAiwFAudrgizT2/BizPLdFaTVxeAilf/mBxwcoa0JWseSWqpJMRtWV1Zr/d24Mo T0E2BzIsps1ZGEThVlJBqVqhfLI/uizlIlI43dLcA6iUqFLN8KP5LSbmKnD9YuAYZuGx mQug==
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=heY1sr1uf/Hds2pJnyHVyyBbQ8zDR8DAnsTNQG94+NM=; b=oESRtvmsIoiJ4au4wrv1fU56Tw0Z4elgG8rxnp2uTGWTZ6JnZzLgOhns6hEyueDK06 epe/bOHXwuKd8LHgPSIgtZ/J3RPQ0L/rYqEphthBw5iXxhHxoO7RmtRJnvLbga5uvM6z wBv2/qN4qZZ26M6S4j6ww3TaMSzIZSfAw+zZU9+62MThnHEZ5NdL1ddI/kRvV+1IJout m1ciU8hjTZBpt0VWfcMNAZdNiinYwyQxX9rUuAToTn0ijLaSH6/DZOa3HldFZDJLRAw9 ckuyd1Jae4l70XoWc9d7wkgjVvCt7DzsvnQeJB+q+uUib8VxeDoR41q25g6w7Jkrcn3A KrJg==
X-Gm-Message-State: AHPjjUi9mLcDG/Ijdt7dY89TsaNFdkP+125oZJnQE9Ox7p7RUuRZQhR7 Zu68khAgdhsAJA==
X-Google-Smtp-Source: ADKCNb4M+s7/Y+8+4/R06EIUkH4FzoqW4Mzh4mhqgpmXNDz+pfHwh1q78+LjLi1/FbDG0PLyxKbwzg==
X-Received: by 10.28.71.135 with SMTP id m7mr1538826wmi.84.1504692038296; Wed, 06 Sep 2017 03:00:38 -0700 (PDT)
Received: from [10.173.22.65] ([92.43.229.90]) by smtp.gmail.com with ESMTPSA id 4sm2758448wrl.60.2017.09.06.03.00.19 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 06 Sep 2017 03:00:24 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <alpine.DEB.2.20.1709060825330.29378@uplift.swm.pp.se>
Date: Wed, 6 Sep 2017 03:00:28 -0700
Cc: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>, "mboned@ietf.org" <mboned@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <73CE4541-4C76-4EF2-B806-041DE8C72A66@gmail.com>
References: <20170725221330.GA4821@cs-it-6805697.local> <alpine.DEB.2.02.1707260908550.29724@svl-jtac-lnx02> <20170904141235.GC3194@faui40p.informatik.uni-erlangen.de> <alpine.DEB.2.02.1709051358300.14937@svl-jtac-lnx02.juniper.net> <f911d57bf77245b8b074d3c557ab28f2@XCH15-06-11.nw.nos.boeing.com> <alpine.DEB.2.20.1709060825330.29378@uplift.swm.pp.se>
To: Mikael Abrahamsson <swmike@swm.pp.se>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/0QlXTSIgQB9nXm96wKT1np1RGag>
Subject: Re: [MBONED] deprecating MSDP
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Sep 2017 10:00:46 -0000

> Running a unicast-only network is quite forgiving, running multicast =
for what people typically use multicast for in an ISP network, is a lot =
less forgiving. Upside is typically small, unless you're providing TV =
for a profit (I don't know of any other typical residential ISP revenue =
stream for multicast), it's just not worth it.

This is why running multicast over a unicast-only overlay has the best =
of both worlds and reduces the cost of running multicast because you =
only have to debug the very edges of the network. And the closer you put =
the encap/decap points to sources and receivers reduces further the =
debug surface.

Dino


From nobody Thu Sep  7 05:58:45 2017
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2AE3413292D for <mboned@ietfa.amsl.com>; Thu,  7 Sep 2017 05:58:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level: 
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 RdKyGZuh4gEE for <mboned@ietfa.amsl.com>; Thu,  7 Sep 2017 05:58:33 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8129713202D for <mboned@ietf.org>; Thu,  7 Sep 2017 05:58:33 -0700 (PDT)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 2650258C4B8; Thu,  7 Sep 2017 14:58:25 +0200 (CEST)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id 0ACF2B0CB05; Thu,  7 Sep 2017 14:58:24 +0200 (CEST)
Date: Thu, 7 Sep 2017 14:58:24 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Leonard Giuliano <lenny@juniper.net>
Cc: "Dale W. Carder" <dwcarder@es.net>, mboned@ietf.org
Message-ID: <20170907125824.GA23219@faui40p.informatik.uni-erlangen.de>
References: <20170725221330.GA4821@cs-it-6805697.local> <alpine.DEB.2.02.1707260908550.29724@svl-jtac-lnx02> <20170904141235.GC3194@faui40p.informatik.uni-erlangen.de> <alpine.DEB.2.02.1709051358300.14937@svl-jtac-lnx02.juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.DEB.2.02.1709051358300.14937@svl-jtac-lnx02.juniper.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/9CHthPpA2T8RpkNkVmaCF8eQisw>
Subject: Re: [MBONED] deprecating MSDP
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Sep 2017 12:58:37 -0000

On Tue, Sep 05, 2017 at 02:20:50PM -0700, Leonard Giuliano wrote:
> IMO, closing the gap between RFC4610 and MSDP would be a step in the wrong 
> direction.  Reinventing MSDP and calling it another name will solve 
> nothing.  "A source discovery protocol by any other name would smell as 
> sweet..."  If someone really wants to run Anycast RP in v6 within his 
> domain, RFC4610 should be good enough.

My argument is that RFC4610 alone is not good enough for a business
criticial deployment of ASM because it misses all the necessary specs
for reliability , hardening and troubleshooting.

> Again, the problem isn't MSDP, the problem is ASM.  Tweaking RFC4610 to 
> match the microscopic (and generally irrelevant) benefits MSDP might have 
> will just create yet another overly complex mcast protocol to address the 
> corner cases of a handful of ill-conceived network deployments.  And have 
> the same result- no one deploys it bc of all this unnecessary complexity.

Nothing what i proposed is IMHO specific to RFC4610 or MSDP. It's instead
what you'd need to have for any network layer protocol of similar
complexity to make it reliable, hardened and troubleshootable. Most
of these operational aspects have in the part left to vendors proprietary
approaches and IMHO thats been one of the biggest issues of success
of more complex solutions in networks.

Wrt to ASM being the problem: Imagine we only do SSM in the network,
and a distributed application layer solution would do source discovery.
Guess how that would be built. Definitely a lot easier troubleshotable
than RFC4610. Much more like what i am suggesting. Definitely on top of
TCP or better and not UDP. 

> If the goal is to change course and get folks to deploy mcast, we should 
> make things unambiguously simple- use SSM in the network layer and let the 
> some other layer handle source discovery.

Sure. ALl i am saying is that ASM without MSDP and with just RFC4610
is less operationally complete. I am not arguing right now how important
it would be to fix that, i would just resist documents stating that
ASM intradomain with just RFC4610 is in good shape.

Cheers
    Toerless

> On Mon, 4 Sep 2017, Toerless Eckert wrote:
> 
> | 
> | Depending to some degree to the vendor implementation,
> | I was suggesting to use MSDP for anycast-RP over RFC4610 because it
> | had evolved a lot earlier and has a lot more bells and whistles that are
> | IMHO highly relevant for business criticial anycast PIM-SM deployments.
> | 
> | Alas of course, MSDP is only IPv4, and we should have something equally
> | good for IPv6 as MSDP has been for IPv4 - for anycast-RP. 
> | 
> | So, IMHO, we should close the gaps of RFC4610 over MSDP: Give
> | it the option to use TCP (arguably in line with PORT), have a
> | config/ops model equivalent to the MSDP MIB (subest required for
> | anycast-RP), and IMHO introduce the equivalent to the MSDP cache
> | for troubleshooting and per-neighbor state limiters and total state
> | limiters.
> | 
> | IMHO thats whats needed to deprecate MSDP completely. Shorter term
> | we can of course have some deployment guide that calls MSDP deprecated,
> | but not change the doc status to historic/deprecated.
> | 
> | Toerless
> | 
> | On Wed, Jul 26, 2017 at 09:43:37AM -0700, Leonard Giuliano wrote:
> | > Dale, 
> | > 
> | > Great questions and thanks for bringing up, as we'd love feedback from the 
> | > I2 community- it's probably the largest user of interdomain MSDP and 
> | > the centerpiece of this conversation.
> | > 
> | > draft-ietf-mboned-interdomainpeering-bcp is scoped to just focus on SSM.  
> | > The plan is for draft-acg-mboned-multicast-models to pick up from there 
> | > and make the strong recommendation to use SSM, not ASM, for interdomain 
> | > mcast deployment.  I am not sure about moving MSDP to historic and what 
> | > that would practically mean, but in IMO, MSDP is somewhat of a scapegoat 
> | > here.  The real culprit is ASM (or rather, network-based source 
> | > discovery); MSDP is merely driving the getaway vehicle, albeit with a 
> | > reckless and dangerous driving style.  Eliminate network-based source 
> | > discovery for interdomain mcast and the vast majority of the complexity 
> | > and problems of mcast go away (RPs, PIM registers, RPTs, SPT switchover, 
> | > MSDP, data-driven state creation, etc).
> | > 
> | > We are scoping this to *interdomain*, as it has been mentioned that within 
> | > a domain there might be reasonable uses for ASM.  And for that matter, 
> | > what you do in your own house is your business, but once you leave your 
> | > home and interact with your neighbors and share the roads with other 
> | > drivers, more stringent rules and guidelines are appropriate for the sake 
> | > of safety and order.  So we are not saying anything about MSDP for 
> | > *intradomain* use (for now).  Aside: there is of course RFC4610, but 
> | > Anycast PIM is pretty much identical to internal MSDP- same behavior by a 
> | > different name.
> | > 
> | > So recommending SSM (and not ASM) for interdomain has overwhelming 
> | > support, and is basically a no-brainer from a network perspective.  But 
> | > the big open question is if it's feasible/meaningful given the state of 
> | > apps today? That is, for those users of interdomain mcast on I2, are the 
> | > apps they use SSM aware?  Is there a good way to find this out from the I2 
> | > community?
> | > 
> | > -Lenny
> | > 
> | > On Tue, 25 Jul 2017, Dale W. Carder wrote:
> | > 
> | > | 
> | > | As was noted in the minutes, there is perhaps a significant set of the
> | > | multicast community (including ourselves) seriously considering 
> | > | turning off inter-domain MSDP for good.
> | > | 
> | > | Related, I am curious what are the barriers to moving MSDP to historic 
> | > | status?  In RFC4611, that document differentiates intra-domain vs 
> | > | inter-domain MSDP.  For that matter, it does a pretty good job at
> | > | explaining the state of MSDP, but doesn't necessarily reflect what to 
> | > | do in deployments today.  
> | > | 
> | > | That seems to me to be different than where draft-acg-mboned-multicast-models
> | > | is headed?  
> | > | 
> | > | draft-ietf-mboned-interdomainpeering-bcp clearly is not advocating for
> | > | more inter-domain MSDP.
> | > | 
> | > | Dale
> | > | 
> | > | _______________________________________________
> | > | MBONED mailing list
> | > | MBONED@ietf.org
> | > | https://www.ietf.org/mailman/listinfo/mboned
> | > | 
> | > 
> | > _______________________________________________
> | > MBONED mailing list
> | > MBONED@ietf.org
> | > https://www.ietf.org/mailman/listinfo/mboned
> | 
> | -- 
> | ---
> | tte@cs.fau.de
> | 

-- 
---
tte@cs.fau.de


From nobody Thu Sep  7 06:45:16 2017
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DB8B132F01 for <mboned@ietfa.amsl.com>; Thu,  7 Sep 2017 06:45:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level: 
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 kirtZrUBXEXX for <mboned@ietfa.amsl.com>; Thu,  7 Sep 2017 06:45:13 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC8C4132F02 for <mboned@ietf.org>; Thu,  7 Sep 2017 06:45:12 -0700 (PDT)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 6215158C4B8; Thu,  7 Sep 2017 15:45:00 +0200 (CEST)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id D2E7BB0CB06; Thu,  7 Sep 2017 15:45:00 +0200 (CEST)
Date: Thu, 7 Sep 2017 15:45:00 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>, "mboned@ietf.org" <mboned@ietf.org>
Message-ID: <20170907134500.GB23219@faui40p.informatik.uni-erlangen.de>
References: <20170725221330.GA4821@cs-it-6805697.local> <alpine.DEB.2.02.1707260908550.29724@svl-jtac-lnx02> <20170904141235.GC3194@faui40p.informatik.uni-erlangen.de> <alpine.DEB.2.02.1709051358300.14937@svl-jtac-lnx02.juniper.net> <f911d57bf77245b8b074d3c557ab28f2@XCH15-06-11.nw.nos.boeing.com> <alpine.DEB.2.20.1709060825330.29378@uplift.swm.pp.se>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.DEB.2.20.1709060825330.29378@uplift.swm.pp.se>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/qlxbDQp12BTACVTdIBzpQcCDLEw>
Subject: Re: [MBONED] deprecating MSDP
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Sep 2017 13:45:14 -0000

Great uplevel, Mikael

IMHO its still worthwhile to brainstorm what an initial IP multicast service
"across the internet" would need to have any change to be adopted/used,
even if only to understand that the problem is not just solved by
"Just use SSM".

here's my best theory what could work:

Get an initial SSM service deployed into Tier 1 SP, available to 10++
million subs:

  - Avoids initial considerations for interdomain transit
  - Creates criticial mass to encourage app developers to support it.

Apps "just" need to support SSM API and congestion control aka RFC8085.
Eg: fountain/network codecs. SSM is easy, the rate adaption is quite advanced.

Operators can not trust that apps perform complint to RFC8085. Most
easily, initial SSM multicast would be in a scavenger class. Makes
all bandwidth used by it free for the SP. Hopefully good enough to make
marketing folks in SPs interested.

(S,G) state in network need to be controlled. On receiver edge,
receivers must only be permitted to join to few # of active (S,G) state.
Else networks can be killed with receiver (S,G) state. This ultimately is
introducing a requirement for some active (S,G) awareness into receiver
edge devices.

Senders should be be a chargeable service option. IMHO charging
for senders hould be handled like SMS was handled in Germany in the
90'th: Make it virtually free first and raise the bar once the junkies,
oops: subscribers can not live without it. Might want to charge some
entrance fee even day 1 to get only senders that have a real business
inererst and large number of receivers (instead of a repetition of
"cameras all over the world").

Cheers
    Toerless

On Wed, Sep 06, 2017 at 08:33:48AM +0200, Mikael Abrahamsson wrote:
> On Tue, 5 Sep 2017, Manfredi, Albert E wrote:
> 
> >default. I'm also informed, second hand I'll admit, that ISPs and
> >CDNs do not much favor multicast, for their own technical and
> >economic reasons. I suppose one reason might be the proliferation
> >of streaming media protocols these days, specific to different
> >devices, which defeats the purpose of multicast.
> 
> There are lots of benefits to using multicast, it's just that there
> are also drawbacks. You can run an imperfect network (0.1% packet
> loss) any few will notice as long you run unicast. As soon as you
> introduce multicast, most applications that an ISP might be
> interested in (generally linear TV), now all of a sudden you need a
> network that has 1 in million packet loss, you run into gnarly fault
> finding cases, you need network verification tools to make sure
> you're assuring quality over time, etc.
> 
> Running a unicast-only network is quite forgiving, running multicast
> for what people typically use multicast for in an ISP network, is a
> lot less forgiving. Upside is typically small, unless you're
> providing TV for a profit (I don't know of any other typical
> residential ISP revenue stream for multicast), it's just not worth
> it.
> 
> -- 
> Mikael Abrahamsson    email: swmike@swm.pp.se
> 
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned

-- 
---
tte@cs.fau.de


From nobody Thu Sep  7 07:00:20 2017
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C94A132F02 for <mboned@ietfa.amsl.com>; Thu,  7 Sep 2017 07:00:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level: 
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 86gwK9KDnpDf for <mboned@ietfa.amsl.com>; Thu,  7 Sep 2017 07:00:16 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B645132EF8 for <mboned@ietf.org>; Thu,  7 Sep 2017 07:00:16 -0700 (PDT)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 6723E58C4FF; Thu,  7 Sep 2017 16:00:01 +0200 (CEST)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id 4DD23B0CB06; Thu,  7 Sep 2017 16:00:01 +0200 (CEST)
Date: Thu, 7 Sep 2017 16:00:01 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Dino Farinacci <farinacci@gmail.com>
Cc: Mikael Abrahamsson <swmike@swm.pp.se>, "mboned@ietf.org" <mboned@ietf.org>
Message-ID: <20170907140000.GC23219@faui40p.informatik.uni-erlangen.de>
References: <20170725221330.GA4821@cs-it-6805697.local> <alpine.DEB.2.02.1707260908550.29724@svl-jtac-lnx02> <20170904141235.GC3194@faui40p.informatik.uni-erlangen.de> <alpine.DEB.2.02.1709051358300.14937@svl-jtac-lnx02.juniper.net> <f911d57bf77245b8b074d3c557ab28f2@XCH15-06-11.nw.nos.boeing.com> <alpine.DEB.2.20.1709060825330.29378@uplift.swm.pp.se> <73CE4541-4C76-4EF2-B806-041DE8C72A66@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <73CE4541-4C76-4EF2-B806-041DE8C72A66@gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/EBUwLO6ngWFW56Xcj6-3fELsPwE>
Subject: Re: [MBONED] deprecating MSDP
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Sep 2017 14:00:18 -0000

On Wed, Sep 06, 2017 at 03:00:28AM -0700, Dino Farinacci wrote:
> > Running a unicast-only network is quite forgiving, running multicast for what people typically use multicast for in an ISP network, is a lot less forgiving. Upside is typically small, unless you're providing TV for a profit (I don't know of any other typical residential ISP revenue stream for multicast), it's just not worth it.

> This is why running multicast over a unicast-only overlay has the best of both worlds and reduces the cost of running multicast because you only have to debug the very edges of the network. And the closer you put the encap/decap points to sources and receivers reduces further the debug surface.

God point. Reducing the number of points in the network where you have to
deal with multicast replication state is a good thing. I don't think we have
a good complete BCP for how to best manae multicast state in SP networks. See
my prior email about amount of SSM sender and receiver state as well. 

Note though, that this is orthogonal to what Mikael mentioned. Current
IPTV style apps without any transport reliability (FEC, fountain codecs,
etc. pp) will also fail miserably when they are tunneled across unicast.
The only place where unicast tunneling magically solves the reliabilty issues
is on WiFi ;-)

Btw: just seeing that no document claims to be updating RFC3170. Does that not say everything about the state of IP multicast apps ? ;-))

Cheers
    Toerless

> Dino
> 
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned

-- 
---
tte@cs.fau.de


From nobody Thu Sep  7 07:09:19 2017
Return-Path: <swmike@swm.pp.se>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3387C132F13 for <mboned@ietfa.amsl.com>; Thu,  7 Sep 2017 07:09:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level: 
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 nTdA11Z2VLvB for <mboned@ietfa.amsl.com>; Thu,  7 Sep 2017 07:09:16 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 21866132F12 for <mboned@ietf.org>; Thu,  7 Sep 2017 07:09:16 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 67481B1; Thu,  7 Sep 2017 16:09:13 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1504793353; bh=vWeE3KTvbCq6j2OpNS1dPOW2JFBlWS3axsazmWDOBrc=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=NGC/Q9aC94zBeinh5SMJJVNM6vEMUp57ycHdHp6v1qfAOqyrDTkolVefKHQG9HkkZ Nb17huYJzr5zpm3Hh8qyVJGJdivhq0rnR+u1p+L9Dh0Ok3SvWEmuoszSDRQXC33Z0s qgQ//pf1fGB1yoPC7f/AuZ/bVmuDzI0YAMoXcg8w=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 6450CAF; Thu,  7 Sep 2017 16:09:13 +0200 (CEST)
Date: Thu, 7 Sep 2017 16:09:13 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Toerless Eckert <tte@cs.fau.de>
cc: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>,  "mboned@ietf.org" <mboned@ietf.org>
In-Reply-To: <20170907134500.GB23219@faui40p.informatik.uni-erlangen.de>
Message-ID: <alpine.DEB.2.20.1709071602420.29378@uplift.swm.pp.se>
References: <20170725221330.GA4821@cs-it-6805697.local> <alpine.DEB.2.02.1707260908550.29724@svl-jtac-lnx02> <20170904141235.GC3194@faui40p.informatik.uni-erlangen.de> <alpine.DEB.2.02.1709051358300.14937@svl-jtac-lnx02.juniper.net> <f911d57bf77245b8b074d3c557ab28f2@XCH15-06-11.nw.nos.boeing.com> <alpine.DEB.2.20.1709060825330.29378@uplift.swm.pp.se> <20170907134500.GB23219@faui40p.informatik.uni-erlangen.de>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/l3YhZ5j59ByIh_qU7QGFHw2ZfDg>
Subject: Re: [MBONED] deprecating MSDP
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Sep 2017 14:09:18 -0000

On Thu, 7 Sep 2017, Toerless Eckert wrote:

> IMHO its still worthwhile to brainstorm what an initial IP multicast 
> service "across the internet" would need to have any change to be 
> adopted/used, even if only to understand that the problem is not just 
> solved by "Just use SSM".

Indeed not solved by "just use SSM". It is still my firm opinion that 
there will be no "IP multicast service across the Internet" unless someone 
comes up with serious money and throws it ISPs way to enable this. And I 
am talking about ALL the ISPs which carry this, not just one. I don't see 
this happening anytime soon.

> Get an initial SSM service deployed into Tier 1 SP, available to 10++
> million subs:
>
>  - Avoids initial considerations for interdomain transit
>  - Creates criticial mass to encourage app developers to support it.
>
> Apps "just" need to support SSM API and congestion control aka RFC8085.
> Eg: fountain/network codecs. SSM is easy, the rate adaption is quite advanced.
>
> Operators can not trust that apps perform complint to RFC8085. Most
> easily, initial SSM multicast would be in a scavenger class. Makes
> all bandwidth used by it free for the SP. Hopefully good enough to make
> marketing folks in SPs interested.

There are a lot of complications beneath this "highish level" overview.

> Senders should be be a chargeable service option. IMHO charging for 
> senders hould be handled like SMS was handled in Germany in the 90'th: 
> Make it virtually free first and raise the bar once the junkies, oops: 
> subscribers can not live without it. Might want to charge some entrance 
> fee even day 1 to get only senders that have a real business inererst 
> and large number of receivers (instead of a repetition of "cameras all 
> over the world").

I attended a one-day conference around 2002 or something, that had a talk 
about "multicast business models" and money flows etc. A lot of problems 
were outlined. These are still true today.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Thu Sep  7 11:33:47 2017
Return-Path: <lenny@juniper.net>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00514132D40 for <mboned@ietfa.amsl.com>; Thu,  7 Sep 2017 11:33:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.011
X-Spam-Level: 
X-Spam-Status: No, score=-3.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H5=-1, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=juniper.net
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 FCAnlAPwuV1U for <mboned@ietfa.amsl.com>; Thu,  7 Sep 2017 11:33:44 -0700 (PDT)
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (mail-cys01nam02on0124.outbound.protection.outlook.com [104.47.37.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 115B1132F9D for <mboned@ietf.org>; Thu,  7 Sep 2017 11:33:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=LxSKzyZJiRguw9bHuG0FRBOmvrhywIZwoc0Kh5yfKs8=; b=dqF07GpursdqAmnmsmse3I+POcN6ElJgXo3GWoWcDwR17d5jliAIki4TUCYC46mYUEp9UD4dR6MoYLvHGjEueLUOpxGmUAaDDpvuKgych19WQKRPcUWOQKwflS5Hocgd11EzGzB1CfHNIjGIlRpdBvya5H7e68up0jXoVmXpiRk=
Received: from DM5PR05CA0013.namprd05.prod.outlook.com (10.173.226.23) by DM5PR05MB3529.namprd05.prod.outlook.com (10.174.242.146) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.56.4; Thu, 7 Sep 2017 18:33:42 +0000
Received: from DM3NAM05FT042.eop-nam05.prod.protection.outlook.com (2a01:111:f400:7e51::206) by DM5PR05CA0013.outlook.office365.com (2603:10b6:3:d4::23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.56.4 via Frontend Transport; Thu, 7 Sep 2017 18:33:42 +0000
Received-SPF: SoftFail (protection.outlook.com: domain of transitioning juniper.net discourages use of 66.129.239.15 as permitted sender)
Received: from P-EMFE01C-SAC.jnpr.net (66.129.239.15) by DM3NAM05FT042.mail.protection.outlook.com (10.152.98.156) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P256) id 15.1.1385.11 via Frontend Transport; Thu, 7 Sep 2017 18:33:42 +0000
Received: from svl-jtac-lnx06.juniper.net (172.17.28.215) by P-EMFE01C-SAC.jnpr.net (172.24.192.21) with Microsoft SMTP Server id 14.3.123.3; Thu, 7 Sep 2017 11:33:41 -0700
Received: by svl-jtac-lnx06.juniper.net (Postfix, from userid 1709)	id 4C2B39F6F0; Thu,  7 Sep 2017 11:33:41 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])	by svl-jtac-lnx06.juniper.net (Postfix) with ESMTP id 484CE9F6EF; Thu,  7 Sep 2017 11:33:41 -0700 (PDT)
Date: Thu, 7 Sep 2017 11:33:40 -0700
From: Leonard Giuliano <lenny@juniper.net>
To: Mikael Abrahamsson <swmike@swm.pp.se>
CC: Toerless Eckert <tte@cs.fau.de>, "mboned@ietf.org" <mboned@ietf.org>
In-Reply-To: <alpine.DEB.2.20.1709071602420.29378@uplift.swm.pp.se>
Message-ID: <alpine.DEB.2.02.1709071111270.19087@svl-jtac-lnx02.juniper.net>
References: <20170725221330.GA4821@cs-it-6805697.local> <alpine.DEB.2.02.1707260908550.29724@svl-jtac-lnx02> <20170904141235.GC3194@faui40p.informatik.uni-erlangen.de> <alpine.DEB.2.02.1709051358300.14937@svl-jtac-lnx02.juniper.net> <f911d57bf77245b8b074d3c557ab28f2@XCH15-06-11.nw.nos.boeing.com> <alpine.DEB.2.20.1709060825330.29378@uplift.swm.pp.se> <20170907134500.GB23219@faui40p.informatik.uni-erlangen.de> <alpine.DEB.2.20.1709071602420.29378@uplift.swm.pp.se>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
X-EOPAttributedMessage: 0
X-MS-Office365-Filtering-HT: Tenant
X-Forefront-Antispam-Report: CIP:66.129.239.15; IPV:NLI; CTRY:US; EFV:NLI; SFV:NSPM; SFS:(10019020)(6009001)(39860400002)(2980300002)(189002)(199003)(52314003)(305945005)(189998001)(93886005)(105596002)(5005980100005)(4001350100001)(356003)(5660300001)(106466001)(50466002)(90966002)(46406003)(110136004)(83506001)(4326008)(86362001)(8676002)(229853002)(47776003)(2810700001)(478600001)(2906002)(54356999)(46386002)(23726003)(50986999)(8936002)(2950100002)(81156014)(69596002)(54906002)(45336002)(81166006)(6916009)(76176999)(76506005)(7126002)(6246003)(68736007)(3240700002)(53936002)(77096006)(97736004)(57986006)(6266002)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:DM5PR05MB3529; H:P-EMFE01C-SAC.jnpr.net; FPR:;  SPF:SoftFail; PTR:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-Microsoft-Exchange-Diagnostics: 1; DM3NAM05FT042; 1:lMh/aa7fDprOm0V4yFAv52Xm8iffX/E6CXF1q/JCeFGKImyp+WzUOZPMvnjwPkfl3vNS49xFReoY1Z5Zga+ZO1koBk54qm8aXFmhabD/Vz3t+6vvHuQAFEtnp6xdH9yn
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 8ad7f949-1870-4a2b-d9ce-08d4f61ef788
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(300000502095)(300135100095)(22001)(2017030254152)(300000503095)(300135400095)(2017052603199)(201703131423075)(201703031133081)(201702281549075)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:DM5PR05MB3529; 
X-Microsoft-Exchange-Diagnostics: 1; DM5PR05MB3529; 3:Ii1ENJPBfvINu9/v+2TQQqK+8FbuT3dTuRMmursmYpuOj6l23DQD5kfFkmYtRYxks/5fFZjOnKX/AmYQm8F1xOuMOsTNvAzAgwMzwlY3ZkPk7e0eTK5oXrE1w6dbiygeZ0BQvE+vxAY8368brqr1jCZTqRcAp1wpyuse9p1GXNs6nAcET36bW4SiZODCDpTJjUOWc0B8Ewvl8Bp/O23peYX1G3X3UemzSGg1YjYs/OB3oK5nE6U+s+Q0sIlQVW/yAd1MS3k7mlkFy7PkuPmSpeWMLVcNuchc1lcEavvTA2pVI6XixMUVkfj2ydjXSOoa/LJXwkTuw9yIbnuiycXUQY1X5TQMa9zcp1xLgoKwASg=; 25:7DMdC1+TVa2QQd3/zhKOhJecOSk/lqPKsVhzbzxZxc5AXU7Ykx5/UWMk9ekGBs/0RAQS+29vuyV6p98MfxPOTcnSSTY2eLUaHZKC3asqCxYEdiWgxa5ubo38ddY1TnfAz8UsQAm5yWcqx+HpC63IvnhIm85/BjA8hn71ZXcRa+0cTBzg+IfwizeW56liF/iCFtO0eDqDqid/r1GLhtqFVFvW6+FYu9lXrfBwpnUAbzjgfaK9hF26BylzGHZaozkYfJ0IFgGojmf3Gwbn3i3Ie0xOaDVrxnMSRdHmeqT+o0/LZjtSPZ9O6XEIclO2Cxe7BPQ6zWRu6s68MGwquQ7fxg==
X-MS-TrafficTypeDiagnostic: DM5PR05MB3529:
X-Microsoft-Exchange-Diagnostics: 1; DM5PR05MB3529; 31:M3ShFgY3FDWer/4wLFsLXXwm2Tw/1PIt29Bjr4G7gAGVfZRMU/lNoMKfiSojVgpMg3NDatSQBYiv8oQrC3w1M3zRKD4QLlH4OWtRPCVAfMp6XGiwr+ttuQ2k8zhrPqjoKN+zDlTxJB2cskmdz2Qb+1NSt9B1XmbD/0iHLbrgoFJDzDjmhkUs8MVbdJUn0DsQpI92UifbodZT8EfaeQEvpipIjY9tP1tp0n2WurGfL/k=; 20:jQsueF7JNZVBrlyvk0OIjJ25c6uJ4XbfJQkF8JoUJ23qy0i5oy/HTnXhhx2sd7o6eAjfOz/KbsTICwX87k1bBp/cCLYLhP0Z4AkfrH51gmhaa2q5UO8Bu0lG1t9O1rxfzXaFviaSwbnquEz/+xYdgyncKYFPNCRKdJ9HXQGpte3Wgz6P+MtcxpIzqj8nAJidu4KgOLR8UmmNtEGCDsrmUStYU+0+B5w7ae4fGg7abQbU0WF/4rIPrerij9KgnXNxatJqEpHRoDSY8TwLmMGWbdUngviuwDOE4J607W6RcG4tf/4EHO5R0+iKJS+ZNpLVZyoGwN7uMMgLeI3d8ncuHAeTpfalXONVNPQ5QxRKVlEucslCwGXdUjKXbGfZ5LuBzSRegR/k+TfWFdWjvtcKyYEPFkhlfBKCrhB7SqPVNAOpOdxodZDuEPZ0c/dlT5dW/mMsbqSsaurYRrtyQjZkhE/xnB06i2Af8EW3ULXHOPAaEU84UAz2sJhv4hdMifhR
X-Exchange-Antispam-Report-Test: UriScan:(244540007438412);
X-Microsoft-Antispam-PRVS: <DM5PR05MB352913CF8856EE5757749CFDA4940@DM5PR05MB3529.namprd05.prod.outlook.com>
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(5005006)(8121501046)(100000703101)(100105400095)(93006095)(93001095)(3002001)(10201501046)(6055026)(6041248)(20161123562025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123558100)(20161123555025)(20161123560025)(20161123564025)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:DM5PR05MB3529; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:DM5PR05MB3529; 
X-Microsoft-Exchange-Diagnostics: 1; DM5PR05MB3529; 4:Yyg7zoMIkCSk1ihr2WjcZmD3GxlHYxnP8D4Vi3EHrfB+dUSNCoBBG1iUmVHHYqlCFK6/Or/BaKqd0P5+aVT4uImqcbGFL9dtiUbme8RljF6FfYJZZWV6opc3v2pxJI1RfsK8sdWsMFJe+91dc6peX4CRCQ4l4a/3sDPHu2mIBFdq1kw7YQ8YfTGe+pmtYBbwiE+Eguis7LsMnn7bsNDO+K1cXnsOJupq+6P5kZPOhixI8bfkgDeoexguUvjt+xyrAsJuJu3NSa/x9Kwo3lwtTqHja6BefnKCiZ7lK1wsIeE=
X-Forefront-PRVS: 04238CD941
X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; DM5PR05MB3529; 23:Drl9VhoyziM/v1RpRjuMiiVqrYnCO6qmhHYStwImS?= =?us-ascii?Q?sEYkqkGdlcFgxOWRs3tARW4M8VKcVIJ9mJkPAB5KO3/EZLl6gQEyYLzAbKDp?= =?us-ascii?Q?34XKItBvuf3a5svPiQo3BUyIydD2R/0Mhr0TwYu139hTAYJSLAtXfXxbYY7b?= =?us-ascii?Q?j1jMlc0h2D98E50QyZhd7iRJF+GqxOP+wCiUcB5s+WK9ztolZ16eNpHkTY2T?= =?us-ascii?Q?XqQL1QFxQfxSNOUzyNpyhZ4N1Hek+wuDzZu4qGL8sayGXEetGDrkLnQr1GEs?= =?us-ascii?Q?KxO+VnzsyZQvhMZPGAWQn62mGiSuN5b6ZpH3sZLlyBtyekTcHg9sbWw/AhU6?= =?us-ascii?Q?zbpYxOSb8DCK4wZDyon+uCSHoo6wfYJM9z8imhn2K9uSEnYlTt5lL39o8jC/?= =?us-ascii?Q?PgErrscYLbuWB03ZuEQDn+bkVMLt359RihmL9mwJeMaVA/en0tYk8o6cgYWw?= =?us-ascii?Q?eEj0dn0PYLzu0S81XC4aIrQZ+DrFdxj+5fn/dM4Sto8bxXBM/jPf7L1bsK+m?= =?us-ascii?Q?8pGk132iArnwoWUqaOC/+mPliqE89SyANHBP09RoRegUz/i9U8drLVF3XkOh?= =?us-ascii?Q?JKVeUNXT81XpvDcsctaooJJWiU4tNOZk0bz5iyYZhQv3wHpnH0St18Cjk7sg?= =?us-ascii?Q?pReaXweJOw3INoA9X47S1ej/+1fRaX9TV2WWmSCpOaj5qmPUNr/4fk7qenpL?= =?us-ascii?Q?HcsBMXu7htODqaZuzUzTvPTVv/eFPi2IErkKl1jPja9fYnDc4Z4i4pWwXJV6?= =?us-ascii?Q?BZVaDThBOA5RMz1cZSeHhMRIleyUkL8Rh1Xg5/ZdgQKUIFFfqvoCW3ujimPN?= =?us-ascii?Q?sqHmZZ6GxSmSlN45mnKz+oac9KCR48uqL8UCCd13m87VGZ+e5OL0Y8nppiCt?= =?us-ascii?Q?H6vsDzZjuVtiKoRXtlzReK34htFROGu+ydVmkekoOj/KJSlHahJ6da2djWpS?= =?us-ascii?Q?Dg1bnlQN9Tb+px8zydCeVdKr6OClfC5WR0t0S5+Ae/CZFBse+J58DnniuH7/?= =?us-ascii?Q?VYa3VvHgVC1QWWpwzWjoQ12kG3oquYQST4Y6unvKuplhRfUMBqCRWP8fIHmI?= =?us-ascii?Q?Xu/Q7G4D8B8rfb1jmzRLxgCnqA209Qt82zwR+RWa8auFgqV9le1lYVnL4O7l?= =?us-ascii?Q?Aw/bhQEKODBrJvDq3orF4d5AXw2/DVTPxXDHLwg0csmt3Q7HqOqKe2WEy6/8?= =?us-ascii?Q?BV594MrryYaYQYlL7DcAMOSRhc0kH5K3+zrJyOthpmk8UJN8muauyMtNNZ1U?= =?us-ascii?Q?+h20VCRD045QER4oFmh25jkJx9suZZ1UT0FD9YO?=
X-Microsoft-Exchange-Diagnostics: 1; DM5PR05MB3529; 6:t/PjyP1WYxgqn9t1x0UjYtzRkX0pWWvvKcSa9DD593I+IL9HkpuBG6ySaB1BIq7jSqiQJQb5TwJWZrePU2C9UlkfxgSdm2rL17SLlAJGhiTOA4DS49l6Y2wvU9TKh73F0tobXHhe1kDOak0A4+ZB9jG1o411h1mh853FmId7TJcjo0eYi+OAuCIwKvYvyMZXh5QEA5JOoIon3LOa1QUhS8eAZYJGF9AJgGNlpHfqfLAYCPWCDvyZSEypWmKmf3najzIrJD3EZotIsY55EL6paUiGd3rD73XDAZ7cY9Hww0df0+PNt2yTmdJKxerRtNX3ZHh7nWgmRw4Ch6Mb09sREQ==; 5:yTTWDCUfjVdr4RTwtfei+Mvtb9YzJQ5V/+APmHUGrz4YMWI3nShVgGNw6sM9DedgYULRgiNUjUWS0ZlOhnb7THyhd//5mFJv2HE0p/wNiQ+4tHzrFoWs1puwkWkMQXfFJsE9XVRi/RjZZBoCFB+eeg==; 24:HS7g7xL6tSN3gvc3ozpNNJoZElIoJZ4vsEFELFm+CDfL2eDVNPofJUB15sYD4NDA7yeNFJGG8OOwyb+vPXNRz4oL15B9J6jDpP7sXM645mk=; 7:g7z1bOxjG5aVpp6CTF+PjZntY/ozy2d8vamXf6ioVodAAMnnsgv7dDmQ2I8Ya8zRGJoSPg/TtHtOQ3x2utw883rh8boCvthH8/MigvvW2Nw6tWaHfUil7mVamKailLcwXbqTfE0qNKjR/VewVhwtfNcqbm92BCW2M5xEiPN7k0qA7RndTNO++PXQLSyMxlQMS90Z5Iw8Sr1rmRtsBzL8QHBqDIHDHqFUJq/jsA8BtCg=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 07 Sep 2017 18:33:42.5194 (UTC)
X-MS-Exchange-CrossTenant-Id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=bea78b3c-4cdb-4130-854a-1d193232e5f4; Ip=[66.129.239.15];  Helo=[P-EMFE01C-SAC.jnpr.net]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR05MB3529
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/Y5SOQxRzrdDXMvcxfN2KpK1ek8s>
Subject: Re: [MBONED] deprecating MSDP
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Sep 2017 18:33:46 -0000

| Indeed not solved by "just use SSM". It is still my firm opinion that there
| will be no "IP multicast service across the Internet" unless someone comes up
| with serious money and throws it ISPs way to enable this. And I am talking
| about ALL the ISPs which carry this, not just one. I don't see this happening
| anytime soon.

FWIW, we wouldn't have the web or netflix or youtube or any of the main 
things that people use the Internet for if such a similar barrier were 
considered for these services.  Content drives deployment.  If mcast is 
able to deliver some really compelling content that isn't available/viable 
via unicast, then it will find a way to get itself deployed.  VR perhaps?  
Anyway, the bar for this to happen is actually much lower now that we have 
AMT, as it only takes one/a few SPs to deploy Internet Mcast to deliver 
the content to end users, as opposed to ~ALL of them as was previously 
required.

FWIW2, all of the exact same arguments for/against mcast can be made for 
IPv6, and IPv6 seems to gaining a bit of momentum and steam after a few 
decades of similar deployment malaise.  Perhaps v6 can provide a teachable 
moment for mcast?

As for business models, anyone seeking massive $$$ for direct revenue from 
Internet mcast will most likely never find it.  I think mcast is best 
viewed like DNS or BGP (or IPv6)- infrastructure that is difficult to 
charge directly for, but enables higher layer services for which there is 
a panoply of viable business models.


From nobody Thu Sep  7 13:24:45 2017
Return-Path: <swmike@swm.pp.se>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B6AA132FC7 for <mboned@ietfa.amsl.com>; Thu,  7 Sep 2017 13:24:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level: 
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 rovErslkAKoX for <mboned@ietfa.amsl.com>; Thu,  7 Sep 2017 13:24:41 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 29C431321D5 for <mboned@ietf.org>; Thu,  7 Sep 2017 13:24:40 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 6B261B1; Thu,  7 Sep 2017 22:24:37 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1504815877; bh=B31S+nv4eP+20jrvkUxplY90M514+oQsjguGIcaobf8=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=HE1oL4AGbfeivThgCLjYo0WF7rw8iY1hASETZYV4IXscP4W/cGRDHTkPPgu+Q3jl7 G+stKHkfLiPI/IpBDg11lh/hL1kvaFmXphMzJl7F7v837hbimGl+d2PufQsZ6i/T93 seaa00zclILbhjY1AiY4gH3nZ4TI/znawDvxDWsc=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 537E2AF; Thu,  7 Sep 2017 22:24:37 +0200 (CEST)
Date: Thu, 7 Sep 2017 22:24:37 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Leonard Giuliano <lenny@juniper.net>
cc: Toerless Eckert <tte@cs.fau.de>, "mboned@ietf.org" <mboned@ietf.org>
In-Reply-To: <alpine.DEB.2.02.1709071111270.19087@svl-jtac-lnx02.juniper.net>
Message-ID: <alpine.DEB.2.20.1709072213470.29378@uplift.swm.pp.se>
References: <20170725221330.GA4821@cs-it-6805697.local> <alpine.DEB.2.02.1707260908550.29724@svl-jtac-lnx02> <20170904141235.GC3194@faui40p.informatik.uni-erlangen.de> <alpine.DEB.2.02.1709051358300.14937@svl-jtac-lnx02.juniper.net> <f911d57bf77245b8b074d3c557ab28f2@XCH15-06-11.nw.nos.boeing.com> <alpine.DEB.2.20.1709060825330.29378@uplift.swm.pp.se> <20170907134500.GB23219@faui40p.informatik.uni-erlangen.de> <alpine.DEB.2.20.1709071602420.29378@uplift.swm.pp.se> <alpine.DEB.2.02.1709071111270.19087@svl-jtac-lnx02.juniper.net>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/Id4qI8aB01GuoL9SfyhGBGTNt-Y>
Subject: Re: [MBONED] deprecating MSDP
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Sep 2017 20:24:43 -0000

On Thu, 7 Sep 2017, Leonard Giuliano wrote:

> FWIW2, all of the exact same arguments for/against mcast can be made for 
> IPv6, and IPv6 seems to gaining a bit of momentum and steam after a few 
> decades of similar deployment malaise.  Perhaps v6 can provide a 
> teachable moment for mcast?

Agreed. I have worked in IPv6 deployment and advocacy for 10 years. IPv6 
solves a problem (adressing), and yet it was really hard to start getting 
it deployed. This is now happening. I don't see the same driver for 
multicast. IPv6 solves the problem of the new entrant into the market who 
doesn't have enough IPv4 addresses. It doesn't solve many problems for the 
incumbents, thus there is no real driver for them to deply IPv6. This is 
now happening anyway, because even they see that they'll have problems if 
IPv6 is not deployed.

Multicast is an optimization over unicast which mostly benefits the 
head-end. At the same time, the world is moving towards more and more 
"on-demand" where multicast has less to offer than it did 15 years ago 
when more content was linear TV and everybody was watching the same thing 
at the same time.

I just don't see the business model for multicast the way Toerless 
described it. I don't see it 15 years ago, I don't see it now.

Having the ISP make money off of linear TV that's provided in cooperation 
with some "cable company". That's obvious. ISP gets paid by "cable 
company" for distribution. Or it does it itself as hygene factor to 
attract more customers.

Now, what would the content be that would have the same "pull", so that 
customers would not buy from ISP if they didn't at least have that 
content/service available as an option? I can't think of one.

> As for business models, anyone seeking massive $$$ for direct revenue from
> Internet mcast will most likely never find it.  I think mcast is best
> viewed like DNS or BGP (or IPv6)- infrastructure that is difficult to
> charge directly for, but enables higher layer services for which there is
> a panoply of viable business models.

Can you give a few examples of these "panoply of viable business models" 
for Internet-wide multicast? I can't think of a single one.

I have deployed multicast in largish ISP networks twice in my life. It's 
painful. It's also expensive because of all the verification needed to be 
done initially and over time, to make sure your customers get all the 
packets.

>From cost/benefit perspective, I just don't see this flying. I would like 
to see it fly, I have always been fascinated by multicast ever since I 
watched a NASA multicast stream (shuttle launch) on my computer in my dorm 
back in 1996 or something. Still... I just don't see what would make ISPs 
do what Toerless described.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Thu Sep  7 13:54:13 2017
Return-Path: <albert.e.manfredi@boeing.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BEA6132397 for <mboned@ietfa.amsl.com>; Thu,  7 Sep 2017 13:54:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 F0MDFxBQ6PhY for <mboned@ietfa.amsl.com>; Thu,  7 Sep 2017 13:54:10 -0700 (PDT)
Received: from phx-mbsout-01.mbs.boeing.net (phx-mbsout-01.mbs.boeing.net [130.76.184.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE898124E15 for <mboned@ietf.org>; Thu,  7 Sep 2017 13:54:10 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id v87Ks98j013209; Thu, 7 Sep 2017 13:54:09 -0700
Received: from XCH15-06-07.nw.nos.boeing.com (xch15-06-07.nw.nos.boeing.com [137.136.238.213]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v87Krx0C012718 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Thu, 7 Sep 2017 13:53:59 -0700
Received: from XCH15-06-11.nw.nos.boeing.com (2002:8988:efdc::8988:efdc) by XCH15-06-07.nw.nos.boeing.com (2002:8988:eed5::8988:eed5) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Thu, 7 Sep 2017 13:53:58 -0700
Received: from XCH15-06-11.nw.nos.boeing.com ([137.136.239.220]) by XCH15-06-11.nw.nos.boeing.com ([137.136.239.220]) with mapi id 15.00.1320.000; Thu, 7 Sep 2017 13:53:58 -0700
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
CC: "mboned@ietf.org" <mboned@ietf.org>
Thread-Topic: [MBONED] deprecating MSDP
Thread-Index: AQHTJtogePZD5u21Ykm+0jRT04oNKaKp5qQAgAAGxICAAEnjAIAAHv+A//+LU4A=
Date: Thu, 7 Sep 2017 20:53:58 +0000
Message-ID: <bd1f3dab5846485a89bf443bd17b5ec4@XCH15-06-11.nw.nos.boeing.com>
References: <20170725221330.GA4821@cs-it-6805697.local> <alpine.DEB.2.02.1707260908550.29724@svl-jtac-lnx02> <20170904141235.GC3194@faui40p.informatik.uni-erlangen.de> <alpine.DEB.2.02.1709051358300.14937@svl-jtac-lnx02.juniper.net> <f911d57bf77245b8b074d3c557ab28f2@XCH15-06-11.nw.nos.boeing.com> <alpine.DEB.2.20.1709060825330.29378@uplift.swm.pp.se> <20170907134500.GB23219@faui40p.informatik.uni-erlangen.de> <alpine.DEB.2.20.1709071602420.29378@uplift.swm.pp.se> <alpine.DEB.2.02.1709071111270.19087@svl-jtac-lnx02.juniper.net> <alpine.DEB.2.20.1709072213470.29378@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.20.1709072213470.29378@uplift.swm.pp.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/M90_TbLVcKHP_yHZ6rJh84__12o>
Subject: Re: [MBONED] deprecating MSDP
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Sep 2017 20:54:12 -0000

-----Original Message-----
From: MBONED [mailto:mboned-bounces@ietf.org] On Behalf Of Mikael Abrahamss=
on

> Multicast is an optimization over unicast which mostly benefits
> the head-end. At the same time, the world is moving towards more
> and more "on-demand" where multicast has less to offer than it
> did 15 years ago when more content was linear TV and everybody
> was watching the same thing at the same time.

I agree completely, and there is more. One of the benefits of Internet deli=
very of TV is precisely because, as a two-way medium, it inherently support=
s on demand. Given the option, much more often than not, people prefer to w=
atch TV when it is convenient for them, not by appointment with a head end =
(in the US, as of mid-2015, only 39% of TV content was consumed by appointm=
ent; the percentage might be even lower today). Broadcast delivery, meaning=
 "by appointment," was the only way of distributing TV content decades ago.=
 People got used to it. But when options became available, like VCRs, peopl=
e began to discover they prefer watching when it is convenient.

And there is still more. Because now different consumer streaming devices h=
ave conjured up their own little walled garden, such as iOS, Android, Roku,=
 Amazon Fire, and so forth, and much of the content is viewed on demand, th=
e solution is to deploy servers at the edges of networks, especially for th=
e more popular content. So the delivery to users is via unicast, and the st=
ream protocol depends on the user's device. And furthermore, these tend to =
be self-adjusting protocols, which probe the end to end link quality on a c=
ontinuing basis. Not ideal for multicast.

But for some niche applications, multicast is the best answer by far. Such =
examples as distribution of navigation and system status data, in a control=
 system network.

> Having the ISP make money off of linear TV that's provided in
> cooperation with some "cable company". That's obvious. ISP gets
> paid by "cable company" for distribution.

Even that is not entirely clear to me. Yes, for live material, the ISP may =
prefer multicast. But even here, some ISPs prefer to be able to count the n=
umber of individual unicast sessions, and charge accordingly. Even live mat=
erial can be distributed to edge servers out of band, and then unicast to e=
nd users, using the specific protocol for that user's device.

Bert



From nobody Thu Sep  7 20:16:07 2017
Return-Path: <swmike@swm.pp.se>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25A021330AC for <mboned@ietfa.amsl.com>; Thu,  7 Sep 2017 20:16:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 hnzqv6UwtNbC for <mboned@ietfa.amsl.com>; Thu,  7 Sep 2017 20:16:03 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C60213309E for <mboned@ietf.org>; Thu,  7 Sep 2017 20:16:03 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id A200BB1; Fri,  8 Sep 2017 05:16:00 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1504840560; bh=O5CQla9H6H87dJ7/VquUGL6gCRhIs6O/QDN3ehMO5Mk=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=wC5u2w41Ph7DBagjEsa2sYdtneSCPndb6z++mA0GAAE0YKsDI1ko4qvP2mujq0b+i wrvk3EriRl8toNlCqX3usjIxa19nRGTXxoDh5W40BNqa8elkOFrZS4xas3RkuC2u/Q kcM0ieXycfXPrxkkSen0qEeCpQ47XMgJd/hC4Vy8=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 9F36DAF; Fri,  8 Sep 2017 05:16:00 +0200 (CEST)
Date: Fri, 8 Sep 2017 05:16:00 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
cc: "mboned@ietf.org" <mboned@ietf.org>
In-Reply-To: <bd1f3dab5846485a89bf443bd17b5ec4@XCH15-06-11.nw.nos.boeing.com>
Message-ID: <alpine.DEB.2.20.1709080445130.29378@uplift.swm.pp.se>
References: <20170725221330.GA4821@cs-it-6805697.local> <alpine.DEB.2.02.1707260908550.29724@svl-jtac-lnx02> <20170904141235.GC3194@faui40p.informatik.uni-erlangen.de> <alpine.DEB.2.02.1709051358300.14937@svl-jtac-lnx02.juniper.net> <f911d57bf77245b8b074d3c557ab28f2@XCH15-06-11.nw.nos.boeing.com> <alpine.DEB.2.20.1709060825330.29378@uplift.swm.pp.se> <20170907134500.GB23219@faui40p.informatik.uni-erlangen.de> <alpine.DEB.2.20.1709071602420.29378@uplift.swm.pp.se> <alpine.DEB.2.02.1709071111270.19087@svl-jtac-lnx02.juniper.net> <alpine.DEB.2.20.1709072213470.29378@uplift.swm.pp.se> <bd1f3dab5846485a89bf443bd17b5ec4@XCH15-06-11.nw.nos.boeing.com>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/-5xOzJvTAMezfdvsRjRu0L1RJR8>
Subject: [MBONED] deploying internet-wide multicast (RE: deprecating MSDP)
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Sep 2017 03:16:05 -0000

On Thu, 7 Sep 2017, Manfredi, Albert E wrote:

> users is via unicast, and the stream protocol depends on the user's

Here is another thing. Most of the traffic to user devices traverse at 
least one wifi hop. The unfortunate truth is that multicast doesn't work 
well on todays wifi environment (I raised this issue within the IETF close 
to two years ago, and we're still nowhere near anything I would say even 
remotely looks like a widespread solution).

So yes, AMT tunnels to unicast everything from the ISP to the devices 
might work. They would have to be initiated by the device/app itself (to 
aid initial deployment).

6to4 was decided to be a really bad way of doing IPv6 (public relays 
nobody knew how well they worked, they were badly maintained etc).

AMT looks like it was designed the same way. Now, with AMT you don't have 
the problem with return path uncertainty that 6to4 had, so that is less of 
a problem.

What I see lacking here is reliable transport. If we're going to do this, 
the client is going to have to be able to request retransmits to work 
around unreliable delivery of packets.

How do we do that? 5 second buffer in the AMT relay (or a device sitting 
next to the relay) that the client can request re-transmits from? It would 
need to be stateful somehow. We'd also need some kind of 
identifier/sequence number in each AMT packet so the end device can tell 
that a packet was missing, and can request a retransmit of this.

Thoughts?

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Fri Sep  8 13:03:22 2017
Return-Path: <lenny@juniper.net>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89A3013263F for <mboned@ietfa.amsl.com>; Fri,  8 Sep 2017 13:03:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.021
X-Spam-Level: 
X-Spam-Status: No, score=-2.021 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=juniper.net
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 qDfbLIhSeeWL for <mboned@ietfa.amsl.com>; Fri,  8 Sep 2017 13:03:18 -0700 (PDT)
Received: from NAM01-SN1-obe.outbound.protection.outlook.com (mail-sn1nam01on0120.outbound.protection.outlook.com [104.47.32.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 647481321E6 for <mboned@ietf.org>; Fri,  8 Sep 2017 13:03:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=i60U68w/mYz0G4QZv9uItXtEc83OqFmuSKN8k2FhyqU=; b=eenGzjVfP0K/yzMLo/AXnfM/ZObzEjVe0wJpL2SWgjPc3nseV0758Su7jUj1untYB67SZ8Ju4iRPQ2yjx4082/efhiytatC9tyCjpOwODV+sXvX60/vvveRTR2Rr0q4nps87Rh/IEVGN28Q7XgU2nAsNi2Q2GIhL81FrsOb/8xU=
Received: from SN4PR0501CA0029.namprd05.prod.outlook.com (10.167.112.42) by DM5PR05MB3529.namprd05.prod.outlook.com (10.174.242.146) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.56.4; Fri, 8 Sep 2017 20:03:17 +0000
Received: from CO1NAM05FT037.eop-nam05.prod.protection.outlook.com (2a01:111:f400:7e50::201) by SN4PR0501CA0029.outlook.office365.com (2603:10b6:803:40::42) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.56.4 via Frontend Transport; Fri, 8 Sep 2017 20:03:16 +0000
Received-SPF: SoftFail (protection.outlook.com: domain of transitioning juniper.net discourages use of 66.129.239.15 as permitted sender)
Received: from P-EMFE01C-SAC.jnpr.net (66.129.239.15) by CO1NAM05FT037.mail.protection.outlook.com (10.152.96.150) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P256) id 15.1.1385.11 via Frontend Transport; Fri, 8 Sep 2017 20:03:15 +0000
Received: from svl-jtac-lnx06.juniper.net (172.17.28.215) by P-EMFE01C-SAC.jnpr.net (172.24.192.21) with Microsoft SMTP Server id 14.3.123.3; Fri, 8 Sep 2017 13:03:09 -0700
Received: by svl-jtac-lnx06.juniper.net (Postfix, from userid 1709)	id 7051A9F71F; Fri,  8 Sep 2017 13:03:09 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])	by svl-jtac-lnx06.juniper.net (Postfix) with ESMTP id 6C7FF9F6F0; Fri,  8 Sep 2017 13:03:09 -0700 (PDT)
Date: Fri, 8 Sep 2017 13:03:08 -0700
From: Leonard Giuliano <lenny@juniper.net>
To: Mikael Abrahamsson <swmike@swm.pp.se>
CC: Toerless Eckert <tte@cs.fau.de>, "mboned@ietf.org" <mboned@ietf.org>
In-Reply-To: <alpine.DEB.2.20.1709072213470.29378@uplift.swm.pp.se>
Message-ID: <alpine.DEB.2.02.1709081222070.3553@svl-jtac-lnx02.juniper.net>
References: <20170725221330.GA4821@cs-it-6805697.local> <alpine.DEB.2.02.1707260908550.29724@svl-jtac-lnx02> <20170904141235.GC3194@faui40p.informatik.uni-erlangen.de> <alpine.DEB.2.02.1709051358300.14937@svl-jtac-lnx02.juniper.net> <f911d57bf77245b8b074d3c557ab28f2@XCH15-06-11.nw.nos.boeing.com> <alpine.DEB.2.20.1709060825330.29378@uplift.swm.pp.se> <20170907134500.GB23219@faui40p.informatik.uni-erlangen.de> <alpine.DEB.2.20.1709071602420.29378@uplift.swm.pp.se> <alpine.DEB.2.02.1709071111270.19087@svl-jtac-lnx02.juniper.net> <alpine.DEB.2.20.1709072213470.29378@uplift.swm.pp.se>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
X-EOPAttributedMessage: 0
X-MS-Office365-Filtering-HT: Tenant
X-Forefront-Antispam-Report: CIP:66.129.239.15; IPV:NLI; CTRY:US; EFV:NLI; SFV:NSPM; SFS:(10019020)(6009001)(39860400002)(2980300002)(189002)(199003)(52314003)(305945005)(46386002)(23726003)(81156014)(50986999)(45336002)(6916009)(8936002)(69596002)(2810700001)(81166006)(54906002)(2950100002)(2906002)(478600001)(97736004)(76176999)(57986006)(6266002)(53936002)(6246003)(54356999)(68736007)(3240700002)(77096006)(76506005)(5660300001)(356003)(106466001)(90966002)(50466002)(5005980100005)(105596002)(93886005)(7126002)(8676002)(86362001)(229853002)(47776003)(46406003)(189998001)(83506001)(4326008)(4001350100001)(110136004)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:DM5PR05MB3529; H:P-EMFE01C-SAC.jnpr.net; FPR:;  SPF:SoftFail; PTR:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-Microsoft-Exchange-Diagnostics: 1; CO1NAM05FT037; 1:Rbsp+si/0RYjqIerufby4QyxwCtRLt1yZku6bwAb1L9aeKyucnmXnVQbVyGcBqdokOyTURCWQYU+nOEd5xFidnuyRNZYZF7uJlEVIt/L8k5ibtK8LESp476UfpaYg4j+
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: ec93e3f0-e801-4da2-b3a0-08d4f6f4a4be
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(300000502095)(300135100095)(22001)(2017030254152)(300000503095)(300135400095)(2017052603199)(201703131423075)(201703031133081)(201702281549075)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:DM5PR05MB3529; 
X-Microsoft-Exchange-Diagnostics: 1; DM5PR05MB3529; 3:BVTqwJFsl0/AgXRzgCsSgf4uSFWv7/0oOmW6DiGlUExrlifV0Hcl195ap2gPPZaipL2wnZJhKj++bSrx+PHsDuPXZ3ZzNLgio85bwxFcgdhK4PWssO3awQYrnEq2E4+eCyCoPopB5Zd7D93tTwgK1FItsqNbQ3IgdLUnyEQZ8VIHXZ/JT3+oHEPL0yEyvyvXiZYZrFmSaUh6roYcT5obUDwJaYBBQ6TshTEbCDoTrEIqrCs/SefIo9jNibjavRGQ2nSxvV3rtDBkni0X4Rih0X1qgRolwbf9kYQsrtLwSnKOz25tFUtCTC9FTw+ifTiw2KtPYDS9ckLa9KSNICMyQ3V4cN6/uRi0i8l2NEBJ96Y=; 25:qroNgFhaVzehhgm8PTVat/xGo+p3BcAWMmetuYBvGsbTKkHlJ2k2URx2+uXGGURFDfr5AB8Ok0Nc7nS4pejTzWQ0AH8iC+akdFT5zmNwagQQG1Sxa7sRUExQZQlTIFkCEIXSeRwO61L62B9jNy1T1OHh8hkN1/qO+DvVOxRt1vrIFaa0B3nN/fiwGomm9Jwvncumuxscki1ppHqm96l6GaBppsDK06xrxdk50opYol3IVjk0e64GwvWWo1X4ADKhOofSbfrdXc2Dau8cuGEyT7nd8/UuT/E5tT8G4qy12/G7Kq0IZrGiP201rg01+23YJSYXDpGSpDl3bnc5seYuDQ==
X-MS-TrafficTypeDiagnostic: DM5PR05MB3529:
X-Microsoft-Exchange-Diagnostics: 1; DM5PR05MB3529; 31:MRXd+jpQ6Kf/YPKfRWYOhbLqxmhuCymfVcmsu85wEYkGHyCZw82/gMNxII7K84RTWLTLwZEYsdGULk7JgW4w3raddxQe4yBo+PsynbJx7eAb9U6O4USDmpSvikeD9a/W1yjoCRSEQ7sEcshzkPJP6JDSK3CLE7bECt6Pxov216AOKv6FWRg4pmueUuxQd25OAWU9V74uVEdTBgv1uiKhNGmTHh9Sf2nt+SBm2V4nPrc=; 20:sCI2Yori8g9iJnyVlg/H/Tc34hJ3iTIl9LIG5yYwkSslKHgg61dC+H1bChXQJdo9jHfu4zOEm2/JWSU4A/dzejwUFsCJTI6sW0XvTNjdgk3v2FIB1R5a0ZFKADqGGNxWN4xKJvd9C4kaHH3662B6UXJtsZ19TKMPSBYebpr5ZeR5pHr5dovX1XNgHn1QpHUTyFIAgw5r0HtOueDtwCj2Mc03quN54VYTkBRDyi+Z6WdS9zef6mGQ2JD/iBxnBbjjjEMH8rDDwejLn4B6ckmdjDX2s7tjT+cAAFID0tmjPTPamsIVGn3Dh1M7l2vkk9pAlLo8C/ePe4VMRQHoXWLQ+TAp5DBn3tgDISuQ+ZvwaiAxD5WnEkr3XzvB6rI1Uilx86o/brhwQ6kG6tOJnWvPXQLUh6VM72db9JLXqmfsArUWyeIe/LVaio8y9gntSnDZylgy82eu/dg3u3fRr0xastIpi5lRAje6kwwXmnXVKpLs/LfLKOyLA6dqiZpwso6U
X-Exchange-Antispam-Report-Test: UriScan:;
X-Microsoft-Antispam-PRVS: <DM5PR05MB3529DF1642DDAD136D49B1BDA4950@DM5PR05MB3529.namprd05.prod.outlook.com>
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(8121501046)(5005006)(93006095)(93001095)(10201501046)(3002001)(100000703101)(100105400095)(6055026)(6041248)(20161123558100)(20161123562025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123564025)(20161123555025)(20161123560025)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:DM5PR05MB3529; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:DM5PR05MB3529; 
X-Microsoft-Exchange-Diagnostics: 1; DM5PR05MB3529; 4:c3MJS/bHiWcRw0tsRLOsbe+rkBRuar51rJEQcUqkPKATlrx3qMRQxAlCpv8e0QsvTzUe+5AufxtV0Hejf4DQPv7XzZHzqmr6UXetuS4cUCGVO+M67/t4607Mt2GSwUIRl4znNTHfVDudgqPNc2vuFnYyzDyzfIJHi2cRCS+zrR4DmwQy3tDSPzCB/DPvZigEX7tGX5rIq+/jXp4HlWPb9ozHEcDYiVkq53G8uWgE9kKifNAtb65O/OxSYQ6/wBZD
X-Forefront-PRVS: 04244E0DC5
X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; DM5PR05MB3529; 23:Supxddn5gvYSc771XYEKNvQWxDhGRw/f+go7T9+bP?= =?us-ascii?Q?Vl2cbtjZBEy0tJN6yao1K6Q90jNaFOOF0mIjNqp/Z8s/xFIQWReNMLGVvRpr?= =?us-ascii?Q?JVT6luO7qZMyBEdMQ6Iklaf/duZhqSaSV0gCAoRTn2hDtsOvRzdj5KyBXIGo?= =?us-ascii?Q?gCR+jftLssP3ggQ4z/AWKZudYPQ8uaAVF7bWd/VqugmQmRCIA22l09Pi1nez?= =?us-ascii?Q?j+c54yjNLW9el9SSCgdvqWJ2VUlPvPIezRLpnhRiUDJme5dgHwt6PlmhC1rJ?= =?us-ascii?Q?RvTSjij0/pI1Ng7eT57zCZex5fM+Wb4bSb+Ik0nUgQZaXTddGLZEcbr0ZnoQ?= =?us-ascii?Q?v3wWgeBhfI+An8k+PaRkkg6d70AL89vWwjVJ3E1eTMtRQv9rzAPhMG6ynIkE?= =?us-ascii?Q?q+WPoCAzPZm0ttGEVg3trVlcTUAKvmLqccqTeKKQ5pGvZPrZqCLF7RyHplYr?= =?us-ascii?Q?jqDTKEFAiYxUORUyHB3ld8ECNNonsGrtceUUAs/q4X+qdL6tC6fZdXPb564L?= =?us-ascii?Q?+j99wJEiIKHiORhQwe/Bo6MrFWF+iPt1yx8BJkeBOSaEqpjLrysgGZmfsg+W?= =?us-ascii?Q?y2cXWNsNO07NvWNEen+uMyOMstsZvq/mH9MBorEFfnP/3T+c0Py1jw8w4qBQ?= =?us-ascii?Q?d5yXHOHAZnKLts4iPaNDo1cFnqoSwjWchknSoq0OGV8PvI1PeFYvcytoL688?= =?us-ascii?Q?3lFf/R63eNaNBn7ZWnj472KS5RRQQrdgOP0/Hnybwncvfe9IOALG6pNQ9saM?= =?us-ascii?Q?cicDSjy+4eZtCMrxZcFW/ARvNtLoYQqV146FBt2SoTFDAHBDEZfXxJ20cdHK?= =?us-ascii?Q?sn8xSYV0VpmgCpBeIHa3mKl42wXo9hh/Wf9KII1OppuyDbav2STpXFMAre8e?= =?us-ascii?Q?rl+eSCZmNyrB6RHepTBJnzUUbfnHgcFeUmyaJob842dSxf4OHGn62UGEcAbY?= =?us-ascii?Q?iorxjraS7M4yrLRgrCQhYstP3TLr+xeE9IU3zvpMbROC2gwCftHNK4wjAiGK?= =?us-ascii?Q?cXp/XWmftzmfJ+TMovYU3Y4oTX1gTy55fGMbHhJhvTRogyew/U4JhXNgdMt0?= =?us-ascii?Q?wjRWEXxEY3bjlvVRSAT8/6yI6ojlyFLdZEh2NuzfWrsAhv4UYjaxnyiOFOuc?= =?us-ascii?Q?yR7iMloI3/zeChzraCeWW+qca8DMTbjVqGOrmi8XEjdLhiHjDGpMmgOoiELW?= =?us-ascii?Q?3rULWOJ5EvLmTk4qa4IotdS9BZkyDip4BzjWdyFF/1PvJmzkqeFBAwN2Ydb0?= =?us-ascii?Q?ueV9wA2Mcp1p+iQBKX12l809yaQbk9X+PNdl6tO?=
X-Microsoft-Exchange-Diagnostics: 1; DM5PR05MB3529; 6:eJ6y1W6tL4N0GjcHCiaZezEucgN+fIy4WmerFAg+QV+/8Or+v1h28d9S+69utmdJ8aF0QdbxYlCHYYM8Xmkmyuo6cdWdM+vgkk2yHfwfi7Ounbjp96j5pgY1pS0bDBJv1E00eJ95sI7xdRdfi2LVvysmrr/230syuA7Wf0QI0vJw32Yf2bURvBVkoOHMUWe7L3ykF2pWVoQb76aLYH06aQBHA0cCRdgWlWMGb69HdKVh+KArTj8Hk4k8eWWp3p9HfDPT6uBQLAmBW7XyRm1It5vsOR616qnuNMifk/y+fJVLGDB0TXAbz+vvDdcpRmVqZkhq2j1buYVH3xzyPgL53g==; 5:3ycvz3j9BxYtoWrVxgtUWt6N+LTukdf+Z6h1r9FGSC5ew2Nsy/d5jEUMaqygTwhVblq7yMw98+pY4JJoSmlABxYXnRJKdZkKwUkS08ck8DqJxIU+E7s61e1L0MKIMda8+3lWB1JAqw/YV7dgyc7GyQ==; 24:QYAWLWScnK4uSgCuc6IeiBhtgg57LnE18RDdkXX4k6NbQtIehqfkkI543iTeqj/EY+s8e71SXktd6Ec/VXBPnxvvBV8tUQFIXrNEvXuzVk4=; 7:l+ZG/zFbbaLyQQJM80QdW7UuBJ1vZADz4kcw+L9/glgGlwvzrbpolm0zNQW7aX76RRl3GeUIbI7Ct14IlWTkILGP/+aLQnkKZDo28P5+OmnVp06+0MsJyrD1yzinUqEyIkZkO4s1pjOkZUhG0o0/4pmfWLDbWmyNR+zN4CwX7bKB5m8N3waSrwyOfU6GjEMXp6r5i51Us5i/oMUegfMayswOpnpZKpxH1GYjl7JnUv8=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 08 Sep 2017 20:03:15.9371 (UTC)
X-MS-Exchange-CrossTenant-Id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=bea78b3c-4cdb-4130-854a-1d193232e5f4; Ip=[66.129.239.15];  Helo=[P-EMFE01C-SAC.jnpr.net]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR05MB3529
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/DIP6FbhnY36RTzoqLYtjBjE9muU>
Subject: Re: [MBONED] deprecating MSDP
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Sep 2017 20:03:20 -0000

| Agreed. I have worked in IPv6 deployment and advocacy for 10 years. IPv6
| solves a problem (adressing), and yet it was really hard to start getting it
| deployed. This is now happening. I don't see the same driver for multicast.
| IPv6 solves the problem of the new entrant into the market who doesn't have
| enough IPv4 addresses. It doesn't solve many problems for the incumbents, thus
| there is no real driver for them to deply IPv6. This is now happening anyway,
| because even they see that they'll have problems if IPv6 is not deployed.

Well, advocates of v6 say it's needed to solve the address space problem, 
whereas skeptics say NAT already solved it.  Likewise, advocates of mcast 
say it solves the problem of duplicated traffic, whereas skeptics say CDNs 
already solved it.  Advocates of v6 suggest that an abundance of address 
space will make possible all sorts of new capabilities that were 
previously not possible or even thought of (IOT, smart appliances, etc).  
Likewise, advocates of mcast suggest that more efficient distribution of 
multidestinational traffic will democratize the streaming of live content 
and make possible all sorts of new *OTT* content that was previously not 
possible or even thought of (VR, etc).  That is, some faith in the unseen 
is a strong driver for both.

Not trying to weigh in on either side (at least of the v6 debate) other 
than to say these are enabling infrastructure technologies that share many 
of the same same arguments for/against.


| Multicast is an optimization over unicast which mostly benefits the head-end.
| At the same time, the world is moving towards more and more "on-demand" where
| multicast has less to offer than it did 15 years ago when more content was
| linear TV and everybody was watching the same thing at the same time.

Indeed, we live in an on-demand world, and that has greatly diminished the 
need for mcast.  But live linear video is not quite dead yet.  Plenty of 
people really do still watch TV.  And some content is simply preferred 
live (sporting events).  And perhaps the most common use of time-shifted 
video is the personal DVR- this uses live linear video (and saves it for 
personal playback later).

With >70% of Internet traffic carrying video, and traffic rates 
skyrocketing unabated- and that's without a ton of live linear content, 
which most consume on the plain-old TV (non Internet) system- I would 
suggest there's now more than ever a thirst for more efficient 
distribution of video content.  Indeed, the GGIE BOF in Chi IETF at least 
highlighted the challenges of video over the Internet (though I can't say 
I quite agreed with the solutions suggested there).

| Can you give a few examples of these "panoply of viable business models" for
| Internet-wide multicast? I can't think of a single one.

Think of any of the *OTT* business models of the unicast Internet: 
advertising, subscriptions, metering, selling customer data to dubious 
entities, etc.  All of these are just as applicable in the mcast world.  
And remember, just bc the content may be delivered via mcast, doesn't mean 
things like ad insertion and audience metering can't be done via unicast 
in the app layer in the background.


From nobody Fri Sep  8 14:37:34 2017
Return-Path: <albert.e.manfredi@boeing.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2197D126B71 for <mboned@ietfa.amsl.com>; Fri,  8 Sep 2017 14:37:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 UqxB3gojYf8r for <mboned@ietfa.amsl.com>; Fri,  8 Sep 2017 14:37:31 -0700 (PDT)
Received: from phx-mbsout-02.mbs.boeing.net (phx-mbsout-02.mbs.boeing.net [130.76.184.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A4D1D124E15 for <mboned@ietf.org>; Fri,  8 Sep 2017 14:37:31 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id v88LbUBV050241; Fri, 8 Sep 2017 14:37:30 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (xch15-06-08.nw.nos.boeing.com [137.136.238.222]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v88LbLq7050128 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Fri, 8 Sep 2017 14:37:21 -0700
Received: from XCH15-06-11.nw.nos.boeing.com (137.136.239.220) by XCH15-06-08.nw.nos.boeing.com (137.136.238.222) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Fri, 8 Sep 2017 14:37:20 -0700
Received: from XCH15-06-11.nw.nos.boeing.com ([137.136.239.220]) by XCH15-06-11.nw.nos.boeing.com ([137.136.239.220]) with mapi id 15.00.1320.000; Fri, 8 Sep 2017 14:37:20 -0700
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Leonard Giuliano <lenny@juniper.net>
CC: "mboned@ietf.org" <mboned@ietf.org>
Thread-Topic: [MBONED] deprecating MSDP
Thread-Index: AQHTKN2IDsHIynVg4kCRsPvIyD4W/aKrcelQ
Date: Fri, 8 Sep 2017 21:37:20 +0000
Message-ID: <3a96c6bf204943aea94c8927886d8a75@XCH15-06-11.nw.nos.boeing.com>
References: <20170725221330.GA4821@cs-it-6805697.local> <alpine.DEB.2.02.1707260908550.29724@svl-jtac-lnx02> <20170904141235.GC3194@faui40p.informatik.uni-erlangen.de> <alpine.DEB.2.02.1709051358300.14937@svl-jtac-lnx02.juniper.net> <f911d57bf77245b8b074d3c557ab28f2@XCH15-06-11.nw.nos.boeing.com> <alpine.DEB.2.20.1709060825330.29378@uplift.swm.pp.se> <20170907134500.GB23219@faui40p.informatik.uni-erlangen.de> <alpine.DEB.2.20.1709071602420.29378@uplift.swm.pp.se> <alpine.DEB.2.02.1709071111270.19087@svl-jtac-lnx02.juniper.net> <alpine.DEB.2.20.1709072213470.29378@uplift.swm.pp.se> <alpine.DEB.2.02.1709081222070.3553@svl-jtac-lnx02.juniper.net>
In-Reply-To: <alpine.DEB.2.02.1709081222070.3553@svl-jtac-lnx02.juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/1tTFbhWEU4t3O_g33f8V41dK-Ss>
Subject: Re: [MBONED] deprecating MSDP
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Sep 2017 21:37:33 -0000

-----Original Message-----
From: MBONED [mailto:mboned-bounces@ietf.org] On Behalf Of Leonard Giuliano

> Indeed, we live in an on-demand world, and that has greatly diminished
> the need for mcast.  But live linear video is not quite dead yet.
> Plenty of people really do still watch TV.

True, but what content is actually preferred live has become the minority -=
 sports and news. The trend has been downward rather steadily, for what amo=
unt of TV content is consumed "live." Mostly, I think, it's just that old h=
abits die hard. People need to start using OTT methods, before they find th=
is second nature. And this is what seems to be happening.=20

> And perhaps the most common use of time-shifted video is the personal
> DVR- this uses live linear video (and saves it for personal playback
> later).

Best I have been able to find on this is that as of the beginning of 2015, =
use of in-home storage, for time shift viewing, accounted for about half of=
 what we might generically call "on demand" viewing. In the US, back then, =
the stat I saw was 47% of on demand viewing was from streaming, the rest fr=
om PVR. But the trend was downward for PVR in-home recording, also due to t=
he cord cutting phenomenon. (Most people in the US are still tied to cable =
or satellite TV, but that number going steadily down. The only practical wa=
y of in-home recording, when tied to a set-top box, becomes via that STB wi=
th built-in PVR. With cord cutting, that box goes away. Cord cutters use st=
reaming, not so much out there buying their own PVRs anymore.)

So, Internet streaming is increasingly used for on demand. By today, I woul=
d be surprised if streaming didn't account for well over half of on demand =
viewing. Which is consistent with all other examples of stored content, mig=
rating to the so-called "cloud."

Which means, in practice, that a scalable solution for on demand viewing is=
 needed regardless. Also, a practical solution to accommodate the multiple =
streaming protocols needed. This is where the CDNs and the servers at the e=
dges come in. But yes, for those major sporting events that many people rea=
lly do watch simultaneously, multicast streaming through ISP networks would=
 be one interesting option. For this, though, the WiFi problem needs a good=
 solution, and if you really want targeted ads, during these very popular s=
porting events, that too needs a unicast solution.

So, another option is to use the same edge server infrastructure, as used f=
or on demand. Deliver the live content to these edge servers out of band (e=
.g. via satellite), which is how on demand content is frequently delivered =
now, to edge servers. This way, no WiFi multicast problem in the user premi=
ses, and no problem accommodating the different type of streaming protocols=
 or the targeted ads.

Best I can tell, multicast is definitely required, but it may never amount =
to a large fraction of Internet traffic. Except maybe in specialty networks=
.

Bert



From nobody Mon Sep 11 04:53:15 2017
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5C0C132DFB for <mboned@ietfa.amsl.com>; Mon, 11 Sep 2017 04:53:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level: 
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 EOnf73egGYLf for <mboned@ietfa.amsl.com>; Mon, 11 Sep 2017 04:53:11 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C21D3132D14 for <mboned@ietf.org>; Mon, 11 Sep 2017 04:53:11 -0700 (PDT)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [131.188.34.77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 52C1858C4B4; Mon, 11 Sep 2017 13:53:07 +0200 (CEST)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id 3FA4BB0CB64; Mon, 11 Sep 2017 13:53:07 +0200 (CEST)
Date: Mon, 11 Sep 2017 13:53:07 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: Leonard Giuliano <lenny@juniper.net>, "mboned@ietf.org" <mboned@ietf.org>
Message-ID: <20170911115306.GA3600@faui40p.informatik.uni-erlangen.de>
References: <20170725221330.GA4821@cs-it-6805697.local> <alpine.DEB.2.02.1707260908550.29724@svl-jtac-lnx02> <20170904141235.GC3194@faui40p.informatik.uni-erlangen.de> <alpine.DEB.2.02.1709051358300.14937@svl-jtac-lnx02.juniper.net> <f911d57bf77245b8b074d3c557ab28f2@XCH15-06-11.nw.nos.boeing.com> <alpine.DEB.2.20.1709060825330.29378@uplift.swm.pp.se> <20170907134500.GB23219@faui40p.informatik.uni-erlangen.de> <alpine.DEB.2.20.1709071602420.29378@uplift.swm.pp.se> <alpine.DEB.2.02.1709071111270.19087@svl-jtac-lnx02.juniper.net> <alpine.DEB.2.20.1709072213470.29378@uplift.swm.pp.se>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.DEB.2.20.1709072213470.29378@uplift.swm.pp.se>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/sqpGccBpjNoCA_DG8Td5qjgargQ>
Subject: Re: [MBONED] deprecating MSDP
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Sep 2017 11:53:14 -0000

On Thu, Sep 07, 2017 at 10:24:37PM +0200, Mikael Abrahamsson wrote:
> I just don't see the business model for multicast the way Toerless
> described it. I don't see it 15 years ago, I don't see it now.

I don't think i said something about the business model, i was just
describing the minimum technical requirements for multicast outside of
closed-group services (eg: L3VPN) in SPs. 

You mentioned that there are difficulties underneath my high level
description. I would love to hear what those are to see if there are
standards gaps we could close (but see below firt for one discussion ;-).

I still think IP multicast is a business opportunity, but i have given
up for a long time now that it will happen with SPs.

The two business models that IMHO came closest where:

a) Regulator mandated equal access for competiors to replication as
   used in SPs own IPTV services. AFAIK, this never came to fruition
   anywhere.

b) OTT providers willing to pay for SP based replication to 
   deal with peak utilization. This one has not come true yet
   either but was one reason for businesses to invest into AMT.

In both cases, competitive and net-neutrality considerations make
these approaches complex.

> Having the ISP make money off of linear TV that's provided in
> cooperation with some "cable company". That's obvious. ISP gets paid
> by "cable company" for distribution. Or it does it itself as hygene
> factor to attract more customers.

Are you describing DTs (and others) existing IPTV business model or something
half-way to my (a) ? (aka: not regulator enforced) ?

> Now, what would the content be that would have the same "pull", so
> that customers would not buy from ISP if they didn't at least have
> that content/service available as an option? I can't think of one.

With Satellite (e.g.: Astra), i can buy bandwidth and broadcast
whatever program i want - and hundreds of millions of STBs will be
able to receive it (instead of "this video requires internet explorer 5.7").
And Astra does not act as a controller for the content (at least not when
encrypted). AFAIK, there is no equivalent offer not even from a single ISP in Europe.

The fact that there is no offered IP equvialent to this is quite perplexing.
Given how much many billions of seed subsidies have been tanked into many
other technologies across europe, maybe the EU should try to get this
going via some initial subsidies.

> I have deployed multicast in largish ISP networks twice in my life.
> It's painful. It's also expensive because of all the verification
> needed to be done initially and over time, to make sure your
> customers get all the packets.

Most QoS/QoE (Quality of Service / Experience) issues exist in unicast as
well, (e.g.: UDP VoD without rate adaptation), or non-existing bandwidth
guarantees for TCP videos (e.g.: Netflix sucks on friday evenings).

In TCP you need to trust sender and receiver to perform
appropriate congestion control. And there are lot of hacks in ISP
to throttle non conforming traffic. Given how slowly this
has all evolved in unicast, one can of course see how difficult it
is for this industry to make something new as rate-adaptive multicast
work fairly.

> >From cost/benefit perspective, I just don't see this flying. I
> >would like
> to see it fly, I have always been fascinated by multicast ever since
> I watched a NASA multicast stream (shuttle launch) on my computer in
> my dorm back in 1996 or something. Still... I just don't see what
> would make ISPs do what Toerless described.

See above. This being mboned (ops), and not mc-business, it should
be fine for us to figure out what missing pieces we should work on to
remove any technical obstacles.

Wrt to business: Lets see how slicing in mobile networks will evolve.
A lot of use cases there are closed group services. Aka: like L3VPN,
the paying customer could force the ISP to deliver what they
want (eg: IP multicast). But unlike wireline networks, those
closed groups could hopefully include residential users that just buy
into some slicing service when they buy an app or service that comes
with the app.

Cheers
    Toerless

> 
> -- 
> Mikael Abrahamsson    email: swmike@swm.pp.se

-- 
---
tte@cs.fau.de


From nobody Mon Sep 11 06:06:08 2017
Return-Path: <swmike@swm.pp.se>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CEC2133078 for <mboned@ietfa.amsl.com>; Mon, 11 Sep 2017 06:06:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level: 
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 l543Ndshoa6q for <mboned@ietfa.amsl.com>; Mon, 11 Sep 2017 06:06:03 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 65D22132199 for <mboned@ietf.org>; Mon, 11 Sep 2017 06:06:03 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id E5507AF; Mon, 11 Sep 2017 15:06:00 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1505135160; bh=027Bmc+e+975R4n9KF7fSC15u1oYZwjzsQZK6KAETDc=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=F6oGCAJVOdjetqF4Avs4euxnBYwGODmaQX9EgureK82zT4QXw2KbVyooJSD846Wwb Jt9qga0UDnGIZp01N3FttBGSHBUmxJT+Lf5JZavMipE/Jwcnj9mv0Yzf49HNS3FAi0 j1YZYGFZ95UjWTwyp7K0HKWPjZpY8UUX2HfN9FO4=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id E324B84; Mon, 11 Sep 2017 15:06:00 +0200 (CEST)
Date: Mon, 11 Sep 2017 15:06:00 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Toerless Eckert <tte@cs.fau.de>
cc: Leonard Giuliano <lenny@juniper.net>, "mboned@ietf.org" <mboned@ietf.org>
In-Reply-To: <20170911115306.GA3600@faui40p.informatik.uni-erlangen.de>
Message-ID: <alpine.DEB.2.20.1709111454170.29378@uplift.swm.pp.se>
References: <20170725221330.GA4821@cs-it-6805697.local> <alpine.DEB.2.02.1707260908550.29724@svl-jtac-lnx02> <20170904141235.GC3194@faui40p.informatik.uni-erlangen.de> <alpine.DEB.2.02.1709051358300.14937@svl-jtac-lnx02.juniper.net> <f911d57bf77245b8b074d3c557ab28f2@XCH15-06-11.nw.nos.boeing.com> <alpine.DEB.2.20.1709060825330.29378@uplift.swm.pp.se> <20170907134500.GB23219@faui40p.informatik.uni-erlangen.de> <alpine.DEB.2.20.1709071602420.29378@uplift.swm.pp.se> <alpine.DEB.2.02.1709071111270.19087@svl-jtac-lnx02.juniper.net> <alpine.DEB.2.20.1709072213470.29378@uplift.swm.pp.se> <20170911115306.GA3600@faui40p.informatik.uni-erlangen.de>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/7BxjCb9ekprrJVVyF774oi4c0JY>
Subject: Re: [MBONED] deprecating MSDP
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Sep 2017 13:06:07 -0000

On Mon, 11 Sep 2017, Toerless Eckert wrote:

> Are you describing DTs (and others) existing IPTV business model or 
> something half-way to my (a) ? (aka: not regulator enforced) ?

I am not describing anything related to any specific ISP.

I was talking generally. I know multiple ISPs that have linear TV 
multicast in their network. I know 0 who have this "over the Internet". 
It's always some special port somewhere to someones headend.

> With Satellite (e.g.: Astra), i can buy bandwidth and broadcast whatever 
> program i want - and hundreds of millions of STBs will be able to 
> receive it (instead of "this video requires internet explorer 5.7"). And 
> Astra does not act as a controller for the content (at least not when 
> encrypted). AFAIK, there is no equivalent offer not even from a single 
> ISP in Europe.

That's because Astra has line-of-sight to these hundreds of millions of 
STBs. The equipment is also very well specified (DVB) and standardized 
(well, perhaps not the encryption part, still still seems to be provider 
specifics).

> The fact that there is no offered IP equvialent to this is quite 
> perplexing. Given how much many billions of seed subsidies have been 
> tanked into many other technologies across europe, maybe the EU should 
> try to get this going via some initial subsidies.

The IP model is to do this over unicast, and use lots of bandwidth for it. 
Astra satellite is probably in the X times gigabit range of bandwidth. 
Largish ISPs are probably 2-3 magnitudes above that. One runs a network 
that is optimized for unicast, the other one runs equipment that is 
optimized for broadcast.

> Most QoS/QoE (Quality of Service / Experience) issues exist in unicast 
> as well, (e.g.: UDP VoD without rate adaptation), or non-existing 
> bandwidth guarantees for TCP videos (e.g.: Netflix sucks on friday 
> evenings).

Indeed, but your customers won't call and complain because they had a 
little bit more buffering when loading youtube (or they might not even 
notice it). They will call when they have magenta blobs floating around on 
their TV because you lost a packet somewhere.

> See above. This being mboned (ops), and not mc-business, it should be 
> fine for us to figure out what missing pieces we should work on to 
> remove any technical obstacles.

Then my point is that we need to invent AMT tunnels with re-transmits, and 
make sure we have everything so applications can initiate these tunnels 
and start receiving data. That way we can overlay over existing networks 
and as this traffic starts to increase, people can start running native 
multicast instead, further and further out towards the edge of their 
networks. These AMT tunnels also need to have some kind of signalling so 
you can have multiple AMT tunnels and know whereto subscribe S,G for what 
groups.

Incremental deployment is the key here in my opinion.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Mon Sep 11 06:52:50 2017
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B5CD133093 for <mboned@ietfa.amsl.com>; Mon, 11 Sep 2017 06:52:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level: 
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 kUq0SLkSVHHF for <mboned@ietfa.amsl.com>; Mon, 11 Sep 2017 06:52:46 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CBC27133086 for <mboned@ietf.org>; Mon, 11 Sep 2017 06:52:45 -0700 (PDT)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 4900B58C4B4; Mon, 11 Sep 2017 15:52:41 +0200 (CEST)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id 2BFEEB0CB66; Mon, 11 Sep 2017 15:52:41 +0200 (CEST)
Date: Mon, 11 Sep 2017 15:52:41 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: Leonard Giuliano <lenny@juniper.net>, "mboned@ietf.org" <mboned@ietf.org>
Message-ID: <20170911135240.GB3600@faui40p.informatik.uni-erlangen.de>
References: <20170904141235.GC3194@faui40p.informatik.uni-erlangen.de> <alpine.DEB.2.02.1709051358300.14937@svl-jtac-lnx02.juniper.net> <f911d57bf77245b8b074d3c557ab28f2@XCH15-06-11.nw.nos.boeing.com> <alpine.DEB.2.20.1709060825330.29378@uplift.swm.pp.se> <20170907134500.GB23219@faui40p.informatik.uni-erlangen.de> <alpine.DEB.2.20.1709071602420.29378@uplift.swm.pp.se> <alpine.DEB.2.02.1709071111270.19087@svl-jtac-lnx02.juniper.net> <alpine.DEB.2.20.1709072213470.29378@uplift.swm.pp.se> <20170911115306.GA3600@faui40p.informatik.uni-erlangen.de> <alpine.DEB.2.20.1709111454170.29378@uplift.swm.pp.se>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.DEB.2.20.1709111454170.29378@uplift.swm.pp.se>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/sWZdgZj9YSrkOzFUt7KiOGgtUfw>
Subject: Re: [MBONED] deprecating MSDP
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Sep 2017 13:52:48 -0000

On Mon, Sep 11, 2017 at 03:06:00PM +0200, Mikael Abrahamsson wrote:
> I was talking generally. I know multiple ISPs that have linear TV
> multicast in their network. I know 0 who have this "over the
> Internet". It's always some special port somewhere to someones
> headend.

I'd already be happy to hear about examples where that headend is
run by somebody else than the ISP (or its subsidiaries, co-owned
business entities), and that somebody else is controlling the content.
That would be progress in the business models.

> >The fact that there is no offered IP equvialent to this is quite
> >perplexing. Given how much many billions of seed subsidies have
> >been tanked into many other technologies across europe, maybe the
> >EU should try to get this going via some initial subsidies.
> 
> The IP model is to do this over unicast, and use lots of bandwidth
> for it. Astra satellite is probably in the X times gigabit range of
> bandwidth. Largish ISPs are probably 2-3 magnitudes above that. One
> runs a network that is optimized for unicast, the other one runs
> equipment that is optimized for broadcast.

One continues to ignore exploiting opportunities for multicasting ? ;-))

> >Most QoS/QoE (Quality of Service / Experience) issues exist in
> >unicast as well, (e.g.: UDP VoD without rate adaptation), or
> >non-existing bandwidth guarantees for TCP videos (e.g.: Netflix
> >sucks on friday evenings).
> 
> Indeed, but your customers won't call and complain because they had
> a little bit more buffering when loading youtube (or they might not
> even notice it). They will call when they have magenta blobs
> floating around on their TV because you lost a packet somewhere.

The visual experience with rate adapting multicast and network/fountain
codecs is pretty much the same as for unicast/ABR.

> >See above. This being mboned (ops), and not mc-business, it should
> >be fine for us to figure out what missing pieces we should work on
> >to remove any technical obstacles.
> 
> Then my point is that we need to invent AMT tunnels with
> re-transmits, and make sure we have everything so applications can
> initiate these tunnels and start receiving data. That way we can
> overlay over existing networks and as this traffic starts to
> increase, people can start running native multicast instead, further
> and further out towards the edge of their networks. These AMT
> tunnels also need to have some kind of signalling so you can have
> multiple AMT tunnels and know whereto subscribe S,G for what groups.
> 
> Incremental deployment is the key here in my opinion.

Without multi-layered rate-adaptive encoding, TCP in AMT will not help,
and after a good standard for multi-layer rate-adaptive encoding,
the incremental deployment option is IMHO not AMT but a proxy:

Getting an open source reference rate-adaptive multicast video
sender/receiver stack (with join/leave to different (S,G) bitrates
according to loss) is IMHO the same problem as good TCP + MPEG/H26X stack
for unicast. We have those now, but how long did those take ?

I know of good commercial or prototpye stacks that do this well
(i actually helped to develop one), but with those stacks stuck in
the proprietary product offerings of those vendors, they are IMHO not
sufficient to create a larger market for multicast technologies.

In this decade (or next), i can not imagine that a few proprietary options
can actually push the needle in this market. Instead, this is something
for middleware developers.  Aka: somebody give a few hundred K to Mozilla 
and let them develop such a stack.

Once there is an open source reference, it can be codified into a standard
(profile of a bunch of existing session/app-layer protocols). And
then it would be a good product offering to build multicast->unicast
proxies - where the unicast side is TCP - indistinguishable from
existing ABR to the receiver - and the proxy does the actual multicast
join/leaves to the different bitrates. 

Yes, you could equally build AMT with TCP, but TCP pushes such an
AMT tunnel implementation out of traditional router forwarding paths.
And once you use a forwarding plane that can do TCP, then you can
equally do the above mentioned proxy function because thats just
a bit more work than an AMT proxy - eg: couple the measured
TCP send-rate to upstream join/leaves.

Cheers
    Toerless

> -- 
> Mikael Abrahamsson    email: swmike@swm.pp.se

-- 
---
tte@cs.fau.de


From nobody Mon Sep 11 07:37:31 2017
Return-Path: <swmike@swm.pp.se>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 661FE1330B3 for <mboned@ietfa.amsl.com>; Mon, 11 Sep 2017 07:37:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level: 
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 AlfTnHloZZFM for <mboned@ietfa.amsl.com>; Mon, 11 Sep 2017 07:37:28 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1DEDC1330B2 for <mboned@ietf.org>; Mon, 11 Sep 2017 07:37:28 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 12DAEAF; Mon, 11 Sep 2017 16:37:25 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1505140646; bh=SODsBFgSuMmaZnDUdM4FlNZrbOzcrt7hmP0mHhmjqTU=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=oqA1bsRBZNA3IOHRH1utm0ulZgdklnYr6UY8tPESSTcP9EFVUeINu4+4Zt7SRGUwD 9jJV2ZpGIpa+RC8e8vocsP4X1fid+3wCvQNeazBM8OuqWre+S3dZMjwkfsuxl8ncZy tyxjIP0rltZSMfYFYi0Cz+WvXVgh1wcGHESx/u/A=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id EF69B84; Mon, 11 Sep 2017 16:37:25 +0200 (CEST)
Date: Mon, 11 Sep 2017 16:37:25 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Toerless Eckert <tte@cs.fau.de>
cc: Leonard Giuliano <lenny@juniper.net>, "mboned@ietf.org" <mboned@ietf.org>
In-Reply-To: <20170911135240.GB3600@faui40p.informatik.uni-erlangen.de>
Message-ID: <alpine.DEB.2.20.1709111633360.29378@uplift.swm.pp.se>
References: <20170904141235.GC3194@faui40p.informatik.uni-erlangen.de> <alpine.DEB.2.02.1709051358300.14937@svl-jtac-lnx02.juniper.net> <f911d57bf77245b8b074d3c557ab28f2@XCH15-06-11.nw.nos.boeing.com> <alpine.DEB.2.20.1709060825330.29378@uplift.swm.pp.se> <20170907134500.GB23219@faui40p.informatik.uni-erlangen.de> <alpine.DEB.2.20.1709071602420.29378@uplift.swm.pp.se> <alpine.DEB.2.02.1709071111270.19087@svl-jtac-lnx02.juniper.net> <alpine.DEB.2.20.1709072213470.29378@uplift.swm.pp.se> <20170911115306.GA3600@faui40p.informatik.uni-erlangen.de> <alpine.DEB.2.20.1709111454170.29378@uplift.swm.pp.se> <20170911135240.GB3600@faui40p.informatik.uni-erlangen.de>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/Rf4w8Iet86gZiigj5C-GHzhjmzY>
Subject: Re: [MBONED] deprecating MSDP
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Sep 2017 14:37:30 -0000

On Mon, 11 Sep 2017, Toerless Eckert wrote:

> I'd already be happy to hear about examples where that headend is run by 
> somebody else than the ISP (or its subsidiaries, co-owned business 
> entities), and that somebody else is controlling the content. That would 
> be progress in the business models.

Yes, this is available. The major channel distribution companies in Sweden 
can offer this themselves or through their partners. As an ISP you order a 
fiber to them, get it lit up, and then you get multicast packets. The same 
entitity will also do EPG etc to the set-top boxes. So as an ISP, you 
don't have to do much if you don't want to.

> The visual experience with rate adapting multicast and network/fountain 
> codecs is pretty much the same as for unicast/ABR.

Ok. All IPTV I have seen had 0 tolerance to packet loss.

> Without multi-layered rate-adaptive encoding, TCP in AMT will not help, 
> and after a good standard for multi-layer rate-adaptive encoding, the 
> incremental deployment option is IMHO not AMT but a proxy:

I am not talking about packet loss induced by congestion. I am talking 
about packet loss induced by CRC errors on packets (and similar kinds of 
errors).

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Mon Sep 11 09:15:02 2017
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EAFEA133022 for <mboned@ietfa.amsl.com>; Mon, 11 Sep 2017 09:15:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level: 
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 EGUTAsxLVpuZ for <mboned@ietfa.amsl.com>; Mon, 11 Sep 2017 09:14:58 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 943E6132EC1 for <mboned@ietf.org>; Mon, 11 Sep 2017 09:14:58 -0700 (PDT)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 47CAA58C4EC; Mon, 11 Sep 2017 18:14:54 +0200 (CEST)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id 32778B0CB66; Mon, 11 Sep 2017 18:14:54 +0200 (CEST)
Date: Mon, 11 Sep 2017 18:14:54 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: Leonard Giuliano <lenny@juniper.net>, "mboned@ietf.org" <mboned@ietf.org>
Message-ID: <20170911161453.GC3600@faui40p.informatik.uni-erlangen.de>
References: <f911d57bf77245b8b074d3c557ab28f2@XCH15-06-11.nw.nos.boeing.com> <alpine.DEB.2.20.1709060825330.29378@uplift.swm.pp.se> <20170907134500.GB23219@faui40p.informatik.uni-erlangen.de> <alpine.DEB.2.20.1709071602420.29378@uplift.swm.pp.se> <alpine.DEB.2.02.1709071111270.19087@svl-jtac-lnx02.juniper.net> <alpine.DEB.2.20.1709072213470.29378@uplift.swm.pp.se> <20170911115306.GA3600@faui40p.informatik.uni-erlangen.de> <alpine.DEB.2.20.1709111454170.29378@uplift.swm.pp.se> <20170911135240.GB3600@faui40p.informatik.uni-erlangen.de> <alpine.DEB.2.20.1709111633360.29378@uplift.swm.pp.se>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.DEB.2.20.1709111633360.29378@uplift.swm.pp.se>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/IE3LEkLR07HIXhheneTofArQ3GI>
Subject: Re: [MBONED] deprecating MSDP
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Sep 2017 16:15:01 -0000

On Mon, Sep 11, 2017 at 04:37:25PM +0200, Mikael Abrahamsson wrote:
> On Mon, 11 Sep 2017, Toerless Eckert wrote:
> 
> >I'd already be happy to hear about examples where that headend is
> >run by somebody else than the ISP (or its subsidiaries, co-owned
> >business entities), and that somebody else is controlling the
> >content. That would be progress in the business models.
> 
> Yes, this is available. The major channel distribution companies in
> Sweden can offer this themselves or through their partners. As an
> ISP you order a fiber to them, get it lit up, and then you get
> multicast packets. The same entitity will also do EPG etc to the
> set-top boxes. So as an ISP, you don't have to do much if you don't
> want to.

Interesting. Any URL where i could find more details ?
Also: i forgot to include the element that the content owner could get
this set up. The way you describe it, it's something where the ISP decides
which content it wants to accept ?

> >The visual experience with rate adapting multicast and
> >network/fountain codecs is pretty much the same as for
> >unicast/ABR.
> 
> Ok. All IPTV I have seen had 0 tolerance to packet loss.

Yes. IPTV is as much of an evolution to TV as SIP was to telephony.

In a world where "use" is a permissible glorification of "abuse",
the best thing about both of them is that they use IP.

> >Without multi-layered rate-adaptive encoding, TCP in AMT will not
> >help, and after a good standard for multi-layer rate-adaptive
> >encoding, the incremental deployment option is IMHO not AMT but a
> >proxy:
> 
> I am not talking about packet loss induced by congestion. I am
> talking about packet loss induced by CRC errors on packets (and
> similar kinds of errors).

A bunch of the IPTV solutions have dealt with that problem. Especially
because the L2 FEC on xDSL is not good enough. There where a couple
of RFCs introduced back in the days when the first IPTV solutions came
along, specifically for RTCP based retransmission requests. Those
would then be handled by a cache sitting eg: near the DSLAM. 
Burst versions of those retransmission requests are also used to support fast
channel change, eg: get the last GOP so you can immediately start
streaming instead of having to wait for the next I-frame (especially
when GOP sizes of 10 seconds are desired). Vendor solutions like
those from Microsoft used proprietary mechanisms achieving the same
goals. Not sure if they implement the standards now.

In any case, that type of proxy-cache functionality could easily
be added to an AMT relay/gateway. The only linkage required would
be to just permit those RTCP/RTP unicast packets through the
AMT tunnel. Is it better than doing TCP ?? You get the option
for fast channel change... TCP gives you ability to make
non-RTP packets reliable but with less controllable latency.
Both would IMHO require non-ASIC forwarding.

Easier yet, just use good FEC like fountain codecs. Network Codecs
should be fine for this too (easier, less IPR encumbered).

Cheers
    Toerless

> -- 
> Mikael Abrahamsson    email: swmike@swm.pp.se

-- 
---
tte@cs.fau.de


From nobody Mon Sep 11 09:35:34 2017
Return-Path: <swmike@swm.pp.se>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65BB6132EA7 for <mboned@ietfa.amsl.com>; Mon, 11 Sep 2017 09:35:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level: 
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 2is6GBDKw_9R for <mboned@ietfa.amsl.com>; Mon, 11 Sep 2017 09:35:30 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8198B132EC1 for <mboned@ietf.org>; Mon, 11 Sep 2017 09:35:30 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id E1953AF; Mon, 11 Sep 2017 18:35:27 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1505147727; bh=tBzmhp8My36rroglpxH4NtubRscfqFud89lVsRwJBmQ=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=snqQV54FaY3mc82ACpx9pm41NaKIzTKc1jw2oR478trSENB6Gg9B2sHhbzgHR1k9y szO7BH/EJoGj5fahGwk/grpnTf1ZC+SXGQ0FghzNWQCWH/hMpXalC3ljV0aEVO8udm bdXKtWfDOnR00rbzqnLofTI33+QZw9gwoi3h98YA=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id DE93184; Mon, 11 Sep 2017 18:35:27 +0200 (CEST)
Date: Mon, 11 Sep 2017 18:35:27 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Toerless Eckert <tte@cs.fau.de>
cc: Leonard Giuliano <lenny@juniper.net>, "mboned@ietf.org" <mboned@ietf.org>
In-Reply-To: <20170911161453.GC3600@faui40p.informatik.uni-erlangen.de>
Message-ID: <alpine.DEB.2.20.1709111834260.29378@uplift.swm.pp.se>
References: <f911d57bf77245b8b074d3c557ab28f2@XCH15-06-11.nw.nos.boeing.com> <alpine.DEB.2.20.1709060825330.29378@uplift.swm.pp.se> <20170907134500.GB23219@faui40p.informatik.uni-erlangen.de> <alpine.DEB.2.20.1709071602420.29378@uplift.swm.pp.se> <alpine.DEB.2.02.1709071111270.19087@svl-jtac-lnx02.juniper.net> <alpine.DEB.2.20.1709072213470.29378@uplift.swm.pp.se> <20170911115306.GA3600@faui40p.informatik.uni-erlangen.de> <alpine.DEB.2.20.1709111454170.29378@uplift.swm.pp.se> <20170911135240.GB3600@faui40p.informatik.uni-erlangen.de> <alpine.DEB.2.20.1709111633360.29378@uplift.swm.pp.se> <20170911161453.GC3600@faui40p.informatik.uni-erlangen.de>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/ib8gMaGDnT1CZ3GetvnOf1V46WA>
Subject: Re: [MBONED] deprecating MSDP
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Sep 2017 16:35:32 -0000

On Mon, 11 Sep 2017, Toerless Eckert wrote:

> Interesting. Any URL where i could find more details ? Also: i forgot to 
> include the element that the content owner could get this set up. The 
> way you describe it, it's something where the ISP decides which content 
> it wants to accept ?

It was cooperation between the content distributor and the ISP. The ISP 
wanted to checkbox having "TV" in their offering, and the content 
distributor wanted to reach more customers.

There is URL I know of.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Mon Sep 11 09:36:42 2017
Return-Path: <swmike@swm.pp.se>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D08A1132EA7 for <mboned@ietfa.amsl.com>; Mon, 11 Sep 2017 09:36:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level: 
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 9ZcouhBPvSRU for <mboned@ietfa.amsl.com>; Mon, 11 Sep 2017 09:36:40 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C91491330C2 for <mboned@ietf.org>; Mon, 11 Sep 2017 09:36:39 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 61BB0AF; Mon, 11 Sep 2017 18:36:38 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1505147798; bh=OMA7lpVqeDq2j53JATf+Tm+PQ6fhKIY7KKv6EVOo280=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=h92Vcm157UHhJQUkXQsbLCe45BKSGXLnOZ+4eRUxlJ4JXrQNSVdRFnM/aPXb4wCOO DQRoufx2aZ5hZkpn1TryI5+7Nd3xpECbFcsJrFIuOpgdenGFfh2/chus5/1exV6vP4 q/DtgeOFH/tfA19KXvrF3bEC/slWOGEy/1jb1R70=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 4A02F84; Mon, 11 Sep 2017 18:36:38 +0200 (CEST)
Date: Mon, 11 Sep 2017 18:36:38 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Toerless Eckert <tte@cs.fau.de>
cc: Leonard Giuliano <lenny@juniper.net>, "mboned@ietf.org" <mboned@ietf.org>
In-Reply-To: <alpine.DEB.2.20.1709111834260.29378@uplift.swm.pp.se>
Message-ID: <alpine.DEB.2.20.1709111835340.29378@uplift.swm.pp.se>
References: <f911d57bf77245b8b074d3c557ab28f2@XCH15-06-11.nw.nos.boeing.com> <alpine.DEB.2.20.1709060825330.29378@uplift.swm.pp.se> <20170907134500.GB23219@faui40p.informatik.uni-erlangen.de> <alpine.DEB.2.20.1709071602420.29378@uplift.swm.pp.se> <alpine.DEB.2.02.1709071111270.19087@svl-jtac-lnx02.juniper.net> <alpine.DEB.2.20.1709072213470.29378@uplift.swm.pp.se> <20170911115306.GA3600@faui40p.informatik.uni-erlangen.de> <alpine.DEB.2.20.1709111454170.29378@uplift.swm.pp.se> <20170911135240.GB3600@faui40p.informatik.uni-erlangen.de> <alpine.DEB.2.20.1709111633360.29378@uplift.swm.pp.se> <20170911161453.GC3600@faui40p.informatik.uni-erlangen.de> <alpine.DEB.2.20.1709111834260.29378@uplift.swm.pp.se>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/o0mQYbxBqkfiI6zHBkriV4cMeUE>
Subject: Re: [MBONED] deprecating MSDP
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Sep 2017 16:36:41 -0000

On Mon, 11 Sep 2017, Mikael Abrahamsson wrote:

> There is URL I know of.

There is *no* URL that I know of.

This isn't volume business afaik. I don't remember which one it was, but 
it was basically in cooperation with one of the larger typical "channel 
package providers" you might get on coax TV. One of Canal Digital, VIASAT 
or someone like that.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Mon Sep 11 09:54:22 2017
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F0A8132EBA for <mboned@ietfa.amsl.com>; Mon, 11 Sep 2017 09:54:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level: 
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 Yspf8Wim81f4 for <mboned@ietfa.amsl.com>; Mon, 11 Sep 2017 09:54:19 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C50C132644 for <mboned@ietf.org>; Mon, 11 Sep 2017 09:54:19 -0700 (PDT)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 4989958C4EE; Mon, 11 Sep 2017 18:54:11 +0200 (CEST)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id 32242B0CB66; Mon, 11 Sep 2017 18:54:11 +0200 (CEST)
Date: Mon, 11 Sep 2017 18:54:11 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: Leonard Giuliano <lenny@juniper.net>, "mboned@ietf.org" <mboned@ietf.org>
Message-ID: <20170911165410.GD3600@faui40p.informatik.uni-erlangen.de>
References: <alpine.DEB.2.20.1709071602420.29378@uplift.swm.pp.se> <alpine.DEB.2.02.1709071111270.19087@svl-jtac-lnx02.juniper.net> <alpine.DEB.2.20.1709072213470.29378@uplift.swm.pp.se> <20170911115306.GA3600@faui40p.informatik.uni-erlangen.de> <alpine.DEB.2.20.1709111454170.29378@uplift.swm.pp.se> <20170911135240.GB3600@faui40p.informatik.uni-erlangen.de> <alpine.DEB.2.20.1709111633360.29378@uplift.swm.pp.se> <20170911161453.GC3600@faui40p.informatik.uni-erlangen.de> <alpine.DEB.2.20.1709111834260.29378@uplift.swm.pp.se> <alpine.DEB.2.20.1709111835340.29378@uplift.swm.pp.se>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.DEB.2.20.1709111835340.29378@uplift.swm.pp.se>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/zXySrH_9L7dG-kPYoGGjlOXeCUw>
Subject: Re: [MBONED] deprecating MSDP
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Sep 2017 16:54:20 -0000

Right. So it would not enable new content owners to come in and get
an easier market entry to reach customers for live streaming... sitting
in front of STBs. 

On Mon, Sep 11, 2017 at 06:36:38PM +0200, Mikael Abrahamsson wrote:
> On Mon, 11 Sep 2017, Mikael Abrahamsson wrote:
> 
> >There is URL I know of.
> 
> There is *no* URL that I know of.
> 
> This isn't volume business afaik. I don't remember which one it was,
> but it was basically in cooperation with one of the larger typical
> "channel package providers" you might get on coax TV. One of Canal
> Digital, VIASAT or someone like that.
> 
> -- 
> Mikael Abrahamsson    email: swmike@swm.pp.se

-- 
---
tte@cs.fau.de


From nobody Thu Sep 14 11:44:00 2017
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FF1C1320D9; Thu, 14 Sep 2017 11:43:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
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 u8px-YQOTMd8; Thu, 14 Sep 2017 11:43:44 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E49CA133064; Thu, 14 Sep 2017 11:43:43 -0700 (PDT)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [131.188.34.77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 5B5BE58C4AF; Thu, 14 Sep 2017 20:43:39 +0200 (CEST)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id 41391B0CBB7; Thu, 14 Sep 2017 20:43:39 +0200 (CEST)
Date: Thu, 14 Sep 2017 20:43:39 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Tomonori Takeda <tomonori.takeda@ntt.com>
Cc: "rtg-ads@ietf.org" <rtg-ads@ietf.org>, "'rtg-dir@ietf.org'" <rtg-dir@ietf.org>, "'draft-ietf-mboned-interdomain-peering-bcp.all@ietf.org'" <draft-ietf-mboned-interdomain-peering-bcp.all@ietf.org>,  "'mboned@ietf.org'" <mboned@ietf.org>
Message-ID: <20170914184339.GA26810@faui40p.informatik.uni-erlangen.de>
References: <EB0F2EAC05E9C64D80571F2042700A2A8684496C@C0561I0.coe.ntt.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <EB0F2EAC05E9C64D80571F2042700A2A8684496C@C0561I0.coe.ntt.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/AI9UJQaOgKPxuYKEgLaBkdWpQcI>
Subject: Re: [MBONED] RtgDir review: draft-ietf-mboned-interdomain-peering-bcp-10.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Sep 2017 18:43:46 -0000

Thanks for your review, Tomonori,

Question/replies inline

On Wed, Aug 23, 2017 at 04:52:36AM +0000, Tomonori Takeda wrote:
> Hello, 
> 
> I have been selected as the Routing Directorate reviewer for this draft. The Routing Directorate seeks to review all routing or routing-related drafts as they pass through IETF last call and IESG review, and sometimes on special request. The purpose of the review is to provide assistance to the Routing ADs. For more information about the Routing Directorate, please see ???http://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir 
> 
[...]

> Minor Issues:
> 1) I think it is better to describe assumed business relationship between AD-1 and AD-2, perhaps in Section 2.
> According to descriptions in Section 4, it seems that AD-1 has the ultimate responsibility to deliver multicast traffic to EU.
> (For example, it says "AD-2 provides relevant performance information to AD-1; this enables AD-1 to create an end-to-end performance view on behalf of the multicast application source.")
> 
> I think another possible model is that AD-1 is providing a wholesale service to AD-2, where AD-1's responsibility is to delivery data up to AD-2, and AD-2 has the ultimate responsibility to delivery data to EUs afterwards.
> (Note that I am not saying this model should be included in the document.)

How about "AD-2 should provide relevant performance information to AD-1..." ?
                ^^^^^^

Sounds to me as in your "wholesale" case this is not necessary , so "should" should capture that ?!

> So I think it is beneficial to describe assumed business relationship between AD-1 and AD-2 in this document.

The document tries to describe only technical aspects. "Business relationship" sounds
as if it might include aspects such as financials or legal obligations. Should we
explicitly say that the document does only discuss technical aspects, but
not business aspects such as financial or legal ? (i thought that was the
voldemort default assumption of IETF documents ;-)

> 2) In Sections 3.1 and 3.2, it says:
> 
>       "o Fewer devices in the path traversed by the multicast stream when
>          compared to unicast transmissions."
> 
> I don't understand this point.

Hopefully one of the co-authors can chime in with an example. Not sure if its
meant to count the total number of hops across all viewer streams
or something else.

> 3) In Section 3.2, it says:
> 
>       "o Ability to support only partial IP multicast deployments in AD-
>          1 and/or AD-2."
> 
> I don't understand this point. For example, are you assuming that GRE is terminated not on AS border routers?

Right. Those two BR in 3.2 do not need to be the two "unicast" domain
border routers, instead they can be anywhere in AD-1 and AD-2.

Maybe add this picture:


     -------------------               -------------------
     /       AD-1        \             /        AD-2       \
    / (Multicast Enabled) \           / (Multicast Enabled) \
   /                       \         /                       \
   | +----+          +---+ |   I1    | +---+                 |
   | |    |   +--+   |uBR|-|---------|-|uBR|   +--+          |   +----+
   | | AS |-->|BR|   +---+-|         | +---+   |BR| -------->|-->| EU |
   | |    |   +--+ <.......|.........|........>+--+          |I2 +----+
   \ +----+                /  GRE    \                       /
    \                     /  Tunnel   \                     /
     \                   /             \                   /
      -------------------               -------------------


   AD = Administrative Domain (Independent Autonomous System)
   AS = Application (e.g., Content) Multicast Source
   uBR = unicast Border Router - not multicast enabled
   BR = Border Router - for multicast
   I1 = AD-1 and AD-2 Multicast Interconnection (e.g., MBGP)
   I2 = AD-2 and EU Multicast Connection

      Figure 2 - Content Distribution via GRE peering

> 
> Nits:
> 1) I think some of the references may not be appropriate. 
> - In Section 1, "PIM-SM [RFC4609]" should be "PIM-SM [RFC7761]"?
> - In Section 4.1, "MBGP [RFC4271]" should be "MBGP [RFC4760]"?

Thanks!

> 2) In Section 1, it says:
> 
>    "Thus, the primary purpose of this document is to describe a scenario
>     where two AD's interconnect via a direct connection to each other."
> 
> I think "a direction connection" is a bit unclear. In deployment scenarios, you are mentioning that the peering point is multicast enabled or not.
> Does it mean that the peering point may be a routed network? It would be good to clarify this.

Did the proposed picture 2 help to answer this question ?
If not, then i am maybe not clear what you mean with routed network.

> 3) In Section 3.2, is says:
> 
>    "Section 4.3 provides an overview of one method that
>     finds the optimal Relay-Gateway combination via the use of an
>     Anycast IP address for AMT Relays."
> 
> I think Section 4.3 should be Section 4.2?

Thanks

Cheers
    Toerless

> Thanks,
> Tomonori Takeda
> 
> 

-- 
---
tte@cs.fau.de


From nobody Thu Sep 21 12:24:45 2017
Return-Path: <session-request@ietf.org>
X-Original-To: mboned@ietf.org
Delivered-To: mboned@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B7111321BB; Thu, 21 Sep 2017 12:24:43 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Meeting Session Request Tool <session-request@ietf.org>
To: <session-request@ietf.org>
Cc: mboned@ietf.org, mboned-chairs@ietf.org, warren@kumari.net, lenny@juniper.net
X-Test-IDTracker: no
X-IETF-IDTracker: 6.62.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150602188328.10419.11666250983794275567.idtracker@ietfa.amsl.com>
Date: Thu, 21 Sep 2017 12:24:43 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/siASiioWg2mZ0cuOR_4xyWtqCLs>
Subject: [MBONED] mboned - New Meeting Session Request for IETF 100
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Sep 2017 19:24:43 -0000

A new meeting session request has just been submitted by Leonard Giuliano, a Chair of the mboned working group.


---------------------------------------------------------
Working Group Name: MBONE Deployment
Area Name: Operations and Management Area
Session Requester: Leonard Giuliano

Number of Sessions: 1
Length of Session(s):  2.5 Hours
Number of Attendees: 50
Conflicts to Avoid: 
 First Priority: bess mmusic pim softwire bier v6ops




People who must be present:
  Joel Jaeggli
  Leonard Giuliano
  Mike McBride
  Stig Venaas
  Greg Shepherd
  Warren Kumari

Resources Requested:

Special Requests:
  Request a 2.5 hr slot for a joint WG session with PIM WG. 
---------------------------------------------------------


From nobody Sun Sep 24 13:09:50 2017
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F88F132F69 for <mboned@ietfa.amsl.com>; Sun, 24 Sep 2017 13:09:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 uebMy6TfeWi9 for <mboned@ietfa.amsl.com>; Sun, 24 Sep 2017 13:09:48 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F982132199 for <mboned@ietf.org>; Sun, 24 Sep 2017 13:09:48 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id E7EF7B80E7F; Sun, 24 Sep 2017 13:09:23 -0700 (PDT)
To: dmm@sprint.net, roll@sprint.net, bclaise@cisco.com, warren@kumari.net, gjshep@gmail.com, lenny@juniper.net
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: worley@ariadne.com, mboned@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset=UTF-8
Message-Id: <20170924200923.E7EF7B80E7F@rfc-editor.org>
Date: Sun, 24 Sep 2017 13:09:23 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/uTLX5lKvpCKRmNS5FV35TKqX24A>
Subject: [MBONED] [Technical Errata Reported] RFC3180 (5121)
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Sep 2017 20:09:49 -0000

The following errata report has been submitted for RFC3180,
"GLOP Addressing in 233/8".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata/eid5121

--------------------------------------
Type: Technical
Reported by: Dale Worley <worley@ariadne.com>

Section: 1

Original Text
-------------
The IANA has allocated 223/8 as per RFC 2770 [RFC2770].

Corrected Text
--------------
The IANA has allocated 233/8 as per RFC 2770 [RFC2770].

Notes
-----


Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party  
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC3180 (draft-ietf-mboned-glop-update-01)
--------------------------------------
Title               : GLOP Addressing in 233/8
Publication Date    : September 2001
Author(s)           : D. Meyer, P. Lothberg
Category            : BEST CURRENT PRACTICE
Source              : MBONE Deployment
Area                : Operations and Management
Stream              : IETF
Verifying Party     : IESG


From nobody Sun Sep 24 13:38:40 2017
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8128A126D0C; Sun, 24 Sep 2017 13:38:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 1pPNybz8bg2g; Sun, 24 Sep 2017 13:38:37 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 59C25126C0F; Sun, 24 Sep 2017 13:38:37 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 4574FB810B7; Sun, 24 Sep 2017 13:38:13 -0700 (PDT)
To: worley@ariadne.com,  dmm@sprint.net, roll@sprint.net
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: warren@kumari.net, iesg@ietf.org, mboned@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset=UTF-8
Message-Id: <20170924203813.4574FB810B7@rfc-editor.org>
Date: Sun, 24 Sep 2017 13:38:13 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/j2PlckC-bYwF0qpnKMeOJnsxVus>
Subject: [MBONED] [Errata Verified] RFC3180 (5121)
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Sep 2017 20:38:38 -0000

The following errata report has been verified for RFC3180,
"GLOP Addressing in 233/8". 

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata/eid5121

--------------------------------------
Status: Verified
Type: Editorial

Reported by: Dale Worley <worley@ariadne.com>
Date Reported: 2017-09-24
Verified by: Warren Kumari (IESG)

Section: 1

Original Text
-------------
The IANA has allocated 223/8 as per RFC 2770 [RFC2770].

Corrected Text
--------------
The IANA has allocated 233/8 as per RFC 2770 [RFC2770].

Notes
-----


--------------------------------------
RFC3180 (draft-ietf-mboned-glop-update-01)
--------------------------------------
Title               : GLOP Addressing in 233/8
Publication Date    : September 2001
Author(s)           : D. Meyer, P. Lothberg
Category            : BEST CURRENT PRACTICE
Source              : MBONE Deployment
Area                : Operations and Management
Stream              : IETF
Verifying Party     : IESG


From nobody Thu Sep 28 14:10:41 2017
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mboned@ietf.org
Delivered-To: mboned@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D3811342F7; Thu, 28 Sep 2017 14:10:22 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: mboned@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.63.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150663302200.27791.13023207115913357958@ietfa.amsl.com>
Date: Thu, 28 Sep 2017 14:10:22 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/VFa1iukVkD-ONGKo2ryay8uFZCY>
Subject: [MBONED] I-D Action: draft-ietf-mboned-interdomain-peering-bcp-11.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Sep 2017 21:10:22 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the MBONE Deployment WG of the IETF.

        Title           : Use of Multicast Across Inter-Domain Peering Points
        Authors         : Percy S. Tarapore
                          Robert Sayko
                          Greg Shepherd
                          Toerless Eckert
                          Ram Krishnan
	Filename        : draft-ietf-mboned-interdomain-peering-bcp-11.txt
	Pages           : 30
	Date            : 2017-09-28

Abstract:
   This document examines the use of Source Specific Multicast (SSM)
   across inter-domain peering points for a specified set of deployment
   scenarios. The objective is to describe the setup process for
   multicast-based delivery across administrative domains for these
   scenarios and document supporting functionality to enable this
   process.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mboned-interdomain-peering-bcp/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-mboned-interdomain-peering-bcp-11
https://datatracker.ietf.org/doc/html/draft-ietf-mboned-interdomain-peering-bcp-11

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-mboned-interdomain-peering-bcp-11


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Fri Sep 29 06:05:44 2017
Return-Path: <pt5947@att.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7371B134532; Fri, 29 Sep 2017 06:05:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.401
X-Spam-Level: 
X-Spam-Status: No, score=-5.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 m7ZjE0mIbcph; Fri, 29 Sep 2017 06:05:40 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0b-00191d01.pphosted.com [67.231.157.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C1FB8134514; Fri, 29 Sep 2017 06:05:40 -0700 (PDT)
Received: from pps.filterd (m0083689.ppops.net [127.0.0.1]) by m0083689.ppops.net-00191d01. (8.16.0.21/8.16.0.21) with SMTP id v8TCt67v030190; Fri, 29 Sep 2017 09:05:39 -0400
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by m0083689.ppops.net-00191d01. with ESMTP id 2d9cbbcc46-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 29 Sep 2017 09:05:39 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id v8TD5ctr004577; Fri, 29 Sep 2017 09:05:38 -0400
Received: from mlpi409.sfdc.sbc.com (mlpi409.sfdc.sbc.com [130.9.128.241]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id v8TD5V89004465 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 29 Sep 2017 09:05:33 -0400
Received: from MISOUT7MSGHUBAH.ITServices.sbc.com (MISOUT7MSGHUBAH.itservices.sbc.com [130.9.129.152]) by mlpi409.sfdc.sbc.com (RSA Interceptor); Fri, 29 Sep 2017 13:05:19 GMT
Received: from MISOUT7MSGUSRDG.ITServices.sbc.com ([169.254.7.116]) by MISOUT7MSGHUBAH.ITServices.sbc.com ([130.9.129.152]) with mapi id 14.03.0361.001; Fri, 29 Sep 2017 09:05:19 -0400
From: "TARAPORE, PERCY S" <pt5947@att.com>
To: "ietf@lmcontreras.com" <ietf@lmcontreras.com>
CC: "mboned@ietf.org" <mboned@ietf.org>, "draft-ietf-mboned-interdomain-peering-bcp@ietf.org" <draft-ietf-mboned-interdomain-peering-bcp@ietf.org>, "mboned-chairs@ietf.org" <mboned-chairs@ietf.org>, "luismiguel.contrerasmurillo@telefonica.com" <luismiguel.contrerasmurillo@telefonica.com>
Thread-Topic: [MBONED] Last Call: <draft-ietf-mboned-interdomain-peering-bcp-10.txt> (Use of Multicast Across Inter-Domain Peering Points) to Best Current Practice
Thread-Index: AQHTHBjiCxfAn/z2mUOD+Yzh+MCLH6LMDauQ
Date: Fri, 29 Sep 2017 13:05:18 +0000
Message-ID: <ACC789373DA69C4285B9678D0CEBF86F13036BC9@MISOUT7MSGUSRDG.ITServices.sbc.com>
References: <150230622113.3494.9085716932582954594.idtracker@ietfa.amsl.com> <9160f7fd4aef47c66383019dcc820e3d@lmcontreras.com>
In-Reply-To: <9160f7fd4aef47c66383019dcc820e3d@lmcontreras.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.10.181.234]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-09-29_04:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1709290185
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/BF6Dw_azwKKv4NEyhwQangz-j_g>
Subject: Re: [MBONED] Last Call: <draft-ietf-mboned-interdomain-peering-bcp-10.txt> (Use of Multicast Across Inter-Domain Peering Points) to Best Current Practice
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Sep 2017 13:05:43 -0000

SGkgTHVpcywNCg0KVGhhbmtzIGZvciB5b3VyIGNvbW1lbnQgb24gdGhpcyBCQ1AuIFdlIGRpc2N1
c3NlZCB0aGUgcG9zc2liaWxpdHkgb2YgYWRkaW5nIGEgbmV3IFVzZSBDYXNlIGZvciBhIHRyYW5z
aXQgcHJvdmlkZXIgQUQtMy4gV2UgZmVsdCB0aGF0IGFkZGluZyB0aGlzIFVzZSBDYXNlIHdvdWxk
IHJlcXVpcmUgc2lnbmlmaWNhbnQgY2hhbmdlcyBpbiB0aGUgU2VjdGlvbiA0IEZ1bmN0aW9uYWwg
R3VpZGVsaW5lcy4gRm9yIHRoYXQgcHVycG9zZSwgd2UgaGF2ZSBhZGRlZCBhIHNob3J0IHBhcmFn
cmFwaCB0b3dhcmRzIHRoZSBlbmQgb2YgU2VjdGlvbiAxICJJbnRyb2R1Y3Rpb24iIHN0YXRpbmcg
dGhhdCB0aGUgcG9zc2liaWxpdHkgb2YgYSB0cmFuc2l0IHNpdHVhdGlvbiBleGlzdHMgYW5kIHRo
YXQgYWRkaXRpb25hbCBjb21wbGV4aXRpZXMgd291bGQgYXJpc2UuIFdlIGluZGljYXRlIHRoZXJl
Zm9yZSB0aGF0IHRoaXMgVXNlIENhc2UgaXMgb3V0IG9mIHNjb3BlIGFuZCBmb3IgZnVydGhlciBz
dHVkeS4gVGhlIG5ldyB2ZXJzaW9uIG9mIHRoZSBkcmFmdCBzdGF0aW5nIHRoaXMgaGFzIGJlZW4g
dXBsb2FkZWQuDQoNClRoYW5rcyBzbyBtdWNoIGZvciB5b3VyIHVzZWZ1bCBjb21tZW50Lg0KDQpC
ZXN0IHdpc2hlcywNCg0KUGVyY3kNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206
IGlldGZAbG1jb250cmVyYXMuY29tIFttYWlsdG86aWV0ZkBsbWNvbnRyZXJhcy5jb21dIA0KU2Vu
dDogV2VkbmVzZGF5LCBBdWd1c3QgMjMsIDIwMTcgMTA6MDUgQU0NClRvOiBpZXRmQGlldGYub3Jn
DQpDYzogbWJvbmVkQGlldGYub3JnOyBkcmFmdC1pZXRmLW1ib25lZC1pbnRlcmRvbWFpbi1wZWVy
aW5nLWJjcEBpZXRmLm9yZzsgbWJvbmVkLWNoYWlyc0BpZXRmLm9yZzsgbHVpc21pZ3VlbC5jb250
cmVyYXNtdXJpbGxvQHRlbGVmb25pY2EuY29tDQpTdWJqZWN0OiBSZTogW01CT05FRF0gTGFzdCBD
YWxsOiA8ZHJhZnQtaWV0Zi1tYm9uZWQtaW50ZXJkb21haW4tcGVlcmluZy1iY3AtMTAudHh0PiAo
VXNlIG9mIE11bHRpY2FzdCBBY3Jvc3MgSW50ZXItRG9tYWluIFBlZXJpbmcgUG9pbnRzKSB0byBC
ZXN0IEN1cnJlbnQgUHJhY3RpY2UNCg0KRGVhciBhbGwsDQoNCkkgaGF2ZSBhIHNwZWNpZmljIGNv
bW1lbnQgcmVnYXJkaW5nIHRvIHRoaXMgZG9jdW1lbnQuIEl0IHN0YXRlcyAodGhpcmQgYnVsbGV0
IGluIHBhZ2UgNSkgdGhhdCB0aGUgbXVsdGljYXN0IHRyYWZmaWMgdG8gYmUgaW50ZXItZXhjaGFu
Z2VkIHZpYSB0aGUgcGVlcmluZyBwb2ludCBpcyB0aGUgb25lIGdlbmVyYXRlZCBsb2NhbGx5LCBp
biB0aGlzIGNhc2UgYnkgQUQtMSAoImEgc2VydmljZSBwcm92aWRlciBjb250cm9scyBvbmUgb3Ig
bW9yZSBhcHBsaWNhdGlvbiBzb3VyY2VzIGluIEFELTEgLi4uIikuIA0KU28gaXQgZG9lcyBub3Qg
Y29uc2lkZXIgdGhlIHNpdHVhdGlvbiB3aGVyZSBvbmUgY2FycmllciBtYXkgYWN0IGFzDQoobXVs
dGljYXN0KSB0cmFuc2l0IHByb3ZpZGVyLiBJbiBvdGhlciB3b3JkcywgYSBzY2VuYXJpbyB3aGVy
ZSBBRC0zIGNvdWxkIG9idGFpbiB2aWEgQUQtMiB0aGUgbXVsdGljYXN0IHRyYWZmaWMgZ2VuZXJh
dGVkIGJ5IEFELTEuDQoNCk1heWJlIEnigJltIHdyb25nLCBidXQgaW4gbXkgdW5kZXJzdGFuZGlu
ZyB0aGUgc2NlbmFyaW9zIGFuZCBtZXRob2RzIGRlc2NyaWJlZCBpbiB0aGUgZHJhZnQgY291bGQg
cGVybWl0IHN1Y2ggdHJhbnNpdCBzY2VuYXJpbywgYnV0IG5vIHN0YXRlbWVudCBpcyBkb25lIHRv
IGNsYXJpZnkgaWYgaXQgaXMgZmVhc2libGUgb3Igbm90LiBJdCBjYW4gYmUgaW50ZXJlc3Rpbmcg
dG8gY2xhcmlmeSB0aGlzIHBvaW50IGluIHRoZSBmaW5hbCB2ZXJzaW9uIG9mIHRoZSBkb2N1bWVu
dC4NCg0KVGhhbmtzDQoNCkx1aXMgTS4gQ29udHJlcmFzDQoNCg0KDQpFbCAyMDE3LTA4LTA5IDIx
OjE3LCBUaGUgSUVTRyBlc2NyaWJpw7M6DQo+IFRoZSBJRVNHIGhhcyByZWNlaXZlZCBhIHJlcXVl
c3QgZnJvbSB0aGUgTUJPTkUgRGVwbG95bWVudCBXRyAobWJvbmVkKSANCj4gdG8gY29uc2lkZXIg
dGhlIGZvbGxvd2luZyBkb2N1bWVudDogLSAnVXNlIG9mIE11bHRpY2FzdCBBY3Jvc3MgDQo+IElu
dGVyLURvbWFpbiBQZWVyaW5nIFBvaW50cycNCj4gICA8ZHJhZnQtaWV0Zi1tYm9uZWQtaW50ZXJk
b21haW4tcGVlcmluZy1iY3AtMTAudHh0PiBhcyBCZXN0IEN1cnJlbnQgDQo+IFByYWN0aWNlDQo+
IA0KPiBUaGUgSUVTRyBwbGFucyB0byBtYWtlIGEgZGVjaXNpb24gaW4gdGhlIG5leHQgZmV3IHdl
ZWtzLCBhbmQgc29saWNpdHMgDQo+IGZpbmFsIGNvbW1lbnRzIG9uIHRoaXMgYWN0aW9uLiBQbGVh
c2Ugc2VuZCBzdWJzdGFudGl2ZSBjb21tZW50cyB0byB0aGUgDQo+IGlldGZAaWV0Zi5vcmcgbWFp
bGluZyBsaXN0cyBieSAyMDE3LTA4LTIzLiBFeGNlcHRpb25hbGx5LCBjb21tZW50cyBtYXkgDQo+
IGJlIHNlbnQgdG8gaWVzZ0BpZXRmLm9yZyBpbnN0ZWFkLiBJbiBlaXRoZXIgY2FzZSwgcGxlYXNl
IHJldGFpbiB0aGUgDQo+IGJlZ2lubmluZyBvZiB0aGUgU3ViamVjdCBsaW5lIHRvIGFsbG93IGF1
dG9tYXRlZCBzb3J0aW5nLg0KPiANCj4gQWJzdHJhY3QNCj4gDQo+IA0KPiAgICBUaGlzIGRvY3Vt
ZW50IGV4YW1pbmVzIHRoZSB1c2Ugb2YgU291cmNlIFNwZWNpZmljIE11bHRpY2FzdCAoU1NNKQ0K
PiAgICBhY3Jvc3MgaW50ZXItZG9tYWluIHBlZXJpbmcgcG9pbnRzIGZvciBhIHNwZWNpZmllZCBz
ZXQgb2YgZGVwbG95bWVudA0KPiAgICBzY2VuYXJpb3MuIFRoZSBvYmplY3RpdmUgaXMgdG8gZGVz
Y3JpYmUgdGhlIHNldHVwIHByb2Nlc3MgZm9yDQo+ICAgIG11bHRpY2FzdC1iYXNlZCBkZWxpdmVy
eSBhY3Jvc3MgYWRtaW5pc3RyYXRpdmUgZG9tYWlucyBmb3IgdGhlc2UNCj4gICAgc2NlbmFyaW9z
IGFuZCBkb2N1bWVudCBzdXBwb3J0aW5nIGZ1bmN0aW9uYWxpdHkgdG8gZW5hYmxlIHRoaXMNCj4g
ICAgcHJvY2Vzcy4NCj4gDQo+IA0KPiANCj4gDQo+IFRoZSBmaWxlIGNhbiBiZSBvYnRhaW5lZCB2
aWENCj4gaHR0cHM6Ly91cmxkZWZlbnNlLnByb29mcG9pbnQuY29tL3YyL3VybD91PWh0dHBzLTNB
X19kYXRhdHJhY2tlci5pZXRmLg0KPiBvcmdfZG9jX2RyYWZ0LTJEaWV0Zi0yRG1ib25lZC0yRGlu
dGVyZG9tYWluLTJEcGVlcmluZy0yRGJjcF8mZD1Ed0lEYVEmDQo+IGM9TEZZWi1vOV9IVU1lTVRT
UWljdmpJZyZyPTRaOXgxWkFSZVpwX21KYWhJNmg5YlEmbT0wR21Icnhnbzg5QnZiZExiVV8NCj4g
TTlPTlR5R09IYUdST3lNbDgyUk5TUzZkSSZzPTRiTWYwZWlRSFZYeVlueXlKNmpxd1BHeTFKSHU4
ZU1Fb3FEdmtyRVMxbQ0KPiBJJmU9DQo+IA0KPiBJRVNHIGRpc2N1c3Npb24gY2FuIGJlIHRyYWNr
ZWQgdmlhDQo+IGh0dHBzOi8vdXJsZGVmZW5zZS5wcm9vZnBvaW50LmNvbS92Mi91cmw/dT1odHRw
cy0zQV9fZGF0YXRyYWNrZXIuaWV0Zi4NCj4gb3JnX2RvY19kcmFmdC0yRGlldGYtMkRtYm9uZWQt
MkRpbnRlcmRvbWFpbi0yRHBlZXJpbmctMkRiY3BfYmFsbG90XyZkPQ0KPiBEd0lEYVEmYz1MRlla
LW85X0hVTWVNVFNRaWN2aklnJnI9NFo5eDFaQVJlWnBfbUphaEk2aDliUSZtPTBHbUhyeGdvODlC
DQo+IHZiZExiVV9NOU9OVHlHT0hhR1JPeU1sODJSTlNTNmRJJnM9UVVUV3Z0UXhtOVd5Z3J0VTlz
UllrdDBhNUVKcHFTNHM3YloNCj4gdUt2bEc3X2smZT0NCj4gDQo+IA0KPiBObyBJUFIgZGVjbGFy
YXRpb25zIGhhdmUgYmVlbiBzdWJtaXR0ZWQgZGlyZWN0bHkgb24gdGhpcyBJLUQuDQo+IA0KPiAN
Cj4gVGhlIGRvY3VtZW50IGNvbnRhaW5zIHRoZXNlIG5vcm1hdGl2ZSBkb3dud2FyZCByZWZlcmVu
Y2VzLg0KPiBTZWUgUkZDIDM5NjcgZm9yIGFkZGl0aW9uYWwgaW5mb3JtYXRpb246DQo+ICAgICBy
ZmMyNzg0OiBHZW5lcmljIFJvdXRpbmcgRW5jYXBzdWxhdGlvbiAoR1JFKSAoUHJvcG9zZWQgU3Rh
bmRhcmQgLSANCj4gTGVnYWN5IHN0cmVhbSkNCj4gICAgIHJmYzM4MTA6IE11bHRpY2FzdCBMaXN0
ZW5lciBEaXNjb3ZlcnkgVmVyc2lvbiAyIChNTER2MikgZm9yIElQdjYgDQo+IChQcm9wb3NlZCBT
dGFuZGFyZCAtIElFVEYgc3RyZWFtKQ0KPiAgICAgcmZjNzQ1MDogQXV0b21hdGljIE11bHRpY2Fz
dCBUdW5uZWxpbmcgKFByb3Bvc2VkIFN0YW5kYXJkIC0gSUVURg0KPiBzdHJlYW0pDQo+ICAgICBy
ZmM0NjA5OiBQcm90b2NvbCBJbmRlcGVuZGVudCBNdWx0aWNhc3QgLSBTcGFyc2UgTW9kZSAoUElN
LVNNKSANCj4gTXVsdGljYXN0IFJvdXRpbmcgU2VjdXJpdHkgSXNzdWVzIGFuZCBFbmhhbmNlbWVu
dHMgKEluZm9ybWF0aW9uYWwgLSANCj4gSUVURiBzdHJlYW0pDQo+ICAgICByZmM0MjcxOiBBIEJv
cmRlciBHYXRld2F5IFByb3RvY29sIDQgKEJHUC00KSAoRHJhZnQgU3RhbmRhcmQgLSANCj4gSUVU
Rg0KPiBzdHJlYW0pDQo+ICAgICByZmM0NjA0OiBVc2luZyBJbnRlcm5ldCBHcm91cCBNYW5hZ2Vt
ZW50IFByb3RvY29sIFZlcnNpb24gMw0KPiAoSUdNUHYzKSBhbmQgTXVsdGljYXN0IExpc3RlbmVy
IERpc2NvdmVyeSBQcm90b2NvbCBWZXJzaW9uIDIgKE1MRHYyKSANCj4gZm9yIFNvdXJjZS1TcGVj
aWZpYyBNdWx0aWNhc3QgKFByb3Bvc2VkIFN0YW5kYXJkIC0gSUVURiBzdHJlYW0pDQo+ICAgICBy
ZmMzMzc2OiBJbnRlcm5ldCBHcm91cCBNYW5hZ2VtZW50IFByb3RvY29sLCBWZXJzaW9uIDMgKFBy
b3Bvc2VkIA0KPiBTdGFuZGFyZCAtIElFVEYgc3RyZWFtKQ0KPiANCj4gDQo+IA0KPiBfX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiBNQk9ORUQgbWFpbGlu
ZyBsaXN0DQo+IE1CT05FREBpZXRmLm9yZw0KPiBodHRwczovL3VybGRlZmVuc2UucHJvb2Zwb2lu
dC5jb20vdjIvdXJsP3U9aHR0cHMtM0FfX3d3dy5pZXRmLm9yZ19tYWlsDQo+IG1hbl9saXN0aW5m
b19tYm9uZWQmZD1Ed0lEYVEmYz1MRllaLW85X0hVTWVNVFNRaWN2aklnJnI9NFo5eDFaQVJlWnBf
bUoNCj4gYWhJNmg5YlEmbT0wR21Icnhnbzg5QnZiZExiVV9NOU9OVHlHT0hhR1JPeU1sODJSTlNT
NmRJJnM9bmFYZDB5RHVhQWUxcg0KPiAzblB2ZktRNE5WekUwX2xmc2RXNGpoTlJOVUhVVG8mZT0N
Cg0KLS0NCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCg0KTHVp
cyBNLiBDb250cmVyYXMNCmlldGZAbG1jb250cmVyYXMuY29tDQpsdWlzbWlndWVsLmNvbnRyZXJh
c211cmlsbG9AdGVsZWZvbmljYS5jb20NCg==


From nobody Fri Sep 29 06:13:50 2017
Return-Path: <pt5947@att.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DBA7134532; Fri, 29 Sep 2017 06:13:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.621
X-Spam-Level: 
X-Spam-Status: No, score=-2.621 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 5cpfTvvVOlCd; Fri, 29 Sep 2017 06:13:42 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0a-00191d01.pphosted.com [67.231.149.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C737132F7C; Fri, 29 Sep 2017 06:13:42 -0700 (PDT)
Received: from pps.filterd (m0048589.ppops.net [127.0.0.1]) by m0048589.ppops.net-00191d01. (8.16.0.21/8.16.0.21) with SMTP id v8TD7oIm015205; Fri, 29 Sep 2017 09:13:41 -0400
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by m0048589.ppops.net-00191d01. with ESMTP id 2d9hd03ef6-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 29 Sep 2017 09:13:40 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id v8TDDc8I012945; Fri, 29 Sep 2017 09:13:39 -0400
Received: from mlpi409.sfdc.sbc.com (mlpi409.sfdc.sbc.com [130.9.128.241]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id v8TDDVnR012873 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 29 Sep 2017 09:13:34 -0400
Received: from MISOUT7MSGHUBAE.ITServices.sbc.com (MISOUT7MSGHUBAE.itservices.sbc.com [130.9.129.149]) by mlpi409.sfdc.sbc.com (RSA Interceptor); Fri, 29 Sep 2017 13:13:13 GMT
Received: from MISOUT7MSGUSRDG.ITServices.sbc.com ([169.254.7.116]) by MISOUT7MSGHUBAE.ITServices.sbc.com ([130.9.129.149]) with mapi id 14.03.0361.001; Fri, 29 Sep 2017 09:13:12 -0400
From: "TARAPORE, PERCY S" <pt5947@att.com>
To: Tomonori Takeda <tomonori.takeda@ntt.com>, "rtg-ads@ietf.org" <rtg-ads@ietf.org>
CC: "'rtg-dir@ietf.org'" <rtg-dir@ietf.org>, "'draft-ietf-mboned-interdomain-peering-bcp.all@ietf.org'" <draft-ietf-mboned-interdomain-peering-bcp.all@ietf.org>, "'mboned@ietf.org'" <mboned@ietf.org>
Thread-Topic: RtgDir review: draft-ietf-mboned-interdomain-peering-bcp-10.txt
Thread-Index: AdMbtumwnLtrsTGiQsK3S0y1oO1rugdbLPyw
Date: Fri, 29 Sep 2017 13:13:12 +0000
Message-ID: <ACC789373DA69C4285B9678D0CEBF86F13036DB1@MISOUT7MSGUSRDG.ITServices.sbc.com>
References: <EB0F2EAC05E9C64D80571F2042700A2A8684496C@C0561I0.coe.ntt.com>
In-Reply-To: <EB0F2EAC05E9C64D80571F2042700A2A8684496C@C0561I0.coe.ntt.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.10.181.234]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-09-29_04:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1709290187
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/A30y5ACDAWdQw2_RWEgDZ47LRmg>
Subject: Re: [MBONED] RtgDir review: draft-ietf-mboned-interdomain-peering-bcp-10.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Sep 2017 13:13:49 -0000

SGkgVG9tb25vcmksDQoNClRoYW5rIHlvdSBmb3IgeW91ciBjYXJlZnVsIHJlYWQgYW5kIGRldGFp
bGVkIGNvbW1lbnRzIG9uIG91ciBCQ1AuIFdlIGhhdmUgYWRkcmVzc2VkIHlvdXIgY29tbWVudHMg
d2l0aCBuZXcgZXhwbGFuYXRvcnkgdGV4dCBhbmQgYXBwcm9wcmlhdGUgY29ycmVjdGlvbnMuIFBs
ZWFzZSBzZWUgaW5saW5lIGJlbG93IGZvciBzcGVjaWZpY3MuIFRoZSBuZXcgdmVyc2lvbiByZWZs
ZWN0cyB0aGVzZSBjaGFuZ2VzIGFuZCBoYXMgYmVlbiB1cGxvYWRlZC4NCg0KVGhhbmtzIGFnYWlu
LA0KDQpCZXN0IHdpc2hlcywNCg0KUGVyY3kNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0N
CkZyb206IFRvbW9ub3JpIFRha2VkYSBbbWFpbHRvOnRvbW9ub3JpLnRha2VkYUBudHQuY29tXSAN
ClNlbnQ6IFdlZG5lc2RheSwgQXVndXN0IDIzLCAyMDE3IDEyOjUzIEFNDQpUbzogcnRnLWFkc0Bp
ZXRmLm9yZw0KQ2M6ICdydGctZGlyQGlldGYub3JnJyA8cnRnLWRpckBpZXRmLm9yZz47ICdkcmFm
dC1pZXRmLW1ib25lZC1pbnRlcmRvbWFpbi1wZWVyaW5nLWJjcC5hbGxAaWV0Zi5vcmcnIDxkcmFm
dC1pZXRmLW1ib25lZC1pbnRlcmRvbWFpbi1wZWVyaW5nLWJjcC5hbGxAaWV0Zi5vcmc+OyAnbWJv
bmVkQGlldGYub3JnJyA8bWJvbmVkQGlldGYub3JnPg0KU3ViamVjdDogUnRnRGlyIHJldmlldzog
ZHJhZnQtaWV0Zi1tYm9uZWQtaW50ZXJkb21haW4tcGVlcmluZy1iY3AtMTAudHh0DQoNCkhlbGxv
LCANCg0KDQoNCkkgaGF2ZSBiZWVuIHNlbGVjdGVkIGFzIHRoZSBSb3V0aW5nIERpcmVjdG9yYXRl
IHJldmlld2VyIGZvciB0aGlzIGRyYWZ0LiBUaGUgUm91dGluZyBEaXJlY3RvcmF0ZSBzZWVrcyB0
byByZXZpZXcgYWxsIHJvdXRpbmcgb3Igcm91dGluZy1yZWxhdGVkIGRyYWZ0cyBhcyB0aGV5IHBh
c3MgdGhyb3VnaCBJRVRGIGxhc3QgY2FsbCBhbmQgSUVTRyByZXZpZXcsIGFuZCBzb21ldGltZXMg
b24gc3BlY2lhbCByZXF1ZXN0LiBUaGUgcHVycG9zZSBvZiB0aGUgcmV2aWV3IGlzIHRvIHByb3Zp
ZGUgYXNzaXN0YW5jZSB0byB0aGUgUm91dGluZyBBRHMuIEZvciBtb3JlIGluZm9ybWF0aW9uIGFi
b3V0IHRoZSBSb3V0aW5nIERpcmVjdG9yYXRlLCBwbGVhc2Ugc2VlIOKAi2h0dHBzOi8vdXJsZGVm
ZW5zZS5wcm9vZnBvaW50LmNvbS92Mi91cmw/dT1odHRwLTNBX190cmFjLnRvb2xzLmlldGYub3Jn
X2FyZWFfcnRnX3RyYWNfd2lraV9SdGdEaXImZD1Ed0lHYVEmYz1MRllaLW85X0hVTWVNVFNRaWN2
aklnJnI9NFo5eDFaQVJlWnBfbUphaEk2aDliUSZtPUt3UDFoZ3h0R1JJT0YwX1FFRk40LXdoY0lP
UUN5eWFjTy1MazVGNjhxUG8mcz04S19jdFpaWTlBZ2d0eDFUdHpvZlpjRHotYnkwMnBMSmdQdUdk
V2JXVGdNJmU9ICANCg0KDQoNCkFsdGhvdWdoIHRoZXNlIGNvbW1lbnRzIGFyZSBwcmltYXJpbHkg
Zm9yIHRoZSB1c2Ugb2YgdGhlIFJvdXRpbmcgQURzLCBpdCB3b3VsZCBiZSBoZWxwZnVsIGlmIHlv
dSBjb3VsZCBjb25zaWRlciB0aGVtIGFsb25nIHdpdGggYW55IG90aGVyIElFVEYgTGFzdCBDYWxs
IGNvbW1lbnRzIHRoYXQgeW91IHJlY2VpdmUsIGFuZCBzdHJpdmUgdG8gcmVzb2x2ZSB0aGVtIHRo
cm91Z2ggZGlzY3Vzc2lvbiBvciBieSB1cGRhdGluZyB0aGUgZHJhZnQuIA0KDQoNCg0KIERvY3Vt
ZW50OiBkcmFmdC1pZXRmLW1ib25lZC1pbnRlcmRvbWFpbi1wZWVyaW5nLWJjcC0xMC50eHQNCg0K
IFJldmlld2VyOiBUb21vbm9yaSBUYWtlZGENCg0KIFJldmlldyBEYXRlOiBBdWcuIDIzcmQsIDIw
MTcNCg0KIElFVEYgTEMgRW5kIERhdGU6IEF1Zy4gMjNyZCwgMjAxNyANCg0KIEludGVuZGVkIFN0
YXR1czogQkNQDQoNCg0KDQpTdW1tYXJ5Og0KDQpUaGlzIGRvY3VtZW50IGlzIGJhc2ljYWxseSBy
ZWFkeSBmb3IgcHVibGljYXRpb24sIGJ1dCBoYXMgbml0cyB0aGF0IHNob3VsZCBiZSBjb25zaWRl
cmVkIHByaW9yIHRvIHB1YmxpY2F0aW9uLg0KDQoNCg0KQ29tbWVudHM6DQoNClRoaXMgZG9jdW1l
bnQgZGVzY3JpYmVzIGRlcGxveW1lbnQgc2NlbmFyaW9zIG9mIG11bHRpY2FzdCAoc3BlY2lmaWNh
bGx5IFNTTSkgYWNyb3NzIGludGVyLWRvbWFpbiBwZWVyaW5nIHBvaW50cy4gQWxzbywgdGhpcyBk
b2N1bWVudCBkZXNjcmliZXMgc3VwcG9ydGluZyBmdW5jdGlvbmFsaXRpZXMgZm9yIHRob3NlIGRl
cGxveW1lbnQgc2NlbmFyaW9zLg0KDQpJIHRoaW5rIHRoZSBkb2N1bWVudCBpcyB3ZWxsLW9yZ2Fu
aXplZCBhbmQgZWFzeSB0byByZWFkLCBidXQgdGhlcmUgYXJlIGEgZmV3IHBvaW50cyB0byBiZSBj
bGFyaWZpZWQuDQoNCg0KDQpNYWpvciBJc3N1ZXM6DQoNCk5vbmUNCg0KDQoNCk1pbm9yIElzc3Vl
czoNCg0KMSkgSSB0aGluayBpdCBpcyBiZXR0ZXIgdG8gZGVzY3JpYmUgYXNzdW1lZCBidXNpbmVz
cyByZWxhdGlvbnNoaXAgYmV0d2VlbiBBRC0xIGFuZCBBRC0yLCBwZXJoYXBzIGluIFNlY3Rpb24g
Mi4NCg0KQWNjb3JkaW5nIHRvIGRlc2NyaXB0aW9ucyBpbiBTZWN0aW9uIDQsIGl0IHNlZW1zIHRo
YXQgQUQtMSBoYXMgdGhlIHVsdGltYXRlIHJlc3BvbnNpYmlsaXR5IHRvIGRlbGl2ZXIgbXVsdGlj
YXN0IHRyYWZmaWMgdG8gRVUuDQoNCihGb3IgZXhhbXBsZSwgaXQgc2F5cyAiQUQtMiBwcm92aWRl
cyByZWxldmFudCBwZXJmb3JtYW5jZSBpbmZvcm1hdGlvbiB0byBBRC0xOyB0aGlzIGVuYWJsZXMg
QUQtMSB0byBjcmVhdGUgYW4gZW5kLXRvLWVuZCBwZXJmb3JtYW5jZSB2aWV3IG9uIGJlaGFsZiBv
ZiB0aGUgbXVsdGljYXN0IGFwcGxpY2F0aW9uIHNvdXJjZS4iKQ0KDQoNCg0KSSB0aGluayBhbm90
aGVyIHBvc3NpYmxlIG1vZGVsIGlzIHRoYXQgQUQtMSBpcyBwcm92aWRpbmcgYSB3aG9sZXNhbGUg
c2VydmljZSB0byBBRC0yLCB3aGVyZSBBRC0xJ3MgcmVzcG9uc2liaWxpdHkgaXMgdG8gZGVsaXZl
cnkgZGF0YSB1cCB0byBBRC0yLCBhbmQgQUQtMiBoYXMgdGhlIHVsdGltYXRlIHJlc3BvbnNpYmls
aXR5IHRvIGRlbGl2ZXJ5IGRhdGEgdG8gRVVzIGFmdGVyd2FyZHMuDQoNCihOb3RlIHRoYXQgSSBh
bSBub3Qgc2F5aW5nIHRoaXMgbW9kZWwgc2hvdWxkIGJlIGluY2x1ZGVkIGluIHRoZSBkb2N1bWVu
dC4pDQoNCg0KDQpTbyBJIHRoaW5rIGl0IGlzIGJlbmVmaWNpYWwgdG8gZGVzY3JpYmUgYXNzdW1l
ZCBidXNpbmVzcyByZWxhdGlvbnNoaXAgYmV0d2VlbiBBRC0xIGFuZCBBRC0yIGluIHRoaXMgZG9j
dW1lbnQuDQoNClBTVDogUGFyYWdyYXBoIGFkZGVkIGluIFNlY3Rpb24gMiBib3R0b20gb2YgcGFn
ZSA1IHN0YXRpbmcgdGhhdCBBRC0xIGhhcyBwcmltZSByZXNwb25zaWJpbGl0eS4NCg0KMikgSW4g
U2VjdGlvbnMgMy4xIGFuZCAzLjIsIGl0IHNheXM6DQoNCg0KDQogICAgICAibyBGZXdlciBkZXZp
Y2VzIGluIHRoZSBwYXRoIHRyYXZlcnNlZCBieSB0aGUgbXVsdGljYXN0IHN0cmVhbSB3aGVuDQoN
CiAgICAgICAgIGNvbXBhcmVkIHRvIHVuaWNhc3QgdHJhbnNtaXNzaW9ucy4iDQoNCg0KDQpJIGRv
bid0IHVuZGVyc3RhbmQgdGhpcyBwb2ludC4NCg0KUFNUOiBCb3RoIHNlbnRlbmNlcyBoYXZlIGJl
ZW4gY2hhbmdlZCB0byBpbmRpY2F0ZSBjb21wYXJpc29uIHdpdGggYW4gQU1UIGVuYWJsZWQgcGVl
cmluZyBwb2ludC4NCg0KMykgSW4gU2VjdGlvbiAzLjIsIGl0IHNheXM6DQoNCg0KDQogICAgICAi
byBBYmlsaXR5IHRvIHN1cHBvcnQgb25seSBwYXJ0aWFsIElQIG11bHRpY2FzdCBkZXBsb3ltZW50
cyBpbiBBRC0NCg0KICAgICAgICAgMSBhbmQvb3IgQUQtMi4iDQoNCg0KDQpJIGRvbid0IHVuZGVy
c3RhbmQgdGhpcyBwb2ludC4gRm9yIGV4YW1wbGUsIGFyZSB5b3UgYXNzdW1pbmcgdGhhdCBHUkUg
aXMgdGVybWluYXRlZCBub3Qgb24gQVMgYm9yZGVyIHJvdXRlcnM/DQoNClBTVDogQ2xhcmlmeWlu
ZyBzZW50ZW5jZSBhZGRlZCBpbiB0aGlzIGJ1bGxldA0KDQpOaXRzOg0KDQoxKSBJIHRoaW5rIHNv
bWUgb2YgdGhlIHJlZmVyZW5jZXMgbWF5IG5vdCBiZSBhcHByb3ByaWF0ZS4gDQoNCi0gSW4gU2Vj
dGlvbiAxLCAiUElNLVNNIFtSRkM0NjA5XSIgc2hvdWxkIGJlICJQSU0tU00gW1JGQzc3NjFdIj8N
Cg0KLSBJbiBTZWN0aW9uIDQuMSwgIk1CR1AgW1JGQzQyNzFdIiBzaG91bGQgYmUgIk1CR1AgW1JG
QzQ3NjBdIj8NCg0KUFNUOiBSZWZlcmVuY2VzIGNoYW5nZWQgYXMgcG9pbnRlZCBvdXQNCg0KMikg
SW4gU2VjdGlvbiAxLCBpdCBzYXlzOg0KDQoNCg0KICAgIlRodXMsIHRoZSBwcmltYXJ5IHB1cnBv
c2Ugb2YgdGhpcyBkb2N1bWVudCBpcyB0byBkZXNjcmliZSBhIHNjZW5hcmlvDQoNCiAgICB3aGVy
ZSB0d28gQUQncyBpbnRlcmNvbm5lY3QgdmlhIGEgZGlyZWN0IGNvbm5lY3Rpb24gdG8gZWFjaCBv
dGhlci4iDQoNCg0KDQpJIHRoaW5rICJhIGRpcmVjdGlvbiBjb25uZWN0aW9uIiBpcyBhIGJpdCB1
bmNsZWFyLiBJbiBkZXBsb3ltZW50IHNjZW5hcmlvcywgeW91IGFyZSBtZW50aW9uaW5nIHRoYXQg
dGhlIHBlZXJpbmcgcG9pbnQgaXMgbXVsdGljYXN0IGVuYWJsZWQgb3Igbm90Lg0KDQpEb2VzIGl0
IG1lYW4gdGhhdCB0aGUgcGVlcmluZyBwb2ludCBtYXkgYmUgYSByb3V0ZWQgbmV0d29yaz8gSXQg
d291bGQgYmUgZ29vZCB0byBjbGFyaWZ5IHRoaXMuDQoNClBTVDogU2VudGVuY2UgY2hhbmdlZCB0
byBzdGF0ZSB0aGF0IHRoZSAyIEFEJ3MgaW50ZXJjb25uZWN0IHZpYSBhIHBlZXJpbmcgcG9pbnQu
DQoNCjMpIEluIFNlY3Rpb24gMy4yLCBpcyBzYXlzOg0KDQoNCg0KICAgIlNlY3Rpb24gNC4zIHBy
b3ZpZGVzIGFuIG92ZXJ2aWV3IG9mIG9uZSBtZXRob2QgdGhhdA0KDQogICAgZmluZHMgdGhlIG9w
dGltYWwgUmVsYXktR2F0ZXdheSBjb21iaW5hdGlvbiB2aWEgdGhlIHVzZSBvZiBhbg0KDQogICAg
QW55Y2FzdCBJUCBhZGRyZXNzIGZvciBBTVQgUmVsYXlzLiINCg0KDQoNCkkgdGhpbmsgU2VjdGlv
biA0LjMgc2hvdWxkIGJlIFNlY3Rpb24gNC4yPw0KDQpQU1Q6IFNlY3Rpb24gbnVtYmVyIGNvcnJl
Y3RlZC4NCg0KDQoNClRoYW5rcywNCg0KVG9tb25vcmkgVGFrZWRhDQoNCg0KDQoNCg0K

